On Nov 24, 2004, at 11:48 AM, [EMAIL PROTECTED] wrote:
I traced the output of the "couriertcpd" process that accepted the outgoing mail, and curiously, I saw the ".courier-x500-default" file accessed, but never read!
Correct. The job of the process kicked off by couriertcpd is to accept a message and place it into the mail queue. Your trace shows that the process verified that the E-mail address is valid, and is deliverable.
That's as far as it needs to go. The message is placed in the mail
queue, and the job of delivering the message falls with another process.
You need to trace the courierlocal process to see what happens during the actual mail delivery.
[...]
I'll try truss'ing "courierlocal" anyway ... thanks for the tip.
OK - truss'ed "courierlocal", and here's what I get:
Recall that my ".courier-x500-default" file contains:
mipl:1:129 [/opt/courier/etc/aliasdir] # cat .courier-x500-default
|/usr/local/sbin/mail500 -f "$SENDER" -h "$HOST" -m [EMAIL PROTECTED] "$EXT"@"$HOST"
24287: execve("/usr/local/sbin/mail500", 0x000A7390, 0x000A7B10) \
argc = 8
24287: argv: /usr/local/sbin/mail500 -f [EMAIL PROTECTED]
24287: -h mipl.JPL.NASA.GOV -m
24287: [EMAIL PROTECTED]
24287: [EMAIL PROTECTED]Courier is doing the aliasing, seeing "[EMAIL PROTECTED]" and
re-writing it as "[EMAIL PROTECTED]". And that's
getting fed to the X.500 mailer ("mail500"). I don't want that -
I want to feed it "[EMAIL PROTECTED]" as the final argument.What I've found is that I can get it to "work" if I use this in ".courier-x500-default" instead:
|/usr/local/sbin/mail500 -f "$SENDER" -h "$HOST" -m [EMAIL PROTECTED] "$EXT2"
I'm not totally happy about this - I'd prefer to use the
original un-aliased recipient ("[EMAIL PROTECTED]") as
the last argument, but I don't see any way of getting "@do.main"
in there - both "$HOST" and "$RECIPIENT" contain "@my.do.main".
But, I'll just leave it like this if that's not possible - at
least it's working now!The only other odd thing left is this error message from
"esmtpd-ssl" ("courieresmtpd", actually):Nov 24 15:48:39 mipl esmtpd-ssl: [ID 702911 mail.info] writev: Broken pipe
It happened about 56 seconds after the last syslog'ed message from the first successful attempt. I sent another (successful) test message and waited to see if it would happen again, but it didn't. (This message came from "courieresmtpd", trying to write a "221 Bye." to stdout after having received a "QUIT" on stdin from, presumably, "couriertls". Not sure why the other end wasn't home anymore.)
Thanks to Sam for all his help.
- Greg
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
