On 5/28/08 8:43 PM, Larry Stone wrote:
On 5/28/08 9:26 PM, David Newman at [EMAIL PROTECTED] wrote:
Another is to enable VERP for your outgoing messages, this allows
you to track the message ID to the individual user.
That sounds very promising, thanks. Trying it now...
I have all my lists VERPed for just that reason. Once I figure out who it
is, they get unsubscribed with extreme prejudice (meaning they also get
banned from the mail server). But you should be aware that will increase
your outgoing mail load. Nothing I do is high enough frequency for that to
be an issue but it can be for some people.
Most of my lists are announcement lists. In fact, for some of them, the
recipients aren't even aware it's a mailing list. I (as a side job) assign
soccer referees for local leagues. Rather than sending out announcements to
my referees with a long BCC: list, I add them to a private mailman list with
VERP so they receive them with them as the To: recipient. That also lets me
know who to remove when they decide that the easiest way to let me know that
they're no longer interested in being notified of available games is to do a
"report as spam". :-(
OK, I've enabled VERP but I'm no closer to isolating who's complaining
in AOL-land.
Possibly this is some VERP config error on my part. I added the
following to mm_cfg.py and rebooted:
VERP_PASSWORD_REMINDERS = Yes
VERP_PERSONALIZED_DELIVERIES = Yes
VERP_DELIVERY_INTERVAL = Yes
VERP_CONFIRMATIONS = Yes
VERP_DELIVERY_INTERVAL = 1
The next AOL feedback report contained a unique Message-ID, as always.
grep'ing for that ID in /usr/local/mailman/logs tells me only that the
message was delivered to 250 recipients in 65 seconds.
grep'ing for that ID in /var/log/maillog produces a lot more output --
in fact, still one entry per mailing list subscriber. I've pasted one
example below (addresses redacted); there are 250 of these in maillog.
So, back to the original question: How to associate one message-ID with
one subscriber?
Many thanks
dn
May 29 10:01:22 mail amavis[24936]: (24936-17) Passed CLEAN, LOCAL
[127.0.0.1] [
207.178.164.26] <[EMAIL PROTECTED]> ->
<[EMAIL PROTECTED]>, Message-ID:
<[EMAIL PROTECTED]>, mail_id
: KdgO9YwQBfML, Hits: -2.403, size: 18328, queued_as: 482E25B31D5, 12089 ms
May 29 10:01:22 mail postfix/cleanup[26083]: 913255B31D7:
message-id=<627766.373
[EMAIL PROTECTED]>
May 29 10:01:22 mail postfix/cleanup[31531]: BE4745B31D8:
message-id=<627766.373
[EMAIL PROTECTED]>
May 29 10:01:22 mail postfix/cleanup[26083]: D9C2E5B31D9:
message-id=<627766.373
[EMAIL PROTECTED]>
May 29 10:01:23 mail postfix/cleanup[31531]: 47F645B31DA:
message-id=<627766.373
[EMAIL PROTECTED]>
May 29 10:01:23 mail postfix/cleanup[26083]: 6E0D65B31DB:
message-id=<627766.373
[EMAIL PROTECTED]>
May 29 10:01:23 mail postfix/cleanup[31531]: 876B85B31DC:
message-id=<627766.373
[EMAIL PROTECTED]>
------------------------------------------------------
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
