Christopher Adams | 4 May 01:50 2016
Picon

Problems using Postfix with Mailman

Hello all,

I previously posted a message about a server "migration" of Mailman to a
new CentOS 7 server. It actually is a rebuild and I will be trying to
restore list info from backup.

Anyway, I have Mailman installed and can access web pages and create lists.
I am using Postfix as the MTA and I restored the main.cf file from the old
server. I have indicated MTA ="Postfix"  in mm_cfg.py, which I also moved
over frrom old server backup.

I restarted Postfix and Mailman. Now, when I post to a list, I get a
variety of errors.

In my own mailbox, I get this:

mymailmanserver.com #<mymailmanserver.com#5.1.1 SMTP; 550 5.1.1 <
osltest <at> mymailmanserver.com <osltest <at> listsmart.osl.state.or.us>>: Recipient
address rejected: User unknown in local recipient table> #SMTP#

In the maillog file, I get NOQUEUE: reject RCPT from localhost [::1] 454
4.71 <my.address <at> mydomain.com>: Relay access denied; from=<
mylist-bounces <at> mymailmanserver.com>

In the Mailman smtp-failure log file, I get: "Relay access denied"

From all that I have read, it must be a Postfix configuration problem, but
since I just moved the old main.cf to the new server, I am perplexed. Posts
to the Postfix-Users list has not been productive.

(Continue reading)

Christopher Adams | 2 May 23:51 2016
Picon

Problems with getting httpd to play well with new Mailman install

Hello all,

I recently had a server fail and I am rebuilding a new server (CentOS 7 )
for Mailman. I have the server and OS working and Mailman installed. I have
installed Mailman a number of times, so kind of know the routine.

I have Apache running and verified that it is by browsing to the root of
the web server. I created a new mailing list and then tried to navigate to
the admin and listinfo page. The result was '403 Forbidden'.

Looking in the httpd error log, I find this:  "client denied by server
configuration: /usr/local/mailman/cgi-bin/listinfo".

I added a block in the httpd.conf file to allow access to the cgi-bin
directory and restarted httpd. Still, I am being forbidden. Files and
directories are owned by mailman.mailman and they seem like they have
proper permissions. I am assuming that it is

<Directory      "/usr/local/mailman/cgi-bin/">
        Order allow,deny
        Allow from all
</Directory>

I then commented out the directory block that limited access to the entire
file system. I restarted httpd. Now, I get this :
Bug in Mailman version 2.1.22 We're sorry, we hit a bug!

--

-- 
Christopher Adams
adamsca <at> gmail.com
(Continue reading)

Holly Hart | 29 Apr 19:42 2016

Seeking Information re: mailman admin page bug

Hello,

I work for an organization that uses several Mailman email lists which I 
administer.  Starting a couple weeks ago (apparently), the admin request 
page commands have ceased to function:  messages held in the queue 
remain stuck there, regardless of attempts to discard, reject or accept.

The source of the issue is apparently on Python's end.  
Unfortunately,there is no way to receive a timely response to what 
should be a basic inquiry (and probably something easy to fix).

Have others experienced this bug?  Does anyone here know how to fix 
this?

--

-- 
Holly Hart
Program Coordinator, Iowa Shares
www.iowashares.org
319.338.1446 (office)
319.331.91616 (cell)
------------------------------------------------------
Mailman-Users mailing list Mailman-Users <at> python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: https://mail.python.org/mailman/options/mailman-users/gmmu-mailman-users%40m.gmane.org

Jim Ohlstein | 25 Apr 13:41 2016
Picon

RBL Management for new list/IP

Hello,

This is not so much a technical question as advice seeking. My apologies 
if it isn't appropriate for this list.

I am new to mailing list management, though not new to mail server 
management. I've never run into this problem.

Background is that I am tasked with creating an announcement list for a 
group. I'm using a dedicated IPv4 which I have controlled for two months 
and not previously used for outgoing email. I have not idea what its 
prior "reputation" was. Mailman settings are pretty much default. I have 
proper SPF and rDNS records.

We have added just short of 1000 members, all by their request at the 
web interface. A few test messages went out about 4-5 days ago. Since 
then the only outgoing mails have been signup confirmations and messages 
to me as list owner.

