Re: TCPIP$SMTP_MIME_HACK
- From: helbig@xxxxxxxxxxxxxxxxxxxxxxxx (Phillip Helbig---remove CLOTHES to reply)
- Date: Tue, 3 Apr 2007 08:48:02 +0000 (UTC)
In article <THdjQaWg3qc3@xxxxxxxxxxxxxxxxxxxxxxxx>,
briggs@xxxxxxxxxxxxxxxxx writes:
In article <euob23$ga7$1@xxxxxxxxx>, helbig@xxxxxxxxxxxxxxxxxxxxxxxx (Phillip Helbig---remove CLOTHES to reply) writes:
$! TCPIP$SMTP_MIME_HACK
$! When set, SMTP accepts 8BITMIME requests from SMTP clients,
$! preventing the clients from converting the message into a 7-bit
$! format.
$!
$!DEFINE/SYSTEM TCPIP$SMTP_MIME_HACK 1
What exactly does this do?
Thanks for the detailed explanation.
So setting
$!DEFINE/SYSTEM TCPIP$SMTP_MIME_HACK 1
causes the VMS SMTP receiver to [at least pretend to] be able to
receive 8 bit SMTP traffic. It will advertise its willingness in
the greeting response. And it will accept the option on the
MAIL FROM: line that it parses.
One can set the TCPIP SMTP configuration to 8 bit. I've had that on for
years. This passes 8-bit characters cleanly through at my end, assuming
that they arrive. Obviously, if the sender has already sone some
encoding a layer up in the protocol, I can't change that. However, if
the sender is deciding it needs to encode during the SMTP dialog, I
would prefer it didn't. Apparently, this could be achieved by defining
the logical name.
Does anyone here actually have it defined?
.
- Follow-Ups:
- Re: TCPIP$SMTP_MIME_HACK
- From: JF Mezei
- Re: TCPIP$SMTP_MIME_HACK
- References:
- TCPIP$SMTP_MIME_HACK
- From: Phillip Helbig---remove CLOTHES to reply
- Re: TCPIP$SMTP_MIME_HACK
- From: briggs
- TCPIP$SMTP_MIME_HACK
- Prev by Date: Re: anti-spam advice
- Next by Date: Re: More on why Javascript is evil
- Previous by thread: Re: TCPIP$SMTP_MIME_HACK
- Next by thread: Re: TCPIP$SMTP_MIME_HACK
- Index(es):
Relevant Pages
|