[Raw Msg Headers][Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: zmailer too restrictive

To: Sven Goldt <goldt@informatik.tu-muenchen.de>
Subject: Re: zmailer too restrictive
From: "Erik E. Fair" (Timekeeper) <fair@clock.org>
Date: Wed, 15 Oct 1997 02:16:47 -0700
Cc: Tom <tom@sdf.com>, Matti Aarnio <mea@nic.funet.fi>, zmailer@nic.funet.fi
Fake-Sender: fair@clock.org
In-reply-to: <Pine.SOL.3.95q.971015104305.18648A-100000@sunrbg6.informatik.tu-muenchen.de>
References: <Pine.BSF.3.95q.971014155701.19295A-100000@misery.sdf.com>
Sender: "Erik E. Fair" <fair@clock.org>

The catch-22 is that in order to identify the local-part (the thing
it's not supposed to mess with when the domain is not the local
host), zmailer has to parse the From: line, as specified in the
BNF on Appendix D of RFC822, as modified by RFC1123.

Which includes parsing the local-part for syntactic correctness,
even if not for validity.

Ooops.

This is why there is a specification for the local-part, and why,
when certain characters occurr in the local-part, it MUST be quoted.

	Erik <fair@clock.org>

Follow-Ups:
- Re: zmailer too restrictive
  - From: Tom <tom@sdf.com> (Wed, 15 Oct 1997 20:21:51 +0300)

References:
- Re: zmailer too restrictive
  - From: Tom <tom@sdf.com>
- Re: zmailer too restrictive
  - From: Sven Goldt <goldt@informatik.tu-muenchen.de>

Prev by Date: Re: zmailer too restrictive
Next by Date: No recipients in transport file
Prev by thread: Re: zmailer too restrictive
Next by thread: Re: zmailer too restrictive
Index(es):
- Date
- Thread