You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by Stefano Bagnara <ap...@bago.org> on 2006/04/10 16:26:43 UTC
Re: I apologize for this, but... Content-Transfer-Encoding: quoted-pr
intable
There is a bug in James 2.3.0a1 about 8bitmime that could cause the
problem you describe. I temporarily disabled 8bitmime in current trunk
but I saw a similar problem with 7bitmime conversion that is still there.
IIRC the problem arise when James relay messages that enter as 7 bit
quotedpritable and are relayed to a server supporting 8bitmime (it loose
the content-transfer-encoding and change it to 8bit while not decoding
the body itself)
You can upgrade to the current nighly builds, but keep in mind that are
nighly builds and *UNSTABLE*.
Stefano
Walker, Aaron L wrote:
> I apologize for using this forum to ask you guys to educate me, but it's for
> the greater good, no?
>
> I'm running james 2.3.0a1 on zOS Unix as a stand-alone server (remember
> me?). Things are going pretty well, but now I have some users complaining
> about how their emails look. Well, after I do some research (seriously, I
> shouldn't be the one figuring this out for the java programmers, but...), I
> find that the problem appears to be when they use Content-Transfer-Encoding:
> quoted-printable. Now I'm not that familiar with that, and I'm trying to
> read up on it and make sense of it, but basically (I'm looking at this
> cosmetically) keeps the content at 76-char lines, and encodes several
> characters.
>
> Now, here's the rub. So, in production they point at a non-James SMTP
> server, and they are happy with the look of their emails, but in test I have
> them pointing to James, and there the equal signs, etc., that get stuck on a
> quoted-printable email are not getting "translated" (I don't know whether
> they are supposed to be or not), so they are not happy with the look.
>
> So... who's at fault, or is it no fault?
>
> Here's a sample:
>
> You will receive the Employer's Liability Notice by mail. If you did not co=
> ntinue to the Employer=92s Tax Information Online (ETIO) system to file rep=
> orts when this account was created, do not delay filing your Employer's Qua=
> rterly Reports after receiving the Employer's Liability Notice. Late report=
> s and/or payments will incur penalties.
>
> Which they want to read:
>
> You will receive the Employer's Liability Notice by mail. If you did not
> continue to the Employer's Tax Information Online (ETIO) system to file
> reports when this account was created, do not delay filing your Employer's
> Quarterly Reports after receiving the Employer's Liability Notice. Late
> reports and/or payments will incur penalties.
>
> Thanks,
> Aaron
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org