Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am using 4 ea sendmail servers to act as proxy servers to filter out abuse from the NDRs & FBLs being returned. The NDRs are being processed by the 20 Selligent StrongMail servers that sent the original message. The FBLs get forwarded to another server that processes them.
The issue is that sendmail is not waiting for the 250 response after sending the RCPT TO which is causing the Selligent server to reset the connection and cause the emails to be deferred & queued.
Code:
220 mta-RRRF.cluster2.<company>.net - ready at Fri, 31 Aug 2018 07:42:49 -0500 for server 32737
>>> EHLO mail301.<company>.net
250-mta-RRRF.cluster2.<company>.net
250-PIPELINING
250-SIZE 10240000
250 8BITMIME
>>> MAIL From:<fbl@bounce.mailstream.senderscore.net> SIZE=19447 BODY=8BITMIME
250 Ok
>>> RCPT To:<complaint@cluster3.<company>.net>
>>> DATA
250 Ok
354 send the mail data, end with .
>>> .
... Deferred: Connection reset by [74.xx.xx.xx]
I have used tcpdump to capture the packets and confirm the issue.
So, the question is: How do I fix this? How do I get Sendmail to wait for the 250 response before sending the DATA?
Update: I have been informed that RFC 2920 states that when a server advertises PIPELINING (which the Selligent server is doing), the client MTA does not have to wait for a 250 response before sending the next command. I have thrown this at Selligent and they now acknowledge a bug with "no timeline" for resolution. They advise, "In the meantime, unfortunately, the only workaround for the moment is to avoid batching of commands (i.e. not making use of pipelining)."
Is there a way to do this in sendmail? Disable that feature?
Update3: Selligent support had me alter a mapping file so that the PIPELINING doesn't come up anymore after the EHLO and so Sendmail does not try to batch commands.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.