Koozali.org: home of the SME Server

Mailman contrib?

bmoore

latest version and bounce processing
« Reply #30 on: February 06, 2007, 01:30:36 PM »
Greetings.  Not sure if this is a real bug so I don't want to raise one yet.  Mailman seems to be working well on sme 7.1 with latest rpms from sme-dev.  However, I am getting delivery failures from the bounce processor. I don't think I have mis-configured anything but not sure.  I get lots of  notices to post master that bounce notices are failing with local aliases not existing
I think there may be an error in this latest version but want to be sure I didn't do something before I raise a real bug.

see below
Hi. This is the qmail-send program at screenreview.org.
I tried to deliver a bounce message to this address, but the bounce bounced!
<
buddys-dogscoop-bounces+323401cb6602df68236929ce14ced54e131dc20e@server.screenreview.org
>:
Sorry, no mailbox here by that name. (#5.1.1)
--- Below this line is the original bounce.
Return-Path: <>
Received: (qmail 26013 invoked by alias); 6 Feb 2007 09:55:11 -0000
Delivered-To:
alias-localdelivery-buddys-dogscoop-bounces+323401cb6602df68236929ce14ced54e131dc20e@screenreview.org
Received: (qmail 26010 invoked for bounce); 6 Feb 2007 09:55:11 -0000
Date: 6 Feb 2007 09:55:11 -0000
From:
MAILER-DAEMON@screenreview.org
To:
buddys-dogscoop-bounces+323401cb6602df68236929ce14ced54e131dc20e@screenreview.org
Subject: failure notice
Hi. This is the qmail-send program at screenreview.org.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<
mcrogers1@verizon.net
>:
206.46.232.11 does not like recipient.
Remote host said: 550 4.2.1 mailbox temporarily disabled:
mcrogers1@verizon.net
Giving up on 206.46.232.11.
--- Below this line is a copy of the message.

bmoore

follow up on bounce processing
« Reply #31 on: March 08, 2007, 03:36:03 PM »
Okay, I will turn this into a bug soon if I can't figure it out.  I have searched the mailman faq the mailman lists and here but haven't gotten much further with this one.

I have the following installed
mailman-2.1.5.1-34.0.el4.sme.i386.rpm
smeserver-mailman-1.3.0-15.el4.sme.noarch.rpm.  I still get delivery failures from the bounce processor.

Code: [Select]

Hi. This is the qmail-send program at screenreview.org.
I tried to deliver a bounce message to this address, but the bounce bounced!
<
juno-l-bounces+7343c8858aefc1102f5c5efbcee8782f1ffff542@server.screenreview.org
>:
Sorry, no mailbox here by that name. (#5.1.1)
--- Below this line is the original bounce.
Return-Path: <>
Received: (qmail 24590 invoked by alias); 8 Mar 2007 13:44:18 -0000
Delivered-To:
alias-localdelivery-juno-l-bounces+7343c8858aefc1102f5c5efbcee8782f1ffff542@screenreview.org
Received: (qmail 24587 invoked for bounce); 8 Mar 2007 13:44:18 -0000
Date: 8 Mar 2007 13:44:18 -0000
From:
MAILER-DAEMON@screenreview.org
To:
juno-l-bounces+7343c8858aefc1102f5c5efbcee8782f1ffff542@screenreview.org
Subject: failure notice
Hi. This is the qmail-send program at screenreview.org.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<
Luvlabpups@aol.com
>:
205.188.158.121 does not like recipient.
Remote host said: 550 We would love to have gotten this email to
luvlabpups@aim.com
. But, your recipient never logged onto their free AIM Mail account. Please contact
them and let them know that they're missing out on all the super features offered
by AIM Mail. And by the way, they're also missing out on your email. Thanks.
Giving up on 205.188.158.121.
--- Below this line is a copy of the message.
Return-Path: <
juno-l-bounces+7343c8858aefc1102f5c5efbcee8782f1ffff542@screenreview.org
>
Received: (qmail 24584 invoked by uid 453); 8 Mar 2007 13:44:13 -0000
Received: from localhost (HELO server.screenreview.org) (127.0.0.1)
    by screenreview.org (qpsmtpd/0.32) with ESMTP; Thu, 08 Mar 2007 08:44:13 -0500
Subject: Juno-l mailing list probe message
From:
juno-l-bounces+7343c8858aefc1102f5c5efbcee8782f1ffff542@screenreview.org
To:
Luvlabpups@aol.com
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1729239141=="
Message-ID: <
mailman.6.1173361451.5407.juno-l@screenreview.org
>
Date: Thu, 08 Mar 2007 08:44:11 -0500
Precedence: bulk
X-BeenThere:
juno-l@screenreview.org
X-Mailman-Version: 2.1.5
List-Id: "Juno-l is A supportive communications forum for Guide Dog users,
and Puppy Raisers. Founded and supported by Guiding Eyes for the Blind
Graduates. " <juno-l.screenreview.org>
X-List-Administrivia: yes
Sender:
juno-l-bounces+7343c8858aefc1102f5c5efbcee8782f1ffff542@screenreview.org
Errors-To:
juno-l-bounces+7343c8858aefc1102f5c5efbcee8782f1ffff542@screenreview.org
--===============1729239141==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
This is a probe message.  You can ignore this message.
The Juno-l mailing list has received a number of bounces from you,
indicating that there may be a problem delivering messages to
Luvlabpups@aol.com
. A bounce sample is attached below.  Please examine
this message to make sure there are no problems with your email
address.  You may want to check with your mail administrator for more
help.
If you are reading this, you don't need to do anything to remain an
enabled member of the mailing list.  If this message had bounced, you
would not be reading it, and your membership would have been disabled.
Normally when you are disabled, you receive occasional messages asking
you to re-enable your subscription.
You can also visit your membership page at
http://www.screenreview.org/mailman/options/juno-l/luvlabpups%40aol.com
On your membership page, you can change various delivery options such
as your email address and whether you get digests or not.  As a
reminder, your membership password is
    poceum
If you have any questions or problems, you can contact the list owner
at
juno-l-owner@screenreview.org
--===============1729239141==
Content-Type: message/rfc822
MIME-Version: 1.0
Return-Path: <>
Delivered-To:
juno-l-bounces@server.screenreview.org
Received: (qmail 23737 invoked by alias); 8 Mar 2007 13:37:43 -0000
Delivered-To:
alias-localdelivery-juno-l-bounces@screenreview.org
Received: (qmail 23698 invoked for bounce); 8 Mar 2007 13:37:35 -0000
Date: 8 Mar 2007 13:37:35 -0000
From:
MAILER-DAEMON@screenreview.org
To:
juno-l-bounces@screenreview.org
Subject: failure notice
Hi. This is the qmail-send program at screenreview.org.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<
Luvlabpups@aol.com
>:
205.188.155.89 does not like recipient.
Remote host said: 550 We would love to have gotten this email to
luvlabpups@aim.com
. But, your recipient never logged onto their free AIM Mail account. Please contact
them and let them know that they're missing out on all the super features offered
by AIM Mail. And by the way, they're also missing out on your email. Thanks.
Giving up on 205.188.155.89.
<
waterloo26@yahoo.com
>:
216.39.53.2 failed after I sent the message.
Remote host said: 554 delivery error: dd Sorry your message to
waterloo26@yahoo.com
 cannot be delivered. This account has been disabled or discontinued [#102]. - mta216.mail.re4.yahoo.com
--- Below this line is a copy of the message.

These messages should increment a bounce score automatically and not be returned to post master but they aren't for some reason. I suspect that the system is not dealing with the temporary aliases correctly but I can't for the life of me figure out how to fix it.

thanks.
Brian.

Offline dmay

  • *
  • 450
  • +0/-0
    • http://myezserver.com
Re: follow up on bounce processing
« Reply #32 on: March 08, 2007, 09:09:21 PM »
Quote from: "bmoore"
mailman-2.1.5.1-34.0.el4.sme.i386.rpm

Also note 2.1.5 is circa 2004. The current stable version is 2.1.9, released on 12-Sep-2006. Before you issue bug reports on an old release, I'd suggest you contact Gordon and see if he is contemplating updating the contrib.

Darrell

Offline kruhm

  • *
  • 680
  • +0/-0
Mailman contrib?
« Reply #33 on: March 11, 2007, 06:31:28 AM »
Do you have bounce_processing turned on or off?

bmoore

bounce processing
« Reply #34 on: March 13, 2007, 12:24:43 PM »
HI.  It is on for all lists.  I would attempt to upgrade to the current stable release of mailman but not sure what it might break in smeserver-mailman.
Brian

tiziano

problem
« Reply #35 on: March 21, 2007, 11:53:42 AM »
hello I have mailman lastest version but

for viewer archive I don't have permision
why ?


http://iw7efc.dyndns.org/mailman/public/hamradio/

Offline chrismaltby

  • 6
  • +0/-0
Re: Mailman contrib?
« Reply #36 on: September 25, 2007, 03:11:46 PM »


I'll post it agian:
Code: [Select]
-create new virtualdomain lists.yourdomain.com

I'm sure there's a simple answer to this question but it's stumping me right now. How do I create a new virtualdomain using smeserver tools. I can make a domain based pseudonym, or put my own custom template in /var/qmail/control/{rcpthosts,virtualdomains}, but nothing in my 7.2 install seems to match the instruction quoted above...
« Last Edit: September 25, 2007, 03:13:25 PM by chrismaltby »

Offline mmccarn

  • *
  • 2,626
  • +10/-0
Re: Mailman contrib?
« Reply #37 on: September 25, 2007, 03:32:50 PM »
I *think* those instructions are telling you to use server-manager::Configuration::Domains::Add domain to create a new "domain".

These were refered to as 'virtual domains' at one point - I think because the main fallout from adding a domain in server-manager was the creation of various 'VirtualHost' sections in /etc/httpd/conf/httpd.conf, modification of qmail's 'virtualdomains' configuration, etc...

Offline chrismaltby

  • 6
  • +0/-0
Re: Mailman contrib?
« Reply #38 on: September 25, 2007, 03:48:50 PM »
Ah.. well I think it's just that it doesn't work the way I expected. Instead of creating a qmail virtualhost entry to forward the entire domain to the mailman account, it creates special mailmanlist account entries, one per list, and uses them to expand qmail user name lookups. That means that list names can't conflict with user names and are accessible from all virtual host names in use for the server. Another way it could be done (better) would be to put listname@listdomain:mailman entries into qmail's virtualhost file to limit the list's email accessibility to its defined virtual host.

<aside>Isn't qmail wonderful... always lots of ways to solve any problem, and never any consensus on which way is best...</aside>