Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Server sending email

Status
Not open for further replies.

Guest_imported

New member
Joined
Jan 1, 1970
Messages
0
I recently began having problems with our email server (Eudora Internet Mail Server version 1.0.4 ~I know this is old) having problems sending and receiving mail to certain other email server. Usually it just comes back with out any reason. However, once I got the following response. Could anyone give me some direction on what this means?

"Sender domain not compliant with RFC 822, section 6.2.7"

One ISP said we are not being blocked for SPAM or anything like that, but said out email server is not configured correctly. I don't know if it is our email or DNS that is causing this problem.
Any help would be much appreciated.

Thank you.
David

 
Here is some help....

5.2.19 Explicit Source Routes: RFC-822 Section 6.2.7

Internet host software SHOULD NOT create an RFC-822 header containing an address with an explicit source route, but MUST accept such headers for compatibility with earlier systems.


DISCUSSION:
In an understatement, RFC-822 says "The use of explicit source routing is discouraged". Many hosts implemented RFC-822 source routes incorrectly, so the syntax cannot be used unambiguously in practice. Many users feel the syntax is ugly. Explicit source routes are not needed in the mail envelope for delivery; see Section 5.2.6. For all these reasons, explicit source routes using the RFC- 822 notations are not to be used in Internet mail headers.

As stated in Section 5.2.16, it is necessary to allow an explicit source route to be buried in the local-part of an address, e.g., using the "%-hack", in order to allow mail to be gatewayed into another environment in which explicit source routing is necessary. The vigilant will observe that there is no way for a User Agent to detect and prevent the use of such implicit source routing when the destination is within the Internet. We can only discourage source routing of any kind within the Internet, as unnecessary and undesirable.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top