While doing some testing today, I noticed in the headers of my digests that
my outgoing aliase for my digests was showing up in the Received: lines.
Naturally, this alarmed me. So I began a day long crusade to locate the
problem and kill it. I wanted to share with the list some interesting this
I found on the way. There is a summary at bottom.
First, if this matters at all, system specs:
Majordomo 1.94.5
RH Linux 6.2
Bulk Mailer 1.9 (according to header Received: lines)
Sendmail 8.9.3 (I think these are the correct numbers)
For my aliases, I found that to prevent the outgoing aliase from showing up
when a digest is normally created by a message that arrives and increases
the number of lines/characters or time past configured limits, I had to use
the following aliase on my undigested test lists outgoing aliase:
test-subfile: "|/usr/sbin/bulk_mailer owner-test@wingscc.com
/var/lib/majordomo/lists/test", "|/usr/lib/majordomo/wrapper digest -r -C
-l test-digest test-digest-subfile,nobody"
The addition of nobody at the very end solved my problem of the outgoing
aliase showing in header Received: lines. But during the process of
figuring this out, I discovered that when a digest is manually forced to be
created, the outgoing aliase returns to the header Received: lines.
I was using the majordomo command, call it form(1) :
mkdigest testpassword
to force the creation. I found that this did not work for some reason. I
will address this in a little while. So I switched to this format, call it
form(2):
mkdigest test-digest-subfile testpassword
This successfully created the digest, but the outgoing aliases did appear
in the header Received: lines. I eventuall switched to the following
format, call it form(3):
mkdigest test-digest-subfile,nobody testpassword
which did not cause the outgoing aliase to show in the header Received: lines.
Back to the issue of using the majordomo command, still calling it form(1):
mkdigest testpassword
I found that if you do not use either form(2) or form(3) and specify the
aliase to which you want the digest to be send, majordomo defaults to the
outgoing aliase of LIST-outgoing form. To make the form(1) command work
again, I had to edit the majordomo script on about line 1095 to read:
$list_outgoing = "$list-subfile,nobody";
My line number may be off, so it is about line 12 of the sub do_mkdigest
subroutine. This changes the default outgoing aliase to -subfile for me,
and includes sending to nobody so that the outgoing aliase does not show in
header Received: lines.
A little long but worth a days work. Here's a summary:
1) On digests aliases, append nobody to list of recipients:
"|/usr/lib/majordomo/wrapper digest -r -C -l test-digest
test-digest-subfile,nobody"
2) When forcing digests, use:
mkdigest test-digest-subfile,nobody testpassword
or edit majordomo script about line 1095, 12 lines down from sub
do_mkdigest:
$list_outgoing = "$list-subfile,nobody";
and use:
mkdigest testpassword
Note, for people that use the MajorCool Web interface, if you use MajorCool
to force the creation of a digest, it will sent the command using the form:
mkdigest testpassword
So you need to make the change in the majordomo script to match your
outgoing aliase if you use something other that the default LIST-outgoing
aliase.
|
|
