Mail relay problem using POP3 service
I have a similar question to another already asked in this forum.
I have several users on my domain that when outside the office can not send to an outside company email address. The difference is that I do not have a SMTP server set up - my users are using a POP3 mail service from an ISP-type of provider.
However, since at work they access the internet thru a Small Business server, and at home they access directly, they get the following error:
"Your message did not reach some or all of the intended recipients.
Subject: RE: Email problem
Sent: 18/04/2005 12:01 PM
The following recipient(s) could not be reached:
'somename@somedomain.com' on 18/04/2005 12:01 PM
550 relaying mail to somedomain.com is not allowed"
Is there any way to address this problem ?
I have several users on my domain that when outside the office can not send to an outside company email address. The difference is that I do not have a SMTP server set up - my users are using a POP3 mail service from an ISP-type of provider.
However, since at work they access the internet thru a Small Business server, and at home they access directly, they get the following error:
"Your message did not reach some or all of the intended recipients.
Subject: RE: Email problem
Sent: 18/04/2005 12:01 PM
The following recipient(s) could not be reached:
'somename@somedomain.com' on 18/04/2005 12:01 PM
550 relaying mail to somedomain.com is not allowed"
Is there any way to address this problem ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Those two alternatives will work, but the process of changing the outgoing e-mail server is quite circumstantial because it needs to be automated (you won't want to ask the user to do it by hand each time), and it must be robust, too. Anything else will drive your 1st level support insane. Personally, I don't like this option at all.
If you're going to go as "dirty" as this, you might as well set up a local DNS server and fake the MX record of your ISP's domain. Make it point to your local SMTP server, and you won't ever have to touch your e-mail client's configuration again. This is a nasty one, too, but it will run more stable.
Running a VPN is by far the best solution if it's designed as a part of your overall IT strategy and embedded into a working, stable environment. Never use VPNs to fix a technical problem; you'll get yourself into trouble in the long run.
If you're going to go as "dirty" as this, you might as well set up a local DNS server and fake the MX record of your ISP's domain. Make it point to your local SMTP server, and you won't ever have to touch your e-mail client's configuration again. This is a nasty one, too, but it will run more stable.
Running a VPN is by far the best solution if it's designed as a part of your overall IT strategy and embedded into a working, stable environment. Never use VPNs to fix a technical problem; you'll get yourself into trouble in the long run.
ASKER
1. When the person goes home, they change their outgoing server to their home ISP server. This allows them to send all their email without relay problems.
2. Run VPN - ask users to connect thru remote access which solves the relay, and removes the need for users to change their settings.