Karl Berry | 24 May 23:47 2016

per-list email at munging?

I just set up some mailman lists for commit archives.  I'd like to avoid
the " <at> " -> " at " munging for them (at least in the bodies, though also
in the headers is fine/expected), while retaining that minimal munging
for the other lists on the server.

Looking at HyperArch.py (and Defaults.py), it seems
ARCHIVER_OBSCURES_EMAILADDRS is server-wide.  Any viable way to make it
per-list?  I couldn't find anything in web searches or at
http://fog.ccsf.cc.ca.us/~msapiro/scripts/ but always easy to miss stuff.

It's not so much that I myself think the " at " munging is so
wonderfully effective at antispam, but I feel sure that if I turn it off
now, my users will complain vociferously and constantly.  Such is life.

Thanks,
Karl

P.S. It seems the original author (Richard Barrett) offered to make it
per-list back in 2003 but no one asked for it :).
https://sourceforge.net/p/mailman/patches/273/
------------------------------------------------------
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

Beu, Ed (DOA | 24 May 02:24 2016

Mm_cfg.py not setting attribute

Hi,

We currently have two instances of Mailman running for test purposes. The newlist command along with a
customized mm_cfg.py file is producing different results on the two systems.

Configurations are as follows on these two test systems.

T1
Solaris 10
Mailman 2.1.20 (csw package)

T2
CentOS 6.7 (Final)
Mailman 2.1.12 (yum package)

On the T1 system I am adding the following statement to the mm_cfg.py file:
DEFAULT_RESPOND_TO_POST_REQUESTS = No

Then, when I run "./newlist -q listname my.email <at> domain.com<mailto:my.email <at> domain.com> 12345678"
the list setting is as desired (respond_to_post_request = No).

On the T2 system using the same scenario above, the "respond_to_post_request" attribute does not change
from the Defaults.py setting of Yes.

On the T2 system I have tried changing the attribute from  DEFAULT_RESPOND_TO_POST_REQUESTS to just
RESPOND_TO_POST_REQUESTS, changed No to Zero (0) and tried DEFAULT_RESPOND_TO_POST_REQUESTS = 0. A
number of combinations, and none work on the CentOS machine.

Do you have any suggestions or recommendations? Our goal is to use the CentOS system for production, so
getting this worked out will be very helpful.
(Continue reading)

Rusty Newton | 23 May 22:57 2016
Gravatar

Mailman suddenly passing through spam from the -bounces addresses

Hi!

New to the list! I'm the community support manager at the Asterisk project.

We've used mailman for ages and we are on 2.1.14 at the moment. I
rarely get too deep with mailman other than the administration
interface. It mostly works and we don't touch much underneath.

Recently I started receiving a lot of spam on the mailman-bounces <at> 
addresses where the From address no longer contains the
mailman-bounces <at>  address and instead contains the spammer's address.

In this case the spam doesn't look like bounce traffic. I'm wondering
if someone can help me identify why mailman might let it through? From
reading documentation and the mailman mail archives I get the
impression that it should be discarding this traffic. However I can't
identify why it isn't discarding this non-bounce traffic.

Here is one example of the spam that comes to the owners addresses via
mailman-bounces:

http://pastebin.com/u2HyNLw6

The list in question has all three bounce notification options set to *no*.

That is:

bounce_unrecognized_goes_to_list_owner
bounce_notify_owner_on_disable
bounce_notify_owner_on_removal
(Continue reading)

Franck Aerts | 23 May 14:57 2016
Picon
Gravatar

accept_these_nonmembers and Reg Expression

Hello everyone,

I am sorry to bother you with this question, but even though the question has been asked on this list and a
answer has been gaven, it doesn’t work for me.

I want any email coming from a particular domain to be accepted without moderation. 

I added a regular expression to accept_these_nonmembers which goes : 

^… <at> domain\.com$
and 
^.* <at> asana\.com$

but with no success : the emails are still moderated. 

Is there an option I should change somewhere that overrule the settings in
« accept_these_nonmembers » ??

The reason i want to have to accept any email from that domain is that the « user » part of the email is a
token that changes all the time.

Thanks in advance,

Franck
------------------------------------------------------
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/
(Continue reading)

Sebastian Hagedorn | 21 May 09:47 2016
Picon

Pending subscription request weirdness

Hi,

I have a problem that looks like this FAQ, but I'm pretty sure it's not:

<http://wiki.list.org/x/EoCE>

There is only one Mailman instance in play, and I can actually see the 
subscription request in /var/lib/mailman/lists/LISTNAME/request.pck. I've 
been getting the email notification for a few days, but in the GUI there 
are "no pending requests".

dumpdb shows this:

dumpdb -p request.pck
[----- start pickle file -----]
<----- start object 1 ----->
{   18: (   2,
            (   1463673214.732806,
                'redacted <at> ukmuenster.de',
                u'Universit\xe4tsklinikum M\xfcnster',
                'redacted',
                0,
                'de')),
    'version': (0, 1)}
[----- end pickle file -----]

This is Mailman 2.1.18. Any ideas?

Cheers
Sebastian
(Continue reading)

jdd | 20 May 19:29 2016
Gravatar

mailman to inn gateway

Hello,

I'm moving a server from openSUSE 13.1 to openSUSE Leap 42.1. Simply 
coping the config files do not get the expected result.

It's probably something small, but I can't put my finger on it.

list manager works fine with mailman + postfix.

I use to have a news server (inn) as mail<>gateway and it worked

my last notes said that mailman do all the job and is simple to configure.

http://dodin.info/wiki/pmwiki.php?n=Doc.Mailman#toc13
but now it's chaotic.

for the list "test", it works from list to news, but not the other way round

for the list linux-31, no result for any way

any hint?

thanks
jdd
------------------------------------------------------
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/
(Continue reading)

Mark Sapiro | 20 May 22:12 2016
Picon

Re: turn on tracing?

On 05/20/2016 12:04 PM, Richard Shetron wrote:
> That only tells me about long running processes, not ones that start and
> stop/die very quickly.  There are programs that aren't starting due to
> permission problems like qrunner.

The qrunners are started by mailmanctl which shoud be started as root
but then sets itself to the user:group that were configured with the
configure options --with-username and --with-groupname. These default to
'mailman'. You can find the values in Defaults.py in the settings for
MAILMAN_USER and MAILMAN_GROUP

> The latest web page now says (which
> doesn't tell me what the eid/gid were when the problem occured):

The web server is a persistent process, it's user:group on Ubuntu are
usually www_data, however, the web server invokes a CGI wrapper, e.g.
/var/lib/mailman/cgi-bin/admin which should be SETGID and group =
Mailman's group.

> Bug in Mailman version 2.1.21rc2
> 
> We're sorry, we hit a bug!
> 
> If you would like to help us identify the problem, please email a copy
> of this page to the webmaster for this site with a description of what
> happened. Thanks!
> Traceback:
> 
> Traceback (most recent call last):
>   File "/var/lib/mailman/scripts/driver", line 86, in run_main
(Continue reading)

Kevin Ross | 20 May 21:08 2016

Re: Lost GNU Web mgmt interface after MAC OSX update

The url is : http://mail.vrcis.com/mailman/admindb/vip

The response is:

Not Found

The requested URL /mailman/admindb/vip was not found on this server.

Apache Server at mail.vrcis.com Port 80

The URL http://mail.vrcis.com

Works fine, however

Mailman logs are empty, /var/apache2 logs have the usual minimal stuff, no
primary website, no webmail, this is just an OSX server running postfix,
clamav and mailman.
We can still execute commandline mailman commands, I have a feeeling its in
the apache httpd conf  possibly where the ./mailman/admindb/...  is added
..?

Thank 

Kevin

-----Original Message-----
From: Mailman-Users
[mailto:mailman-users-bounces+kross=vrcis.com <at> python.org] On Behalf Of Mark
Sapiro
Sent: Friday, May 20, 2016 9:18 AM
(Continue reading)

Richard Shetron | 20 May 20:22 2016

Re: turn on tracing?

How do I find out what uid:gid the programs are running with?
Would I be better downloading a fresh copy of mailman and doing a 
reinstall over the broken copy?  The initial version was installed back 
in ubuntu 8.04 days when mailman wasn't a ubuntu package.  Since then 
for Ubuntu they changed some of the default groups for things, like 
mailing lists.

On 5/20/2016 11:47 AM, Mark Sapiro wrote:
> On 05/20/2016 05:35 AM, Richard Shetron wrote:
>> How do I turn on tracing to find the source of this error.  The
>> interface worked until I told check_perms to fix permissions so I'm sure
>> there is a permission issue.  Also the qrunner won't run, which I also
>> suspect is a permission error.  My partner who did the install has
>> retired for medical reasons so I'm trying to learn how to do all sorts
>> of things in too little time :(  I tried to look in both the mailman
>> logs and the apache logs for errors and didn't find anything.
>>
>> Bug in Mailman version 2.1.21rc2
>>
>> We're sorry, we hit a bug!
>
>
> There should be a traceback and other information about this error in
> Mailman's error log. If it's not there, there is probably a permission
> issue in writing the log.
>
> You can at least temporarily ensure that Mailman's logs are writable by
> anyone and see if that helps.
>
> Also, you can edit $prefix/scripts/driver and at line 33 set
(Continue reading)

Steve Wehr | 20 May 18:57 2016

Valid emails being unsubscribed?

Hi Mark and friends,

I host about 100 mailing lists for clients, and have recently moved to a new installation of mailman. My
clients are telling me they get lots of notices of people being unsubscribed from their lists, that they
never got before, on the older version of mailman.

I've been trying to validate the unsubscribes, but I'm not sure how to do it. I look in mailman's bounce log,
and see that bounces are being received and users are being unsubscribe. I looked in the postfix maillog,
and I see successful sends to these users, then a bounce would be returned. 

I've done some spot checks by sending an email from my personal email account to a few of the users who have
been unsubscribed, and all those emails go through successfully and are not bounced back to me. The users
tell me they are not unsubscribing from the list. I've also see some emails being unsubscribed in the
bounce log, that I personally sent to and know that those are valid email addresses.

Where could I go to learn more about why bounces are received, and try to debug this problem? Does the
community have any suggestions for me? Thanks.

---------------
Steve Wehr 
Tunedin Web Design
www.Tunedinweb.com
------------------------------------------------------
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

(Continue reading)

John Griessen | 20 May 05:20 2016

mailman postfix connection on debian

I am setting up 2.1 on debian and get no receive of a mail to the server that is not a virtual_mailbox_domain
address in postfix.
For instance, a reply to a subscribe request doesn't get received or even mentioned much by the MTA logs in /var/log/mail.log,
but a email to a virtual address, not local to the server, goes fine.

There are so many uids and gids I can't figure it:

This is  ll /run/dovecot    -->

srw------- 1 root    root       0 May 20 02:26 anvil
srw------- 1 root    root       0 May 20 02:26 anvil-auth-penalty
srw------- 1 dovecot root       0 May 20 02:26 auth-client
srw------- 1 dovecot root       0 May 20 02:26 auth-login
srw------- 1 root    root       0 May 20 02:26 auth-master
-rw------- 1 root    root      32 May 20 02:18 auth-token-secret.dat
srw------- 1 vmail   root       0 May 20 02:26 auth-userdb
srw------- 1 dovecot root       0 May 20 02:26 auth-worker
srw------- 1 root    root       0 May 20 02:26 config
srw------- 1 root    root       0 May 20 02:26 dict
srw------- 1 root    root       0 May 20 02:26 director-admin
srw-rw-rw- 1 root    root       0 May 20 02:26 dns-client
srw------- 1 root    root       0 May 20 02:26 doveadm-server
lrwxrwxrwx 1 root    root      25 May 20 02:26 dovecot.conf -> /etc/dovecot/dovecot.conf
drwxr-xr-x 2 root    root      40 May 20 02:18 empty
srw-rw-rw- 1 root    root       0 May 20 02:26 imap-urlauth
srw------- 1 dovecot root       0 May 20 02:26 imap-urlauth-worker
srw-rw-rw- 1 root    root       0 May 20 02:26 indexer
srw------- 1 dovecot root       0 May 20 02:26 indexer-worker
srw------- 1 root    root       0 May 20 02:26 ipc

(Continue reading)


Gmane