Mailing List Problem - Failed Delivery

Mailing List Problem - Failed Delivery **Need Exim Expert's Eyes!

Hello,

I'm the admin of a hosting server with Directadmin on it. I've found out that mailing lists aren't working at all, and I've tested it to figure out why.

I made a list called mylist (@deezsites.com), and it created successfully. Everything appears to be well set up. When I send an email to [email protected], it's fine. But it doesn't send out to the members. So I went in and checked the email of the DirectAdmin signup (admin), and I got:

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:

[email protected]

So it looks like it's not creating the mylist-out mail user...here's the full output of the message:

------ This is a copy of the message, including all the headers. ------

Return-path: <[email protected]>
Received: from mail by 35107.ds.nac.net with spam-scanned (Exim 4.24)
id 1BjiNH-000329-Nl
for [email protected]; Sun, 11 Jul 2004 13:44:30 -0400
Received: from majordomo by 35107.ds.nac.net with local (Exim 4.24)
id 1BjiNH-000326-MM
for [email protected]; Sun, 11 Jul 2004 13:44:27 -0400
Received: from mail by 35107.ds.nac.net with spam-scanned (Exim 4.24)
id 1BjiNE-00031x-Cd
for [email protected]; Sun, 11 Jul 2004 13:44:27 -0400
Received: from [65.213.231.10] (helo=neomail07.traderonline.com)
by 35107.ds.nac.net with esmtp (TLSv1:AES256-SHA:256)
(Exim 4.24)
id 1BjiNE-00031u-A7
for [email protected]; Sun, 11 Jul 2004 13:44:24 -0400
Received: from stevedgz9qjj1g (ip68-225-36-16.hr.hr.cox.net [68.225.36.16])
by neomail07.traderonline.com (8.12.10/8.12.8) with SMTP id i6BHiuaB016921
for <[email protected]>; Sun, 11 Jul 2004 13:44:56 -0400
Message-ID: <003e01c4676e$c7d7ab00$1024e144@stevedgz9qjj1g>
From: "Steven Karam" <[email protected]>
To: <[email protected]>
Subject: Fw: test
Date: Sun, 11 Jul 2004 13:44:56 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_003B_01C4674D.40A95B40"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2720.3000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2739.300
Sender: [email protected]
Precedence: bulk
Reply-To: [email protected]

This is a multi-part message in MIME format.

------=_NextPart_000_003B_01C4674D.40A95B40
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


HELP!

Anyone, please? I have users getting pretty upset...

Take a look at the exim logs (/var/log/exim/mainlog and /var/log/exim/reject) to see if you see the error there. The other thing to check for is the existance of [email protected] in the /etc/virtual/deezsites.com/majordpmo/private.aliases file. Also that this file is owned by majordomo and group is mail so it should look similar to:

-rw-r----- 1 majordomo mail 893 Jan 15 13:34 private.aliases

Click to expand...

Other than that, the only other way I know to help is start putting debug commands in the majrodomo code.

Here's mainlog:

2004-07-13 08:53:30 1BkMmo-0006X5-Bw <= [email protected] H=(neomail07.traderonline.com) [65.213.231.10] P=esmtp X=TLSv1:AES256-SHA:256 S=1524 id=001c01c468d8$7a0eee40$de02020a@karam
2004-07-13 08:53:33 1BkMmo-0006X8-FT <= [email protected] U=mail P=spam-scanned S=1674 id=001c01c468d8$7a0eee40$de02020a@karam
2004-07-13 08:53:33 1BkMmr-0006XH-TF <= [email protected] U=majordomo P=local S=1910 id=001c01c468d8$7a0eee40$de02020a@karam
2004-07-13 08:53:33 1BkMmo-0006X8-FT => |/etc/virtual/majordomo/wrapper resend -C /etc/virtual/deezsites.com/majordomo/majordomo.cf -l mylist -h deezsites.com -f owner-mylist [email protected] <[email protected]> R=majordomo_aliases T=majordomo_pipe
2004-07-13 08:53:33 1BkMmo-0006X8-FT Completed
2004-07-13 08:53:33 1BkMmo-0006X5-Bw => mylist <[email protected]> R=spamcheck_director T=spamcheck
2004-07-13 08:53:33 1BkMmo-0006X5-Bw Completed
2004-07-13 08:53:36 1BkMmr-0006XK-Us <= [email protected] U=mail P=spam-scanned S=2064 id=001c01c468d8$7a0eee40$de02020a@karam
2004-07-13 08:53:36 1BkMmr-0006XK-Us ** [email protected] R=virtual_aliases:
2004-07-13 08:53:37 1BkMmv-0006XQ-0Q <= <> R=1BkMmr-0006XK-Us U=mail P=local S=2886
2004-07-13 08:53:37 1BkMmr-0006XK-Us Completed
2004-07-13 08:53:37 1BkMmr-0006XH-TF => mylist-out <[email protected]> R=spamcheck_director T=spamcheck
2004-07-13 08:53:37 1BkMmr-0006XH-TF Completed
2004-07-13 08:53:40 1BkMmv-0006XT-1s <= <> U=mail P=spam-scanned S=3042 [email protected]
2004-07-13 08:53:40 1BkMmv-0006XT-1s => admin <[email protected]> R=localuser T=local_delivery
2004-07-13 08:53:40 1BkMmv-0006XT-1s Completed
2004-07-13 08:53:40 1BkMmv-0006XQ-0Q => owner-mylist <[email protected]> R=spamcheck_director T=spamcheck
2004-07-13 08:53:40 1BkMmv-0006XQ-0Q Completed

Here's private aliases:

mylist-digest-outgoing: :include:/etc/virtual/deezsites.com/majordomo/lists/mylist-digest
mylist-out: "|/etc/virtual/majordomo/wrapper digest -r -C -c /etc/virtual/deezsites.com/majordomo/majordomo.cf -l mylist-digest mylist-digest-outgoing",:include:/etc/virtual/deezsites.com/majordomo/lists/mylist
test-digest-outgoing: :include:/etc/virtual/deezsites.com/majordomo/lists/test-digest
test-out: "|/etc/virtual/majordomo/wrapper digest -r -C -c /etc/virtual/deezsites.com/majordomo/majordomo.cf -l test-digest test-digest-outgoing",:include:/etc/virtual/deezsites.com/majordomo/lists/test

But here's the result:

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

[email protected]


I'm running:

Compiled for Redhat 9.0
Server Version 1.22.2

Hello,

Try checking the majordomo logs:
/etc/virtual/majordomo/Log

John

Hi John,

That file doesn't exist.

I think I see the problem, I am no exim expert, but it appears that when you turn on spam scanning, it sets the received_protocol to spam-scanned. There is a condition in the exim.conf in the majordomo_private router that is looking for the received_protocol to be local. Since the spam scanner changed it from local to spam-scanned it will never meet this condition and continue down to the other routers. I believe an or condition in the exim.conf needs to be written so that it will accept spam-scanned or local, I believe something like this may work as the condition for majordomo_private, but perhaps an exim expert would double check it:

Thanks, it worked!!!