|
|
Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
I am using POP3 connector in the sbs server and got lots of problem due to
time out and disconnection from the email hosting company (lots of user and
large email and delay in delivery etc...)
I am thinking to put the pop3 account back to the outlook client, and user
can still sync back to the exchange server after they individually downloaded
the messages.
Could anyone point me out what is the major cons using this method? what is
the major benefit to put the pop3 in the server side?
Many thanks.
|
|
Neo wrote:
[Quoted Text] > I am using POP3 connector in the sbs server and got lots of problem due to
> time out and disconnection from the email hosting company (lots of user and
> large email and delay in delivery etc...)
>
> I am thinking to put the pop3 account back to the outlook client, and user
> can still sync back to the exchange server after they individually downloaded
> the messages.
>
> Could anyone point me out what is the major cons using this method? what is
> the major benefit to put the pop3 in the server side?
The obvious con is that mail will only be in Exchange once the Outlook
client has downloaded it. This means that if the user is out of the
office, on holiday etc, then they won't be able to use OWA to read mail
that hasn't yet been downloaded, nor will anyone else. Of course, the
POP provider may supply a webmail client to read mail directly from the
pop box. If mail is uncollected you may hit quota limits imposed by the
POP3 provider. There is also the danger that mail will be downloaded
into a pst file and never hit the Exchange mail box.
I'd seriously consider getting your mail delivered directly via SMTP.
This is fairly trivial to set up even with a dynamic IP address: forward
port 25 to your SBS server and point the MX records for your domains to
your server. If you're worried about viruses, spam and opening port 25
to the whole Internet, then consider using a third party mail cleaning
solution where the 3rd part take your MX records and forward mail to
your server after it's been cleansed. You then only need to open port 25
to the 3rd party's mail servers. There are lots of companies offering
this type of service: Postini, Exchange Defender, MessageLabs,
DynDNS,etc. It's something we do for all our SBS clients by default
using our own Internet mail servers that run
MailScanner,SpamAssassin,ClamAV,FuzzyOCR etc.
-- stephen
|
|
And what are the reasons why you are not switching to hosting your own mail?
--
Claus
"Neo" <Neo[ at ]discussions.microsoft.com> wrote in message
news:AD73311A-89EC-464F-9980-7BCE573E482F[ at ]microsoft.com...
[Quoted Text] >I am using POP3 connector in the sbs server and got lots of problem due to
> time out and disconnection from the email hosting company (lots of user
> and
> large email and delay in delivery etc...)
>
> I am thinking to put the pop3 account back to the outlook client, and user
> can still sync back to the exchange server after they individually
> downloaded
> the messages.
>
> Could anyone point me out what is the major cons using this method? what
> is
> the major benefit to put the pop3 in the server side?
>
> Many thanks.
|
|
Management: you have to go to each workstation to setup and support
Bandwidth: you have 20 users who all get sent a 5 MB attachment and all
those Outlook POPs start downloading at once, say bye-bye bandwidth.
Best Solution: Move away from POP. There is little or no reason a business
should be POP'ing down their email after a short transistion or as a backup
MX type solution.
James Barrett
MCP, MCTS-Vista, MCTS-Sharepoint, SBSC
"Neo" <Neo[ at ]discussions.microsoft.com> wrote in message
news:AD73311A-89EC-464F-9980-7BCE573E482F[ at ]microsoft.com...
[Quoted Text] >I am using POP3 connector in the sbs server and got lots of problem due to
> time out and disconnection from the email hosting company (lots of user
> and
> large email and delay in delivery etc...)
>
> I am thinking to put the pop3 account back to the outlook client, and user
> can still sync back to the exchange server after they individually
> downloaded
> the messages.
>
> Could anyone point me out what is the major cons using this method? what
> is
> the major benefit to put the pop3 in the server side?
>
> Many thanks.
|
|
Thanks.
the problem is very complicated in China... broadband low bandwidth,
unstable, cannot work with "western" dyn ip provider, mail filtering by
authority (they still filter sensitive and religious thing etc...), port
blocking, interesting iproute problem, or worst, power outage...
no way i will do that on my in house server for my customer and put my neck
depending on them
i always expect response about using smtp and not connector, but up till now
i am still not very convinced without a back up system by hosting company in
Hong Kong.
"stephen" wrote:
[Quoted Text] > Neo wrote:
> > I am using POP3 connector in the sbs server and got lots of problem due to
> > time out and disconnection from the email hosting company (lots of user and
> > large email and delay in delivery etc...)
> >
> > I am thinking to put the pop3 account back to the outlook client, and user
> > can still sync back to the exchange server after they individually downloaded
> > the messages.
> >
> > Could anyone point me out what is the major cons using this method? what is
> > the major benefit to put the pop3 in the server side?
>
> The obvious con is that mail will only be in Exchange once the Outlook
> client has downloaded it. This means that if the user is out of the
> office, on holiday etc, then they won't be able to use OWA to read mail
> that hasn't yet been downloaded, nor will anyone else. Of course, the
> POP provider may supply a webmail client to read mail directly from the
> pop box. If mail is uncollected you may hit quota limits imposed by the
> POP3 provider. There is also the danger that mail will be downloaded
> into a pst file and never hit the Exchange mail box.
>
> I'd seriously consider getting your mail delivered directly via SMTP.
> This is fairly trivial to set up even with a dynamic IP address: forward
> port 25 to your SBS server and point the MX records for your domains to
> your server. If you're worried about viruses, spam and opening port 25
> to the whole Internet, then consider using a third party mail cleaning
> solution where the 3rd part take your MX records and forward mail to
> your server after it's been cleansed. You then only need to open port 25
> to the 3rd party's mail servers. There are lots of companies offering
> this type of service: Postini, Exchange Defender, MessageLabs,
> DynDNS,etc. It's something we do for all our SBS clients by default
> using our own Internet mail servers that run
> MailScanner,SpamAssassin,ClamAV,FuzzyOCR etc.
>
> -- stephen
>
|
|
Neo wrote:
[Quoted Text] > Thanks.
>
> the problem is very complicated in China... broadband low bandwidth,
> unstable, cannot work with "western" dyn ip provider, mail filtering by
> authority (they still filter sensitive and religious thing etc...), port
> blocking, interesting iproute problem, or worst, power outage...
>
> no way i will do that on my in house server for my customer and put my neck
> depending on them
>
> i always expect response about using smtp and not connector, but up till now
> i am still not very convinced without a back up system by hosting company in
> Hong Kong.
>
Yes, I've come across the the problem of DynDNS's domain names being
block by the PRC. My workaround was to use one of our own (non-blocked)
domains and update its zone file from the contents of the dyndns name
using a script that checked for changes to the DynDNS IP every minute.
Bit of a hack and only useful if you operate your own Internet DNS
servers, which we do as part of our hosting business. Fortunately, this
client upgraded their broadband to a fixed IP and I could dispense with
this hack.
-- stephen
|
|
|