[Mailman-Developers] Re: monthly notification error

[Eric D. Christensen]

> I'm running debian/testing and just upgraded mailman to the version
> in unstable (2.1.1-5). Last night the cron job to send out the monthly
> password reminders failed with this error:
> 
> Traceback (most recent call last):
>   File "/usr/lib/mailman/cron/mailpasswds", line 218, in ?
>     main()
>   File "/usr/lib/mailman/cron/mailpasswds", line 145, in main
>     password = mlist.getMemberPassword(member)
>   File "/var/lib/mailman/Mailman/OldStyleMemberships.py", line 102, in
> getMemberPassword
>     raise Errors.NotAMemberError, member
> Mailman.Errors.NotAMemberError: rick at niof.net
> 
> Is there some upgrade configuring I need to do? I did create the
> 'mailman' mailing list. Do I need to add myself as a subscriber?
> Should I send a bugreport to the debian maintainer?

It's not just Debian... I'm running 2.1.1 on Linux and had the same
problem. Probably worth filing a bug report against mailman since there
are at least two of us seeing the same problems on different platforms
now.

I've also see this when running the cron/disabled script. It always
seems to be with one specific user, which makes me suspect something
that didn't translate correctly in the database. Attached below are the
details I reported earlier. 

Barry - if it would be helpful, I'd be happy to give you access to the
mailman account on my server so you can poke around. 

-- 
Eric D. Christensen <edc at proadmin.com>
Proadmin, Inc.


--- Attached Message Follows ---


I'm getting an error when running cron/disabled after updating from 2.0
to 2.1.1. I suspect this is due to something that got corrupted /
confused / boggled in the upgrade process, but I'm not finding any
clues. Just wondering if anyone else had run into this before I devote
time tracking it down (which could take awhile with my miserable python
skills).

This is from a list that has existing for several years and has survived
though several mailman upgrades. I'm concerned that there my be rubbish
in one of the pickled db files that might be causing other problems that
I'm not aware of yet....


Traceback (most recent call last):
  File "../cron/disabled", line 209, in ?
    main()
  File "../cron/disabled", line 168, in main
    mlist.disableBouncingMember(member, info, msg)
  File "/home/mailman/Mailman/Bouncer.py", line 163, in
disableBouncingMember
    self.sendNextNotification(member)
  File "/home/mailman/Mailman/Bouncer.py", line 243, in
sendNextNotification
    {'listname'   : self.real_name,
  File "/home/mailman/Mailman/OldStyleMemberships.py", line 102, in
getMemberPassword
    raise Errors.NotAMemberError, member
Mailman.Errors.NotAMemberError: mosterbrink at saturnee.com

The address in question IS a member, and interestingly enough, doesn't
show as disabled form the admin interface or when running list_members
--nomail. 

I also find in the error log:

Apr 18 18:07:05 2003 (29034) Uncaught runner exception:
mosterbrink at saturnee.comApr 18 18:07:05 2003 (29034) Traceback (most
recent call last):
  File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop
    self._onefile(msg, msgdata)
  File "/home/mailman/Mailman/Queue/Runner.py", line 155, in _onefile
    keepqueued = self._dispose(mlist, msg, msgdata)
  File "/home/mailman/Mailman/Queue/BounceRunner.py", line 126, in
_dispose
    mlist.registerBounce(addr, msg)
  File "/home/mailman/Mailman/Bouncer.py", line 155, in registerBounce
    self.disableBouncingMember(member, info, msg)
  File "/home/mailman/Mailman/Bouncer.py", line 163, in
disableBouncingMember
    self.sendNextNotification(member)
  File "/home/mailman/Mailman/Bouncer.py", line 243, in
sendNextNotification
    {'listname'   : self.real_name,
  File "/home/mailman/Mailman/OldStyleMemberships.py", line 102, in
getMemberPassword
    raise Errors.NotAMemberError, member
NotAMemberError: mosterbrink at saturnee.com

Apr 18 18:07:05 2003 (29034) SHUNTING:
1050714405.7204649+8f6a162efa552e48101820d5a680dba33c29e4c5

Anyone have any ideas?