Re: [Mailman-Users] postfix + mailman + mailboxes on the same domain and server

[Matthias Schmidt via Mailman-Users]

> Am 07.11.2016 um 01:06 schrieb Christian :
> 
> Hello,
> 
> I'm trying to get the mailing list to work with postfix and I read a lot
> of information about the difficult usage of it.
> 
> -> It should be possible for a mailbox user 'u...@domain.tld' to send at
> the mailing list 'l...@domain.tld'.
> 
> The only one I found in the archives that addresses my problem:
> https://mail.python.org/pipermail/mailman-users/2012-February/072967.html
> 
> Actually I always get the same error message:
> /var/log/mail.log
> *
> Nov  6 15:50:42 mail postfix/smtpd[757]: connect from IP
> Nov  6 15:50:43 mail postfix/smtpd[757]: Anonymous TLS connection
> established from IP: TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256
> (128/128 bits)
> Nov  6 15:50:43 mail postfix/smtpd[757]: NOQUEUE: reject: RCPT from IP:
> 550 5.1.1 : Recipient address rejected: User unknown in
> virtual mailbox table; from= to=
> proto=ESMTP helo=<[local-IP]>
> Nov  6 15:50:48 mail postfix/smtpd[757]: disconnect from IP
> *
> 
> I hope that my posted configs help you to address the issure.

Postfix doesn’t know about the maiman users so imho your main.cf is missing 
this here:
alias_maps = hash:/private/var/mailman/data/aliases
as well as this:
virtual_alias_maps = hash:/private/var/mailman/data/virtual-mailman

imho the postfix-to-mailman.py script is outdated and not needed anymore.
Therefore you don’t need to modify master.cf.

http://www.list.org/mailman-install/node12.html

cheers
Matthias


> 
> The usual comments has been removed.
> 
> 
> /etc/mailman/mm_cfg.py
> *
> from Defaults import *
> MAILMAN_SITE_LIST = 'mailman'
> DEFAULT_URL_PATTERN = 'http://%s/cgi-bin/mailman/'
> IMAGE_LOGOS  = '/images/mailman/'
> DEFAULT_EMAIL_HOST = 'domain.tld'
> DEFAULT_URL_HOST   = 'www.domain.tld'
> add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
> DEFAULT_SERVER_LANGUAGE = 'de'
> USE_ENVELOPE_SENDER= 0  # Still used?
> DEFAULT_SEND_REMINDERS = 0
> MTA = None # So that mailman skips aliases generation
> DEB_LISTMASTER = 'postmas...@domain.tld'
> POSTFIX_STYLE_VIRTUAL_DOMAINS = ['domain.tld']
> POSTFIX_MAP_CMD = '/var/lib/mailman/data/virtual_to_transport'
> *
> 
> root@mail:/var/lib/mailman/data# ls -l
> insgesamt 64
> -rw-rw-r-- 1 list list  1843 Nov  6 15:07 aliases
> -rw-rw-r-- 1 list list 12288 Nov  6 15:07 aliases.db
> -rw-rw-r-- 1 root list10 Okt 20 11:48 last_mailman_version
> -rw-r--r-- 1 root list 14100 Sep 15 08:04 sitelist.cfg
> -rw-rw-r-- 1 list list  1606 Nov  6 15:07 transport-mailman
> -rw-r--r-- 1 list list 12288 Nov  6 15:07 transport-mailman.db
> -rw-rw 1 root list  1698 Nov  6 15:07 virtual-mailman
> -rwxr-x--- 1 root list   149 Nov  6 15:07 virtual_to_transport
> 
> /var/lib/mailman/data/transport-mailman
> *
> mailman-l...@domain.tld mailman:
> 
> mail...@domain.tld  mailman:
> mailman-ad...@domain.tldmailman:
> mailman-boun...@domain.tld  mailman:
> mailman-conf...@domain.tld  mailman:
> mailman-j...@domain.tld mailman:
> mailman-le...@domain.tldmailman:
> mailman-ow...@domain.tldmailman:
> mailman-requ...@domain.tld  mailman:
> mailman-subscr...@domain.tldmailman:
> mailman-unsubscr...@domain.tld  mailman:
> 
> l...@domain.tld  mailman:
> list-ad...@domain.tldmailman:
> list-boun...@domain.tld  mailman:
> list-conf...@domain.tld  mailman:
> list-j...@domain.tldmailman:
> list-le...@domain.tldmailman:
> list-ow...@domain.tldmailman:
> list-requ...@domain.tld  mailman:
> list-subscr...@domain.tldmailman:
> list-unsubscr...@domain.tld  mailman:
> *
> 
> /etc/postfix/master.cf
> *
> mailman unix  -   n   n   -   -   pipe
>  flags=FR user=list
>  argv=/var/lib/mailman/bin/postfix-to-mailman.py ${nexthop} ${user}
> *
> 
> /etc/postfix/main.cf
> *
> smtpd_banner = $myhostname
> biff = no
> append_dot_mydomain = no
> readme_directory = /usr/share/doc/postfix
> html_directory = /usr/share/doc/postfix/html
> 
> myhostname = mail.domain.tld
> alias_maps = hash:/etc/aliases
> alias_database = hash:/etc/aliases
> myorigin = mail.domain.tld
> mydestination = mail.domain.tld, localhost
> relayhost =
> mynetworks = 127.0.0.0/8 [:::127.0.0.0]/104 [::1]/128
> mailbox_size_limit = 0
> virtual_mailbox_limit = 0
> recipient_delimiter = +
> inet_interfaces = all
> inet_protocols = ipv4

Re: [Mailman-Users] cannot subscribe from outside using web interface

[Matthias Schmidt via Mailman-Users]

> Am 27.10.2016 um 20:23 schrieb Camelia Botez :
> 
> Our mailman server is on DMZ and a couple of month ago was changed to work 
> https.
> From inside LAN we can access mailman.domain/mailman/listinfo/test and 
> subscribe using browser interface.
> From outside LAN we get :
> The site cannot be reachedmailman.org refused to connect.
> 
> Any idea ?
> 

dns
firewall
else check the logs ;-)
Matthias


signature.asc
Description: Message signed with OpenPGP using GPGMail
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] Migrating Mailman to New Server (Same Domain)

[Matthias Schmidt via Mailman-Users]

> Am 24.10.2016 um 22:41 schrieb Jewel Brueggeman-Makda 
> :
> 
> Would it be best to copy the entire mailman directory to the new server or 
> just the lists and archives?
> Command issued on new server to copy data from old.
> rsync -avr root@serverip:/usr/local/mailman /usr/local/mailman

