-
Notifications
You must be signed in to change notification settings - Fork 47
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
Comments
(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.) |
Yes, this should not happen. How do you inject the mails? Via OpenBSD smtpd? You can send me the mail to leah@vuxu.org. |
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. |
(Running smtpd with |
Reproducible with
|
Ok, try the new mmime, and please report all issues, i could only test it lightly! |
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. |
OpenSMTPD on OpenBSD 6.0 is rejecting replies to a particular message, with the error:
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?
The text was updated successfully, but these errors were encountered: