Disappearing email - could be OT
ka at pacific.net
Mon Feb 11 18:53:23 GMT 2013
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" ?
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: r1BGGT8J017339: from=<xxxxxx at yyyyy.
> com>, size=0, class=0, nrcpts=1, proto=ESMTP, daemon=MTA,
> ta.suddenlink.net [22.214.171.124] (may be forged)
> On the primary (relayed from the secondary above):
> sendmail: r1BGGZCZ031249: from=<debbie at kcprc.com>, size=0,
> class=0, nrcpts=1, proto=SMTP, daemon=MTA,
> relay=mailserver1.cnpapers.net [10.0.0.103]
> 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?
> steve campbell
> Thanks for any
Pacific Internet - http://www.pacific.net
Latest Pacific.Net Status - http://twitter.com/pacnetstatus
More information about the MailScanner