On Mar 26, 2004, at 6:46 PM, Sam Varshavchik wrote:
There are two problems here.
One is that you have the machine name set to "penguin". You must
always use a fully-qualified domain name. Adjust your "me" and/or
"locals" and/or "default" configuration files accordingly.
Secondly you do need a local postmaster address in every case.
If this is a relay-only box, then just create a postmaster address
that bitbuckets all mail. There are many ways to do that. One of
them is to create an empty file
$sysconfdir/aliasdir/.courier-postmaster, owned by the courier userid
and groupid.
A more intelligent way to do this, is to assign an unroutable, fake,
but an otherwise valid hostname to the machine. Pick one of your
domains, such as example.com. Your DNS zone file most certainly
defines localhost.example.com, as 127.0.0.1. Set the machine name,
using the "me" configuration file (and locals/default/whatever). From
Courier's perspective the domain name is valid, with a local
postmaster mailbox, which will bitbucket all doublebounces. Yet you
may provide postmaster mailboxes in all of your real domains just like
any other address.
Sam,
Thanks for the assistance. As per your suggestion, I've changed the
default hostname of the system in accordance with the RedHat way of
doing things (/etc/sysconfig/network)
This is a relay-only box, so I have now created the .courier-postmaster
file as you suggested. It's just a backup MX, and has no local
delivery whatsoever, so I have no need for any "real" accounts to exist
(they wouldn't be accessible anyway, would they?)
One last question for you. Is there any easy way to flush out
everything that is currently in the bounce cycle to get a fresh start
and see if these changes have helped my situation any?
Thanks again!
--Kevin
4 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Re: Postmaster bo...
