-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"UTF-8" and "US-ASCII" Errors While Scanning Mail. #88
Comments
I am getting this error |
maia-1.0.4_10 having same issue 451 4.5.0 Error in processing, id=81081-08, mime_decode-1 FAILED: Unknown encoding 'UTF-8;' at /usr/local/sbin/maiad line 3837, line 4587. (in reply to end of DATA command)) 451 4.5.0 Error in processing, id=84476-01, mime_decode-1 FAILED: Unknown encoding 'windows-1251; boundary="zlJYX7vINDvB=_B5yve2siHNUDWgwWSCmQ"' at /usr/local/sbin/maiad line 3837, line 664. (in reply to end of DATA command)) |
Hi, Makioro. Please update to the latest version of Maia-Mailguard on FreeBSD (maia-1.0.4_11) which includes a patch to fix this issue. |
Thanks. This is helpful |
I've updated the FreeBSD port (security/maia) for this project to the latest commit (48df5fb) and I've had multiple reports of issues with mail delivery both incoming and outgoing. The error appears as:
"to=[email protected], relay=127.0.0.1[127.0.0.1]:10024, delay=397, delays=395/0.02/1.8/0.08, dsn=4.5.0, status=deferred (host 127.0.0.1[127.0.0.1] said: 451 4.5.0 Error in processing, id=23197-01, mime_decode-1 FAILED: Unknown encoding 'US-ASCII;' at /usr/local/sbin/maiad line 3837, line 76. (in reply to end of DATA command))"
and
"to=[email protected], relay=127.0.0.1[127.0.0.1]:10024, delay=638, delays=636/0.01/1.7/0.08, dsn=4.5.0, status=deferred (host 127.0.0.1[127.0.0.1] said: 451 4.5.0 Error in processing, id=26621-01, mime_decode-1 FAILED: Unknown encoding 'UTF-8;' at /usr/local/sbin/maiad line 3837, line 146. (in reply to end of DATA command))"
After removing the three line "if {}" block (3834-3836) in commit ff107ff, everything appears to be working smoothly again. I'm not sure what the actual issue is here, but it certainly seems to be problematic. Any chance someone could take a look at this?
The text was updated successfully, but these errors were encountered: