[pfx] Re: Headers and Forwarding

2023-04-08 Thread Wietse Venema via Postfix-users
Viktor Dukhovni via Postfix-users:
> Apparently, reading RFC5321 and RFC5322 is too tedious.

 Reading RFCs is so old-school. It's much easier to be ignorant.

Wietse
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org


[pfx] Re: Headers and Forwarding

2023-04-08 Thread Doug Hardie via Postfix-users
> On Apr 8, 2023, at 13:15, Viktor Dukhovni via Postfix-users 
>  wrote:
> 
> On Sat, Apr 08, 2023 at 12:16:30PM -0700, Doug Hardie via Postfix-users wrote:
> 
 Are there any others and how close am I?
>>> 
>>>   
>>> https://www.iana.org/assignments/mail-parameters/mail-parameters.xhtml#mail-parameters-7
>> 
>> Wow, I never would have guessed there would be that many.  Thanks.
> 
> For SMTP (as opposed to LMTP), you were only off by a factor of ~2,
> there's a second "base" value of "UTF8SMTP".  The full set for SMTP is:
> 
>SMTP Simple Mail Transfer Protocol [RFC5321]
>ESMTP SMTP with Service Extensions [RFC5321]
>ESMTPA ESMTP with AUTH [RFC3848]
>ESMTPS ESMTP with STARTTLS [RFC3848]
>ESMTPSA ESMTP with both STARTTLS and AUTH [RFC3848]
>UTF8SMTP ESMTP with SMTPUTF8 [RFC6531]
>UTF8SMTPA ESMTP with SMTPUTF8 and AUTH [RFC4954][RFC6531]
>UTF8SMTPS ESMTP with SMTPUTF8 and STARTTLS [RFC3207][RFC6531]
>UTF8SMTPSA ESMTP with SMTPUTF8 and both STARTTLS and AUTH 
> [RFC3207][RFC4954][RFC6531]
> 
> These are correctly used in Postfix and a few other MTAs, and then
> there's Microsoft, where even the basic atom syntax is violated:
> 
>with Microsoft SMTP Server
> 
> or MessageLabs:
> 
>with AES128-GCM-SHA256 encrypted SMTP
> 
> c.f.
> 
>https://www.rfc-editor.org/rfc/rfc5321#section-4.4
> 
>   Protocol   = "ESMTP" / "SMTP" / Attdl-Protocol
>   Attdl-Protocol = Atom
>  ; Additional standard names for protocols are
>  ; registered with the Internet Assigned Numbers
>  ; Authority (IANA) in the "mail parameters"
>  ; registry [9].  SMTP servers SHOULD NOT
>  ; use unregistered names.
> 
> other violations are less severe:
> 
>with HTTP
>with mapi
>with bizsmtp
>with ngmta

Thanks for that info.  I don't think that will affect me as the first Received 
header in the message (last in time) will always be from postfix
.  I only need postfix's queue id so I can trace what happened if required.  

>...
> 
> Apparently, reading RFC5321 and RFC5322 is too tedious.

Reading is not tedious.  You can't force everyone to use your software if you 
follow the standards.

___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org


[pfx] Re: Headers and Forwarding

2023-04-08 Thread Viktor Dukhovni via Postfix-users
On Sat, Apr 08, 2023 at 12:16:30PM -0700, Doug Hardie via Postfix-users wrote:

> >> Are there any others and how close am I?
> > 
> >
> > https://www.iana.org/assignments/mail-parameters/mail-parameters.xhtml#mail-parameters-7
> 
> Wow, I never would have guessed there would be that many.  Thanks.

For SMTP (as opposed to LMTP), you were only off by a factor of ~2,
there's a second "base" value of "UTF8SMTP".  The full set for SMTP is:

SMTP Simple Mail Transfer Protocol [RFC5321]
ESMTP SMTP with Service Extensions [RFC5321]
ESMTPA ESMTP with AUTH [RFC3848]
ESMTPS ESMTP with STARTTLS [RFC3848]
ESMTPSA ESMTP with both STARTTLS and AUTH [RFC3848]
UTF8SMTP ESMTP with SMTPUTF8 [RFC6531]
UTF8SMTPA ESMTP with SMTPUTF8 and AUTH [RFC4954][RFC6531]
UTF8SMTPS ESMTP with SMTPUTF8 and STARTTLS [RFC3207][RFC6531]
UTF8SMTPSA ESMTP with SMTPUTF8 and both STARTTLS and AUTH 
[RFC3207][RFC4954][RFC6531]

These are correctly used in Postfix and a few other MTAs, and then
there's Microsoft, where even the basic atom syntax is violated:

with Microsoft SMTP Server

or MessageLabs:

with AES128-GCM-SHA256 encrypted SMTP

c.f.

https://www.rfc-editor.org/rfc/rfc5321#section-4.4

   Protocol   = "ESMTP" / "SMTP" / Attdl-Protocol
   Attdl-Protocol = Atom
  ; Additional standard names for protocols are
  ; registered with the Internet Assigned Numbers
  ; Authority (IANA) in the "mail parameters"
  ; registry [9].  SMTP servers SHOULD NOT
  ; use unregistered names.

other violations are less severe:

with HTTP
with mapi
with bizsmtp
with ngmta
...

Apparently, reading RFC5321 and RFC5322 is too tedious.

-- 
Viktor.
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org


[pfx] Re: Headers and Forwarding

2023-04-08 Thread Doug Hardie via Postfix-users
> On Apr 8, 2023, at 11:59, Viktor Dukhovni via Postfix-users 
>  wrote:
> 
> On Sat, Apr 08, 2023 at 11:51:06AM -0700, Doug Hardie via Postfix-users wrote:
> 
>> A couple of questions.  Looking in the postfix generated Received:
>> header, the SMTP id often has a few other letters included:  ESMTPA
>> etc.  I am guessing that the extra letters mean: 
>> 
>>  E - EHLO used rather the HELO
>>  S - SSL was used in the connection
>>  A - the originator was authenticated
>> 
>> Are there any others and how close am I?
> 
>
> https://www.iana.org/assignments/mail-parameters/mail-parameters.xhtml#mail-parameters-7

Wow, I never would have guessed there would be that many.  Thanks.

> 
>> When the alias file pipes an email to a program, does it expect any
>> response from that program,
> 
> Only a 0 exit status code, in which case the program should not generate
> any output.
> 
>> or would it do anything with a response?
> 
> If an error occurs some of the output might be included in the bounce.

Now that sounds like a useful feature.  I'll have to try it out.

-- Doug
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org


[pfx] Re: Headers and Forwarding

2023-04-08 Thread Viktor Dukhovni via Postfix-users
On Sat, Apr 08, 2023 at 11:51:06AM -0700, Doug Hardie via Postfix-users wrote:

> A couple of questions.  Looking in the postfix generated Received:
> header, the SMTP id often has a few other letters included:  ESMTPA
> etc.  I am guessing that the extra letters mean: 
> 
>   E - EHLO used rather the HELO
>   S - SSL was used in the connection
>   A - the originator was authenticated
> 
> Are there any others and how close am I?


https://www.iana.org/assignments/mail-parameters/mail-parameters.xhtml#mail-parameters-7

> When the alias file pipes an email to a program, does it expect any
> response from that program,

Only a 0 exit status code, in which case the program should not generate
any output.

> or would it do anything with a response?

If an error occurs some of the output might be included in the bounce.

-- 
Viktor.
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org