>>>>> "CH" == Carl Hage <email@example.com> writes:
CH> The "defective" mailers are using the Reply-To: for bounces.
Yet another reason not to use Reply-To:.
CH> The Majordomo administrator should maintain an up-to-date best effort
CH> filter of offending bounce/vacation programs for all lists rather than
You deleted something, but I get the gist. The problem is, of course, that
there will always be strings which you don't know in advance. Many
vacation programs will let the user specify the subject, so no amount of
regexp futzing will help. That's why it's nice to have the capability to
enable the individual list owner to take care of this without having to
rouse the administrator from bed.
>> Alpha3 is beyond ancient.
CH> Well, that's what I got when I downloaded this morning from
Well, that's why it's dumb to put development versions up on a web page. I
thought Chan had nuked the link from meadow.net, but you never can tell who
has put what up where.
CH> The FAQ should have pointed to a URL which is the lastest, or a
CH> directory with a selection of releases.
1.93 is the latest released version. If you want to play with development
versions (and especially modify development code) then you really need to
join the development mailing list and at least follow for a while. At the
very minimum, drop in and ask what the latest version is. There really
isn't a better way to keep synchronized. Putting that info in the FAQ
would only invite people who shouldn't be playing with development code.
CH> Were there more taboo_headers added since 1.94a3?
I don't know. That code is something like a year old.
CH> The more that are added, the fewer loops that will occur.
And the more false positives you will get. This is a tradeoff. In any
case, the regexps you use look OK to me, but we are in a mode where we're
only fixing installation bugs in an attempt to get a release out. I don't
see this change as a potentially hazardous one, but it's up to Chan.
Of course we will try to find and include a full set of regexps in the next