what worked for me, was copying/syncing all mailman directories to the new 
volume and run an update on mailman by downloading the last version and 
recompile it with the same settings of config as before. Then I just checked 
the settings file. Without that mailman wouldn’t start.
cheers
Matthias



signature.asc
Description: Message signed with OpenPGP using GPGMail
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] Start qrunner on ElCapitan (MacOS X Server)

[Matthias Schmidt via Mailman-Users]

Mark,

thanks.

> Am 19.10.2016 um 23:55 schrieb Mark Sapiro <m...@msapiro.net>:
> 
> On 10/19/2016 02:51 AM, Matthias Schmidt wrote:
>> 
>> Now I get in the system log:
>> com.apple.xpc.launchd[1] (org.mailman): Service only ran for 1 seconds. 
>> Pushing respawn out by 9 seconds.
>> 
>> and after that I get:
>> The master qrunner lock could not be acquired because it appears as if 
>> another
>> master qrunner is already running.
>> in mailman’s error log
> 
> 
> Because the original master IS still running. The PID in the lockfile
> exists. The problem is 'mailmanctl start' forks a watcher process. The
> original mailmanctl exits so launchd thinks it only ran for 1 second,
> but it’s child and all the qrunners are still running.
> 
> 
>> after unloading the plist and running mailmanctl -s start again, I get the 
>> same error as output.
>> When I delete these 2 lock files and run mailmanctl start as sudo all is 
>> fine.
> 
> 
> All is not fine. You have 2 Mailman instances running. See
> <https://wiki.list.org/x/4030715>.
> 
> I don't know how to set up plist's for launchd. There may be some sort
> of daemon option to account for processes that fork a daemon and then exit.


that was the right hint, adding sleep 1 to my script did the trick :-)

thank you :-)

Matthias

> 
> See <https://wiki.list.org/x/4030523> and posts linked therefrom, in
> particular
> <http://www.mail-archive.com/mailman-users@python.org/msg56923.html>.
> This is for 10.6, and I don't know if 10.11 is different in this respect
> or not. I think there is more recent discussion in this list's archives
> which you may find by searching at
> <http://www.mail-archive.com/mailman-users@python.org/>.






signature.asc
Description: Message signed with OpenPGP using GPGMail
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] Start qrunner on ElCapitan (MacOS X Server)

[Matthias Schmidt via Mailman-Users]

Mark,

> Am 19.10.2016 um 13:04 schrieb Mark Sapiro <m...@msapiro.net>:
> 
> On 10/18/2016 07:39 AM, Matthias Schmidt via Mailman-Users wrote:
>> 
>> the -s option should fix that problem ;-)
> 
> 
> If it can determine that the lock is stale.
> 
> 
>> but if mailman is started as local then -s doesn’t remove a stray pid file.
> 
> 
> What do you mean by “if mailman is started as local"?

oh I had that before, it was starting as localhost, that was at least the 
message.

Now I get in the system log:
com.apple.xpc.launchd[1] (org.mailman): Service only ran for 1 seconds. Pushing 
respawn out by 9 seconds.

and after that I get:
The master qrunner lock could not be acquired because it appears as if another
master qrunner is already running.
in mailman’s error log

after unloading the plist and running mailmanctl -s start again, I get the same 
error as output.
When I delete these 2 lock files and run mailmanctl start as sudo all is fine.

So starting mailman manually is not a problem.
I just don’t get it started via a plist with launchd.

I also created a  script like this and pointed the plist to the script:
#!/bin/sh
function fstartup()
{
/usr/local/mailman/bin/mailmanctl -s start
}
function fshutdown()
{
/usr/local/mailman/bin/mailmanctl stop
tail -f /dev/null &
wait $!
}

trap fshutdown SIGTERM
trap fshutdown SIGKILL
fstartup;

this seams to do nothing at all …at least there’s nothing in the logs.

cheers
Matthias




signature.asc
Description: Message signed with OpenPGP using GPGMail
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] Start qrunner on ElCapitan (MacOS X Server)

[Matthias Schmidt via Mailman-Users]

> Am 18.10.2016 um 22:50 schrieb mailman-admin <mailman-ad...@uni-konstanz.de>:
> 
> Am 18.10.2016 um 10:57 schrieb Matthias Schmidt via Mailman-Users:
>> Hello,
>> I’m trying to start mailman on startup with ElCapitan.
>> 
>> I tried a plist in LaunchDaemons - that was working in the past with the 
>> command:
>> /usr/local/mailman/bin/mailmanctl -s start
>> 
>> this produces now the error:
>> Service only ran for 2 seconds. Pushing respawn out by 8 seconds
>> 
>> the error log says:
>> The master qrunner lock could not be acquired because it appears as if 
>> another
>> master qrunner is already running
>> 
>> So it starts, creates a lock as localhost … and then it tries to start again.
>> 
>> than I created a startup script as described here:
>> https://developer.apple.com/library/content/documentation/MacOSX/Conceptual/BPSystemStartup/Chapters/StartupItems.html#//apple_ref/doc/uid/1172i-SW9-CJBBHDII
>> 
>> and it does … nothing
>> 
>> the only thing which works currently is starting it manually with sudo
>> and this is kind of inconvenient
>> 
>> I installed mailman manually without using macports or something like that.
>> 
>> I hope someone on the list can share some insight here.
>> 
> 
> Do you shutdown mailman cleanly?

mailman was not running before startup and for the test I made sure that there 
are no pid files present

> If not, you leave a pid file behind, which will prevent mailman from
> starting.


the -s option should fix that problem ;-)
but if mailman is started as local then -s doesn’t remove a stray pid file.

cheers
Matthias




signature.asc
Description: Message signed with OpenPGP using GPGMail
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

[Mailman-Users] Start qrunner on ElCapitan (MacOS X Server)

[Matthias Schmidt via Mailman-Users]

Hello,
I’m trying to start mailman on startup with ElCapitan.

I tried a plist in LaunchDaemons - that was working in the past with the 
command:
/usr/local/mailman/bin/mailmanctl -s start

this produces now the error:
Service only ran for 2 seconds. Pushing respawn out by 8 seconds

the error log says:
The master qrunner lock could not be acquired because it appears as if another
master qrunner is already running

So it starts, creates a lock as localhost … and then it tries to start again.

than I created a startup script as described here:
https://developer.apple.com/library/content/documentation/MacOSX/Conceptual/BPSystemStartup/Chapters/StartupItems.html#//apple_ref/doc/uid/1172i-SW9-CJBBHDII

and it does … nothing

the only thing which works currently is starting it manually with sudo
and this is kind of inconvenient

I installed mailman manually without using macports or something like that.

I hope someone on the list can share some insight here.

