Re: [Exim] does exim not follow the RFC 1652 ?

Top Page
Delete this message
Reply to this message
Author: Chris Caswell
Date:  
To: Guillaume Morin
CC: Dave C., exim-users
Subject: Re: [Exim] does exim not follow the RFC 1652 ?

Guillaume Morin wrote:
>
> Dans un message du 07 jun à 20:31, Dave C. écrivait :
> >
> > >Indeed, I've seen
> > > that someone who sends a EHLO command to Exim will not get a 250
> > > 8bitmime response as it is required by the RFC 1652. I think that is the
> >
> > This response is not actually _required_ by the RFC, it is simply
> > provided as an option for an MTA which uses to advertise that
> > capability.
>
> Are you sure of that ? In that RFC, I quote : "
> If a server SMTP does not support the 8-bit MIME transport extension
> (either by not responding with code 250 to the EHLO command, or by not
> including the EHLO keyword value 8BITMIME in its response), then the
> client must not, under any circumstances, attempt to transfer a content
> which contains characters outside the US-ASCII octet range"
>
> So my understanding of that is that you have to send a 250 response with
> 8bitmime to show your 8-bit full support.


This clearly leaves the responsibility with the client to not send
8bitmime to sites that do not declare the capability to accept it. It
does not require anything of the server.


Chris Caswell
Systems / Network Engineer
NC Research and Education Network