At 01:06 PM 5/31/2005 -0400, Valdis(_dot_)Kletnieks(_at_)vt(_dot_)edu wrote:
On Tue, 31 May 2005 09:46:57 PDT, David MacQuigg said:
> I would accept as proof two messages, one sent directly to the receiver,
> the other through the forwarder, both identical going in.
a) This tells you something between zero and diddly about any of the headers
that were acquired along the route through the forwarder - and we could
*easily*
be talking 20-25 of them if the forwarder is a mailing list.
Doesn't matter. All I care about is that the Trusted Forwarder not
re-order the headers he receives. He can add whatever headers he wants
within his own administrative domain.
b) The fact that your test case shows up without anything reordered doesn't
prove that there's no misbehavior in other cases (or did you actually *test*
cases like "more than 900 local recipients *and* more than 100 recipients at
another host that happens to have us as a secondary MX forwarder" - had *that*
give some software some indigestion. Worst part was that it actually
manifested
as a doubly-linked file in the message store - seems when a %3d rolled over in
the same message, the same filename got created for the 3rd and 1003rd
recipients ;)
If this were a widespread problem, you would be able to show an example and
explain it in simple words.
--
Dave
************************************************************ *
* David MacQuigg, PhD email: david_macquigg at yahoo.com * *
* IC Design Engineer phone: USA 520-721-4583 * * *
* Analog Design Methodologies * * *
* 9320 East Mikelyn Lane * * *
* VRS Consulting, P.C. Tucson, Arizona 85710 *
************************************************************ *