I just brought this topic up a couple of days ago. The inconvenience is
being caused by the message going through resend. What I have done to
temporarily "fix" the problem is to alias listname to listname-outgoing
without going through resend. One of my aliases looks something like
listname: "|/u1/programs/majordomo/wrapper resend -l listname listname-outgoing"
This takes away all of the benifits of resend, but eliminates duplicate
messages. You will still be able to use commands through majordomo to
maintain the lists. If your list is completely internal, you can look
into using procmail to keep a message cache and delete duplicate messages
when received. Check this month's archives for the recent discussions.
On Mon, 10 Aug 1998 email@example.com wrote:
>Before implementing majordomo, if I sent email to two aliases and a user
>happened to be a member of both, sendmail would detect this and only send
>that user one copy of the message.
>However, now that majordomo is expanding aliases via the :include:
>mechanism, duplicates are resulting.
>We also do a lot of sub-listing in our aliases. We may have a user in
>the vlis alias, the compiler alias, and the layout alias. Then we may
>create an alias called engrs which is comprised of vlsi,debug,and layout.
>This is causing triplicates and quadripicates (new word 8^)).
>Is there a workaround for this problem? If not, we'll have to go back
>to maintaining our alias file manually because the user community is
>not going to accept all this duplication of messages.
>J.C. Webber III