[prev in list] [next in list] [prev in thread] [next in thread] 

List:       qmail
Subject:    Re: How can this get in my queue?
From:       Scott Gifford <sgifford () suspectclass ! com>
Date:       2003-02-28 19:34:04
[Download RAW message or body]

Robert Stoeber <Robert@usabusiness.net> writes:

[...]

> ------
> messages in queue: 1
> messages in queue but not yet preprocessed: 0
> 28 Feb 2003 15:39:52 GMT  #16229  3835  <regin_1@hotmail.com>
>          local   usabusiness.net-szailyk@usabusiness.net
> ------
> 
> There is no local user (or alias) called szailyk@usabusiness.net so
> why it didn't get bounced is one question.  The maildrop rule is
> scanning the header for /szailyk/ and should be dropping those
> messages anyway, but more on that below.

qmail accepts all messages to your domain, then creates bounces for
them later.

[...]

> The header doesn't mention the invalid user so that would explain, I
> guess, why maildrop isn't trapping the message.  But then how is it
> getting into the queue for that user?

I'm not really all that familiar with maildrop; does it run as part of
qmail, or from individual user's .qmail files?

SMTP deteremines senders and recipients of mail from the message's
envelope, not the headers.

When qmail delivers the message, it will add a "Delivered-To" line to
it which gives the envelope recipient.  Before that, you can't
determine it from the queue file you're looking at; there should be a
corresponding queue file which gives the envelope sender and
recipient(s).

> If the delivery addresses are not in the header, where are they and
> is there a way to use maildrop or something else to catch them
> before they get into the queue?

There are various patches like "badmailfrom" and "badrcptto" which let
you block these before they get into the queue; for more extreme
filtering you can use the QMAILQUEUE patch and your own hand-written
filters.

> 
> In case it helps, here is a chunk of the log where you can see the
> incoming message and delivery attempt:

[...]

> 2003-02-28 08:40:18.773585500 delivery 137: deferral: Sorry,_no_mailbox_here_by_
> that_name._vpopmail_(#5.1.1)/maildrop:_error_writing_to_mailbox./

That's a bit unusual, though.  You might want to ask on the vpopmail
list why it considers "no mailbox here by that name" a temporary
error.  It should bounce the message immediately, instead of trying to
deliver it over and over again.

Hope this helps,

----ScottG.

[prev in list] [next in list] [prev in thread] [next in thread]