Dan Egli <[EMAIL PROTECTED]> writes: > Ok. On a whim, I used tmda-check-address to check a confirmation address. > Here's the result: > > [EMAIL PROTECTED] dan]$ tmda-check-address [EMAIL PROTECTED] > STATUS: Invalid cryptographic tag format. > Traceback (most recent call last): > File "/usr/bin/tmda-check-address", line 127, in ? > main() > File "/usr/bin/tmda-check-address", line 122, in main > print "EXPIRED: %s" % addr.timestamp(1, localtime) > TypeError: timestamp() takes exactly 1 argument (3 given)
Ugh. Apparently tmda-check-address hasn't been updated in a while, and the ConfirmAddress class in Address.py, which tmda-address and tmda-check-address use, hasn't been either. Not surprising, since people usually don't generate or check confirm addresses, but bad nonetheless. I've checked in several fixes to Address.py and tmda-check-address. If you're comfortable with CVS, you can check out TMDA from the repository and just copy those two files to the appropriate locations. If not, the changes will be in the next release. If you're desparate, contact me off-list and I'll send you a patch. > I saw the invalid cryptographic tag format and figured I'd generate a new > crypy_key. Perhaps my old one was somehow corrupted. So I ran tmda-keygen, > and echoed the new key into my ~/.tmda/crypt_key file. Then I created a > new confirmation request, tried it again, and got the exact same error. It's probably not invalid. tmda-check-address would just die when used with any confirm address. > Anyone got any tips on this one? I really need to get this working! It's > bugging a lot of people when they try to confirm their address, only to > get anonther confirmation message. I'm getting several flames because of > it. I don't think it's your address that's wrong. If it were, the people sending you mail would receive an automated message telling them that they had replied to an invalid address. I still suspect the EXTENSION, mostly because after looking at the code, I can't imagine what else it could be. Could you put something like the following in your .procmailrc before running TMDA? :0 c | cat > /dev/null ; env > ~/env.out This should absorb the mail to avoid pipe errors in procmail and then write the environment to $HOME/env.out. If you could verify that EXTENSION is actually in the env.out file, that would either answer the question or tell me I need to look harder! Thanks, Tim _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
