I'm not sure how to deal with this problem:
A request comes into a smartlist-managed request alias, where the
"From:" headers are unqualified, but the address on the "subscribe
ADDRESS" command *is* fully-qualified.
Our mailer, on the assumption that "plain", unqualified names can only
be local, qualifies the names with our default domain. Thus, in the
request header below, we see "email@example.com", when, in fact, the
original request had "ats@hubert", without any domain name.
Since our mailer is doing the qualifying, there is no way SmartList, or
any other list managing software, can know that both the From: or From
address is wrong, unless they compare them against the address in the
Message-Id: (if there is one).
Does anyone know of an automatic heuristic to deal with these kinds of
problems, or should I just let 'em bounce?
>From firstname.lastname@example.org Tue Jun 13 19:58:02 1995
>Received: from hubert.wustl.edu (eliot42.wustl.edu) by hub.ucsb.edu; id AA29354
> sendmail 4.1/UCSB-2.1-sun
> Tue, 13 Jun 95 19:58:02 PDT for flist hyperbole-request
>Received: from localhost (ats@localhost) by hubert.wustl.edu (8.6.12/8.6.12) with SMTP id VAA13670 for <email@example.com>; Tue, 13 Jun 1995 21:57:18 -0500
>X-Authentication-Warning: hubert.wustl.edu: Host localhost didn't use HELO protocol
>Subject: Subscribe <firstname.lastname@example.org> (Alan Shutko
>Comments: Hyperbole mail buttons accepted, v03.18.13.
>Date: Tue, 13 Jun 1995 21:57:12 -0500
>From: Alan Shutko <email@example.com>
> hyperbole-announce - Hyperbole announcements only