| Home | Register | Members | Search | Links |
 |
| Thread Tools | Display Modes |
|
Guest
Posts: n/a
|
|
|
|
||
|
|
| |
|
Guest
Posts: n/a
|
|
|
|
|
||
|
Guest
Posts: n/a
|
|
|
|
|
||
|
Guest
Posts: n/a
|
"Danny" <(E-Mail Removed)> wrote in message news:C825FA25-183E-4C1E-A6BD-(E-Mail Removed)... > Thanks for your reply. > > I've 2 domains. Both are hosted at colocation. > The server at office is only for spread the mail to the workstations. Oh my. This is a very strange setup, I must say, unless you're not mentioning all relevant details.... I don't understand why you'd use an SBS server as only a sort of mail relay point....that is WAY overkill. Exchange itself (even outside of SBS) is way overkill for this purpose. If nobody is using that server for anything else, you don't need it. Why not just get rid of it and have all mail delivered directly to your office Exchange server? Why are you using colo at all? If you want backup/redundancy of any sort for mail delivery, look at having somoene else's SMTP server specified as a lower-priority/higher-cost MX record in your domain's DNS - it should queue up mail for your domains when your server is unavailable, and automatically retry delivery (via SMTP) for X days. If your ISP won't do this, see MailHop BackupMX at www.dyndns.org. (In fact, if you use a dynamic public IP in the office, you will likely need www.dyndns.org anyway - or similar). If you really want mail delivered to a server in your colo facility, don't use Exchange for it. Again, it's way overkill. > > Because I don't want that every workstation connect with POP3 to the > colocation, They shouldn't be connecting to anything via POP at all, really. > I let the sbserver at office do that. But the problem is that I > must wait 15 minutes to see the mail. Understood. Don't use the POP connector. Don't use POP at all. POP is not meant for servers to communicate with each other - it's for clients to communicate with servers. SMTP = push. POP = pull. > > Do you understand my problem? Yes, but I don't understand your setup. Read the link I posted for hosting your own mail, and please post future SBS questions in the SBS group I mentioned. You will get a lot more help in there. > Sorry, my english is not good. No, don't worry - your English is fine.  > > Regards. > > > "Lanwench [MVP - Exchange]" wrote: > >> >> "Danny" <(E-Mail Removed)> wrote in message >> news:C7A9D481-19CC-4580-B64F-(E-Mail Removed)... >> > Hi all, >> > >> > My situation: >> > >> > 1 Server (SBS 2003 / Exchange ) at colocation. >> > 1 Server (SBS 2003 / Exchange ) at office. >> > >> > The mail witch is send to (E-Mail Removed) or (E-Mail Removed) are >> > delivered at the colocation-server. >> > >> > At office I check every 15 minutes with the pop-connector by the >> > colocation-server. >> > >> > That works fine, but is there a way to push the mail to my office? So, >> > when >> > I receive a mail at colocation, that server must push directly the mail >> > to >> > my >> > office. >> > >> > Is that possible? >> > >> > Danny. >> >> So you have two Internet domains you use for mail, and domain1 is handled >> by >> one SBS box, and domain2 is handled by the other? Why do you have two SBS >> boxes....how do users on the one in the colo center access it? What's the >> relationship between the users who access these servers? >> >> See http://www.msexchange.org/tutorials/MF002.html for info on hosting >> your >> own mail (as opposed to using POP). You can do this for each >> domain/location. Since you're using SBS, you will want to re-run the >> CEICW >> in each server....and note that the best place to post SBS 2003 questions >> is >> >> microsoft.public.windows.server.sbs. >> >> >> >> |
|
|
|
|
|||
|
Guest
Posts: n/a
|
The reasen that I have a server at colo, is that I don't want to deliver the
mail directly to the office because the ADSL line at the office is not 24/7 up. When the line goes down, the mail can't be delivered anywhere else. Is there no other way to do this with 2 servers? "Lanwench [MVP - Exchange]" wrote: > > "Danny" <(E-Mail Removed)> wrote in message > news:C825FA25-183E-4C1E-A6BD-(E-Mail Removed)... > > Thanks for your reply. > > > > I've 2 domains. Both are hosted at colocation. > > The server at office is only for spread the mail to the workstations. > > Oh my. This is a very strange setup, I must say, unless you're not > mentioning all relevant details.... > > I don't understand why you'd use an SBS server as only a sort of mail relay > point....that is WAY overkill. Exchange itself (even outside of SBS) is way > overkill for this purpose. > > If nobody is using that server for anything else, you don't need it. Why not > just get rid of it and have all mail delivered directly to your office > Exchange server? Why are you using colo at all? > > If you want backup/redundancy of any sort for mail delivery, look at having > somoene else's SMTP server specified as a lower-priority/higher-cost MX > record in your domain's DNS - it should queue up mail for your domains when > your server is unavailable, and automatically retry delivery (via SMTP) for > X days. If your ISP won't do this, see MailHop BackupMX at www.dyndns.org. > > (In fact, if you use a dynamic public IP in the office, you will likely need > www.dyndns.org anyway - or similar). > > If you really want mail delivered to a server in your colo facility, don't > use Exchange for it. Again, it's way overkill. > > > > > Because I don't want that every workstation connect with POP3 to the > > colocation, > > They shouldn't be connecting to anything via POP at all, really. > > > I let the sbserver at office do that. But the problem is that I > > must wait 15 minutes to see the mail. > > Understood. Don't use the POP connector. Don't use POP at all. POP is not > meant for servers to communicate with each other - it's for clients to > communicate with servers. SMTP = push. POP = pull. > > > > > Do you understand my problem? > > Yes, but I don't understand your setup. > Read the link I posted for hosting your own mail, and please post future SBS > questions in the SBS group I mentioned. You will get a lot more help in > there. > > > Sorry, my english is not good. > > No, don't worry - your English is fine. > > > > Regards. > > > > > > "Lanwench [MVP - Exchange]" wrote: > > > >> > >> "Danny" <(E-Mail Removed)> wrote in message > >> news:C7A9D481-19CC-4580-B64F-(E-Mail Removed)... > >> > Hi all, > >> > > >> > My situation: > >> > > >> > 1 Server (SBS 2003 / Exchange ) at colocation. > >> > 1 Server (SBS 2003 / Exchange ) at office. > >> > > >> > The mail witch is send to (E-Mail Removed) or (E-Mail Removed) are > >> > delivered at the colocation-server. > >> > > >> > At office I check every 15 minutes with the pop-connector by the > >> > colocation-server. > >> > > >> > That works fine, but is there a way to push the mail to my office? So, > >> > when > >> > I receive a mail at colocation, that server must push directly the mail > >> > to > >> > my > >> > office. > >> > > >> > Is that possible? > >> > > >> > Danny. > >> > >> So you have two Internet domains you use for mail, and domain1 is handled > >> by > >> one SBS box, and domain2 is handled by the other? Why do you have two SBS > >> boxes....how do users on the one in the colo center access it? What's the > >> relationship between the users who access these servers? > >> > >> See http://www.msexchange.org/tutorials/MF002.html for info on hosting > >> your > >> own mail (as opposed to using POP). You can do this for each > >> domain/location. Since you're using SBS, you will want to re-run the > >> CEICW > >> in each server....and note that the best place to post SBS 2003 questions > >> is > >> > >> microsoft.public.windows.server.sbs. > >> > >> > >> > >> > > > |
|
|
|
|
|||
|
Guest
Posts: n/a
|
"Danny" <(E-Mail Removed)> wrote in message news:9B2397F7-1577-49D8-B2C1-(E-Mail Removed)... > The reasen that I have a server at colo, is that I don't want to deliver > the > mail directly to the office because the ADSL line at the office is not > 24/7 > up. When the line goes down, the mail can't be delivered anywhere else. OK, well, a) fix your ADSL or upgrade to something more reliable b) if you need another server to act as a relay/queue, see MailHop BackupMX or similar and fix your DNS so the primary MX record goes to your seerver, and the secondary goes somewhere such as Mailhop. You don't need to manage this yourself. Your users are not accessing the remote/colo SBS box at all, for any reason, so when your internet connection is down in the office, > > Is there no other way to do this with 2 servers? I fear you are missing the larger issues here. It's overly complicated to do this with Exchange alone, let alone SBS, which is not meant for this purpose...and you are likely paying a lot more than you need to, as well as making a lot more work for yourself. Regardless, you need to get rid of POP... If you *really* want to manage this yourself, get a non-Exchange server (heck, Postfix/Sendmail) and put that in your colo, configure it to relay mail to your server. I wouldn't bother. > > "Lanwench [MVP - Exchange]" wrote: > >> >> "Danny" <(E-Mail Removed)> wrote in message >> news:C825FA25-183E-4C1E-A6BD-(E-Mail Removed)... >> > Thanks for your reply. >> > >> > I've 2 domains. Both are hosted at colocation. >> > The server at office is only for spread the mail to the workstations. >> >> Oh my. This is a very strange setup, I must say, unless you're not >> mentioning all relevant details.... >> >> I don't understand why you'd use an SBS server as only a sort of mail >> relay >> point....that is WAY overkill. Exchange itself (even outside of SBS) is >> way >> overkill for this purpose. >> >> If nobody is using that server for anything else, you don't need it. Why >> not >> just get rid of it and have all mail delivered directly to your office >> Exchange server? Why are you using colo at all? >> >> If you want backup/redundancy of any sort for mail delivery, look at >> having >> somoene else's SMTP server specified as a lower-priority/higher-cost MX >> record in your domain's DNS - it should queue up mail for your domains >> when >> your server is unavailable, and automatically retry delivery (via SMTP) >> for >> X days. If your ISP won't do this, see MailHop BackupMX at >> www.dyndns.org. >> >> (In fact, if you use a dynamic public IP in the office, you will likely >> need >> www.dyndns.org anyway - or similar). >> >> If you really want mail delivered to a server in your colo facility, >> don't >> use Exchange for it. Again, it's way overkill. >> >> > >> > Because I don't want that every workstation connect with POP3 to the >> > colocation, >> >> They shouldn't be connecting to anything via POP at all, really. >> >> > I let the sbserver at office do that. But the problem is that I >> > must wait 15 minutes to see the mail. >> >> Understood. Don't use the POP connector. Don't use POP at all. POP is not >> meant for servers to communicate with each other - it's for clients to >> communicate with servers. SMTP = push. POP = pull. >> >> > >> > Do you understand my problem? >> >> Yes, but I don't understand your setup. >> Read the link I posted for hosting your own mail, and please post future >> SBS >> questions in the SBS group I mentioned. You will get a lot more help in >> there. >> >> > Sorry, my english is not good. >> >> No, don't worry - your English is fine. >> > >> > Regards. >> > >> > >> > "Lanwench [MVP - Exchange]" wrote: >> > >> >> >> >> "Danny" <(E-Mail Removed)> wrote in message >> >> news:C7A9D481-19CC-4580-B64F-(E-Mail Removed)... >> >> > Hi all, >> >> > >> >> > My situation: >> >> > >> >> > 1 Server (SBS 2003 / Exchange ) at colocation. >> >> > 1 Server (SBS 2003 / Exchange ) at office. >> >> > >> >> > The mail witch is send to (E-Mail Removed) or (E-Mail Removed) are >> >> > delivered at the colocation-server. >> >> > >> >> > At office I check every 15 minutes with the pop-connector by the >> >> > colocation-server. >> >> > >> >> > That works fine, but is there a way to push the mail to my office? >> >> > So, >> >> > when >> >> > I receive a mail at colocation, that server must push directly the >> >> > to >> >> > my >> >> > office. >> >> > >> >> > Is that possible? >> >> > >> >> > Danny. >> >> >> >> So you have two Internet domains you use for mail, and domain1 is >> >> handled >> >> by >> >> one SBS box, and domain2 is handled by the other? Why do you have two >> >> SBS >> >> boxes....how do users on the one in the colo center access it? What's >> >> the >> >> relationship between the users who access these servers? >> >> >> >> See http://www.msexchange.org/tutorials/MF002.html for info on hosting >> >> your >> >> own mail (as opposed to using POP). You can do this for each >> >> domain/location. Since you're using SBS, you will want to re-run the >> >> CEICW >> >> in each server....and note that the best place to post SBS 2003 >> >> questions >> >> is >> >> >> >> microsoft.public.windows.server.sbs. >> >> >> >> >> >> >> >> >> >> >> |
|
|
|
|
|||
|
|
| |
|
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Morange V: Free Mobile Push Mail and Social Network | XyZaa | Wireless Internet | 0 | 08-09-2008 10:52 PM |
| Exchange DNS (and possibly mail server) backup | Coop DNS | Broadband | 3 | 03-21-2005 08:31 AM |
| Remote Exchange e-mail | =?Utf-8?B?cmlmZi1yYWZm?= | Windows Networking | 4 | 10-14-2004 01:06 AM |
| Exchange server lost mail | =?Utf-8?B?Q2hyaXMgTC4gV2hpdGU=?= | Windows Networking | 1 | 01-07-2004 08:18 AM |
| Linux POP mail and MS Exchange integration | Marvin | Linux Networking | 3 | 12-08-2003 11:29 AM |
Linear Mode
