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

2016-11-07 Thread 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

2016-10-27 Thread 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)

2016-10-25 Thread 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)

2016-10-22 Thread Matthias Schmidt via Mailman-Users 
Mark,

thanks.

> Am 19.10.2016 um 23:55 schrieb Mark Sapiro :
> 
> 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
> .
> 
> 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  and posts linked therefrom, in
> particular
> .
> 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
> .






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)

2016-10-19 Thread 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)

2016-10-18 Thread 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)

2016-10-18 Thread 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

2016-09-25 Thread 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

2016-09-05 Thread 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

2016-09-04 Thread 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 :
> 
> 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 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

2016-09-03 Thread 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

2016-09-03 Thread 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

2016-09-03 Thread 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