Outgoing mail question

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We have an exchange server, all my users are a remote users and using POP3
services that means all the users are using different ISP's. If I sent an
email to the outside user I get a reply back as
Your message did not reach some or all of the intended recipients.
Subject: test
Sent: 2/14/2006 2:54 PM
The following recipient(s) could not be reached:

Yet if I sent an email to some one on the same domain it reaches it's
destination without any problems. It tells me that the the mail services
reached all the way to my mail server and it refused to send email out
because it did not know the source. How can I get my outlook to send email
using exchange servers services without opening myself to open relay
situation.
 
Most likely this question has more to do with verifying the Microsoft
Exchange Server configuration and not Microsoft Outlook. In any case, can
you post the version numbers of each? You should also state if the users
are using their ISP's SMTP server or your Exchange server to send messages.
If your server, are the clients connecting to your SMTP server on port 25 or
a non-standard port like 465 or 587.


"(e-mail address removed)"
 
Hello, My server is a small business server 2003 running exchange. We want
to be able to use the outgoing mail server of the exchange not the ISP's.
One of the reasons is the users travel all over the place, we don't want them
to go and change the outgoing mail server info. everytime they move to new
location. Outlook 2003 is the client software. We are using port 25 on
SMTP and port 110 as pop3 account.
 
Are the users authenticating against the SMTP server? (needed in order to
relay messages and can be configured via the account properties.)

"(e-mail address removed)"
 
neo,

Port 587 is NOT a non-standard port. It is the OFFICAL port that MUA should
be sending mail to. MUA should not be sending mail to port 25 as that's for
MTA to MTA. I know it used to be that way but since the new RFC was approved
several years ago everyone should be switching to the MSA port 587.

What I'd like to know is if Exchange will fully support MSA functions? I'd
also like to know if you can block users from sending mail through port 25?
The only thing I want coming in to port 25 is mail from MTAs. I don't want
users using that port at all.
 
I hear ya, but unfortunately if you install Office/Outlook 2003 (no service
packs or updates) you will quickly find yourself with a receding hairline in
trying to get SSL/TLS over port 587 working. One *must* apply Office 2003
Service Pack 2 in order to get this working right.

As for Exchange 2003, I generally setup 2 SMTP virtual servers when
IMAP/POP3/SMTP support is a requirement. SMTP VS1 is for anonymous inbound
only connections on port 25. SMTP VS2 is for authenticated TLS/SSL
connections on 587. Unfortunately there is no way in Exchange to say it
will only accept connections on port 25 from other MTAs. If it did, Rolex
wouldn't get the e-mail coverage it does today. ;)

Outside of that and if you can get away with it, try to persuade the site to
go with RPC over HTTPs. This method of connection to Exchange 2003 is far
superior than any IMAP/POP3 session. Only draw back is that it is only for
Windows XP/Office 2003 platform or newer.
 
Back
Top