thanks
Matthias


signature.asc
Description: Message signed with OpenPGP using GPGMail
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] cannot send mails to yahoo, hotmail and gmail

[Matthias Schmidt via Mailman-Users]

> Am 19.09.2016 um 00:39 schrieb Timothy Jasionowski :
> 
> You may also want to make sure that you're configured SPF for your domain... 
> I know that Google can be suspicious of new or small domains unless SPF (or 
> even DKIM) is implemented.
> 
> SPF is easy to implement. You just need to put a TXT entry into DNS.

as others said before, your MTA needs to be configured correctly.
Besides SPF and DMARK your server has to have a reverse pointer, which resolves 
properly.
In mailman either set the reply-to to the original sender or the FROM to the 
list itself.
If that all is given and you’re not blacklisted, contact the postmasters via 
their help page.
If all is OK, they will white-list your server.

cheers
Matthias

> 
> Timothy
> 
> Sent from my iPhone
> 
>> On Sep 18, 2016, at 17:19, Mark Sapiro  wrote:
>> 
>>> On 09/17/2016 11:05 PM, Eko Budiharto wrote:
>>> dear all,
>>> I have a list using mailman. It cannot send mails to yahoo, hotmail and 
>>> gmail. I check all setting in the mailman, but I still cannot find the 
>>> problem yet. Please help me if someone who ever experience like this.
>> 
>> 
>> It's hard to tell without more information such as bounce messages or
>> log messages, but this could be a DMARC issue. See
>>  and .
>> 
>> It is also possible your server is on one or more blacklists. Check at,
>> e.g., 
>> 
>> Also see .
>> 
>> --
>> Mark Sapiro The highway is for gamblers,
>> San Francisco Bay Area, Californiabetter use your sense - B. Dylan
>> --
>> Mailman-Users mailing list Mailman-Users@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/timothy.d%40jasionow.ski
> --
> Mailman-Users mailing list Mailman-Users@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/beta%40admilon.net



signature.asc
Description: Message signed with OpenPGP using GPGMail
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] Update mailman MacServer5

[Matthias Schmidt via Mailman-Users]

Timothy,

thanks for the tip, but I do not intend to install MacPorts as I had different 
experiences with it in the past.

Besides that, mailman is now running fine now.

The only problem left is that the include of the cgi link of the mailman config 
is not working with the current Apache setup.
I guess it has something to do with the new way Apple handles every website 
hosted on the box through a proxy and I still need to find out how that works - 
will do so tomorrow ;-)

If you don’t mind, you could post your config for your website hosting your 
list.

thanks
Matthias

> Am 05.09.2016 um 02:52 schrieb Timothy Jasionowski <timoth...@jasionow.ski>:
> 
> I think I may have sent this directly, but...
> 
> Mattias,
> 
> I had good luck installing mailman on El Capitan/Server 5 using MacPorts, as 
> it manages all the dependencies and integrates all the chron jobs and startup 
> stuff, but due to some legacy issues with the MacPorts configuration file, 
> the build appends the .cgi prefix in the URI construction. It, otherwise, 
> works fine. It avoided a lot of the issues you had in configuring it and, 
> more importantly, maintaining it.
> 
> If you want to get rid of the extension, download macports, refresh the build 
> index, then edit the macports mailman build file, replacing:
> 
> configure.args  --with-cgi-ext=.cgi \
> --with-cgi-gid=${cgigroup} \
> 
> with
> 
> configure.args  --with-cgi-gid=${cgigroup} \
> 
> Thanks again to Marius Schamschula for that tip, as it drove me crazy.
> 
> Timothy
> 
> Sent from my iPhone
> 
>> On Sep 4, 2016, at 11:53, Mark Sapiro <m...@msapiro.net> wrote:
>> 
>>> On 09/04/2016 01:56 AM, Matthias Schmidt via Mailman-Users wrote:
>>> sorry for being such a pain today _/\_
>>> 
>>> now the webinterface is not coming up.
>>> It looks like the cgi is not executed instead a 404 error is generated
>>> 
>>> my mailman.conf for apache looks like that (it’s basically the same as on 
>>> 10.6, I just changed the path):
>>> 
>>> ScriptAlias /mailman/ "/usr/local/mailman/cgi-bin/"
>> 
>> 
>> This is OK, but ...
>> 
>> 
>>> Alias /pipermail/ "/var/mailman/archives/public/"
>>> 
>>>   Options FollowSymLinks MultiViews Indexes
>>>   AllowOverride None
>>>   Order allow,deny
>>>   Allow from all
>>> 
>>> 
>>> it is included with http.conf
>>> 
>>> for the site I have a redirect:
>>> RewriteCond %{HTTP_HOST}%{REQUEST_URI} ^liste\.dinj\.de.$
>>> RewriteRule ^/(.*) https://%{SERVER_NAME}/mailman/listinfo/dinj  
>>> [L,R=permanent]
>>> and that stuff was working on 10.6
>> 
>> 
>> And all that does is redirect 'http(s)://liste.dinj.de/' to
>> 'https://%{SERVER_NAME}/mailman/listinfo/dinj'
>> 
>> 
>>> the logs say this:
>>> [Sun Sep 04 17:41:42.375938 2016] [:debug] [pid 95364] 
>>> mod_hfs_apple2.c(397): [client 127.0.0.1:59199] mod_hfs_apple: Allowing 
>>> access with matching directory. filename = /WebFolder/dinj/mailman
>>> [Sun Sep 04 17:41:42.375977 2016] [core:info] [pid 95364] [client 
>>> 127.0.0.1:59199] AH00128: File does not exist: 
>>> /WebFolder/dinj/mailman/listinfo/dinj
>> 
>> 
>> So why is Apache looking for /WebFolder/dinj/mailman/listinfo/dinj? Is
>> /WebFolder/dinj the DocumentRoot?
>> 
>> Does this happen with any mailman URL? If you go to
>> 'https://liste.dinj.de/mailman/admin/dinj' do you get a similar 404 or
>> only if you go to' https://liste.dinj.de/'.
>> 
>> Somehow your 'ScriptAlias /mailman/' directive is not effective. In a
>> more or less normal apache configuration it is not sufficient to put
>> mailman.conf in /etc/apache2/conf.d/, you must also have a symlink to it
>> in /etc/apache2/conf-enabled/. I have no idea if this applies to Mac OX
>> X Server, but you need to look at your Include and IncludeOptional
>> directives in the main apache2.conf or whatever it's called to ensure
>> that mailman.conf is directly or indirectly included.
>> 
>> 
>>> /usr/local/mailman/cgi-bin/ has permissions set to 775
>> 
>> 
>> It should be 2775 (drwxrwsr-w) but the important thing is the files
>> therein should be 2755 (-rwxr-sr-x).
>> 
>> --
>> Mark Sapiro <m...@msapiro.net>The highway is for gamblers,
>> San Francisco Bay Area, Californiabetter use your sense - B. Dylan
>> 
>> --
>> Mailman-Users mailing list Ma

