Lloyd Zusman <[EMAIL PROTECTED]> writes:
> [ ... ]
>
> Well, it turns out that no incoming messages seem to have a Return-Path
> header [ ... ]
>
> So perhaps Courier is stripping off that header ... ???
>
> I have to check my the Courier configuration.
I did so, and now I figured out the problem. I had previously been
invoking spamassassin and tmda via the ~/.courier file (corresponds to
the ~/.qmail file).
However, I recently changed this and started to use the maildrop
configuration files instead. In this case, Courier doesn't include the
Return-Path or Delivered-To headers, which only get added to a message
if it's filtered through ~/.courier. The excerpt of the dot-courier(5)
man page below explains this.
The Courier folks have strongly suggested that I do this kind of
filtering through maildrop, not through ~/.courier, and so I now have to
use Courier's "preline" command to cause the Return-Path and
Delivered-To headers to be put on the messages.
So now I have done so, and the problem is solved.
To test this, I manually added a Return-Path to the three test messages
in the pending queue, and now, tmda-cgi releases them just fine.
Thanks a lot for all your help!
Here's the excerpt from the dot-courier(5) manpage. It's in
the section that describes how external filter programs are
invoked from within courier.
Note: When the external program reads the message
from standard input, the message will NOT have the
customary From_, Return-Path:, and Delivered-To:
headers which are customary for locally-delivered
messages. The external program can find those head-
ers in the respective environment variables. If you
have a command that expects to see those headers as
a part of the message, you can use the preline(1)
wrapper to add them to the message. For example,
the procmail mail filter requires those headers.
--
Lloyd Zusman
[EMAIL PROTECTED]
_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users
