On Sun, Jun 17, 2012 at 1:25 AM, Mark Sapiro wrote:
>
> David wrote:
>
> >In mm_cfg.py I have these settings:
> >
> >OWNERS_CAN_ENABLE_PERSONALIZATION=Yes
> >VERP_PERSONALIZED_DELIVERIES=Yes
> >VERP_PASSWORD_REMINDERS = Yes
> >VERP_CONFIRMATIONS = Yes
> >
> >
> > If I set VERP_DELIVERY_INTERVAL =
I have no idea why AOL wants to make it difficult for list
administrators to unsubscribe people who don't want to be subscribed and
who complain to AOL about list posts being spam. The only explanations
that come to mind are very sinister ones, but given the way things are
going these days, it may
David wrote:
>In mm_cfg.py I have these settings:
>
>OWNERS_CAN_ENABLE_PERSONALIZATION=Yes
>VERP_PERSONALIZED_DELIVERIES=Yes
>VERP_PASSWORD_REMINDERS = Yes
>VERP_CONFIRMATIONS = Yes
>
>In a list with personalize (nondigest) set to NO, does that mean that all
>personalization options, including tho
On Sun, Jun 17, 2012 at 1:00 AM, Mark Sapiro wrote:
> David wrote:
> >
> >How would I update from the version of Mailman 2.1.14 from Ubuntu's
> >repository (on Ubuntu 12.04)?
>
>
> If you are really interested in keeping up with GNU Mailman project
> releases as they are released,
>
This particu
I have no idea why AOL wants to make it difficult for list
administrators to unsubscribe people who don't want to be subscribed and
who complain to AOL about list posts being spam. The only explanations
that come to mind are very sinister ones, but given the way things are
going these days, it may
David wrote:
>
>How would I update from the version of Mailman 2.1.14 from Ubuntu's
>repository (on Ubuntu 12.04)?
If you are really interested in keeping up with GNU Mailman project
releases as they are released, I suggest you back up your Mailman
lists/ and archives/ directories, remove your pa
On Jun 16, 2012, at 3:20 PM, David wrote:
> Thanks, but I'm not sure how to do that. The message ID we get from AOL is
> something like "snt0-p5-eas297e02bc8f051ef1aab0bfd3...@phx.gbl" and it is
> related to the sender. This same ID will show up in the postfix log for
> every outgoing copy of that
We are getting pretty frustrated with AOL. Their feedback report redacts
addresses, so we enabled VERP and full personalization so the "envelope"
can send us the actual address. No good:
Return-Path:
To: redac...@aol.com
Errors-To: all-bounces+redacted=aol@discuss.fiteyes.com
Sender: all-bou
If you look carefully at the full headers in the AOL notice you'll see that not
all the VERP addresses are redacted. I believe the Sender header isn't
redacted. I haven't visited the issue recently since I have a script on my
servers which extracts the subscriber address from these AOL notices a
On Jun 16, 2012, at 5:20 PM, David wrote:
> On Sat, Jun 16, 2012 at 5:00 PM, Larry Stone
> wrote:
>
>
> On Jun 16, 2012, at 3:15 PM, Ralf Hildebrandt
> wrote:
>
> > * David :
> >
> >> Is there any method to identify the user from the AOL feedback loop?
>
>
> I trace from message ID a
On Sat, Jun 16, 2012 at 5:00 PM, Larry Stone wrote:
>
>
> On Jun 16, 2012, at 3:15 PM, Ralf Hildebrandt
> wrote:
>
> > * David :
> >
> >> Is there any method to identify the user from the AOL feedback loop?
>
>
> I trace from message ID and matching to my Postfix logs.
>
Thanks, but I'm not sure
In mm_cfg.py I have these settings:
OWNERS_CAN_ENABLE_PERSONALIZATION=Yes
VERP_PERSONALIZED_DELIVERIES=Yes
VERP_PASSWORD_REMINDERS = Yes
VERP_CONFIRMATIONS = Yes
In a list with personalize (nondigest) set to NO, does that mean that all
personalization options, including those above are not in eff
On Jun 16, 2012, at 3:15 PM, Ralf Hildebrandt
wrote:
> * David :
>
>> Is there any method to identify the user from the AOL feedback loop?
>
> Of course, just use verp :)
> --
>
The last I knew, AOL redacts the user name in their notice. In other words, a
something sent to this list mar
* David :
> Is there any method to identify the user from the AOL feedback loop?
Of course, just use verp :)
--
Ralf Hildebrandt Charite Universitätsmedizin Berlin
ralf.hildebra...@charite.deCampus Benjamin Franklin
http://www.charite.de Hindenburgdamm 30,
David wrote:
>On Fri, Jun 15, 2012 at 1:04 PM, Mark Sapiro wrote:
>> I am happy to announce the final release of Mailman 2.1.15.
>How would I update from the version of Mailman 2.1.14 from Ubuntu's repository
>(on Ubuntu 12.04)?
Ubuntu won't update this package by the normal route until the n
* Terry Earley :
> Maybe VERP is the best solution for AOL and her evil step-sisters if you
> can stand the overhead?
Yep.
--
Ralf Hildebrandt Charite Universitätsmedizin Berlin
ralf.hildebra...@charite.deCampus Benjamin Franklin
http://www.charite.de Hind
On Fri, Jun 15, 2012 at 1:04 PM, Mark Sapiro wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I am happy to announce the final release of Mailman 2.1.15.
How would I update from the version of Mailman 2.1.14 from Ubuntu's
repository (on Ubuntu 12.04)?
--
On Sat, 16 Jun 2012, Larry Stone wrote:
Sad to say, that does appear to be how AOL thinks. Their customers never
make mistakes, etc. If a customer clicked "Mark as spam", then it's spam
and that point is not open to discussion.
They're not the only one. Roadrunner blocked all the mail from t
>
> I can usually figure out who did it my some sleuthing through the mail
> server logs.
>
I would be very interested to know how you track these down from the logs.
Have you or anyone used VERP so AOL cannot mung that email address?
Terry
On Sat, Jun 16, 2012 at 10:20 AM, Larry Stone wrote:
>
On Jun 16, 2012, at 11:02 AM, Richard Damon wrote:
> On 6/15/12 8:51 PM, David wrote:
>> On Fri, Jun 15, 2012 at 1:04 AM, Ralf Hildebrandt <
>> ralf.hildebra...@charite.de> wrote:
>>
>>> * Thomas Hochstein :
Ralf Hildebrandt schrieb:
> Yahoo! users are truly special.
AOL user
On 6/15/12 8:51 PM, David wrote:
> On Fri, Jun 15, 2012 at 1:04 AM, Ralf Hildebrandt <
> ralf.hildebra...@charite.de> wrote:
>
>> * Thomas Hochstein :
>>> Ralf Hildebrandt schrieb:
>>>
Yahoo! users are truly special.
>>> AOL users are, too. (They also have a feedback loop.)
>> Yeah, and it's e
On Fri, Jun 15, 2012 at 8:04 PM, Mark Sapiro wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I am happy to announce the final release of Mailman 2.1.15. This
> release is identical to the 2.1.15rc1 release except for the version
> number and the inclusion of a missing part of the HTM
David writes:
> Is there any method to identify the user from the AOL feedback loop?
Not for sure. Over time, they seem redact ever more information from
the report.
> If not, how does AOL expect us to unsubscribe the user who complained?
Why would they care? Customers rarely remember accid
23 matches
Mail list logo
