Re: [Mailman-Users] Message.UserNotification vs Message.OwnerNotification in Handlers/Hold.py

2016-10-19 Thread Mark Sapiro 
On 10/11/2016 09:11 AM, Mark Sapiro wrote:
> On 10/11/2016 08:37 AM, Jim Popovitch wrote:
>>
>> The emails fail DMARC because the From: is the virtual list domain,
>> but the Sender is set to the site-list (often a neutral domain used
>> for the MTA that hosts the virtual lists).   OpenDKIM signs based on
>> the Sender (see: "MAILING LISTS" at
>> http://www.opendkim.org/opendkim-README), so the sig is NOT aligned
>> with From, thus failing DMARC...and getting notification emails
>> de-prioritized or worse.
> 
> 
> I haven't yet looked at your suggested changes, and I will.


I haven't forgotten. I still have only briefly looked at your changes,
but I'm concerned about your rev 1381 in light of the two comment lines
that precede the change.

The issue is if owner notifications come from the list-bounces rather
than the site email bounces. Then if an owner notice bounces, the owner
is sent a notice of the bounce and it bounces again and so on in a
bounce loop.

I don't understand why you are making this change as the sender
originally is Utils.get_site_email(mlist.host_name, 'bounces'), so it
already has the list's domain.

-- 
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/archive%40jab.org

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

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

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
.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan



signature.asc
Description: OpenPGP digital signature
--
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 :
> 
> 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