Despite the relatively low volume, my IP keeps getting listed at 
Spamhaus CSS (https://www.spamhaus.org/css/). I can manually de-list it 
but it seems as though whenever we send out any mail we get re-listed. I 
have tried contacting them but gotten nowhere.

The only other RBL where we are listed is http://www.dnsblchile.org/. I 
put in a de-listing request with them over the weekend but they only 
work during the week.

Has anyone dealt with this, and if so, can you offer any ideas?

(Continue reading)

Mark J Bradakis | 25 Apr 07:12 2016

Logging sequence?

Mailman is not working. Messages come in, nothing goes out. Logs are 
useless, providing no clue as to what is happening.

In a working mailman system. what is the sequence of logging that a 
message would go through?

mjb.

------------------------------------------------------
Mailman-Users mailing list Mailman-Users <at> python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: https://mail.python.org/mailman/options/mailman-users/gmmu-mailman-users%40m.gmane.org

Martin Stein | 21 Apr 15:02 2016
Picon

Sending reminder without password

Hello,

I'm looking for a way to send the monthly password reminder message 
without the member(s) password(s). The list member should only see the 
name(s) of the subcribed list(s) and the corresponding URL.
How can I modify the responsible mailpasswds-Script in 
/usr/lib/mailman/cron to preventing it from sending the password(s)?

Thank You!

--

-- 
Martin Stein
Attac Germany Webteam

Attac Germny
M√ľnchener Str. 48
60329 Frankfurt am Main
Mail: martin.stein <at> attac.de

------------------------------------------------------
Mailman-Users mailing list Mailman-Users <at> python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: https://mail.python.org/mailman/options/mailman-users/gmmu-mailman-users%40m.gmane.org
Jim Ohlstein | 21 Apr 05:29 2016
Picon

New user - SMTP failure

Hello,

I am trying to set up a new system for a new list but finding that 
outgoing mail is failing.

The setup I have is FreeBSD 10.3 in a jail with localhost at 
10.0.250.37. I have confirmed that routing in and out of the jail are 
correct by sending mail from it via command line, via telnet, and by 
posting to a newly created list. Unfortunately those messages are not 
relayed out, nor are list invitations.

The system is Mailman 2.1.21, Postfix 3.1.0, and Python 2.7.11.

I see this in logs/smtp-failure:

Apr 20 23:07:27 2016 (19197) Low level smtp error: [Errno 61] Connection 
refused, msgid: <mailman.0.1461205537.18941.c2-list <at> lists.my.domain>
Apr 20 23:07:27 2016 (19197) delivery to my <at> email.address failed with 
code -1: [Errno 61] Connection refused
Apr 20 23:07:27 2016 (19197) Low level smtp error: [Errno 61] Connection 
refused, msgid: <mailman.0.1461205853.19010.c2-list <at> lists.my.domain>
Apr 20 23:07:27 2016 (19197) delivery to my <at> email.address ailed with 
code -1: [Errno 61] Connection refused
Apr 20 23:07:27 2016 (19197) Low level smtp error: [Errno 61] Connection 
refused, msgid: <mailman.0.1461206277.19201.c2-list <at> lists.my.domain>
Apr 20 23:07:27 2016 (19197) delivery to my <at> email.address failed with 
code -1: [Errno 61] Connection refused
Apr 20 23:07:27 2016 (19197) Low level smtp error: [Errno 61] Connection 
refused, msgid: <mailman.0.1461207076.19195.mailman <at> lists.my.domain>
Apr 20 23:07:27 2016 (19197) delivery to my <at> email.address failed with 
(Continue reading)

Camelia Botez | 21 Apr 09:39 2016
Picon
Picon

admin web commands not working

A couple of weeks ago we configured apache https on our mailman server.
Since then we cannot approve/discard/reject any messages using web interface - why?
Does anyone have any idea?
------------------------------------------------------
Mailman-Users mailing list Mailman-Users <at> python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: https://mail.python.org/mailman/options/mailman-users/gmmu-mailman-users%40m.gmane.org

Camelia Botez | 21 Apr 08:21 2016
Picon
Picon

cannot discard messages using web interface

We have a problem on several mailing lists - the moderator cannot discard or approve messages using web
interface to administration of the list.
No matter what action we took the message still appears in Held Messages

Any idea how to fix this.
From command line is working , but the admin user has no access to the server to run mailman commands.
------------------------------------------------------
Mailman-Users mailing list Mailman-Users <at> python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: https://mail.python.org/mailman/options/mailman-users/gmmu-mailman-users%40m.gmane.org

Mailman and Thunderbird

Hi all 

I have no idea where this question belongs to... but there might be some knowing person out here, I hope!

We switched our lists to a new provider and now are using Mailman 2.1.20 from Cpanel. 

A user complained that his Thunderbird mail application (on MacOS X, if this matters) does no longer treat
incoming list mails properly - means, the message is treated by Thunderbird as if it was sent to his
"default" mail address (we call it "A" for now) instead of the address he used to subscibe to the list
(address "B").

This would not be a big problem - but when he replies to a list message, the reply is sent from "A" instead of
"B", resulting in an error message from Mailman...

He has analysed the headers and compared with the old list setup headers. As far as he could see, the only
difference was that Mailman list includes an "Envelope-To"-header with his subscription address,
while the precious list version included a "Delivered-To"-header. 

I am not a "mail header specialist", but I would guess that these two headers are added by the receiving mail
server and not by the list software. Is this assumption correct? If not, can Mailman be configured to send
the "Delivered-To"-header? 

And if there are by chance any Thunderbird-specialists among us: what can he do to correct the situation? 

Thank you, Christian 

--

-- 
Christian F. Buser, Hohle Gasse 6, CH-5507 Mellingen (Switzerland)      
Hilfe fuer Strassenkinder in Ghana: http://www.chance-for-children.org
------------------------------------------------------
(Continue reading)

Richard Robbins | 20 Apr 02:28 2016
Picon

Bounce Processing

I recently switched my mailman host to a new provider.  One of my users is
now encountering problems that he hasn't had before.  When he sends a
message to a list an error message is generated that is in the following
form:

From: Mail Delivery System <Mailer-Daemon <at> cloud1.emwd.com>
To: announce-bounces <at> usml.net
Cc:
Date: Thu, 14 Apr 2016 13:09:24 -0400
Subject: Mail delivery failed: returning message to sender
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:

  [subscriber's email address appeared here and I deleted it]
    host mxa-00149702.gslb.pphosted.com [67.231.156.216]
    SMTP error from remote mail server after end of data:
    550 5.7.0 You are not authorized to use our domain as a sender address.

Action: failed
Final-Recipient: rfc822; [subscriber's email address appeared here and I
deleted it]
Status: 5.0.0
Remote-MTA: dns; mxa-00149702.gslb.pphosted.com
Diagnostic-Code: smtp; 550 5.7.0 You are not authorized to use our domain
as a sender address.

When I asked my host about this I was told that this is an SPF
configuration issue and that the sender needs to adjust relevant DNS
(Continue reading)


Gmane