From rgx1 at hsm.hellespont.com  Wed Aug 20 04:31:43 2014
From: rgx1 at hsm.hellespont.com (Georg Rabenstein)
Date: Wed, 20 Aug 2014 08:31:43 +0000 (UTC)
Subject: [Pymilter] Pymilter upgrade 0.9.5 - 1.0
Message-ID: <1390029759.723906.1408523503839.JavaMail.zimbra@hsm.hellespont.com>

Good day,

we are running your pymilter in version 0.9.5 on our live mail server with implemented scripts from a former colleague.
I was wondering i there is a way to upgrade pymilter to 1.0 with a fallback option in case the scripts stop working properly.

The System runs ubuntu 12.04 with 3.11.0-22-generic kernel and python2.7

Help is much appreciated. 

Georg
-- 
Hellespont Ship Management GmbH & Co. KG
Beim Strohhause 27, 20097 Hamburg, Germany
Tel +49 40 879798-0
Domicile: Hamburg, Germany
Register: Amtsgericht Hamburg HRA 104691
TaxID: DE250768150
General Partner: Hellespont Verwaltung GmbH (Amtsgericht Hamburg HRB 97617)
Man.Dir.: P.Papachristidis, J.Brack, M.Kennedy


From stuart at bmsi.com  Thu Aug 21 15:49:31 2014
From: stuart at bmsi.com (Stuart D Gathman)
Date: Thu, 21 Aug 2014 15:49:31 -0400 (EDT)
Subject: [Pymilter] Pymilter upgrade 0.9.5 - 1.0
In-Reply-To: <1390029759.723906.1408523503839.JavaMail.zimbra@hsm.hellespont.com>
References: <1390029759.723906.1408523503839.JavaMail.zimbra@hsm.hellespont.com>
Message-ID: <alpine.LRH.2.11.1408211540420.2016@bmsred.bmsi.com>

On Aug 20, Georg Rabenstein transmitted in part:

> we are running your pymilter in version 0.9.5 on our live mail server
> with implemented scripts from a former colleague.  I was wondering i
> there is a way to upgrade pymilter to 1.0 with a fallback option in
> case the scripts stop working properly.

> The System runs ubuntu 12.04 with 3.11.0-22-generic kernel and python2.7

I am not aware of any backwards compatibility issues.  The "1.0" 
in this case means that the complete milter API is finally implemented
(and has been stable for a long time).

On Fedora and EPEL, the pymilter package does not include the start.sh
script.  This is because start.sh is an ugly, incomplete hack, and I've
updated all packages that used it to use daemonize instead.  If that is
an issue for you, I'm sure that ubuntu has a daemonize package.

As an example, this is how the SysVInit script for pysrs starts pysrs with
daemonize:

   echo -n "Starting $prog: "
   daemon --check pysrs --pidfile "${piddir}/${prog}.pid" --user mail \
   daemonize -a -e "${logdir}/${prog}.log" -o "${logdir}/${prog}.log" \
 	  -c "${workdir}" -p "${piddir}/${prog}.pid" \
 	  /usr/bin/${python} ${prog}.py
   RETVAL=$?

How to "unupgrade" is a distribution question.  In an rpm based system,
you would force install the old rpm, or use yum downgrade.