Subject: Developers of Sympa
List archive
- From: Jeff Abbott <address@concealed>
- To: address@concealed
- Subject: [sympa-dev] Loop Prevention
- Date: Tue, 14 Feb 2006 13:39:54 -0500
Sympa devs,
We're looking at doing different things with Sympa now that we've begun its deployment here at Duke, and one of those things is for contact addresses to which our various servers can send mail for stuff like alerts, cron jobs, etc. The problem is, a great many of those messages come from addresses which trigger the following conditional in sympa.pl:
if ($sender =~ /^(mailer-daemon|sympa|listserv|mailman|majordomo| smartlist|$conf_email)(\@|$)/mio) {
do_log('notice','Ignoring message which would cause a loop, sent by %s', $sender);
return undef;
}
What types of loops is this trying to prevent? There are lots of valid messages which may come from address@concealed that list owners, and in our case list members, may wish to see, unless I'm misunderstanding the purpose or potential failings which not having this in-place would cause. Is there a reason we couldn't make this a per-list configuration option? I can understand not looping based on the X-Loop header, but what good does blocking anything from mailer-daemon do?
Thanks,
Jeff
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
-
[sympa-dev] Loop Prevention,
Jeff Abbott, 02/14/2006
- RE: [sympa-dev] Loop Prevention, Paul Haldane, 02/14/2006
-
Re: [sympa-dev] Loop Prevention,
Aumont - Comite Reseaux des Universites, 02/15/2006
-
Re: [sympa-dev] Loop Prevention,
Jeff Abbott, 02/15/2006
- RE: [sympa-dev] Loop Prevention, Paul Haldane, 02/15/2006
- Re: [sympa-dev] Loop Prevention, Aumont - Comite Reseaux des Universites, 02/16/2006
-
Re: [sympa-dev] Loop Prevention,
Jeff Abbott, 02/15/2006
Archive powered by MHonArc 2.6.19+.