Re: [Mailman-Users] Update mailman MacServer5

[Matthias Schmidt via Mailman-Users]

sorry for being such a pain today _/\_

now the webinterface is not coming up.
It looks like the cgi is not executed instead a 404 error is generated

my mailman.conf for apache looks like that (it’s basically the same as on 10.6, 
I just changed the path):

ScriptAlias /mailman/ "/usr/local/mailman/cgi-bin/"
Alias /pipermail/ "/var/mailman/archives/public/"

Options FollowSymLinks MultiViews Indexes
AllowOverride None
Order allow,deny
Allow from all


it is included with http.conf

for the site I have a redirect:
RewriteCond %{HTTP_HOST}%{REQUEST_URI} ^liste\.dinj\.de.$
RewriteRule ^/(.*) https://%{SERVER_NAME}/mailman/listinfo/dinj  [L,R=permanent]

and that stuff was working on 10.6

the logs say this:
[Sun Sep 04 17:41:42.375938 2016] [:debug] [pid 95364] mod_hfs_apple2.c(397): 
[client 127.0.0.1:59199] mod_hfs_apple: Allowing access with matching 
directory. filename = /WebFolder/dinj/mailman
[Sun Sep 04 17:41:42.375977 2016] [core:info] [pid 95364] [client 
127.0.0.1:59199] AH00128: File does not exist: 
/WebFolder/dinj/mailman/listinfo/dinj

/usr/local/mailman/cgi-bin/ has permissions set to 775

thanks again
Matthias


> Am 04.09.2016 um 14:06 schrieb Mark Sapiro <m...@msapiro.net>:
> 
> On 09/03/2016 09:53 PM, Matthias Schmidt wrote:
>> 
>> now I’m stuck here:
>> local[74919]: fatal: execvp /usr/share/mailman/mail/mailman: No such file or 
>> directory
>> 
>> local is owned by postfix so far I found out.
>> What I can’t find is where this line is to be able to correct it (Spotlight 
>> also finds nothing)
> 
> 
> It's in your Postfix aliases for Mailman.
> 
> --
> Mark Sapiro <m...@msapiro.net>The highway is for gamblers,
> San Francisco Bay Area, Californiabetter use your sense - B. Dylan
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] Update mailman MacServer5

[Matthias Schmidt via Mailman-Users]

Hello,

now I’m stuck here:
local[74919]: fatal: execvp /usr/share/mailman/mail/mailman: No such file or 
directory

local is owned by postfix so far I found out.
What I can’t find is where this line is to be able to correct it (Spotlight 
also finds nothing)

thanks
Matthias

> Am 04.09.2016 um 01:10 schrieb Mark Sapiro <m...@msapiro.net>:
> 
> On 09/03/2016 08:48 AM, Matthias Schmidt via Mailman-Users wrote:
>> 
>> I’ve been updating a MacOS10.6 Server to Server 5 (elCapitan).
>> Mailman is not shipped anymore with the current version.
>> So I downloaded 2.1.23, installed the lat version of phyton as well as 
>> dnsphyton.
>> Then I copied the old mailman folders over to /usr/local/mailman and 
>> /var/mailman
>> Then I ran configure and the installation went through.
>> but when I try to start mailman I get this error:
>> File "/usr/local/mailman/bin/mailmanctl", line 106, in 
>>from Mailman import mm_cfg
>> ImportError: No module named Mailman
> 
> 
> It would appear that there is some confusion, probably due to the
> '--prefix' and '--with-var-prefix' you configured with not being
> correct. It looks like they should be --prefix=/usr/local/mailman
> --with-var-prefix=/var/mailman.
> 
> What's in /usr/local/mailman/bin/paths.py for 'prefix =' and is there a
> Mailman directory and a Mailman/__init__.py file in that directory?
> 
> --
> Mark Sapiro <m...@msapiro.net>The highway is for gamblers,
> San Francisco Bay Area, Californiabetter use your sense - B. Dylan
> 
> --
> Mailman-Users mailing list Mailman-Users@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/beta%40admilon.net



signature.asc
Description: Message signed with OpenPGP using GPGMail
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] Update mailman MacServer5

[Matthias Schmidt via Mailman-Users]

Mark,

thanks.
> Am 04.09.2016 um 01:10 schrieb Mark Sapiro <m...@msapiro.net>:
> 
> On 09/03/2016 08:48 AM, Matthias Schmidt via Mailman-Users wrote:
>> 
>> I’ve been updating a MacOS10.6 Server to Server 5 (elCapitan).
>> Mailman is not shipped anymore with the current version.
>> So I downloaded 2.1.23, installed the lat version of phyton as well as 
>> dnsphyton.
>> Then I copied the old mailman folders over to /usr/local/mailman and 
>> /var/mailman
>> Then I ran configure and the installation went through.
>> but when I try to start mailman I get this error:
>> File "/usr/local/mailman/bin/mailmanctl", line 106, in 
>>from Mailman import mm_cfg
>> ImportError: No module named Mailman
> 
> 
> It would appear that there is some confusion, probably due to the
> '--prefix' and '--with-var-prefix' you configured with not being
> correct. It looks like they should be --prefix=/usr/local/mailman
> —with-var-prefix=/var/mailman.

I ran configure again like this:
mailman-2.1.23/configure --prefix=/usr/local/mailman 
--with-var-prefix=/var/mailman

> 
> What’s in /usr/local/mailman/bin/paths.py for 'prefix =' and is there a

ah: the old path to the 10.6 installation
prefix = ‘/usr/share/mailman'
and it should be
prefix:’/usr/local/mailman’

> Mailman directory and a Mailman/__init__.py file in that directory?

yes

seams mailman at least starts after I corrected the prefix, but it’s not yet 
working.
I guess I have to do some more digging into the postfix setup ;-)

thanks again
Matthias

> 
> --
> Mark Sapiro <m...@msapiro.net>The highway is for gamblers,
> San Francisco Bay Area, Californiabetter use your sense - B. Dylan
> 
> --
> Mailman-Users mailing list Mailman-Users@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/beta%40admilon.net



signature.asc
Description: Message signed with OpenPGP using GPGMail
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

[Mailman-Users] Update mailman MacServer5

[Matthias Schmidt via Mailman-Users]

Hello,

