Tanstaafl wrote:
On 12/10/2009, [email protected]
([email protected]) wrote:
It would be great if Paul (or another moderator, if any) could be
directly asked to force-unsubscribe somebody, like "Michael
Considine" ([email protected]), who is bombing the users list
with demands to be unsubscribed.
Maybe he encountered the same problem I am encountering right now.
No, BATV on sent messages is not his problem. The address he posted from
is shown as subscribed, unlike the one you were using before. If
anything is messing up the process there, it's on the receive end (not
getting the unsubscribe confirmation, or not being able to reply to it).
What was happening to you was that sent messages were not recognized as
being from a subscriber.
I subscribed to the OOo users list from my work email address. We use an
outsourced anti-spam service (webroot), and use their system for our
outbound relay host. Well, webroot uses what is called BATV address
tagging, to minimize/eliminate backscatter problems - and it works very
well for this:
http://en.wikipedia.org/wiki/Bounce_Address_Tag_Validation
Yes, the RFC is expired, but that is irrelevant - a LOT of people are
starting to use it, or something similar.
What this does is adds a unique tag to the envelope sender address, so
that instead of a simple email address:
[email protected]
it looks like this:
prvs=2588cf9233=local=example.com
I am subscribed to literally dozens of lists with this address right
now, and have been subscribed to hundreds using this address in the past
3 years we have been using them, and only encountered this kind of
problem once a long time ago on some obscure list that I can't even
remember what it was.
The problem is, the OOo list software is ezmlm, which is brain-dead when
it comes to BATV address tagging, and now I CANNOT UNSUBSCRIBE MYSELF.
To unsubscribe your old account, you'll need to use the indirect form.
The normal process uses the "From" (which in your case has the BATV
prefix) and tries to unsubscribe that, but of course you were not
subscribed by that name. If messages are coming to you from the list (as
opposed to the cc'ed versions you've gotten because you appear to be
unsubscribed), you probably subscribed prior to the BATV implementation,
and can use the indirect form to unsubscribe:
[email protected]. From there,
you can reply to the unsubscribe confirmation and the new BATV prefix
won't matter. Otherwise, your subscription would have been established
using the then-current BATV prefix, and you'll have to look at the
Return-Path header of one of the messages *directly from the list* and
dig it out of there for use in the indirect unsubscribe. I gather you're
currently receiving duplicate copies (or maybe more, when people cc the
old account in responding to one of your earlier messages), right?
Thanks for explaining this -- I'll add it to my discussion of why an
unsubscribe might not be seen as coming from a subscribed account.
I assure you, I am *very* experienced with this kind of thing, so I know
I am trying to unsub using the proper procedure. The problem is, the
only method the OOo lists provide for unsubscribing is via email, and
since every time I send an email from my work address, it has a
different BATV tag, the unsub process fails - and since either ezmlm
doesn't have a user web interface that would let me do this myself (like
Mailman does), or the OOo list moms haven't enabled it, so I cannot do
it through the web.
The correct solution is for either ezmlm to be patched to accommodate
BATV address tagging (we are NOT the only ones using it I assure you),
or the OOo list moms should switch to a list manager that can handle it
- like Mailman.
I've seen how much backscatter this blocks, so I assure you, I wouldn't
ask webroot to disable this feature even if they would, which I doubt.
I gather that ezmlm/CollabNet is not at all likely to change -- there
have been lots of discussions relative to that both here and on the
discuss list. There's no point in pursuing that here, maybe on discuss.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
