Does this happen only to rich text messages, or messages
sent in pure ASCII "text/plain" messages too? If this is
happening to *all* mail passing through the list, examine
your majordomo.cf file's $whereami variable. If you are
not using a static "mydomain.com" value, rather than some
result of a command like `/bin/dnsdomainname`, it is most
likely you are introducing blank lines into the message's
header fields. A blank line signifies the end of headers
and anything after that blank line is displayed as the
body content of the email message. If the problem is only
on rich text messages or HTML MIME content messages, you
could consider "cleaning up" the messages with demime
before majordomo sees them.
Dani Koesterich wrote:
> Thanks! Your advice worked! Everything is working perfectly now,
> except one thing.... Whenever I send a mailing, on the first blank
> line of the mailing, Majordomo sticks in the Sender address, and
> "Precedence: bulk"
> Any idea how to make this not show in the mailings?
> At 02:08 PM 10/2/2003 -0500, you wrote:
>> I would not say you have done anything wrong (other than
>> somehow advertise that users can send to the -list alias
>> of your mailing list). Preventive and Recovery measures
>> are now required.
>> 1. Change the listname alias so that resend delivers to
>> a different address. Something obscure like -yomama is
>> not likely to be guessed easily.
>> 2. Expand the thought above by also preventing the -yomama
>> alias from being revealed in the headers of outgoing mail
>> by your MTA. In the case of sendmail, simply adding another
>> recipient (,nobody) after -yomama will do the trick.
>> 3. Allow sendmail to see and use the listname-yomama alias
>> but prevent it from being used by anyone else. This requires
>> an entry in /etc/mail/virtusertable (on newer sendmails) that
>> looks like this;
>> firstname.lastname@example.org error:nouser User unknown
>> and I might as well complete this response aliases examples;
>> listname: "|/path-to/majordomo/wrapper resend -l listname
>> listname-owner: you,
>> owner-listname: listname-owner
>> listname-yomama: :include:/path-to/majordomo/lists/listname
>> listname-request: "|/path-to/majordomo/wrapper request-answer listname"
>> listname-approval: email@example.com
>> Other aliases available, but the above should be considered the
>> minimum alias requirement for a moderated list with sendmail as
>> the MTA.
>> Of special note are:
>> a. ,nobody in the listname alias
>> This prevents sendmail from showing listname-yomama in
>> the "Received:" headers of outgoing mail.
>> b. the trailing comma on the RHS of listname-owner
>> This prevents sendmail from rewriting "To: listname-owner"
>> as "To: you"
>> c. global replacement of -list with -yomama
>> Recovery method since people already know of listname-list.
>> d. and existance of a listname-request address
>> This address is required by RFC 2142 for all mailing lists.
>> It can be directed to a human or an automated script.
>> Dan Liston
>> Dani Koesterich wrote:
>>> I'm having what seems to be a really 'stupid' problem.
>>> I've set moderate = yes in my config file, and I've set moderator
>>> to my email address. I've also setup all the passwords, and have
>>> set restrict_post to a file I created containing just my email address.
>>> Yet, for some reason, any user on this list can submit messages
>>> to firstname.lastname@example.org and the whole list recevies the
>>> message instantly. This is an announcement list, so I need to configure
>>> my majordomo so that ONLY I can post, and all others are rejected.
>>> What am I doing wrong?