After successfully removing the problematic user (with the two @ in their
email address), I am still seeing a problem with the 'disabled' cron,
pointing to this user that was already removed (thanks to your help).
Here's the cron output (with the offending email address redacted)

# /usr/bin/python -S /usr/lib/mailman/cron/disabled
Traceback (most recent call last):
  File "/usr/lib/mailman/cron/disabled", line 224, in <module>
    main()
  File "/usr/lib/mailman/cron/disabled", line 161, in main
    if mlist.getDeliveryStatus(member) <> MemberAdaptor.ENABLED:
  File "/usr/lib/mailman/Mailman/OldStyleMemberships.py", line 140, in
getDeliveryStatus
    self.__assertIsMember(member)
  File "/usr/lib/mailman/Mailman/OldStyleMemberships.py", line 114, in
__assertIsMember
    raise Errors.NotAMemberError, member
Mailman.Errors.NotAMemberError: user@@example.com


Thoughts on how I might make this cron happy again?  Thank you!!

- Scott

On Sat, Dec 28, 2024 at 12:55 AM Scott Neader <sc...@qth.com> wrote:

> It worked!!  Many thanks!
>
> - Scott
>
> On Fri, Dec 27, 2024 at 4:52 PM Mark Sapiro <m...@msapiro.net> wrote:
>
>> On 12/27/24 07:20, Scott Neader wrote:
>> > Hello all!  Somehow, one of our Mailman2 lists has a member with a bad
>> > email address, in the format of user@@example.com  (i.e. two @
>> symbols).
>> > This is breaking at least one cron (disabled)
>> >
>> > I've tried removing the address via the backend admin, as well as
>> command
>> > line, but it's not working.
>>
>> By command line I'm guessing you did
>> ```
>> bin/remove_members LISTNAME user@@example.com
>> ```
>> and that returned
>> ```
>> No such member: user@@example.com
>> ```
>> If that's the case, you can do the following:
>>
>> put this one line in a file
>> ```
>> del mlist.members['user@@example.com']
>> ```
>> Then run
>> ```
>> bin/config_list -i path_to_the_above_file LISTNAME
>> ```
>> I think that should do it.
>>
>>
>> --
>> Mark Sapiro <m...@msapiro.net>        The highway is for gamblers,
>> San Francisco Bay Area, California    better use your sense - B. Dylan
>>
>> ------------------------------------------------------
>> Mailman-Users mailing list -- mailman-users@python.org
>> To unsubscribe send an email to mailman-users-le...@python.org
>> https://mail.python.org/mailman3/lists/mailman-users.python.org/
>> Mailman FAQ: http://wiki.list.org/x/AgA3
>> Security Policy: http://wiki.list.org/x/QIA9
>> Searchable Archives:
>> https://www.mail-archive.com/mailman-users@python.org/
>>     https://mail.python.org/archives/list/mailman-users@python.org/
>> Member address: sc...@qth.com
>>
>
------------------------------------------------------
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
    https://mail.python.org/archives/list/mailman-users@python.org/
Member address: arch...@mail-archive.com

Reply via email to