[Mailman-Developers] Re: notify disabled not working;
bad subscribed address problem
davidb at pins.net
Wed Apr 9 16:30:11 EDT 2003
I should clarify - notifications to the USER are working, just not
notifications to the owner.
On Wed, 9 Apr 2003, David Birnbaum wrote:
> As near as I can tell, the bounce_notify_owner_on_disable option is not
> working. At the moment, even though it is set to "yes" for lists, no
> notifications are being sent. Unsubscribe notifications are being sent,
> I have double checked the list option, and switched the options around, to
> no avail. This was a conversion from 2.0 to 2.1.1 (what I'm currently
> running) in case that makes any difference.
> Problem No. 2, had to do with a e-mail address that somehow got subscribed
> with a non-ASCII character and it. I cannot delete the address, either on
> the web site or any other way, as best as I can tell. list_members
> prompt% list_members thebody
> [ names up to hm... ]
> Traceback (most recent call last):
> File "list_members", line 232, in ?
> File "list_members", line 207, in main
> s = formataddr((name, addr)).encode(enc, 'replace')
> UnicodeError: ASCII decoding error: ordinal not in range(128)
> Any python gurus who can suggest a simple fix to at least get the entire
> list enumerated? I suppose I don't really need to unsubscribe the bad
> address as long as I can list everything.
> Otherwise, 2.1.1 has been functioning flawlessly. Bounce detection is
> much better, as well.
> Thanks in advance,
More information about the Mailman-Developers