Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#958388: dkimpy-milter: `UnicodeDecodeError` for some spam mail
42 views
Skip to first unread message
Ansgar
Apr 21, 2020, 7:10:03 AM4/21/20
to
Package: dkimpy-milter
Version: 1.2.1-1~bpo10+1
I saw the following message in my mail server's mail.log:
2020-04-21T07:18:09.247360+02:00 dkimpy-milter[697987]: UnicodeDecodeError: 'utf-8' codec can't decode byte 0xa0 in position 5: invalid start byte
2020-04-21T07:18:09.247522+02:00 dkimpy-milter[697987]: dkimpy-filter: milter claimed not to reply in state 7 but did anyway 4
2020-04-21T07:22:16.144238+02:00 postfix/cleanup[772747]: warning: milter unix:dkimpy-milter-verify/dkimpy-milter-verify.socket: can't read SMFIC_BODYEOB reply packet header: Success
2020-04-21T07:22:16.144978+02:00 postfix/cleanup[772747]: 044A47FC99: milter-reject: END-OF-MESSAGE from unknown[...]: 4.7.1 Service unavailable - try again later; from=<...> to=<...> proto=ESMTP helo=<...>
It was most likely caused by a spam mail that was then rejected. So I
can't say much more about the mail.
It looks like a bug for dkimpy-milter to expect any particular character
encoding.
Ansgar
Version: 1.2.1-1~bpo10+1
I saw the following message in my mail server's mail.log:
2020-04-21T07:18:09.247360+02:00 dkimpy-milter[697987]: UnicodeDecodeError: 'utf-8' codec can't decode byte 0xa0 in position 5: invalid start byte
2020-04-21T07:18:09.247522+02:00 dkimpy-milter[697987]: dkimpy-filter: milter claimed not to reply in state 7 but did anyway 4
2020-04-21T07:22:16.144238+02:00 postfix/cleanup[772747]: warning: milter unix:dkimpy-milter-verify/dkimpy-milter-verify.socket: can't read SMFIC_BODYEOB reply packet header: Success
2020-04-21T07:22:16.144978+02:00 postfix/cleanup[772747]: 044A47FC99: milter-reject: END-OF-MESSAGE from unknown[...]: 4.7.1 Service unavailable - try again later; from=<...> to=<...> proto=ESMTP helo=<...>
It was most likely caused by a spam mail that was then rejected. So I
can't say much more about the mail.
It looks like a bug for dkimpy-milter to expect any particular character
encoding.
Ansgar
Christian Kujau
Apr 29, 2021, 8:40:03 AM4/29/21
to
Same here with dkimpy-milter 1.2.1-1~bpo10+1 (upstream is at 1.2.2), but I
didn't manage to get a sample of that invalid looking email yet:
postfix/smtpd[1872437]: 818E75FD3A: client=XXX[XXX]
postfix/cleanup[1872438]: 818E75FD3A: message-id=<XXX>
dkimpy-milter[1846888]: UnicodeDecodeError: 'utf-8' codec can't decode byte 0x92 in position 5: invalid start byte
dkimpy-milter[1846888]: dkimpy-filter: milter claimed not to reply in state 7 but did anyway 4
didn't manage to get a sample of that invalid looking email yet:
postfix/smtpd[1872437]: 818E75FD3A: client=XXX[XXX]
postfix/cleanup[1872438]: 818E75FD3A: message-id=<XXX>
dkimpy-milter[1846888]: UnicodeDecodeError: 'utf-8' codec can't decode byte 0x92 in position 5: invalid start byte
dkimpy-milter[1846888]: dkimpy-filter: milter claimed not to reply in state 7 but did anyway 4
Scott Kitterman
Feb 26, 2023, 6:20:05 PM2/26/23
to
On Thu, 28 Oct 2021 22:51:36 -0400 David Mandelberg <da...@mandelberg.org>
wrote:
> With dkimpy-milter 1.2.2-1, I get the same error, and I managed to
> capture one of the emails that triggered it, see attached.
>
> I think these are the log messages that correspond to the attached
> email, but there were some other similar messages nearby so it's
> possible these are for a different email:
>
> Oct 29 01:32:00 mail-inbound-119b7863 dkimpy-milter[642]:
> UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc0 in position 1:
> invalid start byte
> Oct 29 01:32:00 mail-inbound-119b7863 dkimpy-milter[642]: dkimpy-filter:
milter binding (pymitler) and this package. As of pymilter 1.0.5, it's fixed
and this will at least not have failures like this in the next dkimpy-mitler
release.
Scott K
wrote:
> With dkimpy-milter 1.2.2-1, I get the same error, and I managed to
> capture one of the emails that triggered it, see attached.
>
> I think these are the log messages that correspond to the attached
> email, but there were some other similar messages nearby so it's
> possible these are for a different email:
>
> Oct 29 01:32:00 mail-inbound-119b7863 dkimpy-milter[642]:
> UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc0 in position 1:
> invalid start byte
> Oct 29 01:32:00 mail-inbound-119b7863 dkimpy-milter[642]: dkimpy-filter:
> milter claimed not to reply in state 7 but did anyway 4
It looks like these were caused by a combination of failures in the Python
milter binding (pymitler) and this package. As of pymilter 1.0.5, it's fixed
and this will at least not have failures like this in the next dkimpy-mitler
release.
Scott K
0 new messages