-----Original Message-----
From: cour...@lists.sourceforge.net
[mailto:cour...@lists.sourceforge.net]On Behalf Of Sam
Varshavchik
Sent: 03 January 2003 23:18
To: cour...@lists.sourceforge.net;
cour...@lists.sourceforge.net
Subject: [maildropl] Re: Maildrop and no such mailbox
bi...@mics.org.uk writes:
Sam Varshavchik writes:
bi...@mics.org.uk writes:
Sam Varshavchik writes:
Your mail server should not be accepting mail to
nonexistent recipients.
I know that's how Qmail works. It's broken.
Sadly, my courier server *is* accepting mail to
non-existent recipients
in my local domain. Any idea what I might have done to
screw it up?
If you're doing "@domain: account" rewriting, that account's home
directory must have global read and execute permissions, so that
courieresmtpd, running as a non-privileged user, can
determine whether the
corresponding .courier files exist.
No domain rewriting is going on, unless I've missed a
default setting
somewhere. I have one small set of users, listed without
domain names, in
userdb. I have 2 domains listed in locals (one whose MX
records point
directly to this server's dumb smarthost, the other from my
old dial-up POP3
account, collected by fetchmail and being delivered via the
dumb smarthost).
There are a few aliases set up in aliasdir, but they all
map user names 1:1
like the aliases/system file does.
Are you sure of that? A single, carefully chosen .courier
file in aliasdir
can swallow an entire domain.
Mail to non-existent users in domains listed in locals is
being accepted.
aliasdir/.courier-default
# ls -a /etc/courier/aliasdir
. ..
# find / -name .courier-default
/home/bill/.courier-default
#
10 messages in net.sourceforge.lists.courier-maildropRE: [maildropl] Re: Maildrop and no s...
