On Sat, 2004-01-31 at 19:46 -0800, Bill Moseley wrote:
> I agree that it makes sense to not allow bounces (null senders) to the
> list submission address.
<...>
> So, have you implemented this in exim? Can I do a null sender check in
> a director? If I do it in the ACL then I need to determine if the
> recipient is indeed for a list when checking for a null sender.
Yes, yes -- and yes. I preferred to do it in a router too for the same reasons.
> My director uses this to check for a valid list.
>
> list_director:
> driver = accept
> require_files = MAILMAN_HOME/lists/${lc::$local_part}/config.db
> retry_use_local_part
> transport = list_transport
Is that it? Don't you have to have the bits about local_part_suffix too?
Otherwise how does it accept messages to list-admin@ ?
Try want something like this before the above:
list_reject_bounces:
driver = redirect
require_files = MAILMAN_HOME/lists/${lc::$local_part}/config.db
senders = :
allow_fail
data = :fail: Lists do not send messages and should not receive bounces
Bear in mind that if you're doing recipient verification callouts on a
backup MX you need to make that not break.
I do recipient verification callouts on the MX backups to prevent them
from accepting mail to invalid local_parts. Of course I use defer_ok,
otherwise they'd never accept mail while the primary is down.
But recipient verification callouts are done with a null sender, so
caused my backup MX to refuse to accept mail for the lists :)
My solution to this was... actually I can't remember what my solution
was. I think I just exempted the mailman_domains from the verification
_callouts_.
http://www.infradead.org/~dwmw2/eximconf/master if you _really_ care how
I did it; just be aware of the possibility.
--
dwmw2
