On 2012-06-16 3:54 PM, Ralf Hildebrandt wrote:
* Terry Earley:
Maybe VERP is the best solution for AOL and her evil step-sisters if you
can stand the overhead?
Yep.
Is it possible to enable VERP *only* for certain domains (like AOL,
Yahoo, etc)?
--
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
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
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,
* 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 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
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
Is there any method to identify the user from the AOL feedback loop? If
not, how does AOL expect us to unsubscribe the user who complained?
I set personalization to yes and have something like the following in
the non-digest
footers:
Unsubscribe:
%(web_page_url)soptions%(cgiext)s/%(_internal_
Maybe VERP is the best solution for AOL and her evil step-sisters if you
can stand the overhead?
Terry Earley
On Fri, Jun 15, 2012 at 6:51 PM, David wrote:
> On Fri, Jun 15, 2012 at 1:04 AM, Ralf Hildebrandt <
> ralf.hildebra...@charite.de> wrote:
>
>> * Thomas Hochstein :
>> > Ralf Hildebrand
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 even worse, since it tries to weed
* Thomas Hochstein :
> Ralf Hildebrandt schrieb:
>
> > Yahoo! users are truly special.
>
> AOL users are, too. (They also have a feedback loop.)
Yeah, and it's even worse, since it tries to weed out all info one
needs to identify the user :(
--
Ralf Hildebrandt Charite Univer
Ralf Hildebrandt schrieb:
> Yahoo! users are truly special.
AOL users are, too. (They also have a feedback loop.)
-thh
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: htt
US upgraded version (yes I have an account!) its next to the Forward
button and the 'move to selected folder'
On 2012-06-13 13:56, Ralf Hildebrandt wrote:
It could be "fat finger" syndrome: Gmail, for example, puts the
Report
Spam button next the Delete Message button. I wouldn't be surprised
> It could be "fat finger" syndrome: Gmail, for example, puts the Report
> Spam button next the Delete Message button. I wouldn't be surprised
> if Yahoo! does the same thing.
Nope (at least not in the German Version)
There are two buttons security clearance in-between.
--
Ralf Hildebrandt
David writes:
> If she pressed the "this is SPAM/Junk"-Button 23 times today, you
> would think she would remember doing it when we asked her today.
It could be "fat finger" syndrome: Gmail, for example, puts the Report
Spam button next the Delete Message button. I wouldn't be surprised
if Yah
* Ralf Hildebrandt :
> * David :
>
> > These 23 notices from Yahoo were from the same user, but for 23 different
> > messages from our list over the time period from 07 June 2012 to 13 June
> > 2012.
>
> This is the usual "I mistook the spam button for the delete button"
>
> > We received these
* David :
> We received 23 Yahoo feedback loop notices this morning from one user.
> Supposedly these are abuse or complaint notices. The person joined us in
> Sept of last year. After we received these notices from Yahoo today, we
> contacted the member. She did not remember reporting us as spam.
* David :
> These 23 notices from Yahoo were from the same user, but for 23 different
> messages from our list over the time period from 07 June 2012 to 13 June
> 2012.
This is the usual "I mistook the spam button for the delete button"
> We received these today. But the user did not remember ma
On Wed, Jun 13, 2012 at 11:39 AM, Mailman Admin <
mailman-ad...@uni-konstanz.de> wrote:
>
> > 3. Is anyone else seeing notification delays coupled with multiple
> notices
> > like this?
> >
>
> I never got multiple ones on the same message from one user, but from
> multiple users and on multiple m
Hello David
On 2012-06-13 17:16, David wrote:
> We received 23 Yahoo feedback loop notices this morning from one user.
> Supposedly these are abuse or complaint notices. The person joined us in
> Sept of last year. After we received these notices from Yahoo today, we
> contacted the member. She d
We received 23 Yahoo feedback loop notices this morning from one user.
Supposedly these are abuse or complaint notices. The person joined us in
Sept of last year. After we received these notices from Yahoo today, we
contacted the member. She did not remember reporting us as spam. She didn't
offer u
27 matches
Mail list logo
