Brady,
As I understand it, yes that is the problem. You can submit a bugzilla request, and
wait (not indefinitely) for James to support 8bitmime, but it is not currently on the
list for 2.1.
--- Noel
-----Original Message-----
From: Brady Moritz [mailto:[EMAIL PROTECTED]]
Sent: Sunday, August 18, 2002 18:54
To: James Users List; James Users List
Subject: RE: problem repeat
guys- is there anything special required to support 8bitmime? I hesitate to turn this
off at the front server because we have several servers running behind the firewall,
and hate to make a change that woudl only be needed for the james server. I imagine
that turning off 8bitmime will cause problems with an umber of users whose email
clients default to this encoding?
Im still curious if the 8bitmime is truly the problem anyway, as I had read that
almost all email nowdays is 8 bit anyway??
Thanks
Brady
-----Original Message-----
From: Noel J. Bergman [mailto:[EMAIL PROTECTED]]
Sent: Sun 8/18/2002 5:31 PM
To: James Users List
Cc:
Subject: RE: problem repeat
Danny,
> The command is EHLO and it returns the *optional* ESMTP verbs the server
supports, I think
> you're right in assuming this empty response by James is the cause, please
file a bug.
As I read RFC 2821, we are responding acceptably to EHLO. There is no
negative response. You only reply with those ESMTP verbs that you DO support. Even
if we implemented some service extensions (VRFY and EXPN are strongly recommended), we
would not be accepting 8bitmime until such time as we do. The problem is that he's
using Exchange as a relay, and the relay is accepting 8bitmime without knowing if it
can forward 8bitmime. AIUI, this is a known problem for Exchange, with documented
fixes.
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
