Re: OpenSMTPD Problem
On Fri, May 23, 2014 at 02:17:51PM -0600, Nicholas Janzen wrote: I'm really looking forward to the new OpenSMTP included in OpenBSD. I'm having an issue with both the mail program and inbound SMTP both give the same error Is there a way for it accept: n...@test.com in addition to: n...@test.com ? Why would you want to do that ? It violates RFC 5321 which explicitely states that: Reverse-path = Path / Forward-path = Path Path = [ A-d-l : ] Mailbox and mail = MAIL FROM: Reverse-path CRLF rcpt = RCPT TO: ( Postmaster@ Domain / Postmaster / Forward-path ) [SP Rcpt-parameters] CRLF If anything not only we should disallow: MAIL FROM: f...@bar.com But we should also disallow: MAIL FROM: f...@bar.com As space is not allowed between ':' and '' This is not about being rfc pedantic but about preventing people from writing broken SMTP code because we're too permissive and tolerant with protocol error. What is the real problem that has prompted you to ask this question ? -- Gilles Chehade https://www.poolp.org @poolpOrg -- You received this mail because you are subscribed to misc@opensmtpd.org To unsubscribe, send a mail to: misc+unsubscr...@opensmtpd.org
Re: OpenSMTPD Problem
The real problem is when using mutt and mail, a command like this also gives the error: mail -s subject n...@test.com, this of course works: 'n...@test.com' On Sat, May 24, 2014 at 01:43:02PM +0200, Gilles Chehade wrote: On Fri, May 23, 2014 at 02:17:51PM -0600, Nicholas Janzen wrote: I'm really looking forward to the new OpenSMTP included in OpenBSD. I'm having an issue with both the mail program and inbound SMTP both give the same error Is there a way for it accept: n...@test.com in addition to: n...@test.com ? Why would you want to do that ? It violates RFC 5321 which explicitely states that: Reverse-path = Path / Forward-path = Path Path = [ A-d-l : ] Mailbox and mail = MAIL FROM: Reverse-path CRLF rcpt = RCPT TO: ( Postmaster@ Domain / Postmaster / Forward-path ) [SP Rcpt-parameters] CRLF If anything not only we should disallow: MAIL FROM: f...@bar.com But we should also disallow: MAIL FROM: f...@bar.com As space is not allowed between ':' and '' This is not about being rfc pedantic but about preventing people from writing broken SMTP code because we're too permissive and tolerant with protocol error. What is the real problem that has prompted you to ask this question ? -- Gilles Chehade https://www.poolp.org @poolpOrg -- /-\ | Nicholas Janzen Personal Site: http://obsd.com| | Email: n...@obsd.comSecurity Site: http://secure6.net | | VE6OBS VE6TS (Basic+Advanced) Weather Site: http://nicholasjanzen.ca| | Short URL's: http://clearurl.net/ Balloon Site: http://arawr.ca | \-/ -- You received this mail because you are subscribed to misc@opensmtpd.org To unsubscribe, send a mail to: misc+unsubscr...@opensmtpd.org
Re: OpenSMTPD Problem
On Sat, May 24, 2014 at 07:16:07AM -0600, Nicholas Janzen wrote: The real problem is when using mutt and mail, a command like this also gives the error: mail -s subject n...@test.com, this of course works: 'n...@test.com That's very strange, I have been using mutt daily for as long as OpenSMTPD exists and I have never ever ran into such an issue. As for mail, there's definitely something broken on your side because `mail` uses `sendmail` internally which should be a hardlink to `smtpctl` when OpenSMTPD gets installed ... and `smtpctl` never uses FROM FROM: foo@bar, so at the very least your local enqueuer is incorrectly configured which probably explains mutt too. On Sat, May 24, 2014 at 01:43:02PM +0200, Gilles Chehade wrote: On Fri, May 23, 2014 at 02:17:51PM -0600, Nicholas Janzen wrote: I'm really looking forward to the new OpenSMTP included in OpenBSD. I'm having an issue with both the mail program and inbound SMTP both give the same error Is there a way for it accept: n...@test.com in addition to: n...@test.com ? Why would you want to do that ? It violates RFC 5321 which explicitely states that: Reverse-path = Path / Forward-path = Path Path = [ A-d-l : ] Mailbox and mail = MAIL FROM: Reverse-path CRLF rcpt = RCPT TO: ( Postmaster@ Domain / Postmaster / Forward-path ) [SP Rcpt-parameters] CRLF If anything not only we should disallow: MAIL FROM: f...@bar.com But we should also disallow: MAIL FROM: f...@bar.com As space is not allowed between ':' and '' This is not about being rfc pedantic but about preventing people from writing broken SMTP code because we're too permissive and tolerant with protocol error. What is the real problem that has prompted you to ask this question ? -- Gilles Chehade https://www.poolp.org @poolpOrg -- /-\ | Nicholas Janzen Personal Site: http://obsd.com| | Email: n...@obsd.comSecurity Site: http://secure6.net | | VE6OBS VE6TS (Basic+Advanced) Weather Site: http://nicholasjanzen.ca| | Short URL's: http://clearurl.net/ Balloon Site: http://arawr.ca | \-/ -- Gilles Chehade https://www.poolp.org @poolpOrg -- You received this mail because you are subscribed to misc@opensmtpd.org To unsubscribe, send a mail to: misc+unsubscr...@opensmtpd.org
Question about auth and auth-optional
The manual for auth-optional looks like this: If auth-optional is specified, then SMTPAUTH is not required to establish an SMTP transaction. This is only useful to let a listener accept incoming mail from untrusted senders and outgoing mail from authenticated users in situations where it is not possible to listen on the submission port. What is submission port? I noticed, that if option auth is specified, than nobody can send messages to my server without password, even gmail or other external services. If option auth-optional is specified, i successfully receive mail from gmail, yandex and everything else. So, I think auth-optional is the only choise for most of servers, am i right? I'm very happy using OpenSMTPD! This is the best MTA ever! Could you help me with one more question, please. Will OpenSMTPD ever support non-tls PLAIN login auth mechanism? For me it is not a problem to use tls, but some old or thin mua does not support tls or ssl, i know this is not secure, but for the OpenSMTPD full greatness it would be nice. Thank you for all! -- You received this mail because you are subscribed to misc@opensmtpd.org To unsubscribe, send a mail to: misc+unsubscr...@opensmtpd.org