I’ve been updating a MacOS10.6 Server to Server 5 (elCapitan).
Mailman is not shipped anymore with the current version.
So I downloaded 2.1.23, installed the lat version of phyton as well as 
dnsphyton.
Then I copied the old mailman folders over to /usr/local/mailman and 
/var/mailman
Then I ran configure and the installation went through.
but when I try to start mailman I get this error:
File "/usr/local/mailman/bin/mailmanctl", line 106, in 
from Mailman import mm_cfg
ImportError: No module named Mailman

All what I found on google is more about Linux installations …

So I guess I’m missing something here.

Thanks for help
Matthias



signature.asc
Description: Message signed with OpenPGP using GPGMail
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

[Mailman-Users] MacOS 10.6 ->OS X Server 5.x (=10.11.x)

[Matthias Schmidt]

Hello,
I’m currently running a 10.6.8 Server installation with a couple of mailman 2.x 
mailing lists („Apple’s mailman“ + virtual domains).
Works great :-)

since iOS9 and MacOS 10.11 were published some things are not working anymore 
via SSL (WebDAV etc) anymore.
So I’m thinking about updating the box.

The current version of OS X Server 5 doesn’t ship with mailman anymore.
Therefore I was thinking to upgrade mailman to v3.
Did anybody upgrade mailman from v2 (apple) to version 3 in connection with an 
OS update?
If so, how did it go and what’s best practice?
(I did google before, but no results showed up - sorry, if that has been 
discussed before and I couldn’t find it)

thanks and cheers
Matthias



signature.asc
Description: Message signed with OpenPGP using GPGMail
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

[Mailman-Users] virtual domain https and admin interface

[Matthias Schmidt]

Hello,
I have mailman 2.1.14 running on OS X Server 10.6.8
One list runs on a virtual domain.
All webpages for the list are addressed via https.
I achieved that with a redirect rule in apache, it simply redirects all http of 
that domain to https.
That works fine so far, but when I try to approve the message of a moderated 
user nothing happens, the page just gets reloaded with no change.
What I'm missing here?
thanks
Matthias 
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] virtual domain https and admin interface

[Matthias Schmidt]

Am 29.01.2013 um 18:27 schrieb Matthias Schmidt:

 Hello,
 I have mailman 2.1.14 running on OS X Server 10.6.8
 One list runs on a virtual domain.
 All webpages for the list are addressed via https.
 I achieved that with a redirect rule in apache, it simply redirects all http 
 of that domain to https.
 That works fine so far, but when I try to approve the message of a moderated 
 user nothing happens, the page just gets reloaded with no change.
 What I'm missing here?

hmm, I found this: 
http://wiki.list.org/display/DOC/4.27+Securing+Mailman's+web+GUI+by+using+Secure+HTTP-SSL
and followed these advice, but now it still doesn't work and on top of it I get 
redicted to the default url host with the login page after trying to accept a 
moderated mail.

mm_cfg.py looks like this:
MTA = 'Postfix'
DEFAULT_EMAIL_HOST = 'mcgregor.admilon.net'
DEFAULT_URL_HOST = 'mcgregor.admilon.net'
DEFAULT_URL_PATTERN = 'https://%s/mailman/'
PUBLIC_ARCHIVE_URL = 'https://%(hostname)s/pipermail/%(listname)s'
VIRTUAL_HOSTS.clear()
add_virtualhost('www.virtualA.com', 'virtualA.com')
add_virtualhost('liste.virtualB.com', 'virtualB.com')
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['virtualA.com','virtualB.com']

thanks
Matthias


--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman Problems under OSX Lion

[Matthias Schmidt]

Am 20.08.2012 um 12:33 schrieb Brad Knowles:

 On Aug 19, 2012, at 8:11 PM, Lindsay Haisley fmouse-mail...@fmp.com wrote:
 
 There are lots of mailing lists available.  Mailman is only one of them.
 Apple no doubt supports _a_ mailing list, but as Apple Enterprise
 Support says, one can seldom expect support from a proprietary software
 vendor for software which isn't their own.
 
 This has long been a major bone of contention.  We're happy to have them take 
 our software, but if they're going to make modifications to it, they need to 
 share those modifications back with us -- and support their mods.  If they're 
 going to ship a modified version of our software but then not provide those 
 modifications back to us and not support their modifications, and not provide 
 any support for what they have shipped? Well, then that makes them the bad 
 guys -- they don't give us any way to be able to provide support to their 
 customers, and they don't support their customers themselves.  Regretfully, 
 the Server team at Apple is well known for ignoring feedback and input from 
 anyone else, especially anyone else in the company.
 

that's partly also true for postfix. The mods Apple made are undocumented and 
not reported back to the postfix developers. This concerns basically the 
OpenDirectory integration.

Besides that, Apple is not shipping mailman anymore with MoutainLion Server, so 
people are already installing it separately and that's what I would do under 
Lion as well.

What makes me wonder is that the OP has an AppleSupport contract and mailman is 
shipping with Lion, I find that more than strange ...

cheers
Matthias


--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman Problems under OSX Lion

[Matthias Schmidt]

Am 13.08.2012 um 00:25 schrieb David Dodell:

 This list is my last hope on getting my problems fixed.
 
 I am running OSX Lion  (not Mountain Lion). Mailman was part of the 
 default installation.
 
 I have two issues which I have gotten absolutely no help from Apple 
 Enterprise Support ... basic answer, we don't support open source software 
 and couldn't answer me on why they installed / advertised mailing lists but 
 don't support it ... but I regress.
 
 
 (1) First issue is cosmetic.At the bottom of each administrative page, 
 mailman does not display the icons which I see on ever other mailman website 
 ... basically the mailman / python logos.   Not a real big deal, besides the 
 cosmetic irk.   I've checked the docs, found the path in the config file, and 
 sure enough the images are there in the path, but they still do not display.  
  Ideas?

where is apache looking for the icons.
I think I read on the OS X Server List that the icons are on a different place 
than they should be.

 
 
 (2) Second issue is more serious.I can't get list moderation to work.
 A message comes in to be moderator, I get email notification of this.   
 However, if I login to the administrator page, pending moderator requests, 
 if I try to approve, reject, or any other command on that page, NOTHING 
 happens ... the message keeps appearing, no action is taken etc.

anything in the logs (apache, mailman ...)?

 
 
 I've repaired all permissions, but besides that, lost on what to try next.

did you try your own install of mailman as it was suggested on the os x server 
list?


cheers
Matthias

 

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman Problems under OSX Lion

[Matthias Schmidt]

