RE: [cobalt-users] Help configuring Bulk_mailer on Cobalt server

[Milum Software <shayes@xxxxxxxxxxxxxxxxx>]

At 05:59 PM 07/02/02 -0400, you wrote:
> -----Original Message-----
> From: Milum Software
> To: cobalt-users@xxxxxxxxxxxxxxx
> Sent: 7/2/02 5:32 PM
> Subject: [cobalt-users] Help configuring Bulk_mailer on Cobalt server
>
> I have searched through the archive and did not find any special
> information related to using Bulk_mailer on my raq so I have a question
> and
> hope someone on the list has had the same problem.
>
> I'm running a Raq4 and attempting to configure bulk_mailer 1.13 to speed
> up
> a 9k list. I downloaded and ran the make and Install files and all looks
>
> well with the build of Bulk_Mailer (BM). I seem to be having problems
> adding BM to my aliases.majordomo. When I make what I believe is the
> correct change and then run newaliases all seems fine until I send email
> to
> the list. When I send email to the list I get no response and I see
> nothing
> in the maillog and nothing in mailq. If someone has experience setting
> up
> bulk_mailer I would love to hear how you where able to get it to work.
>
> Majordomo has the following as the correct aliases setting:
> sample-outgoing: |"/path/to/bulk_mailer owner-sample@xxxxxxxxx
> /path/to/lists/sample"
>
> One question is what goes in the location "owner-sample@xxxxxxxxx"
>
> My Cobalt servers has a slightly different aliases setting:(Modified to
> hide true info)
> officetrack_site3-list:
> :include:/usr/local/majordomo/www.my.com/lists/officetrack
>
> Any help would be greatly appreciated.
> --------------------------
>
> The "usual" convention for an '-outgoing" alias is that
> it is the list of addresses to which the mail will be
> distributed. I've always seen "-outgoing" aliases defined
> in terms of an ":include" not as a pipe.
> I've never seen an "-outgoing" type alias
> used for the receiving side of a mail-list alias, i.e.
> the type of alias defined as a pipe.
>
> In most cases, I've seen mailing lists set up with two
> aliases, one for the receiving side which for majordomo
> is usually in the form of:
>
> mylist: "/usr/local/majordomo/wrapper resend -l listname
> listname-outgoing
>
> And then for the distribution list:
>
> listname-outgoing: :include listname,nobody
>
> The first alias defines the receiving side, the second
> defines the distribution list.
>
> You don't appear to be using majordomo but rather bulk-mailer
> for the receiving side. My WAG is that the first parameter
> to bulk-mailer is the From: header value.

Joel,

I also found some extra info from deja.com that a list manager submitted. 
The following is his version of the aliases that uses resend with 
Bulk_mailier to get the best of Majordomo which is what I'm attempting to do.

His Instructions follow:

Here's a real life example with the list name changed to protect the guilty.

Resend only:
mylist: "|/usr/local/majordomo/wrapper resend -l mylist mylist-list"
mylist-list: :include:/usr/local/majordomo/Lists/mylist
mylist-request: "|/usr/local/majordomo/wrapper request-answer mylist"
owner-mylist: mylist-approval
mylist-owner: mylist-approval
mylist-approval: goodguy@xxxxxxxx

Resend + bulk_mailer:
mylist: "|/usr/local/majordomo/wrapper resend -l mylist mylist-list"
mylist-list: "|/usr/local/majordomo/bulk_mailer owner-mylist 
/usr/local/majordomo/Lists/mylist"
mylist-request: "|/usr/local/majordomo/wrapper request-answer mylist"
owner-mylist: mylist-approval
mylist-owner: mylist-approval
mylist-approval: goodguy@xxxxxxxx

Just replacing the include with a call to bulk_mailer should do the trick.

End of his posting

Do you have any Ideas here?


--
Best Regards,

Scott Hayes
Milum Software
800-257-2120 Sales
512-469-2967 Support
http://www.milum.com