From: Ian Lance Taylor <ian@wasabisystems.com>
To: Christopher Faylor <cgf@timesys.com>
Cc: overseers@sources.redhat.com
Subject: Re: ezmlm problem with Received: headers from "ezmlm-send -r"
Date: Mon, 05 Apr 2004 14:52:00 -0000 [thread overview]
Message-ID: <m3k70uiiiu.fsf@gossamer.airs.com> (raw)
In-Reply-To: <20040403212447.GA18287@coc.bosbc.com>
Christopher Faylor <cgf@timesys.com> writes:
> And, wrongness abounds. I made a simple change to 'ezmlm-send' to
> reorganize the headers and that does not fix the problem. Exchange
> seems to be arbitrarily dropping certain headers. The odd thing is that
> when I telnet to port 25 and inject email, the headers come through
> unscathed.
That is weird to the point of being inexplicable. I haven't heard of
this problem before.
Ian
next prev parent reply other threads:[~2004-04-05 14:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-03 19:32 Christopher Faylor
2004-04-03 21:08 ` Christopher Faylor
2004-04-03 21:24 ` Christopher Faylor
2004-04-05 14:52 ` Ian Lance Taylor [this message]
2004-04-05 15:35 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3k70uiiiu.fsf@gossamer.airs.com \
--to=ian@wasabisystems.com \
--cc=cgf@timesys.com \
--cc=overseers@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).