On Wed, 7 Jun 2000, Guillaume Morin wrote:
> Hi all,
>
> I have checked the website and the archives of the list and I could
> not find an answer.
>
> Since many monthes, I had problems sending mail
> using my ISP to some domains. It seems that most of them uses Exim. The
> problem is that I cannot send 8bitmime messages to these domains. I
> always received a mailer-daemon message.
>
> Recently, I've configured my
> own mail service with Exim. And I've seen that adding the
> accept_8bitmime option makes my ISP's smtp happier. 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.
The exim config file gives the administrator of a system running exim
the capability to decide wether they wish exim to offer that feature or
not. Some sites may wish to not permit this feature.
That is what the 'accept_8bitmime' option is for (And when it is
set, exim does in fact include the '8BITMIME' response to an ehlo
command.)
I include an example below.
| Connected my-server.domain.com (127.0.0.1).
| Escape character is '^]'.
| 220 my-server.domain.com ESMTP *NO UCE* (RBL,DUL,DSSL,ORBS) Exim 3.14 : Wed, 07 Jun 2000 20:26:29 -0400
| ehlo foo
| 250-my-server.domain.com Hello root at foo [127.0.0.1]
| 250-SIZE 1048576
| 250-8BITMIME
| 250-PIPELINING
| 250 HELP
| mail from: <foo@???> body=8bitmime
| 250 <foo@???> is syntactically correct
| rset
| 250 Reset OK
| quit
| 221 my-server.domain.com closing connection
> reason why the smtp believes it cannot send the 8bitmime messages.
>
> So my question is why Exim does not follow that RFC although it is 8-bit
> clean or where am I wrong ?
>
> Thank you in advance. Regards,
>
>
--
