This bug was supposed to be fixed in 1.94.5. If this is the
version you are running, and it is still happening, I would
post to the majordomo-workers list and ask for a solution.
Personally, any lines in my mail index without subjects or the
subject is blank get automatically deleted without being read.
I am not one of the developers/workers, but I understand perl
to the point of occasionally being able to offer fixes or even
a patch, but this one is outside my level of expertise.
Dan Liston
Thomas Hucke wrote:
>
> Dan, thank you very much for your answer.
>
> `subject_prefix = [$LIST]` works only if you write anything else into the
> Subject: field. If you let it blank it won't work. Do you have any idea why ?
>
> With best regards - Thomas.
>
> >===== Original Message From Dan Liston <dliston@netscape.com> =====
> >-
> >-FROM:, SUBJECT:, and DATE: are the default column headings in most mail
> >reader clients. Using a quick glance from inside your mail client as to
> >who sent a message that you received is still accurate, even though the
> >message was relayed through majordomo to get to you.
> >
> >If you want a "fast" method of identifying messages that have been
> >relayed
> >through a mailing list, I would suggest using mail filtering
> >capabilities
> >in outlook, eudora, netscape, or other mail clients to put these
> >messages
> >into folders. This can also be done in unix for pine, elm, mutt, etc.
> >by
> >using procmail to filter your messages.
> >
> >For example, I use netscape messenger as my mail client. I have a
> >folder
> >called majordomo, and a message filter which matches on "sender contains
> >greatcircle.com". I could have narrowed this to "sender contains
> >majordomo-users-owner@greatcircle.com", but I am also subscribed to the
> >workers and announce lists for majordomo which also come from
> >greatcircle.com, and I do not receive any other correspondence from that
> >domain. Now, all my majordomo related messages are conveniently grouped
> >together in their own mail folder, and
> >I always know that if/when I open that folder, it will contain messages
> >from greatcirlce.com.
> >
> >If you wanted to modify the email headers to fake the origination of
> >messages to
> >listname@listhost.domain.edu, you would basically be creating an
> >anonymous remailer. Your other choice, since "subject:" can be scanned
> >with a quick glance
> >too, is to add a subject prefix to your majordomo lists. This can be
> >accomplished
> >with `subject_prefix = [$LIST]` in your listname.config file.
> >
> >I cannot speak for violation of RFCs by other lists, but technically,
> >there is no
> >way a message can be "from:" a list. They are from their original
> >author, and
> >relayed by majordomo (or other list software) to the subscribers of the
> >list.
> >
> >Hopefully, the prefix suggestion will solve your problem.
> >
> >Dan Liston
> >
> >Thomas Hucke wrote:
> >>
> >> Dan,
> >> searching for a solution of a problem with the From: field I found your
> >> message (see above). The problem is taht many users here at the university
> are
> >> subscribed to several lists and want to be able, when they open their INBOX
> ,
> >> to identify inmediatly from which list people are sending mail.When I open
> my
> >> e-mail reader, I get a large list of e-mails and the FROM: field displays
> just
> >> the personal e-mail address of the senders. In order to know from which
> list
> >> the mail is coming, I have to open the mail and read the To: field. It
> would
> >> be much better, if the the Incoming Mail list displays the name of the list
> >> instead of the users name.
> >> You say that RFC822 do not permit modify the From field, but I am member of
> >> different mail lists and the mail I receive from them shows the lisname as
> >> sender address.
> >>
> >> What can we do in order to identify rapidly the name of the list where the
> >> e-mail is coming from ?
> >>
> >> Sorry for bothering you - Thomas.
> >>
> >> ************************************
> >> I am afraid that the best majordomo can do in this regard is to set the
> >> reply-to address back to the address of the list itself (unless you want
> >> to modify the perl code). RFCs are very specific about not changing any
> >> existing email header information, but you are allowed to add to them.
> >>
> >> When a list's reply-to address is the list itself, it does not matter
> >> whether I hit reply or reply-all from netscape, the message is addressed
> >> back to the list. (but the senders "From: " line still appears in the
> >> header.
> >>
> >> Majordomo does have a configuration option called message_fronter which
> >> can be used with a $SENDER token to put the senders address in the top of
> >> the message body.
> >>
> >> I don't think this gives you exactly what you requested, but it is close.
> >>
> >> Dan Liston
> >>
> >> ----------------------------------------------------
> >> Ing. Thomas Hucke
> >> Programa de Telecomunicaciones PROTEL
> >> Universidad Autonoma de Baja California Sur
> >> La Paz 23080 BCS. / Mexico
> >> e-mail: hucke@uabcs.mx Tel/Fax: (112)80741
>
> ----------------------------------------------------
> Ing. Thomas Hucke
> Programa de Telecomunicaciones PROTEL
> Universidad Autonoma de Baja California Sur
> La Paz 23080 BCS. / Mexico
> e-mail: hucke@uabcs.mx Tel/Fax: (112)80741
Follow-Ups:
References:
|
|
