Kern Sibbald <[EMAIL PROTECTED]> writes:
> The tmda-pending problems: well, among the 2,500 identical
> messages there were a few others, and for some reason they
> cause tmda-pending to crash. Once it crashes, it apparently
> looses track of the fact that it already released several
> hundred messages, so the next invocation of tmda-pending,
> I'm back to square one.
This is a problem. I have a couple of thoughts on how to solve this
that I'll take up with Jason.
> Here is the output of a typical tmda-pending crash:
>
> 1030555269.2975.msg (276 of 1890 / 27893 bytes)
> >> Date: Tue, 27 Aug 2002 03:33:36 -0500
> >> From: "Brian Fleener" <[EMAIL PROTECTED]>
> >> To: None
> >> Subj: $5 IN YOUR MAILBOX ! LEARN HOW !!
> ([p]ass / [s]how / [r]el / [d]el / [w]hite / [b]lack / [q]uit) [pass]:
> release 1030555269.2975.msg
> Traceback (most recent call last):
> File "/usr/local/tmda/bin/tmda-pending", line 497, in ?
> main()
> File "/usr/local/tmda/bin/tmda-pending", line 463, in main
> release(headers, body, msg)
> File "/usr/local/tmda/bin/tmda-pending", line 295, in release
> Util.sendmail(headers, body, recipient, return_path)
> File "./TMDA/Util.py", line 425, in sendmail
> File "./TMDA/SMTP.py", line 51, in sendmail
> File "/usr/lib/python2.2/smtplib.py", line 651, in sendmail
> (code,resp) = self.data(msg)
> File "/usr/lib/python2.2/smtplib.py", line 449, in data
> q = quotedata(msg)
> File "/usr/lib/python2.2/smtplib.py", line 185, in quotedata
> re.sub(r'(?:\r\n|\n|\r(?!\n))', CRLF, data))
> File "/usr/lib/python2.2/sre.py", line 143, in sub
> return _compile(pattern, 0).sub(repl, string, count)
This doesn't appear to be the full output of the traceback. I can't
tell much from it except that the problem occurred in Python's regular
expression library. If you can cause this to happen again, I would
very much appreciate it if you could send me the .msg file that
triggers it.
> However, given the sheer volume it is impossible to do it
> manually. I was at the point of feeding tmda-pending 1890
> "r" commands via a script when this bug came up.
Assuming GNU grep...
$ cd ~/.tmda/pending
$ grep --files-with-matches 'UniqueString' *.msg | xargs tmda-pending -bd
will delete all messages containing 'UniqueString'. Then you can
process the remainder interactively with tmda-pending, releasing those
you choose.
> ======= end of first problem causing total loss of pending folder ====
>
> Now, I look in my tmda log file, and I have 2.7 megabytes of the
> following messages:
>
> ============ log messages ============
> Uncaught Python 2.2 Exception (Fri Aug 30 17:01:23 2002):
> ---------------------------------------------------------
> Traceback (most recent call last):
> File "/usr/local/tmda/bin/tmda-filter", line 50, in ?
> execfile(os.path.join(execdir, 'tmda-rfilter'))
> File "/usr/local/tmda/bin/tmda-rfilter", line 736, in ?
> main()
> File "/usr/local/tmda/bin/tmda-rfilter", line 693, in main
> bouncegen('bounce', Defaults.BOUNCE_TEXT_FILTER_INCOMING)
> File "/usr/local/tmda/bin/tmda-rfilter", line 629, in bouncegen
> send_bounce(bounce_message, already_confirmed=1)
> File "/usr/local/tmda/bin/tmda-rfilter", line 344, in send_bounce
> envelope_sender, Defaults.BOUNCE_ENV_SENDER)
> File "./TMDA/Util.py", line 425, in sendmail
> File "./TMDA/SMTP.py", line 51, in sendmail
> File "/usr/src/build/87651-i386/install/usr/lib/python2.2/smtplib.py", line 650,
>in sendmail
> raise SMTPRecipientsRefused(senderrs)
> SMTPRecipientsRefused: {'[EMAIL PROTECTED]': (550, '5.1.1 <[EMAIL PROTECTED]>...
>User unknown')}
Well, this is trying to send an bounce message (because your filter
said 'bounce') to [EMAIL PROTECTED] The SMTP server that TMDA is
trying to relay through (localhost, unless you've set the SMTPHOST
configuration variable) is refusing to accept mail for that
recipient. When that happens, TMDA tells the MTA (sendmail, you said)
that there is a problem and leaves the original mail in the sendmail
queue. Sendmail will keep trying to deliver that message for a while
(usually less than a week) and will eventually attempt to bounce it
itself. If you can fix this problem at the SMTP server, then you
won't get these messages anymore. If you can't, then don't worry too
much about it. Sendmail will eventually bounce them itself.
Tim
_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users
