Folks,
I don't know if this one is a bug or a configuration error on my part.
It seems very easy to have digest generate messages with bogus header
addresses if the -digest.config variables reply_to, sender, and resend_host
are not set correctly. I tried a number of combinations of values for these
parameters on my test list. Unfortunately I cannot give you an exact statement
of what causes the problem. But I can show you an example. With my
test-list-digest configured with the following:
reply_to =
resend_host = Dartmouth.EDU
sender =
the digest message that was generated had these headers:
Date: Mon, 4 Nov 1996 12:16:28 -0500 (EST)
Message-Id: <199611041716.MAA24046@dartvax.dartmouth.edu>
From: @Dartmouth.EDU (test-list-digest)
To: test-list-digest@Dartmouth.EDU
Subject: test-list-digest V1 #23
Sender: @Dartmouth.EDU
Errors-To: @Dartmouth.EDU
Note the errors in the From, Sender, and Errors-to headers.
I have other combinations producing other invalid headers. I can send them if
you want them. In general terms, many combinations of reply_to and sender
(either blank, a "localpart" only, or "localpart@domain) and resend_host
(blank or with a "domain") generated invalid headers. What *did* seem to work
was specifying a "localpart" only for reply_to and sender and specifying a
"domain" for resend_host. And yes, $whoami is defined in majordomo.cf.
Steve Campbell
Dartmouth College
|
|