Am 20.08.2012 um 01:00 schrieb David Dodell:

 where is apache looking for the icons.
 I think I read on the OS X Server List that the icons are on a different 
 place than they should be.
 
 
 This problem has been fixed.   Strangely enough, found where apache was 
 looking for the icons, put them in that directory ... everything started 
 working.Even redid the icons to reflect the new Mailman logo.No 
 problems for several days, yesterday, it resorted to the original logos, 
 which aren't even in that location anymore.   Very strange.
 
 (2) Second issue is more serious.I can't get list moderation to work.   
  A message comes in to be moderator, I get email notification of this.   
 However, if I login to the administrator page, pending moderator 
 requests, if I try to approve, reject, or any other command on that page, 
 NOTHING happens ... the message keeps appearing, no action is taken etc.
 
 anything in the logs (apache, mailman ...)?
 
 
 
 Stupid question ... where is the mailman log so I can look.

I'd look here:
/private/var/mailman/logs

 
 did you try your own install of mailman as it was suggested on the os x 
 server list?
 
 
 Not yet ... everything else is working very smoothly, and installing mailman 
 I'm afraid is above my abilities.I will have to seek outside help.
 

it's not that difficult  I'd could help you.

cheers
Matthias


--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Error: Mach task special port 9

[Matthias Schmidt]

Am/On Thu, 16 Jul 2009 17:06:21 -0400 schrieb/wrote Steve Burling:

--On July 16, 2009 4:57:24 PM -0400 Rob penng...@mac.com wrote:

 I would also appreciate your launchd.plists! It's a task I've been
 putting off doing myself...

To which I reply:

You can grab the tarball here:

http://www.burling.org/files/mailman-launchd.tgz

If anyone grabs these and makes any significant improvements, please share 
back!

thanks a lot. I  see that also in my logs since quite some time.

cheers,
Matthias

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Users] Detecting Autoresponders

[Matthias Schmidt]

Am/On Mon, 29 Jun 2009 00:27:22 -0500 schrieb/wrote Grant Taylor:

On 6/28/2009 8:15 PM, Mark Sapiro wrote:
 I would say the autoresponder is broken if it is responding 
 repeatedly to the same address on behalf of the same recipient. I 
 would also say it's broken it it responds to the list for an 
 individual message (not a digest) unless the list is anonymous and 
 puts the list address in the From: of delevered posts. Finally, this 
 is probably more controversial, but I think it's broken if it can't 
 identify its own autoresponses from Message-ID: or something else and 
 not respond to one of its own messages.

I *REALLY* /wish/ that was the case.  I've got an end user that has set 
up an Out of Office (a.k.a. OoO) auto-reply in Outlook that is replying 
to every frigging message that comes in.

OoO auto responders usually reply to the From: (header) address of 
messages as they have on concept of the SMTP envelope sender.  So if the 
mailing list either sets the From: or Reply-To: header, that's where the 
OoO replies will go.

I have seen more than a few OoO auto-responders that generate a 
completely new message to the From: / Reply-To: address with out any 
form of identification as to who it is replying to.

In my opinion, OoO auto responders are probably some of the worst things 
in email.  I've been in an environment where two OoO auto responders 
were battling with each other and generated almost 100,000 messages over 
a weekend.

we immediately ban people sending autoresponses to a list.
We've put that in our list rules.

Basically it's up to the list participant to set up his/her
autoresponder to not reply to any list messages.

Probably one could set up a filter or something to catch most of the
autoresponses and filter them out.
cheers,
Matthias

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Users] Mailman vs OSX vs launchd

[Matthias Schmidt]

Am/On Fri, 26 Jun 2009 11:06:40 -0500 schrieb/wrote Larry Stone:

On Fri, 26 Jun 2009, Sebastian Hagedorn wrote:

 On 6/18/09 7:11 PM, Bryan Harrison at br...@bryanharrison.com wrote:
 
 If I allow launchd to start it
 ScaronI get an endless succession ofScaron
 
 Jun 18 16:50:26 org.list.mailmanctl[1697]: Starting Mailman's master
 qrunner.
 Jun 18 16:50:26 com.apple.launchd[1] (org.list.mailmanctl[1697]):
 Stray process with PGID equal to this dead job: PID 1698 PPID 1 Python
 Jun 18 16:50:26 com.apple.launchd[1] (org.list.mailmanctl): Throttling
 respawn: Will start in 9 seconds

I just caught that Bryan notes that he receives an endless succession of 
those messages where as I see one and that's it.

Comparing our launchd .plist files, I see a few differences:
Bryan:
   keyOnDemand/key
   false/
Me:
   keyOnDemand/key
   true/
   keyRunAtLoad/key
   true/

Larry,

you are my hero, thanks!
That looks like working :-)

cheers,
Matthias

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Users] Mailman vs OSX vs launchd

[Matthias Schmidt]

Am/On Thu, 18 Jun 2009 19:22:02 -0500 schrieb/wrote Larry Stone:

On 6/18/09 7:11 PM, Bryan Harrison at br...@bryanharrison.com wrote:

 I've built and installed Mailman 2.12 from current source code and
 have it running just fine under OS X Server 10.5.7, with on exception,
 which is not properly speaking a Mailman problem at all.
 
 If I start Mailman from the CLI, using /usr/share/mailman/bin/
 mailmanctl -s start, all is well.
 
 If I allow launchd to start it
 ScaronI get an endless succession ofScaron
 
 Jun 18 16:50:26 org.list.mailmanctl[1697]: Starting Mailman's master
 qrunner.
 Jun 18 16:50:26 com.apple.launchd[1] (org.list.mailmanctl[1697]):
 Stray process with PGID equal to this dead job: PID 1698 PPID 1 Python
 Jun 18 16:50:26 com.apple.launchd[1] (org.list.mailmanctl): Throttling
 respawn: Will start in 9 seconds

Known issue, no idea why. I've been running Mailman on Client OS X since the
Tiger days. As soon as I upgraded to Leopard, I started seeing this happen
intermittently. I have a launchd plist almost identical to yours.

It is intermittent for me. Probably happens about 1 in 3 boots. I try to
remember to check that it's running after reboots. If not, I have a cron job
that runs hourly to check for the proper number of qrunners and send me
e-mail if any or all are missing.

I have the same issue as Bryan (and my plist looks simular) and find
this in my logs, when I start mailman via launchd, if I start it by CLI,
I don't see this issue:

