Jim Ramsay <[EMAIL PROTECTED]> writes: > Hmmm... First of all, I think if he's clicking "Whitelist" in > tmda-cgi, it should be going to his PENDING_WHITELIST_APPEND instead > of CONFIRM_APPEND - but these are the same in his posted config, so > that doesn't really matter.
I think he might have just meant "Confirm", and typed "Whitelist" instead. If you look at his messages on -users and the logfile excerpts he included, it's clear he is confirming the messages. > Whereas releasing a message by confirmation email does a completely > different thing in tmda-rfilter. Also, releasing it by URL > confirmation would probably work fine, as this approximates the same > code in tmda-rfilter. It's not quite the same code though. tmda-cgi uses it's own block of code in Release.py to do this, though it does call some of the same functions. What I was wondering is if someone (such as yourself) who is very familiar with tmda-cgi could figure out why when Jeff confirms a message via tmda-cgi the wrong address gets appended to CONFIRM_APPEND, when this isn't the case when he confirms via e-mail. I hope I'm not missing something obvious here? > So, what could the issue in TMDA/Pending.py be? It looks like the > "initMessage" routine in the Message class completely ignores > x-primary-address. This is fine. X-Primary-Address is only meant to get involved during the confirmation process, not during pending operations. We could change this in the future, but this is a separate issue I don't want to pursue at the moment as it's not related to Jeff's bug report. _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
