[courier-users] alias@hosteddomain catch-all

Greetings.

I have installed a new courier server. I created a single domain, and
that domain has exactly 2 accounts: postmaster and alias. I am using a
MySQL backend for authentication. And before anyone tries, right now
the server has all ports blocked from any addresses outside our NAT.

I have tried with a .courier-default of zero-size, and also with the
..courier-default I want, which consists of:

-------------------------------------------------------
[root@com1 alias]# cat .courier-default
| /var/mailman/bin/courier-to-mailman.py
-------------------------------------------------------

This is stored in /var/quica/domains/lists.gomillion.org/alias

I tried this without a space after the pipe, but it didn't seem to make
a difference.

When I send email to the account, the following message pops up in the
logs:

Mar 1 11:10:37 com1 courieresmtpd:
error,relay=::ffff:192.168.1.235,from=<deleted>,to =<test@lists.gomillion
..org>: 550 User unknown.

I get the message from the email server:
<test@lists.gomillion.org>:
lists.gomillion.org [192.168.1.225]:
>>> RCPT TO:<test@lists.gomillion.org>
<<< 550 User unknown.

So, I thought that the alias account must have a problem, so I sent an
email directly to it, which was received and delivered, as expected.

From the error messages, it would appear that Courier is not using the
alias@hosteddomain account at all. I have another Courier server that
has a catch-all on one of the domains, which is working quite well.
When I receive email for that catch-all, I get:

Mar 1 11:20:51 com3 courierd:
started,id=0031696F.4224A473.00004D13,from=<delete d>,module=local,host=a
lias@<nospam>!fakeuser!502!502!/var/quica/domains/<nospam>/alias!!524288
000S,10000C,addr=<>
Mar 1 11:20:51 com3 courierd: Waiting. shutdown time=none, wakeup
time=none, queuedelivering=1, inprogress=1
Mar 1 11:20:51 com3 courierlocal:
id=0031696F.4224A473.00004D13,from=<deleted>,addr= <fakeuser@<nospam>>,si
ze=671,success: Message delivered.

So, I see that "host" is set to the actual account it's going to use.
Why is the newer server not doing this correctly? What did I miss?

Thanks,
David Gomillion





-------------------------------------------------------
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users