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=userx@domain.x, 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=userx@domain.x, 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?
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=userx@domain.x, 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=userx@domain.x, 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?