Greg Earle writes:
@domain: user
This special entry results in any recipient address of the
form foo@domain to be rewritten as user-foo@me, where me is
the hostname of the machine, which we expect to be a local
domain.
The trouble is, I don't want virtual domains. I'm trying to
send outgoing mail through a special external mailer if the
recipient address is of a special form (us...@JPL.NASA.GOV).
And that's exactly how you go about doing it.
This is exactly how you take all mail going to one domain, and push it
somewhere else. The "somewhere else" is defined as a local mailbox. And,
since local mailbox deliveries can be handled by a script, via the .courier
mechanism, that's how you get all mail for a domain to go to a custom
script, which can do whatever it wants with it.
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 strace 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 strace the courierlocal process to see what happens during the
actual mail delivery.
11 messages in net.sourceforge.lists.courier-users[courier-users] Re: Can Courier call ...
