Mark Martinec:
> > Nope, RFC 2821 and RFC 5321 still has the same text.
> > It even goes on to say ...
>
> RFC 5321 does not allow empty ehlo-keyword:
>
> section 4.1.1.1:
>
>ehlo-ok-rsp= ( "250" SP Domain [ SP ehlo-greet ] CRLF )
> / ( "250-" Domain [ SP ehlo-greet ]
> Nope, RFC 2821 and RFC 5321 still has the same text.
> It even goes on to say ...
RFC 5321 does not allow empty ehlo-keyword:
section 4.1.1.1:
ehlo-ok-rsp= ( "250" SP Domain [ SP ehlo-greet ] CRLF )
/ ( "250-" Domain [ SP ehlo-greet ] CRLF
*( "250
On Thursday, October 27, 2011, 13:07:37, Wietse Venema wrote:
> Mark Martinec:
>> Seems like the smtp-sink appends one empty EHLO option
>> at the end of its reply to an ehlo command.
>> Should this be fixed? - my content filter is currently logging
>> a warning, I wonder if I should remove the war
Mark Martinec:
> Seems like the smtp-sink appends one empty EHLO option
> at the end of its reply to an ehlo command.
> Should this be fixed? - my content filter is currently logging
> a warning, I wonder if I should remove the warning :)
>
> Using postfix-current-2.9.20111012 from FreeBSD ports.
Seems like the smtp-sink appends one empty EHLO option
at the end of its reply to an ehlo command.
Should this be fixed? - my content filter is currently logging
a warning, I wonder if I should remove the warning :)
Using postfix-current-2.9.20111012 from FreeBSD ports.
$ smtp-sink 127.0.0.1:200
