"Stuart" <> wrote in message
news:94469082-B6DF-45F7-A726-...
> Hi Larry,
>
> Thanks for that idea, Can I just clarify why that would solve my issue as
> it would appear that all the emails are being delivered to the Exchange
> server correctly and as I understand it, it is a delivery issue to the
> user and your idea would not impact on the delivery method to the user. Im
> not questioning your solution just trying to understand what you think has
> gone wrong and why this would fix it.
>
> Cheers
>
> Stuart
If I may jump in, what Larry's offering is a way to first, drastically
reduce the complexity that you currently have, and eliminate the POP3
connector, which wasn't designed as a long term solution, rather for an
interim solution until the mail server will direclty send and receive mail
on the internet. The POP3 solution can become problematic, as you can see if
you search back on the numerous complaints regarding the POP3 connector.
Once your mail server is configured to send and receive, administration will
be much simpler, instead of juggling accounts on the Exchange server and
your mail hosting provider.
And yes, you will definitely need a static IP, or as Larry suggested, use
something such as DynDNS.org for the solution. Honestly I would change the
ISP to a static line, because from my experience, many ISP providers that
provide a DHCP address for the WAN link, are usually classed as
"residential" lines and *may* not allow inbound port 25 (mail) traffic. You
should consult with your ISP first.
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.
Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.