I've narrowed this down (hopefully) a bit. It only seems to happen when you do the confirmation request through a browser (tested both IE under XP and Mozilla under Linux).
Replying to the email confirmation via email worked every time. (Probably did 50 or so tests.) Handling the confirmation through the web interface failed probably 80% of the time. Our web server is not running on the same machine as our MTA/mailman, but both mount the same NFS share for the mailman files. The webserver is running as the user mailman. Since it works some of the time, it would seem like there is a race condition. I noticed that the faster I handled the confirmation the more it was apt to fail. I take it that the the email confirmation and web interface are not calling the same exact code to do the confirmation? Thanks, Todd > > Mailman sends out a welcome message after doing a read of the database > > and finding that the user is not a current member. That means it could > > have failed in it's attempt to write to the database - though that would > > definitely send some errors to see in the logs. ------------------------------------------------------ Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
