On 2009-12-21 at 11:00 -0500, Brent Bloxam wrote: > I'm trying to figure out how this issue is occurring and how to stop it. > Somehow messages are getting into our inbound Exim spool without any \n > at the end. When our outbound Exim process tries to deliver these mails, > they fail as Exim outputs '.' on the same line as the one it just sent. > I've verified this by capturing the SMTP conversation from both sides > with tcpdump
How sure are you that the point where you use tcpdump is not being filtered by something like a protocol-level firewall messing up the connection? Exim assumes that the content of the spool contains a trailing newline. When using a transport filter, which is the case that might change this, Exim double-checks and puts the newline in if needed, otherwise it trusts the spool format. So one bandaid would be to use a transport filter of 'cat'. That's rather gross. > No \ns. These messages getting stuck in the spool seem to only ever be > spam. What I see in the outbound log, > > > /var/log/exim/eximout.log:2009-12-21 08:00:00 1NLolk-0003aD-3V == > > [email protected] > > R=Storage T=Storage defer (-46): SMTP error from remote mail server after > > end of > > data: host 192.168.1.3 [192.168.1.3]: 421 mda.local SMTP incoming data > > timeout - > > closing connection. > > Does anyone have any ideas? "message_suffix" sounded like it would have > been a good bandaid, but it only applies to appendfile and pipe. Can you use { exim -Mvb } to look at the message-body, or go look at the raw file in the spool itself? What are the paths for spam to get into the system? Is this a dedicated mail-server, or the mail-server on a web-host used for sending mail from forms, or what? -Phil -- ## List details at http://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
