Re: [Mailman-Users] Somebody could not subscribe to pypy-...@python.org

2015-04-21 Thread Laura Creighton
In a message of Tue, 21 Apr 2015 16:31:46 -0700, Mark Sapiro writes: >On 04/21/2015 03:55 PM, Laura Creighton wrote: >> Forwarded message here. He just tried to subscribe as ben.jol...@xad.com >> but apparantly can only subscribe if he leaves the password field blank. >> >> It is, of course, work

Re: [Mailman-Users] Somebody could not subscribe to pypy-...@python.org

2015-04-21 Thread Mark Sapiro
On 04/21/2015 03:55 PM, Laura Creighton wrote: > Forwarded message here. He just tried to subscribe as ben.jol...@xad.com > but apparantly can only subscribe if he leaves the password field blank. > > It is, of course, working just fine for me. And it has nothing to do with the password being b

[Mailman-Users] Somebody could not subscribe to pypy-...@python.org

2015-04-21 Thread Laura Creighton
Forwarded message here. He just tried to subscribe as ben.jol...@xad.com but apparantly can only subscribe if he leaves the password field blank. It is, of course, working just fine for me. Laura --- Forwarded Message Return-Path: Received: from na01-bl2-obe.outbound.protection.outlook.co

Re: [Mailman-Users] packages vs sources

2015-04-21 Thread Carl Zwanzig
On 4/21/2015 1:38 PM, Danil Smirnov wrote: Using 'service' scripts to control ALL server's services [...] Considering this 'packagers related' stuff as not important and insisting on 'native' way to use cron has less sense for me than the opposite. Why standard control of Mailman service in ver

Re: [Mailman-Users] packages vs sources

2015-04-21 Thread Mark Sapiro
On 04/21/2015 02:17 PM, Danil Smirnov wrote: > > You described cron entries copying procedure as 'artifacts' Yes, I described the specific content of your init.d/mailman script as an artifact[1] if your package. >> Do we have a communication disconnect of some kind here? > > Perhaps. :) I u

Re: [Mailman-Users] packages vs sources

2015-04-21 Thread Danil Smirnov
2015-04-22 0:05 GMT+03:00 Mark Sapiro : > The source distribution also includes an init.d script at > scripts/mailman and instructions for installing it are in comments at > its beginning and in the installation manual at > , so you can see, we > def

Re: [Mailman-Users] packages vs sources

2015-04-21 Thread Mark Sapiro
On 04/21/2015 01:38 PM, Danil Smirnov wrote: > > Using 'service' scripts to control ALL server's services (Mailman IS a > service irrespective of its version, right?) isn't absurd or > non-sense. I think one should respect distribution structure and keep > things work as distribution creator's int

Re: [Mailman-Users] packages vs sources

2015-04-21 Thread Danil Smirnov
2015-04-21 23:10 GMT+03:00 Mark Sapiro : > They are things that are in some sense left over from a prior install of > a distro's Mailman package. Had you just installed Mailman from source > without ever installing the package, you would not be aware of them. > Thus, they are artifacts left over fr

Re: [Mailman-Users] packages vs sources

2015-04-21 Thread Mark Sapiro
On 04/21/2015 12:18 PM, Danil Smirnov wrote: > 2015-04-21 21:23 GMT+03:00 Mark Sapiro : >> But this raises the question, if you are installing Mailman from source, >> why do you still have artifacts from the distro's package still in your >> installation. > > Why you name them 'artefacts'? I consi

Re: [Mailman-Users] packages vs sources (was: Cron command?)

2015-04-21 Thread Danil Smirnov
2015-04-21 21:23 GMT+03:00 Mark Sapiro : > But this raises the question, if you are installing Mailman from source, > why do you still have artifacts from the distro's package still in your > installation. Why you name them 'artefacts'? I consider them very convenient technology working great for

Re: [Mailman-Users] packages vs sources (was: Cron command?)

2015-04-21 Thread Mark Sapiro
On 04/21/2015 10:37 AM, Danil Smirnov wrote: > > Many people rely on their distribution packagers - is this bad? > > I always prefer to use yum/apt-get instead of compiling software from source. > The reasons are obvious (all they are in any package system mission > statement). > > Mailman is o

Re: [Mailman-Users] sync_members

2015-04-21 Thread Marco Stoecker
On 04/21/2015 07:03 PM, Mark Sapiro wrote: This looks like which was initially addressed in Mailman 2.1.17 and further fixed in 2.1.18. Your's appears to be a pre 2.1.17 version. A patch is attached. Thx Mark, works perfect now :-D BR Marco ---

[Mailman-Users] packages vs sources (was: Cron command?)

2015-04-21 Thread Danil Smirnov
2015-04-21 19:47 GMT+03:00 Mark Sapiro : > This is a packager thing (RHEL/CentOS ?). Mailman as distributed by the > GNU Mailman project does not do this (never did). Our docs are > and recommend > installing our crontab as a user crontab with the c

Re: [Mailman-Users] sync_members

2015-04-21 Thread Marco Stoecker
On 04/21/2015 07:03 PM, Mark Sapiro wrote: This looks like which was initially addressed in Mailman 2.1.17 and further fixed in 2.1.18. Your's appears to be a pre 2.1.17 version. A patch is attached. Hi Mark, in fact I use Debian wheezy which pr

Re: [Mailman-Users] Cron command?

