#17 Non RFC 2821 4.3.1 Client -

[TheCocce]

Hi I use EmailRelay to configure relay from HP rack server using ILO.
My problem is the a lot of email are not sent.

Watching log I see the problem is similar to this ticket:
https://sourceforge.net/p/emailrelay/support-requests/37/

Seems the client is not RFC 2821 4.3.1 compliant.

There is a possibility to solve this issue, i cannot change client at the moment.

Regards.

Here a piece of logs.

emailrelay: 20200731.165231.323: info: tx>>: "220 SRVGEST01.mydomain.local -- E-MailRelay V2.1a -- Service ready"
emailrelay: 20200731.165231.323: info: rx<<: "HELO [192.168.1.20]"
emailrelay: 20200731.165231.323: info: tx>>: "250 OK"
emailrelay: 20200731.165231.324: info: rx<<: "MAIL FROM:ILOCZxxxxxx.@myrelaydomain.com"
emailrelay: 20200731.165231.324: info: content file: C:\ProgramData\E-MailRelay\spool\emailrelay.3204.1596206860.9.content
emailrelay: 20200731.165231.324: info: tx>>: "250 OK"
emailrelay: 20200731.165231.325: info: rx<<: "RCPT TO:xxxx@yyyy.com"
emailrelay: 20200731.165231.325: info: tx>>: "250 OK"
emailrelay: 20200731.165231.325: info: rx<<: "DATA"
emailrelay: 20200731.165231.325: info: tx>>: "354 start mail input -- end with <crlf>.<crlf>"
emailrelay: 20200731.165231.383: info: rx<<: [message content not logged]
emailrelay: 20200731.165231.383: info: rx<<: "."
emailrelay: 20200731.165231.384: info: envelope file: C:\ProgramData\E-MailRelay\spool\emailrelay.3204.1596206860.9.envelope.new
emailrelay: 20200731.165231.384: info: rx<<: "QUIT"
emailrelay: 20200731.165231.384: info: tx>>: "221 OK"
emailrelay: 20200731.165231.384: info: smtp connection closed: smtp protocol done: 192.168.1.20:52606
emailrelay: 20200731.165231.384: info: forwarding: [client disconnect]
emailrelay: 20200731.165231.385: info: forwarding: no messages to send</crlf></crlf>

When the message is sent the code is like this: "DATA" is followed by "250 OK".

emailrelay: 20200731.164836.458: info: tx>>: "250 OK"
emailrelay: 20200731.164836.458: info: rx<<: "DATA"
emailrelay: 20200731.164836.459: info: tx>>: "354 start mail input -- end with <crlf>.<crlf>"
emailrelay: 20200731.164836.513: info: rx<<: [message content not logged]
emailrelay: 20200731.164836.513: info: rx<<: "."
emailrelay: 20200731.164836.514: info: envelope file: C:\ProgramData\E-MailRelay\spool\emailrelay.3204.1596206860.4.envelope.new
emailrelay: 20200731.164836.515: info: tx>>: "250 OK"
emailrelay: 20200731.164836.516: info: rx<<: "QUIT"
emailrelay: 20200731.164836.516: info: tx>>: "221 OK"</crlf></crlf>

[Graeme Walker]

Ignoring the out-of-sequence QUIT is simple enough, but will the client keep the connection open while waiting for a response? If not, then the socket disconnect would need to be ignored too, with an idle timeout used to clean up the session. That would be messy.

I can offer you a v2.2 beta-test build for windows with an undocumented command-line option to ignore the out-of-sequence QUIT. Let me know if you want to try that.

[TheCocce]

Thank you very much.

I'll try this.

P.s.
Anyway other relay software like "https://www.xeams.com/" works propertly.
Is very strange if the client is not RFC.

Regards.

[Graeme Walker]

I've made code changes to support non-standard SMTP command pipelining, so I hope that will be a suffient workround for this issue. It's checked in to sf svn trunk with a version number of 2.2rc3 and I have put a windows executable in the 'OldFiles' directory: https://sourceforge.net/projects/emailrelay/files/OldFiles/

(sha1 d98f6ca070e6c64729cd87992dd925e89faeb533)

[TheCocce]

Hi Greame, it works like a charm....
Thankyou very much. I think it will be useful for everybody need to operate with old client.

Regards.

[Brian McKinney]

What is the command line option to enable this?

[Graeme Walker]

There is none; just pick up the windows binary from OldFiles or build from svn trunk. (I would also appreciate more feedback on this issue in order to justify its inclusion in the 2.2 release, given that it complicates the emailrelay code for well-behaved smtp clients.)

[Carlos Monzon]

Hi,
perform the installation of version number of 2.2rc3, but the problem remains.
The recipient did not receive the mail

