Re: [Mailman-Users] Wrong perms?(fwd) Cron mailman@patronus /usr/lib/mailman/cron/nightly_gzip

2015-07-10 Thread Steve Matzura
On Thu, 09 Jul 2015 08:00:38 -0700, Mark wrote:

On 07/09/2015 06:48 AM, Steve Matzura wrote:
 After solving my cron confusions, I get these messages daily:
 
 Subject: Cron mailman@{mynode} /usr/lib/mailman/cron/checkdbs
 
 ...
 IOError: [Errno 13] Permission denied:
 '/var/lock/mailman/mailman.lock.{mynode}.{mydomain.com}.7552.0'
 
 Subject: Cron mailman@{mynode} /usr/lib/mailman/cron/disabled
 
 ...
 IOError: [Errno 13] Permission denied:
 '/var/lock/mailman/mailman.lock.{mynode}.{mydomain.com}.7837.0'
 
 When I looked for this file, it wasn't even there.
 
 Subject: Cron mailman@{mynode} /usr/lib/mailman/cron/senddigests
 
 ...
 IOError: [Errno 13] Permission denied:
 '/var/lib/mailman/lists/mailman/config.pck'
 
 This file is owned by root and is in the mailman group. 
 
 check_perms reports no problems found.


In that case, these are almost certainly SELinux issues. Google things like

selinux logging
redhat disable selinux
redhat disable selinux without reboot

for information.

I checked to see if SELinux is even enabled on this system. It isn't.
getenforce says disabled.
--
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] Wrong perms?(fwd) Cron mailman@patronus /usr/lib/mailman/cron/nightly_gzip

2015-07-10 Thread Mark Sapiro
On 7/10/15 5:11 PM, Steve Matzura wrote:
 On Thu, 09 Jul 2015 08:00:38 -0700, Mark wrote:
 
 On 07/09/2015 06:48 AM, Steve Matzura wrote:

 ...
 IOError: [Errno 13] Permission denied:
 '/var/lib/mailman/lists/mailman/config.pck'

 This file is owned by root and is in the mailman group. 

 check_perms reports no problems found.


 In that case, these are almost certainly SELinux issues. Google things like

 selinux logging
 redhat disable selinux
 redhat disable selinux without reboot

 for information.
 
 I checked to see if SELinux is even enabled on this system. It isn't.
 getenforce says disabled.


What happens if you do

sudo -u mailman file /var/lib/mailman/lists/mailman/config.pck

If that fails with permissions denied, you'll need to figure out why. If
it succeeds, you'll vave to figure out why you running as 'mailman' can
access the file, but cron running as 'mailman' can't.

-- 
Mark Sapiro m...@msapiro.netThe 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] Header filtering regex issue

2015-07-10 Thread Sibi John
Mark that was the issue !

You are the dude, behind the dude who is behind the other dude ! Super excited 
that this is working again :)

Again for people that did not see the solution,  the regex needed to be ^From: 
.+@(?!(xxx|yyy)\.com).+

-Original Message-
From: Mark Sapiro [mailto:m...@msapiro.net] 
Sent: July 07, 2015 3:55 PM
To: Sibi John
Cc: Mailman Users
Subject: Re: [Mailman-Users] Header filtering regex issue

On 07/07/2015 12:41 PM, Sibi John wrote:
 None whatsoever !! which is what boggles my mind !

In reply to:
 -Original Message-
 From: Mailman-Users On Behalf Of Mark Sapiro
 Sent: July 07, 2015 2:40 PM
 To: mailman-users@python.org
 Subject: Re: [Mailman-Users] Header filtering regex issue
 
 On 07/07/2015 04:43 AM, Sibi John wrote:

 In my spam filter rules, this is the regex that I have and it matches 
 perfectly.

 From: .+@(?!(xxx|yyy)\.com).+


 For some reason, it discards all email and I cannot seem to figure out what 
 I am doing wrong. Any suggestions ?
 
 
 The regexp should work. It might match some desired addresses like 
 u...@sub.xxx.com and not match some undesired ones like u...@xxx.com.au, but 
 it should work for the obvious cases.
 
 Do you have any other header_filter_rules? If so, what are they?


