Thanks Dan -
the following.../etc/aliases has...
post-list_name: "|/home/majordomo/majordomo-1.94.4/wrapper resend
@/home/majordomo/resend/list_name"
In /home/majordomo/resend/list_name, I have the following...
-l list_name list_name-1134,nobody
In /etc/aliases, the list_name-1134 looks like ...
energy-1134: :include:/home/majordomo/majordomo-1.94.4/lists/list_name
In checking the mail received (headers) you are correct. I do see the email
address of the individual after the "From:". I also see under "Received:" the
"post-list_name@hostname". Put these together, someone can keep
the server busy. The "nobody" is there. Could there be something else
that causes an "autoreply" to "re-post" for duplicate messages?
Will Bryant (see thread) mentioned "Approved Posting via password". I'm
going to check this out. New to sendmail & Majordomo.
Thanks for the tips.
Steve Magee
Thanks
"D. Liston" wrote:
> Danger Will Robinson! Danger! (quote from robot on "Lost in Space")
>
> Your resend address does not have ,nobody in your delivery argument. This means
> sendmail will advertise your -outgoing address in the "Received: " headers.
>
> Steve Magee wrote:
> >
> > I just sent out a posting to 8,000 on Jan 24, 1600 hrs. Going smoothly until
> > this morning when I received a duplicate copy (included was a duplicate
> > message_footer). Than another came this afternoon. This problem was solved
> > months ago by putting in a line from the message_footer into the taboo_body.
> > Somehow, the taboo_body (from the config file) was left out when I created the
> > 'list'.
>
> You can automate this for each new list by modifying your config_parse.pl script.
> >
> > My knowledge of sendmail is less then a tip of an iceberg. You (Dan), most likely
> > are correct but what do you think of the scenario of an auto reply 're-posting'
> > the
> > message back to majordomo and the posting starts all over again? This is how the
> > second "message_footer" is appended to the first posting (with the
> > message_footer).
>
> Possibly. The same could happen if the message bounced, and the MTA is brain dead.
> >
> > With the software of today, could somebody grab the "From" and "To" lines and
> > create an e-mail that looks like someone that is the moderator (access control)
> > list?
> > In other words, fake Majordomo out. I have the address of the one that we show
> > sending it back to us. This individual has an autoreply turned on. I'm going to
> > test
> > the address out (while they are on vacation) with just 2 in the list and see what
> > happens.
>
> If someone posts directly to your -outgoing alias, the message would not get the
> second footer appended. If your taboo_* filters are working, the message should
> be BOUNCEd before a second footer has a chance to get appended. An autoresponder
> that includes an entire message body with no additional text added is also brain
> dead in my opinion. This could be someone that did not know how to unsubscribe,
> so they are becoming obnoxious enough to have the list-owner remove the address.
>
> Dan Liston
> >
> > Thanks
> > Steve Magee
> >
> > Dan Liston wrote:
> >
> > > Anthony Banez wrote:
> > > >
> > > > Part 1.1Type: Plain Text (text/plain)
> > >
> > > Great! I get to go cut and paste again because the
> > > message was an attachment instead of part of the body.
> > > It would also be nice if you would use the SUBJECT: field
> > > in your messages.
> > >
> > > > This a a sample list on my /etc/aliases
> > > >
> > > > # MAJORDOMO Config
> > > > majordomo: "|/usr/local/majordomo-1.94.5/wrapper majordomo"
> > > > owner-majordomo: tekla
> > > > majordomo-owner: tekla
> > > >
> > > > # Mabuhay List
> > > > mabuhay: "|/usr/local/majordomo-1.94.5/wrapper resend -l mabuhay
> > > > mabuhay-list"
> > > > mabuhay-list: :include:/usr/local/majordomo-1.94.5/lists/mabuhay
> > > > owner-mabuhay: mabuhay@summitmedia.com.ph
> > > > mabuhay-owner: mabuhay@summitmedia.com.ph
> > > > mabuhay-approval: mabuhay@summitmedia.com.ph
> > > > mabuhay-request: "|/usr/local/majordomo-1.94.5/wrapper majordomo -l mabuhay"
> > > >
> > > > # Newsletters (changed from Majordomo)
> > > > newsletters: "|/usr/local/majordomo-1.94.5/wrapper majordomo"
> > >
> > > Why not just say ...
> > > newsletters: majordomo,
> > >
> > > >
> > > > Duplicate emails are rejected upon subscription so i think its on the mail
> > > > queue. The recieved mails are totally the same. Just yesterday we send a
> > >
> > > Do you mean duplicate email-addresses? True, but how can you tell the
> > > difference between dliston@netscape.com, danliston@netscape.net, and
> > > dan_liston@hotmail.com? Now, if all three addresses are subscribed to
> > > your list, and the dliston@netscape.com address has an auto-forward set
> > > up to go to both of the other addresses, it would look like 2 out of the
> > > three addresses got duplicates.
> > >
> > > > dispatch to a list of 100+ members and i got 3 dupicate emails from the
> > > > list. On other occasions i get 2 duplicate mails on a dispatch for 30,000+
> > > > list members . Is this due to the mail queue (Time before giving up = 2h)
> > > > and (time before sending warning = 4h) . Should i increase the time?
> > >
> > > You should consider using bulk_mailer, or a newer version of sendmail that
> > > lets you utilize multiple queues. Until that time, I would recommend
> > > stretching out your queue runs. If sendmail is started with a command like
> > > sendmail -bd -q30m
> > > I would try setting it to
> > > sendmail -bd -q2h
> > >
> > > To increase your delivery performance, you should sort your lists by domain
> > > remove any "bad" addresses as soon as possible, and strip comments out of
> > > the list.
> > >
> > > Dan Liston
Follow-Ups:
References:
|
|