emailrelay-2.2rc3-w64: 20201127.085418.129: info: tx>>: "220 ServerBDCentury -- E-MailRelay V2.2rc3 -- Service ready"
emailrelay-2.2rc3-w64: 20201127.085418.129: info: rx<<: "HELO 10.110.21.2"
emailrelay-2.2rc3-w64: 20201127.085418.129: info: tx>>: "250 OK"
emailrelay-2.2rc3-w64: 20201127.085418.130: info: rx<<: "MAIL FROM:xxxx@texo.com.py"
emailrelay-2.2rc3-w64: 20201127.085418.130: info: content file: C:\ProgramData\E-MailRelay\spool\emailrelay.107656.1606478028.2.content
emailrelay-2.2rc3-w64: 20201127.085418.131: info: tx>>: "250 OK"
emailrelay-2.2rc3-w64: 20201127.085418.131: info: rx<<: "RCPT TO:xxxx@century.com.py"
emailrelay-2.2rc3-w64: 20201127.085418.131: info: tx>>: "250 OK"
emailrelay-2.2rc3-w64: 20201127.085418.138: info: rx<<: "DATA"
emailrelay-2.2rc3-w64: 20201127.085418.139: info: tx>>: "354 start mail input -- end with <crlf>.<crlf>"
emailrelay-2.2rc3-w64: 20201127.085418.139: info: rx<<: [message content not logged]
emailrelay-2.2rc3-w64: 20201127.085418.139: info: rx<<: "."
emailrelay-2.2rc3-w64: 20201127.085418.155: info: envelope file: C:\ProgramData\E-MailRelay\spool\emailrelay.107656.1606478028.2.envelope.new
emailrelay-2.2rc3-w64: 20201127.085418.163: info: tx>>: "250 OK"
emailrelay-2.2rc3-w64: 20201127.085418.163: info: rx<<: "QUIT"
emailrelay-2.2rc3-w64: 20201127.085418.163: info: tx>>: "221 OK"
emailrelay-2.2rc3-w64: 20201127.085418.164: info: smtp connection closed: smtp protocol done: 10.110.21.2:51852</crlf></crlf>

regards

[Carlos Monzon]

Hi,
perform the installation of version number of 2.2rc3, but the problem remains.
The recipient did not receive the mail

emailrelay-2.2rc3-w64: 20201127.085418.129: info: tx>>: "220 ServerBDCentury -- E-MailRelay V2.2rc3 -- Service ready"
emailrelay-2.2rc3-w64: 20201127.085418.129: info: rx<<: "HELO 10.110.21.2"
emailrelay-2.2rc3-w64: 20201127.085418.129: info: tx>>: "250 OK"
emailrelay-2.2rc3-w64: 20201127.085418.130: info: rx<<: "MAIL FROM:xxxx@texo.com.py"
emailrelay-2.2rc3-w64: 20201127.085418.130: info: content file: C:\ProgramData\E-MailRelay\spool\emailrelay.107656.1606478028.2.content
emailrelay-2.2rc3-w64: 20201127.085418.131: info: tx>>: "250 OK"
emailrelay-2.2rc3-w64: 20201127.085418.131: info: rx<<: "RCPT TO:xxxx@century.com.py"
emailrelay-2.2rc3-w64: 20201127.085418.131: info: tx>>: "250 OK"
emailrelay-2.2rc3-w64: 20201127.085418.138: info: rx<<: "DATA"
emailrelay-2.2rc3-w64: 20201127.085418.139: info: tx>>: "354 start mail input -- end with <crlf>.<crlf>"
emailrelay-2.2rc3-w64: 20201127.085418.139: info: rx<<: [message content not logged]
emailrelay-2.2rc3-w64: 20201127.085418.139: info: rx<<: "."
emailrelay-2.2rc3-w64: 20201127.085418.155: info: envelope file: C:\ProgramData\E-MailRelay\spool\emailrelay.107656.1606478028.2.envelope.new
emailrelay-2.2rc3-w64: 20201127.085418.163: info: tx>>: "250 OK"
emailrelay-2.2rc3-w64: 20201127.085418.163: info: rx<<: "QUIT"
emailrelay-2.2rc3-w64: 20201127.085418.163: info: tx>>: "221 OK"
emailrelay-2.2rc3-w64: 20201127.085418.164: info: smtp connection closed: smtp protocol done: 10.110.21.2:51852</crlf></crlf>

regards

[Graeme Walker]

I was offline when you sent that last comment, so I'm sorry I did not respond. There is nothing suspicious in your log snippet, and it does not seem to be the same 'dot-quit' pipelining problem discussed earlier in that the 250 OK acknowledgement is sent before the incoming QUIT is processed. Let me know if you still need help, but I'm closing this issue since the recent v2.2 release contains the relevant workround.