Jun 26 20:16:29 myMac org.list.mailmanctl[40673]: The master qrunner
lock could not be acquired because it appears as if another
Jun 26 20:16:29 myMac org.list.mailmanctl[40673]: master qrunner is
already running.
Jun 26 20:16:29 myMac com.apple.launchd[1] (org.list.mailmanctl):
Throttling respawn: Will start in 9 seconds
Jun 26 20:16:41 myMac org.list.mailmanctl[40675]: The master qrunner
lock could not be acquired because it appears as if another
Jun 26 20:16:41 myMac org.list.mailmanctl[40675]: master qrunner is
already running.
Jun 26 20:16:41 myMac com.apple.launchd[1] (org.list.mailmanctl):
Throttling respawn: Will start in 8 seconds
Jun 26 20:16:52 myMac org.list.mailmanctl[40680]: The master qrunner
lock could not be acquired because it appears as if another
Jun 26 20:16:52 myMac org.list.mailmanctl[40680]: master qrunner is
already running.
Jun 26 20:16:52 myMac com.apple.launchd[1] (org.list.mailmanctl):
Throttling respawn: Will start in 8 seconds
Jun 26 20:17:02 myMac org.list.mailmanctl[40757]: The master qrunner
lock could not be acquired because it appears as if another
Jun 26 20:17:02 myMac org.list.mailmanctl[40757]: master qrunner is
already running.
Jun 26 20:17:03 myMac com.apple.launchd[1] (org.list.mailmanctl):
Throttling respawn: Will start in 8 seconds
Jun 26 20:17:13 myMac org.list.mailmanctl[40760]: The master qrunner
lock could not be acquired because it appears as if another
Jun 26 20:17:13 myMac org.list.mailmanctl[40760]: master qrunner is
already running.
Jun 26 20:17:13 myMac com.apple.launchd[1] (org.list.mailmanctl):
Throttling respawn: Will start in 8 seconds

But I have this issue always on a 10.5.7 PPC-Server .
So what would be the alternative?

cheers,
Matthias

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Users] Mailman vs OSX vs launchd

[Matthias Schmidt]

Am/On Fri, 26 Jun 2009 13:49:57 +0200 schrieb/wrote Sebastian Hagedorn:

--On 26. Juni 2009 20:22:13 +0900 Matthias Schmidt b...@admilon.net wrote:

 Am/On Thu, 18 Jun 2009 19:22:02 -0500 schrieb/wrote Larry Stone:

 On 6/18/09 7:11 PM, Bryan Harrison at br...@bryanharrison.com wrote:

 I've built and installed Mailman 2.12 from current source code and
 have it running just fine under OS X Server 10.5.7, with on exception,
 which is not properly speaking a Mailman problem at all.

 If I start Mailman from the CLI, using /usr/share/mailman/bin/
 mailmanctl -s start, all is well.

 If I allow launchd to start it
 ScaronI get an endless succession ofScaron

 Jun 18 16:50:26 org.list.mailmanctl[1697]: Starting Mailman's master
 qrunner.
 Jun 18 16:50:26 com.apple.launchd[1] (org.list.mailmanctl[1697]):
 Stray process with PGID equal to this dead job: PID 1698 PPID 1 Python
 Jun 18 16:50:26 com.apple.launchd[1] (org.list.mailmanctl): Throttling
 respawn: Will start in 9 seconds

The reason this happens is that launchd expects the processes it launches 
to stick around. They must not daemonize. But mailmanctl terminates after 
it has started the runners. I assume that Apple modified their own 
distribution of Mailman so that mailmanctl behaves differently. I'd suggest 
comparing the two.

thanks, that was the information I missed and it also explains why Apple
uses -startf in the plist, which is not documented for mailman.
I meanwhile found out, that the voodoo here is to use mailmanctl from
the original Apple distribution.

cheers,
Matthias

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Users] What does this message mean?

[Matthias Schmidt]

Am/On Tue, 28 Apr 2009 20:31:05 +1000 schrieb/wrote James Reid:

I have one single user on one of my lists whose posts regularly (though not
always) result in her messages coming to me as list owner with the following
message:

 

The attached message has been automatically discarded.

html attachment instead of multipart or stuff like that?

cheers,
Matthias

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Users] Archive 3rd Party List

[Matthias Schmidt]

Am/On Fri, 17 Apr 2009 10:31:22 -0600 schrieb/wrote Jim Redman:

I subscribe to a mailing list that has no archive capabilities.

I don't really want to try to take over the list, but would like to 
archive the messages as a service to other list users.

Would it be possible to do this with Mailman?  Or does anyone have an 
alternate system that may be better capable to do this?

besides that, what Brad suggested, I'd go with www.nabble.com,
www.mail-archive.com or some other free service for archiving.
I think the list owner has to be asked in any case.

cheers,
Matthias

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Users] Mailman server not accept mail from Google Apps domain

[Matthias Schmidt]

Am/On Tue, 14 Apr 2009 09:26:47 -0700 schrieb/wrote Hung Phan:

Hello,

All emails from google hosted domain (either gmail or our Google Apps  
domain) to our mailman server is being rejected while emails from  
other domains like me.com pass through. Is there a place in Mailman to  
whitelist a domain? Where can we check for the blacklisted domains?


Technical details of temporary failure:
The recipient server did not accept our requests to connect. Learn  
http://mail.google.com/support/bin/answer.py?answer=7720
[listserv.canby.k12.or.us (1): Connection timed out]

did you actually read this page from google?
It clearly tells you were the problem is.
It's your MTA, your smtp server, who isnot accepting connections from google.

So probably google is just blacklisted either in your spamfilter, mta,
firewall ... 

cheers,
Matthias

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Users] How to send moderator email approval

[Matthias Schmidt]

Am/On Thu, 9 Apr 2009 20:45:17 -0700 schrieb/wrote Mark Sapiro:

Abdul Javid wrote:
 
Is there a setting to let list moderators a notification that a pending
request is approved/rejected.
 
If there are 3 email ids in moderators, if one approves, i would like
other 2 to know that the email has been taken care.


I'm sorry.  There is no such notification option within Mailman.

usually one can set up mailman to send a disapproval-mail in a moderated list.
Wouldn't it be than possible either in mailman itself or in the MTA to
send a copy to a list of admins?
Just an idea, didn't try that.

cheers,
Matthias

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Users] Compile on Mac Leopard - config settings?

[Matthias Schmidt]

Mark,

thanks for your suggestions.

Am/On Tue, 7 Apr 2009 08:18:57 -0700 schrieb/wrote Mark Sapiro:

Matthias Schmidt wrote:

I just subscribed after fiddeling around for a day with mailman on
Leopard (Mac OS 10.5.6 Server on a G4 PPC dual).


And it's probably a good idea to look at the FAQ and list archives
before posting :)

I did so, but somehow the most important information found here:
http://wiki.list.org/pages/viewpage.action?pageId=4030530
slipped through my attention.
imho it would be a good idea to included that information from above in
the documentation which comes with the download package.

