On Sat, 2007-09-08 at 17:38 -0400, Sam Varshavchik wrote:
> Lindsay Haisley writes:
>
> > Sam, when you could not confirm this bug, what version of Courier were
> > you using? I'm using 0.55.1-r1 ("r1" = Gentoo Linux revision number).
> > You mentioned that there have been some extensive revisions to the code
> > supporting alias accounts. Did you test on this version, or on one that
> > contains changes to courierlocal which might affect this problem?
>
> I am using the current code, but there are no major to courierlocal in
> 0.56+, the major changes lie elsewhere. courierlocal only handles final,
> local mail delivery. All the logic, that determines where the message should
> be delivered to, lies elsewhere, in courierd, where all the major changes
> are.
>
> Your logs showed that courierlocal received and delivered the message:
>
> Sep 8 12:02:19 shakti courierlocal:
> id=000000000014255A.0000000046E2D55D.000076C7,from=<[EMAIL PROTECTED]>
> ,addr=<@fmp.com>,size=703,success: Message delivered.
>
> This is irrefutable.
>
> Sep 8 12:02:19 shakti courierd:
> started,id=000000000014255A.0000000046E2D55D.000076C7,from=<[EMAIL PROTECTED]
> tus.org>,module=local,[EMAIL PROTECTED]/home/vmail/domains/fmp.com/al
> ias!!,addr=<[EMAIL PROTECTED]>
>
> This is courierd telling courierlocal to deliver this message to
> /home/vmail/domains/fmp.com/alias
>
> You have a .courier-default file in there. Prepend something before the
> final delivery instruction in there, something like:
>
> | cat >/tmp/lastmessage.txt
Done, and we find that this delivery instruction is ignored altogether
when sending an email to "@fmp.com". There is no /tmp/lastmessage.txt
file! I tried appending "2>&1" and still nothing. Sending a message to
a properly formed, non-existent mailbox, however, invokes this, as
expected and as it should, and the contents of said msg end up
in /tmp/lastmessage.txt.
There was no .courier-default file for the alias account, but several
other .courier-* files (household and business group addresses) so I
created one and moved the other redirects elsewhere, all
except .courier-default, and the result was the same. Nada!
> By viewing its contents, you'll be able to confirm what was the last message
> processed by that .courier-default file.
>
> I see two possibilities:
>
> 1) A normal message get saved in /tmp/lastmessage.txt, but the one in
> question isn't
>
> 2) Both messages get saved in /tmp/lastmessage.txt
>
> The next steps to unravel this mystery depends on which possibility turns
> out to be the case, here.
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________ courier-users mailing list
> [email protected] Unsubscribe:
> https://lists.sourceforge.net/lists/listinfo/courier-users
--
Lindsay Haisley | "In an open world, | PGP public key
FMP Computer Services | who needs Windows | available at
512-259-1190 | or Gates" | http://pubkeys.fmp.com
http://www.fmp.com | |
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
