A couple things, but they requires your ISP's help. I am not sure why sendmail would think your message was MIME encapsulated. Are you sending "plain text" or HTML messages from your mail user agent? What is "email 2000" anyway?
If sendmail is using smrsh, you will need a link to bulk_mailer in the smrsh directory. This should solve the unknown mailer issue. Also, your outgoing alias needs to be better protected via the aliases file, and the naming convention should be
questioned. You correctly want obscurity in the name, but not to the point that it becomes confusing to the mailer itself. Not only that, but your alias never makes use of bulk_mailer, it just goes out to the list. Resend needs to deliver to the alias
that implements the use of bulk_mailer.
I have a feeling your ISP has not done any majordomo virtual hosting before either. Majordomo is somewhat dependent on alias suffixes. Have you noticed -owner -request -digest -approval -outgoing, etc.? Based on this, your aliases should really be more
along the lines of;
[/etc/aliases]
owner-online-exchange.com-majordomo: real-user@online-exchange.com
#comment owner- prefix is sendmail related, not majordomo#
online-exchange.com-majordomo: "|/usr/local/majordomo/wrapper majordomo -C /path/to/online-exchange/majordomo.cf"
online-exchange.com-majordomo-owner: owner-majordomo@online-exchange.com
owner-online-exchange.com-ezine: real-user@online-exchange.com
online-exchange.come-zine: "|/usr/local/majordomo/wrapper resend -C /path/to/online-exchange/majordomo.cf -l ezine -h online-exchange.com online-exchange.com-ezine-outgoing,nobody"
#comment Your ezine.config should have resend_host = online-exchange.com#
online-exchange.com-ezine-at-owner: owner-ezine@online-exchange.com
online-exchange.com-ezine-outgoing: "|/usr/local/bin/bulk_mailer -maxdomains 1 owner-ezine@online-exchange.com /path/to/online-exchange/lists/ezine"
online-exchange.com-ezine-digest: ezine@online-exchange.com
online-exchange.com-ezine-digest-owner: owner-ezine@online-exchange.com
online-exchange.com-ezine-digest-outgoing: :include:/path/to/online-exchange/lists/ezine-digest
online-exchange.com-ezine-digestify: "|/usr/local/majordomo/wrapper digest -r -C -c path/to/online-exchange/majordomo.cf -l ezine-digest online-exchange.com-ezine-digest-outgoing,nobody"
online-exchange.com-ezine-archive: "|/usr/local/majordomo/wrapper archive2.pl -C path/to/online-exchange/majordomo.cf -f /path/to/online-exchange/archive/ezine/ezine -a -M"
#comment You would add ,online-exchange.com-ezine-digestify,online-exchange.com-ezine-archive in place of ,nobody in online-exchange.come-ezine alias, or outside the bulk_mailer quotes of the online-exchange.come-ezine-outgoing alias to enable archive
and digest.#
online-exchange.com-ezine-request: "|/usr/local/majordomo/wrapper majordomo -C path/to/online-exchange/majordomo.cf -l ezine"
online-exchange.com-ezine-approval: owner-ezine@online-exchange.com
online-exchange.com-ezine-digest-request: "|/usr/local/majordomo/wrapper majordomo -C path/to/online-exchange/majordomo.cf -l ezine-digest"
online-exchange.com-ezine-digest-approval: owner-ezine@online-exchange.com
Please note, that there is "always" a space after the colon in aliases. These are not 100% mandatory but they are 100% recommended. (at least by me they are)
In order for these aliases to work, there would also have to be the following in the virtusertable;
(and sendmail would have to support virtusertable)
[/etc/mail/virtusertable]
majordomo@online-exchange.com online-exchange.com-majordomo
owner-majordomo@online-exchange.com owner-online-exchange.com-majordomo
majordomo-owner@online-exchange.com online-exchange.com-majordomo-owner
ezine@online-exchange.com online-exchange.com-ezine
owner-ezine@online-exchange.com owner-online-exchange.com-ezine
ezine-owner@online-exchange.com online-exchange.com-ezine-owner
ezine-request@online-exchange.com online-exchange.com-ezine-request
ezine-approval@online-exchange.com online-exchange.com-ezine-approval
ezine-outgoing@online-exchange.com unknown
ezine-digest@online-exchange.com online-exchange.com-ezine-digest
ezine-digest-owner@online-exchange.com online-exchange.com-ezine-digest-owner
ezine-digest-request@online-exchange.com online-exchange.com-ezine-digest-request
ezine-digest-approval@online-exchange.com online-exchange.com-ezine-digest-approval
ezine-digest-outgoing@online-exchange.com unknown
White space in this file requires a TAB character, and the "unknown" are so spammers can not bypass your resending alias and send their spam directly to your -outgoing alias. (security?)
And finally, to fully and totally separate each virtual domain from each other, I would put a domainname.tld directory under majordomo with it's own Log and majordomo.cf files, and it's own archives, digests, and lists subdirectories.
[/path/to/majordomo/]
/path/to/majordomo/domainname.tld/
/path/to/majordomo/domainname.tld/Log
/path/to/majordomo/domainname.tld/majordomo.cf
/path/to/majordomo/domainname.tld/archive/
/path/to/majordomo/domainname.tld/archive/listname/
/path/to/majordomo/domainname.tld/archive/listname-digest/
/path/to/majordomo/domainname.tld/digest/
/path/to/majordomo/domainname.tld/digest/listname-digest/
/path/to/majordomo/domainname.tld/lists/
/path/to/majordomo/domainname.tld/lists/listname
/path/to/majordomo/domainname.tld/lists/listname.config
/path/to/majordomo/domainname.tld/lists/listname-digest
/path/to/majordomo/domainname.tld/lists/listname-digest.config
The specific domainname.tld/majordomo.cf would have to reflect these locations, and the individual listname.config files under this virtual domain should all have "sender" and "resend_host" accordingly.
[domainname.tld/majordomo.cf]
$whereami = "domainname.tld";
$datadir = "/path/to/majordomo/domainname.tld";
$listdir = "$datadir/lists";
$filedir = "$datadir/archive";
$filedir_suffix = "";
$digest_work_dir = "$datadir/digest";
Dan Liston
References:
|
|
