Hello,
Several days ago I upgraded to TMDA 0.65 and since then I have noticed
a problem with UnicodeError's. I have updated all the headers in my
templates, here is the bounce.txt header from the account I will use
in this example:
From.US-ASCII: <%(confirm_accept_address)s>
Subject.US-ASCII: failure notice
I have updated the confirm_request.txt and confirm_accept.txt files too.
Here is what is being spit out in my LOGFILE_DEBUG:
Uncaught Python 2.2.1 Exception (Thu Nov 28 00:02:14 2002):
-----------------------------------------------------------
Traceback (most recent call last):
File "/usr/local/tmda/bin/tmda-filter", line 53, in ?
execfile(os.path.join(execdir, 'tmda-rfilter'))
File "/usr/local/tmda/bin/tmda-rfilter", line 771, in ?
main()
File "/usr/local/tmda/bin/tmda-rfilter", line 766, in main
do_default_action(default_action, 'action_incoming', bouncetext)
File "/usr/local/tmda/bin/tmda-rfilter", line 392, in do_default_action
bouncegen('request')
File "/usr/local/tmda/bin/tmda-rfilter", line 669, in bouncegen
send_bounce(bounce_message, mode)
File "/usr/local/tmda/bin/tmda-rfilter", line 362, in send_bounce
ar.create()
File "./TMDA/AutoResponse.py", line 170, in create
File "./TMDA/pythonlib/email/Header.py", line 164, in __init__
File "./TMDA/pythonlib/email/Header.py", line 230, in append
UnicodeError: ASCII decoding error: ordinal not in range(128)
The strange thing is that some messages make it through. I do not know what
the "ASCII decoding error: ordinal not in range(128)" error message means. I
thought that it might have something to do with the charset, so I looked in
qmail's queue and found a message that was causing this error. Here is the
top of that file:
Received: (qmail 3148 invoked by uid 507); 28 Nov 2002 03:15:33 -0000
Received: from [EMAIL PROTECTED] by silver.standblue.net by uid 504 with
qmail-scanner-1.15
(clamscan: 0.24. Clear:.
Processed in 1.037939 secs); 28 Nov 2002 03:15:33 -0000
X-Qmail-Scanner-Mail-From: [EMAIL PROTECTED] via silver.standblue.net
X-Qmail-Scanner: 1.15 (Clear:. Processed in 1.037939 secs)
Received: from unknown (HELO webserver) (218.17.67.29)
by a.mx.standblue.net with SMTP; 28 Nov 2002 03:15:32 -0000
From: "" <Wonlo Century>
To: "solutions" <[EMAIL PROTECTED]>
Subject: Fw: wonlo.com - <BB><E1><D2><E9><B5><E7><BB><B0>
Date: Thu, 28 Nov 02 11:00:12 <D6><D0><B9><FA><B1><EA><D7><BC><CA><B1><BC><E4>
MIME-Version: 1.0
Content-Type: multipart/mixed;boundary= "----=_NextPart_000_0059_1F24EBBF.8DD3BFED"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2462.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
X-Qmail-Scanner-Message-ID: <[EMAIL PROTECTED]>
------=_NextPart_000_0059_1F24EBBF.8DD3BFED
Content-Type: text/html; charset= "gb2312"
Content-Transfer-Encoding: base64
<Attachment not pasted>
Is this a problem with my template headers? Must I specify each charset that I
want, or can I do something like:
Subject.US-ASCII: failure notice in us-ascii
Subject.DEFAULT: failure notice for all others
Searching for "ordinal not in range" returned zero results in both the tmda-users
and tmda-workers list archives, so no help there.
Any insight is appreciated,
Cory Wright
Stand Blue Technology
http://www.standblue.net/
_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users