Anyway I found and read the mails from Larry Stone, but there was
nothing in it, I didn't know already.




After looking a bit on mailman, I just decided to download the last
version and try to install it.
That looked actually good, but the startup daemon plist doesn't like the
new mailman meal I just cooked.

I was running configure like this:
sudo ./configure --prefix=/usr/share/mailman --with-username=_mailman --
with-groupname=_mailman --with-mail-gid=_mailman --with-cgi-gid=_www --
with-cgi-ext=.cgi

and with with-mail-gid=_postfix

in both cases I get these errors:

Apr  7 12:03:35 mymac org.list.mailmanctl[31389]:   File /usr/share/
mailman/bin/mailmanctl, line 548, in module
Apr  7 12:03:35 mymac org.list.mailmanctl[31389]: main()
Apr  7 12:03:35 mymac org.list.mailmanctl[31389]:   File /usr/share/
mailman/bin/mailmanctl, line 430, in main
Apr  7 12:03:35 mymac org.list.mailmanctl[31389]: kids =
start_all_runners()
Apr  7 12:03:35 mymac org.list.mailmanctl[31389]:   File /usr/share/
mailman/bin/mailmanctl, line 268, in start_all_runners
Apr  7 12:03:35 mymac org.list.mailmanctl[31389]: pid =
start_runner(qrname, slice, count)
Apr  7 12:03:35 mymac org.list.mailmanctl[31389]:   File /usr/share/
mailman/bin/mailmanctl, line 246, in start_runner
Apr  7 12:03:35 mymac org.list.mailmanctl[31389]: pid = os.fork()
Apr  7 12:03:35 mymac org.list.mailmanctl[31389]: OSError: [Errno 35]
Resource temporarily unavailable
Apr  7 12:03:35 mymac org.list.mailmanctl[31389]: Starting Mailman's
master qrunner.
Apr  7 12:03:35 mymac com.apple.launchd[1] (org.list.mailmanctl):
Throttling respawn: Will start in 8 seconds
Apr  7 12:03:44 mymac org.list.mailmanctl[31394]: Starting Mailman's
master qrunner.
Apr  7 12:03:44 mymac com.apple.launchd[1] (org.list.mailmanctl[31394]):
Stray process with PGID equal to this dead job: PID 31395 PPID 1 Python
Apr  7 12:03:44 mymac com.apple.launchd[1] (org.list.mailmanctl):
Throttling respawn: Will start in 10 seconds

so obviously I'm missing something


See thae FAQ at http://wiki.list.org/x/O4A9 and posts linked
therefrom which may help.

I was aware that Apple changed those pathes, therefore I changed them in
my configure as well.
But I was not aware, that Apple used its own binary package - they do so
with postfix as well, which I found out the hard way ;-)

The whole interface Apple provides for administrating mailman is not
only minimalistic, but useless if one wants to do a bit more.
Apple's GUI makes simple things more simple, but a bit more complicated
things even more complicated.



also what I'm a bit confused, I find 2 data folders:
one in the mailman folder: /usr/share/mailman
and another one in the var folder: /var/mailman

what's the difference?


/usr/share/mailman is from your configure and make install. anything
else is from Apple's pre installed Mailman. As Sebastian suggests,
there are probably conflicts.

and that was actually my question.
/usr/share/mailman is the place Apple thinks mailman has to go to and I
just wanted to to rip out everything they've got and install your own
copy from the official Mailman source, so my question was, what else do
I have to set to do so.

I was also asking myself, what the other directory in /var/ does and how
do I set the path for it correctly in the configure. 

On the end I will either keep the version installed by Apple or install
everything in a separate directory, so that I keep control over things.
This exercise I did mainly to understand better, what's going on with
mailman, because I never used it before (but LetterRip in the old days ;-)

cheers,
Matthias

p.s. try a google search on Leopard and mailman ... every list message
about Leopard is going to pop up :-D

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

[Mailman-Users] Compile on Mac Leopard - config settings?

[Matthias Schmidt]

Hello All,

I just subscribed after fiddeling around for a day with mailman on
Leopard (Mac OS 10.5.6 Server on a G4 PPC dual).

After looking a bit on mailman, I just decided to download the last
version and try to install it.
That looked actually good, but the startup daemon plist doesn't like the
new mailman meal I just cooked.

I was running configure like this:
sudo ./configure --prefix=/usr/share/mailman --with-username=_mailman --
with-groupname=_mailman --with-mail-gid=_mailman --with-cgi-gid=_www --
with-cgi-ext=.cgi

and with with-mail-gid=_postfix

in both cases I get these errors:

Apr  7 12:03:35 mymac org.list.mailmanctl[31389]:   File /usr/share/
mailman/bin/mailmanctl, line 548, in module
Apr  7 12:03:35 mymac org.list.mailmanctl[31389]: main()
Apr  7 12:03:35 mymac org.list.mailmanctl[31389]:   File /usr/share/
mailman/bin/mailmanctl, line 430, in main
Apr  7 12:03:35 mymac org.list.mailmanctl[31389]: kids =
start_all_runners()
Apr  7 12:03:35 mymac org.list.mailmanctl[31389]:   File /usr/share/
mailman/bin/mailmanctl, line 268, in start_all_runners
Apr  7 12:03:35 mymac org.list.mailmanctl[31389]: pid =
start_runner(qrname, slice, count)
Apr  7 12:03:35 mymac org.list.mailmanctl[31389]:   File /usr/share/
mailman/bin/mailmanctl, line 246, in start_runner
Apr  7 12:03:35 mymac org.list.mailmanctl[31389]: pid = os.fork()
Apr  7 12:03:35 mymac org.list.mailmanctl[31389]: OSError: [Errno 35]
Resource temporarily unavailable
Apr  7 12:03:35 mymac org.list.mailmanctl[31389]: Starting Mailman's
master qrunner.
Apr  7 12:03:35 mymac com.apple.launchd[1] (org.list.mailmanctl):
Throttling respawn: Will start in 8 seconds
Apr  7 12:03:44 mymac org.list.mailmanctl[31394]: Starting Mailman's
master qrunner.
Apr  7 12:03:44 mymac com.apple.launchd[1] (org.list.mailmanctl[31394]):
Stray process with PGID equal to this dead job: PID 31395 PPID 1 Python
Apr  7 12:03:44 mymac com.apple.launchd[1] (org.list.mailmanctl):
Throttling respawn: Will start in 10 seconds

so obviously I'm missing something

also what I'm a bit confused, I find 2 data folders:
one in the mailman folder: /usr/share/mailman
and another one in the var folder: /var/mailman

what's the difference?


thanks and all the best,
Matthias

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9