Actually, there is a problem with your regexp. header_filter_rules regexps are 
searched (re.search, not re.match) in multiline mode case insensitively. This 
your regexp will match 'from:' in other places in the headers. Try

^From: .+@(?!(xxx|yyy)\.com).+

to match only a true 'From: header.

-- 
Mark Sapiro m...@msapiro.netThe 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


[Mailman-Users] MM3/HyperKitty and importing Malman2 lists

2015-07-10 Thread Isaac Bennetch
Hi,

Thanks for the good work bringing us Mailman3. I'm doing a new install,
which is intended to import data from a different server which had been
running Mailman2. I've used the mailman-bundler to install and have a
few questions. At this point, I'm still using the SQLite backend but
have hopes of using MySQL (I know MySQL better than PostgreSQL, and the
manual seems to imply that sticking with SQLite may not be ideal).

I'm currently attempting to import the old mbox into Hyperkitty[0],
which I think I've adapted in to

 ./bin/django-admin hyperkitty-import --pythonpath
eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/ -l test...@example.org
/home/mailman/old-list.mbox

Which doesn't say much (full output below[1]), but didn't fully work.
Out of approximately 18300 messages, only six are visible to me through
the Mailing-List Archives web page, and one of them has a very strange
date. It is the second message of the mbox, from 9 Apr 2001, but appears
in the web page with approximately the date/time of the import: 9 July
2015  7:27 p.m. Additionally, the remaining five messages are all the
most recent -- with the exception of the most recent message not
appearing at all.

Additionally, if I use the Search box to search for a word that I know
appears in (at least) one message, I get no results found.

I feel I'm missing something here, any idea what it could be?

Furthermore, I haven't found any substantial documentation on importing
a subscriber list from Mailman2; is there anything that will allow me to
transfer subscribers, their digest preference, and so on without
requiring them all to resubscribe manually?

Thanks in advance,
~isaac


0 - https://hyperkitty.readthedocs.org/en/latest/development.html

1 -
 Importing from mbox file /home/mailman/old-list.mbox to test...@example.org
 /No 'Message-Id' header in email from None about None
 -No 'Message-Id' header in email from None about None
 \No 'Message-Id' header in email from None about None
 |No 'Message-Id' header in email from None about None
 /No 'Message-Id' header in email from None about None
 -No 'Message-Id' header in email from None about None
 \No 'Message-Id' header in email from None about None
 |No 'Message-Id' header in email from None about None
 /No 'Message-Id' header in email from None about None
 -No 'Message-Id' header in email from None about None
 \No 'Message-Id' header in email from None about None
 |No 'Message-Id' header in email from None about None
 Computing thread structure
 Synchronizing properties with Mailman
 /usr/local/src/mailman-bundler/eggs/Django-1.7.8-py2.7.egg/django/db/models/fields/__init__.py:1282:
  RuntimeWarning: DateTimeField MailingList.created_at received a naive 
 datetime (2015-07-04 14:30:22.803087) while time zone support is active.
   RuntimeWarning)
 
 WARNING 
 /usr/local/src/mailman-bundler/eggs/Django-1.7.8-py2.7.egg/django/db/models/fields/__init__.py:1282:
  RuntimeWarning: DateTimeField MailingList.created_at received a naive 
 datetime (2015-07-04 14:30:22.803087) while time zone support is active.
   RuntimeWarning)
 
 The full-text search index will be updated every minute. Run the 'manage.py 
 runjob update_index' command to update it now.


--
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] MM3/HyperKitty and importing Malman2 lists

2015-07-10 Thread Stephen J. Turnbull
Isaac Bennetch writes:

  I feel I'm missing something here, any idea what it could be?

Dunno what's going with your import, but you probably won't find the
core HyperKitty devs here -- they are mostly on
mailman-develop...@python.org.

Sorry I can't be of more direct help!

Steve
--
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