Stephen Bosch <[EMAIL PROTECTED]> wrote:
> Dave Sill wrote:
> > Stephen Bosch <[EMAIL PROTECTED]> wrote:
> > 
> > >Well, my logs are filling up with garbage
> > 
> > Garbage or log entries? Sample, please?
> 
> Sorry -- it's just that I quoted it at great length before...
[...]
> > Jun 12 14:09:12 hotcube qmail: 992376552.507323 info msg 1005716: bytes
> > 266 from <[EMAIL PROTECTED]> qp 27390 uid 502
> > Jun 12 14:09:12 hotcube qmail: 992376552.660776 info msg 1005715: bytes
> > 266 from <[EMAIL PROTECTED]> qp 27403 uid 502
> > Jun 12 14:09:12 hotcube qmail: 992376552.815629 info msg 1005716: bytes
> > 266 from <[EMAIL PROTECTED]> qp 27416 uid 502
> > Jun 12 14:09:42 hotcube qmail: 992376582.939013 info msg 1005715: bytes
> > 266 from <[EMAIL PROTECTED]> qp 27450 uid 502

Each of those messages has a different qmail-queue PID.  From this, you can
deduce that the sender is connecting to your server, sending the message,
and somehow disconnecting or misinterpreting qmail's response to the DATA
command.  The sender thinks the delivery failed, so it tries again, and again,
ad infinitum.

Capture one of the messages' SMTP conversation using recordio.  That should
tell you exactly how the sender's MTA is broken.  You can then inform
postmaster at that domain.

Or block their IP address from connecting to your SMTP daemon.  You choice.

Charles
-- 
-----------------------------------------------------------------------
Charles Cazabon                            <[EMAIL PROTECTED]>
GPL'ed software available at:  http://www.qcc.sk.ca/~charlesc/software/
Any opinions expressed are just that -- my opinions.
-----------------------------------------------------------------------

Reply via email to