2015-04-21 Thread Mark Sapiro
On 04/21/2015 09:42 AM, Adam McGreggor wrote: > > This makes me wonder if it might be useful to have two files in the > Mailman source: > > mailman/cron/crontab.in-system > mailman/cron/crontab.in-user > > with -system including the 'user' column? Why? Our distribution works when insta

Re: [Mailman-Users] sync_members

2015-04-21 Thread Mark Sapiro
On 04/21/2015 06:59 AM, Marco Stoecker wrote: > > indeed it throws an exception: > > user@machine:~# ./mailinglist_sync.sh > Traceback (most recent call last): > File "/usr/sbin/sync_members", line 288, in > main() > File "/usr/sbin/sync_members", line 259, in main > s = email.Utils.

Re: [Mailman-Users] Cron command?

2015-04-21 Thread Adam McGreggor
On Tue, Apr 21, 2015 at 11:32:48AM -0500, Lindsay Haisley wrote: > The bottom line is that it's best, as always, to install a component > such as a crontab using the supplied tools rather trying to second-guess > the tool set and copying files directly. This makes me wonder if it might be useful t

Re: [Mailman-Users] Cron command?

2015-04-21 Thread Mark Sapiro
On 04/21/2015 09:32 AM, Lindsay Haisley wrote: > On Tue, 2015-04-21 at 18:46 +0300, Danil Smirnov wrote: >> # This file is copied to /etc/cron.d/mailman from >> # /usr/lib/mailman/cron/crontab.in when the mailman service is started via >> its >> # init.d script and the file /etc/cron.d/mailman is

Re: [Mailman-Users] Cron command?

2015-04-21 Thread Lindsay Haisley
On Tue, 2015-04-21 at 18:46 +0300, Danil Smirnov wrote: > # This file is copied to /etc/cron.d/mailman from > # /usr/lib/mailman/cron/crontab.in when the mailman service is started via its > # init.d script and the file /etc/cron.d/mailman is removed when the > # service is stopped. Therefore any

Re: [Mailman-Users] Cron command?

2015-04-21 Thread Lindsay Haisley
On Tue, 2015-04-21 at 18:46 +0300, Danil Smirnov wrote: > # This file is copied to /etc/cron.d/mailman from > # /usr/lib/mailman/cron/crontab.in when the mailman service is started via its > # init.d script and the file /etc/cron.d/mailman is removed when the > # service is stopped. Therefore any

Re: [Mailman-Users] Cron command?

2015-04-21 Thread Mark Sapiro
This thread is getting too convoluted for me to parse, but here's the complete story: There are two possible places where Mailman's crontab can be installed. For purposes of discussion, assume the Mailman user on your server is 'mailman'. - The crontab can be a user crontab in /var/spool/cron/mai

Re: [Mailman-Users] Cron command?

2015-04-21 Thread Lindsay Haisley
On Tue, 2015-04-21 at 18:46 +0300, Danil Smirnov wrote: > 2015-04-21 17:43 GMT+03:00 Danil Smirnov : > > 2015-04-21 17:24 GMT+03:00 Lindsay Haisley : > >> so a direct copy of the > >> Mailman crontab to this directory can't be done without modifying the > >> file. > > You are right but not because

Re: [Mailman-Users] Cron command?

2015-04-21 Thread Danil Smirnov
2015-04-21 17:43 GMT+03:00 Danil Smirnov : > 2015-04-21 17:24 GMT+03:00 Lindsay Haisley : >> so a direct copy of the >> Mailman crontab to this directory can't be done without modifying the >> file. You are right but not because of improper format of crontab.in file: # This file is copied to /etc

Re: [Mailman-Users] Cron command?

2015-04-21 Thread Danil Smirnov
2015-04-21 17:24 GMT+03:00 Lindsay Haisley : > The crontab provided with Mailman in ~mailman/cron/crontab.in is not in > the proper format for use in /etc/cron.d/ so a direct copy of the > Mailman crontab to this directory can't be done without modifying the > file. I have absolutely identical fil

Re: [Mailman-Users] Cron command?

2015-04-21 Thread Lindsay Haisley
Your old notes are incorrect. First, the proper command on modern Unix or Unix-ish systems such as Linux is simply: sudo crontab -e -u mailman Copy and paste the crontab provided with Mailman in the ~mailman/cron directory into the edit window opened by this command. The crontab provided with M

Re: [Mailman-Users] sync_members

2015-04-21 Thread Marco Stoecker
On 04/17/2015 04:57 PM, Mark Sapiro wrote: > How does it fail? Does it throw an exception? If so, please provide a > traceback. If not, what does it do? > > What is the list's preferred_language? > Hi Mark late answer, my laptop crashed. the default language for this list is German: preferred_

Re: [Mailman-Users] Cron command?

2015-04-21 Thread Danil Smirnov
Check if you already have /etc/cron.d/mailman, if not just cp /opt/local/share/mailman/cron/crontab.in /etc/cron.d/mailman with sufficient rights. 2015-04-21 8:21 GMT+03:00 Bill Christensen : > Hi all, > > I recently updated and my digests stopped going out (I was able to push out > the waiting

Re: [Mailman-Users] Cron command?

2015-04-21 Thread E Kogler
>Hi all, > I recently updated and my digests stopped going out (I was able to push out > the waiting digest manually by doing > /opt/local/share/mailman/cron/senddigests so I know the function is > working).  My old notes tell me the command for cron is: > sudo /opt/local/share/mailman/cron/cront