Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » U++ Library support » U++ MT-multithreading and servers » smtp problem
Re: smtp problem [message #28680 is a reply to message #28678] Sat, 11 September 2010 19:44 Go to previous message
Zbych is currently offline  Zbych
Messages: 326
Registered: July 2009
Senior Member
Mindtraveller wrote on Sat, 11 September 2010 17:14

Servers usually accept login which is equal to "FROM:" record because of their internal options. It is done to fight spam and phishing.


HELO has nothing to do with authorization.
According to RFC 821 smtp client uses HELO to tell sever who he is (smtp client should send his ip address or domain name).

Quote:


5.2.5 HELO Command: RFC-821 Section 3.5

The sender-SMTP MUST ensure that the <domain> parameter in a HELO command is a valid principal host domain name for the client host. As a result, the receiver-SMTP will not have to perform MX resolution on this name in order to validate the HELO parameter.

The HELO receiver MAY verify that the HELO parameter really corresponds to the IP address of the sender. However, the receiver MUST NOT refuse to accept a message, even if the sender's HELO command fails verification.

DISCUSSION:

Verifying the HELO parameter requires a domain name lookup and may therefore take considerable time. An alternative tool for tracking bogus mail sources is suggested below (see "DATA Command").

Note also that the HELO argument is still required to have valid <domain> syntax, since it will appear in a Received: line; otherwise, a 501 error is to be sent.

IMPLEMENTATION:

When HELO parameter validation fails, a suggested procedure is to insert a note about the unknown authenticity of the sender into the message header (e.g., in the "Received:" line).

 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Socket: SYN_SENT stalled when ipscan connections in CoWork (MT)
Next Topic: Basic MT queries
Goto Forum:
  


Current Time: Sun May 05 10:15:02 CEST 2024

Total time taken to generate the page: 0.02561 seconds