On Tuesday, November 26, 2002, at 06:43 PM, Steve Werby wrote:
"Parker Morse" <morse@xxxxxxxxxxx> wrote::0h: * ^Envelope-to: ouruser@ourdomain /var/spool/mail/ouruserUnfortunately, Envelope-To is not a required field according to RFC2822 andin my experience it is rarely present. See http://www.faqs.org/rfcs/rfc2822.html. That header is not even mentioned once. Is there a Sendmail modification you've used to make the envelope address available via that header? Or am I missing something?
The original poster indicated that the field was always present in the mail which wasn't routing correctly. If it isn't, then obviously this solution won't work. :-) Assuming it is, though, it's not important whether it appears in other mail; just that it is in the specific ones he mentioned.
Any other header field which is unique to the problem messages would work as well, though; in fact, given the headers OP quoted:
Envelope-to: ouruser@ourdomain To: <them@xxxxxxxxxxxxxxx> :0h: * ^To: <them@xxxxxxxxxxxxxxx> /var/spool/mail/ouruserwould work just as well, but would also mis-route mail sent To: <them@xxxxxxxxxxxxxxx> AND anotheruser@xxxxxxxxxxxxxx I'd want an additional condition to be safe on that one.
pjm