| |||||||||||||||||||||||||||||||
|
> I started with modifying an existing one but found that needed a > little bit more. > Eventually I got to the point where there was little resembling the > original. > > besides, what I am finding in the existing ones is that they do not > comply with the RFC specification. For example MSDW modules, a > classic, tracks information until DATA is received and then just > pipes everything into a temporary file until it's no longer being > read from the network socket. With SMTP, the DATA ends with "." on a line by itself, and the receiver removes '.' at the beginning of all other lines. > Problem with this, as I understand it, is that EHLO allows me to send > messages in the form of: EHLO has nothing to do with the handling of '.'. > HELO > MAIL FROM > RCPT TO > DATA > ... > . That last '.' is the end of the first message. > MAIL FROM > RCPT TO > DATA > ... > . That last '.' is the end of the second message. > QUIT > > That being the case, EHLO would result in ONE MASSIVE email... This results in multiple deliveries, regardless of whether EHLO was sent. Wietse
| ||||||||||||||||||||||||||||||
© 2004-2008 readlist.com