On Thu, Oct 16, 2003 at 12:28:22PM -0700, Professional Software
Engineering wrote:
At 13:03 2003-10-16 +0200, Dallman Ross wrote:
I find it rather ridiculous to put this list mail through
SpamAssassin and reject posts that trigger its positive evaluation.
Ok, I'd agree that on a list such as this one, that probably doesn't
work well, but then your message didn't bounce because of content.
It didn't? What, then? I do know that I sent that -- that was
the *second* attempt -- through Outlook, and that SA has beeen known
erroneously to call my Outlook a "forged Microsoft client." Was
that it? But even if so, its no respite, because I sent that after
my first try -- sent from Mutt, as is this -- bounced similarly.
I cancelled that one and resent after changing the Subject: line,
thinking that (with residue of the former SA hit from the original
poster) maybe have been the reason.
Moreover, we have not had a dependable list moderator for quite some
time (as in, about a year). I don't know if the message that I spent
forty minutes creating is ever going to be published to this list or
not.
Well, it's not really a moderator, since the list messages don't
generally go through a moderation process. Messages with "issues"
having to be approved is somewhat different, and yes, I recognize that
the admin tasked with this isn't around as often as listmembers might
hope, however, I know from my administrative duties on some other
lists that it can sap a lot from you keeping on top of other peoples'
problems.
Well, sure it can. I've done similar things myself. I have no
beef per se with the person volunteering to take that on. But
he should try to make his own job easier, too, and IMHO, SA on
this list isn't doing so.
I don't receive the list bounces (thankfully), but I've been in
contact with the list admin last month [. . .] and as a result,
Phillip and I both have the proverbial keys to the list to attend to
problems when we see something amiss. Seeing as Phillip isn't around
often, if you've got a posting problem, let me know and I'll check
into it (it's all done via the web administrative interface).
Okay, that's excellent, and I had no idea you were already
helping out. That's very good to hear. I did see the discussion
where you volunteered to help, but I never saw much more come of
it. Didn't know something had gelled.
Btw, I'm glad to hear Philip is still breathing. :-) Do you
have any inside scoop on whether he's going to be able to make
time for procmail development again any time in the foreseeable
future, and even return here?
Note that the listadmin interface has no controls for whether the
list is affected by SpamAssassin, which appears to be a server-level
implementation.
Too bad.
Message has a suspicious header
Implies there was something wrong with the headers of your message.
Upon checking, it seems probable that it is because your message was
relayed by a host in a certain DNSBL.
But I sent the message about SA from the very same server! And
this one, too. So something fishy is going on. And remember,
the fellow's message I was replying to was also caught. And he
did have all those p e n i s words in it . . .
Note that I locally filtered out the original message to which
you were replying (which was multipart/mixed, and matched other
characteristics).
I see.
I've gone ahead and approved the message to the list, which should
have arrived sometime before this reply.
That is excellent. Thanks, Sean. I will add that I'm gun-shy
after once having lost, entirely, a message I spent well over 1.5
hours preparing; when it was shunted to the administrator for
approval and I had no backup copy (SNAFU at my end; I almost always
generate a private copy for my archives). That all happened over
a year ago, but the memory of it is still painful.
--
dman
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail