Skip to content
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

message refused: Message is not RFC 2822 compliant #20

Closed
larryhynes opened this issue Mar 27, 2017 · 7 comments
Closed

message refused: Message is not RFC 2822 compliant #20

larryhynes opened this issue Mar 27, 2017 · 7 comments

Comments

@larryhynes
Copy link
Contributor

larryhynes commented Mar 27, 2017

OpenSMTPD on OpenBSD 6.0 is rejecting replies to a particular message, with the error:

smtp event=failed-command command="DATA" result="550 5.7.1 Delivery not authorized, message refused: Message is not RFC 2822 compliant"

I don't think there's anything particularly out of the ordinary in the message that I'm trying to send, and replies to this person have been going through today already, so I'm a bit stumped. I'm also aware that debugging this could take a lot of time!

Are there any known 'gotcha' areas regarding RFC compliance and mblaze?

@larryhynes
Copy link
Contributor Author

(I can .tar up the message in question and email it on to you as an attachment if you would like to play with it; there's nothing earth-shaking it there.)

@leahneukirchen
Copy link
Owner

Yes, this should not happen. How do you inject the mails? Via OpenBSD smtpd? You can send me the mail to leah@vuxu.org.

@larryhynes
Copy link
Contributor Author

femail as sendmail on localhost -> openbsd smtpd on local gateway -> openbsd smtpd on main server, is the usual route. This mail is getting stopped at the local gateway smtpd i.e femail is passing it on, but opensmtpd is rejecting it. I'll send along a copy of it to you. My reply was just some plain text, [m]imed, then [s]ent.

@larryhynes
Copy link
Contributor Author

larryhynes commented Mar 27, 2017

(Running smtpd with smtpd -d -vv -T all doesn't seem to reveal anything beyond that error message, i.e. it doesn't say where or why the message isn't RFC 2822 compliant. :(

@leahneukirchen
Copy link
Owner

Reproducible with

mmime <<EOF
References: <aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa@a> <bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb@b> <ccccccccccccccccccccccccccccccc@c>

Body
EOF

@leahneukirchen
Copy link
Owner

Ok, try the new mmime, and please report all issues, i could only test it lightly!

@larryhynes
Copy link
Contributor Author

Great - thanks. It's already passed the first hurdle, and sent the offending message. I'll let you know if there's any further issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants