RE: still unable to receive mail from all domains...only a few

  • From: "John Tolmachoff \(Lists\)" <johnlist@xxxxxxxxxxxxxxxxxxx>
  • To: "'[ExchangeList]'" <exchangelist@xxxxxxxxxxxxx>
  • Date: Wed, 14 Jan 2004 08:36:29 -0800

You need to understand what relaying e-mail means.

 

Relaying is delivering e-mail for some one else to some one else.

 

In the case of internal users, they send outgoing e-mail to your server,
which then contacts the recipients e-mail server and hands off the message
to it. In doing this, your e-mail server is relaying your message to the
recipient server. This is needed because if we had each user trying to send
out each individual message to each recipient, it would be a big traffic
jam. 

 

But, you do not want just anyone relaying through your server. So you have
to have a way of restricting who can access. You do this by either
specifying the IP address or range that it will relay for, such as internal
IP addresses, or you have your users authenticate to the server and then
allowed to send out.

 

Therefore, the best way to allow internal users to relay is to have them
authenticate and not list any IP addresses in the relay settings. 

 

The 4.4.7 error is not related to relaying, that is a delivery problem. That
could be either the recipient e-mail server was unavailable, or your server
could not contact it. The best place to start would be to look at the SMTP
log to see what the conversation was like when your server was trying to
contact the recipient server. You can also do a nslookup from your mail
server to the recipient mail server to see if you are able to resolve the
needed DNS records.

 

John Tolmachoff

Engineer/Consultant/Owner

eServices For You

 

-----Original Message-----
From: Marvin Cummings [mailto:marvc@xxxxxxxxxxxxx] 
Sent: Tuesday, January 13, 2004 5:56 AM
To: [ExchangeList]
Subject: [exchangelist] RE: still unable to receive mail from all
domains...only a few

 

http://www.MSExchange.org/

I honestly couldn't tell you why it's this way because it was configured
this way prior to me getting here. I did finally get a delayed response, be
delay I mean the next day, telling me that the mail timed out while trying
to contact the server and #4.4.7.I've removed the loopback adapter and the
firewall IP from the relay settings and I'm trying to search on this error
but would like to know of some other things to try. Is it OK to add the
network ID and subnet to the relay settings? What about adding the IP's of
the ISP's external DNS servers to the Delivery tab? 

 

Thanks

 

  _____  

From: John Tolmachoff (Lists) [mailto:johnlist@xxxxxxxxxxxxxxxxxxx] 
Sent: Monday, January 12, 2004 7:16 PM
To: [ExchangeList]
Subject: [exchangelist] RE: still unable to recevie mail from all
domains...only a few

 

http://www.MSExchange.org/

By loopback do you mean 127.0.0.1? If so, that means that if a spammer is
able to figure out how to get some process on that server to send e-mail,
your server will freely relay that.

 

Why would you have the IP of the firewall in allow relay? What that means is
if a spammer is able to send e-mail to your server through your firewall for
some one else, your server will freely relay that.

 

John Tolmachoff

Engineer/Consultant/Owner

eServices For You

 

-----Original Message-----
From: Marvin Cummings [mailto:mcummings@xxxxxxxxxxxxxxx] 
Sent: Monday, January 12, 2004 4:10 PM
To: [ExchangeList]
Subject: [exchangelist] still unable to recevie mail from all domains...only
a few

 

http://www.MSExchange.org/

Back again trying to figure out why I'm only receiving email from a few
domains and not all. I'm wondering if anyone know of any issues resulting
from having both the loopback adapter and the IP of the firewall in the
relay settings? This is how it's configured here and I wanted to ask before
I began changing things. 

 

Thanks

------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
Leading Network Software Directory: http://www.serverfiles.com
No.1 ISA Server Resource Site: http://www.isaserver.org
Windows Security Resource Site: http://www.windowsecurity.com/
Network Security Library: http://www.secinf.net/
Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
------------------------------------------------------ 

------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
Leading Network Software Directory: http://www.serverfiles.com
No.1 ISA Server Resource Site: http://www.isaserver.org
Windows Security Resource Site: http://www.windowsecurity.com/
Network Security Library: http://www.secinf.net/
Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
------------------------------------------------------ 

------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
Leading Network Software Directory: http://www.serverfiles.com
No.1 ISA Server Resource Site: http://www.isaserver.org
Windows Security Resource Site: http://www.windowsecurity.com/
Network Security Library: http://www.secinf.net/
Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
------------------------------------------------------ 

Other related posts: