Disappearing email - could be OT

Steve Campbell campbell at cnpapers.com
Mon Feb 11 19:27:35 GMT 2013

Nope, there's nothing more than the two log entries, one from each server.

I've found two thing that's strange, though. Whenever an email comes 
from that email address, a log entry shows up first in the primary 
server, and later a second log entry shows up on the primary from the 

You may be right on there with the broken smtp session - firstly a 
broken session on the primary and then an attempt from the secondary to 
the primary.

The second thing is no matter where the connection is made, the size 
always seems to be zero, which might indicate the broken session.

I get other emails from the same sending IP just fine, it's mostly this 
user. Could it be her client?

Thanks Ken

On 2/11/2013 1:53 PM, Ken A wrote:
> Hi Steve,
> It doesn't look unusual if the secondary checks for valid recipients
> with the primary. What you may be seeing is just a broken smtp session
> where the client disconnected at DATA or something upstream intercepted
> it (another anti-spam system?).
> If the secondary doesn't check with the primary to validate recipients,
> then there must be more logs on the secondary.
> "grep r1BGGT8J017339 /var/log/maillog" ?
> Ken
> On 2/11/2013 12:06 PM, Steve Campbell wrote:
>> I'm seeing a problem from a couple of my servers. I have a primary
>> server for one of our domains, but I see emails coming through a
>> secondary server for this domain. The email that gets sent through the
>> secondary is relayed to the primary just fine.
>> The problem is that the primary accepts the email and then disappears. I
>> see a line in my sendmail logs like the following:
>> On the secondary:
>> sendmail[17339]: r1BGGT8J017339: from=<xxxxxx at yyyyy.
>> com>, size=0, class=0, nrcpts=1, proto=ESMTP, daemon=MTA,
>> relay=173-219-91-250.s
>> ta.suddenlink.net [] (may be forged)
>> On the primary (relayed from the secondary above):
>> sendmail[31249]: r1BGGZCZ031249: from=<debbie at kcprc.com>, size=0,
>> class=0, nrcpts=1, proto=SMTP, daemon=MTA,
>> relay=mailserver1.cnpapers.net []
>> The logs above are for the same message. This is the only entries I see
>> for this email in both logs. The email isn't delivered, logged through
>> Mailscanner, and doesn't exist in the mqueue or mqueue.in directory.
>> Has anyone seen this type of problem before? How did it get solved? Any
>> reason to believe there's a problem in  the processing database and how
>> do I discover this?
>> thanks
>> steve campbell
>> Thanks for any

More information about the MailScanner mailing list