Re: New: mail/minimalist
On Jul 02 11:18:30, madro...@gmerlin.de wrote:
> On Sun, 30 Jun 2013 21:13:06 +0200
> Jan Stary wrote:
> >
> > Thank you for the port. I have been using
> > the previous verions from github.
> >
> > I am having the following problem with the default installation.
> >
> > Jun 30 10:35 2013 h...@nove.stare.cz: L="example" T="test" S=441
> > Use of uninitialized value $nconf{"archive"} in lc at /dev/fd/3 line
> > 1755, line 6.
> > Jun 30 14:16 2013 h...@stare.cz: L="mnichov" T="test" S=787
> > Use of uninitialized value $nconf{"archive"} in lc at /dev/fd/3 line
> > 1755, line 6.
> > Insecure dependency in open while running with -T switch at /dev/fd/3
> > line 1883.
> > Jun 30 17:32 2013 ryby.dru...@tomucha.cz: L="mnichov" T="Re:
> > [mnichov] test" S=3 006
> >
> > The culprit seems to this line:
> >
> > $nconf{archive} = lc($nconf{archive}); } }
> >
> >
> > When I comment it out (but not the horrendously
> > styled and indented braces), minimalist works
> > just fine.
> >
> > I remember almost nothing from my Perl coding skills.
> > Could you please shed some light on what could be causing that?
> >
> > Thanks again
> >
> > Jan
> >
>
>
> Hi Jan,
>
> thanks for using and testig the port!
> does the following diff fix the error for you?
This patch doesn't seem to apply
to the minimalist.pl installed by minimalist-20130413
$ patch < /home/hans/minimalist.diff
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--
|diff --git a/minimalist.pl b/minimalist.pl
|index 8d683b7..684dd4c 100755
|--- a/minimalist.pl
|+++ b/minimalist.pl
--
Patching file minimalist.pl using Plan A...
Hunk #1 failed at 1752.
Hunk #2 failed at 1770.
Hunk #3 failed at 1779.
Hunk #4 failed at 1879.
4 out of 4 hunks failed--saving rejects to minimalist.pl.rej
done
> diff --git a/minimalist.pl b/minimalist.pl
> index 8d683b7..684dd4c 100755
> --- a/minimalist.pl
> +++ b/minimalist.pl
> @@ -1752,7 +1752,9 @@ sub read_config ($$) {
> $nconf{archive} = "pipe"; }
> else {
> $nconf{archpgm} = 'BUILTIN';
> - $nconf{archive} = lc($nconf{archive}); } }
> + $nconf{archive} = lc($value);
> + }
> + }
> when ('status') {
> # Calculate mask for status
> my %strel = ("open", $OPEN, "ro", $RO, "closed", $CLOSED,
> "mandatory", $MANDATORY);
> @@ -1768,7 +1770,8 @@ sub read_config ($$) {
> when ('maxusers') { $nconf{maxusers} = $value; }
> when ('maxrcpts') {
> $nconf{maxrcpts} = 20 if ($value < 1);
> - $nconf{maxrcpts} = 50 if ($value > 50); }
> + $nconf{maxrcpts} = 50 if ($value > 50);
> + }
> when ('delay') { $nconf{delay} = $value; }
> when ('maxsize') { $nconf{maxsize} = $value; }
> when ('language') { $nconf{language} = lc $value; }
> @@ -1776,7 +1779,8 @@ sub read_config ($$) {
> # Make lowercase if value isn't URL
> $nconf{listinfo} = lc($value) if ($value =~ /^(yes|no)$/i);
> # In global config only 'yes' or 'no' allowed
> - $nconf{listinfo} = 'no' if ($scope eq 'global' &&
> $nconf{listinfo} ne 'yes'); }
> + $nconf{listinfo} = 'no' if ($scope eq 'global' &&
> $nconf{listinfo} ne 'yes');
> + }
> when ('strip rrq') { $nconf{strip_rrq} = lc($value); }
> when ('modify message-id') { $nconf{modify_msgid} = lc($value); }
> when ('remove resent') { $nconf{remove_resent} = lc($value); }
> @@ -1875,7 +1879,12 @@ sub archive ($$$) {
> my $msgnum;
> if (open(NUM, $path."SEQUENCE")) {
> read NUM, $msgnum, 16;
> - $msgnum = int($msgnum);
> + if ($msgnum =~ /^([0-9]+)$/) {
> + $msgnum = int($1);
> + }
> + else {
> + die "Error reading sequence number from ${path}SEQUENCE";
> + }
> close NUM;
>}
> else { $msgnum = 0 }
Re: New: mail/minimalist
On Jun 18 17:40:06, madro...@gmerlin.de wrote:
> this has been rotting in openbsd-wip for quite some time now. But since
> some people seem to be actually using it I updated it and propose it
> for inclusion in the official ports tree.
> I adopted this project from Vladimir Litovka who has abandoned it and
> improved it security wise.
Thank you for the port. I have been using
the previous verions from github.
I am having the following problem with the default installation.
Jun 30 10:35 2013 h...@nove.stare.cz: L="example" T="test" S=441
Use of uninitialized value $nconf{"archive"} in lc at /dev/fd/3 line
1755, line 6.
Jun 30 14:16 2013 h...@stare.cz: L="mnichov" T="test" S=787
Use of uninitialized value $nconf{"archive"} in lc at /dev/fd/3 line
1755, line 6.
Insecure dependency in open while running with -T switch at /dev/fd/3
line 1883.
Jun 30 17:32 2013 ryby.dru...@tomucha.cz: L="mnichov" T="Re: [mnichov] test" S=3
006
The culprit seems to this line:
$nconf{archive} = lc($nconf{archive}); } }
When I comment it out (but not the horrendously
styled and indented braces), minimalist works
just fine.
I remember almost nothing from my Perl coding skills.
Could you please shed some light on what could be causing that?
Thanks again
Jan
Re: New: mail/minimalist
On 2013/06/18 20:44, Christopher Zimmermann wrote:
> On Tue, 18 Jun 2013 18:04:22 +0100
> Stuart Henderson wrote:
>
> > On 2013/06/18 18:46, Peter Hessler wrote:
> > > On 2013 Jun 18 (Tue) at 17:40:06 +0200 (+0200), Christopher
> > > Zimmermann wrote: :Hi,
> > > :
> > > :this has been rotting in openbsd-wip for quite some time now. But
> > > since :some people seem to be actually using it I updated it and
> > > propose it :for inclusion in the official ports tree.
> > > :I adopted this project from Vladimir Litovka who has abandoned it
> > > and :improved it security wise.
> > > :Because I don't plan to add new features, only to fix bugs I have
> > > no :real scheme for releases and versioning numbers, so I figured
> > > it would :probably be best to version it by date. Is this sensible?
> > > OK for commit? :
> > >
> > >
> > > Please use "PKGNAME = minimalist-0.0.${DATE}" so if they ever do
> > > real releases, we don't need EPOCH.
> >
> > Better still Christopher, since you're upstream anyway, how about
> > rolling a real release :-)
>
> I did a release 3.0 and 3.1, but since I will only do bugfixes, what
> sense is there in doing a "release" for every bug I fix?
> This is no rhetorical question. I really am looking for input on this
> matter. If I do releases how do I decide when...
If the changes you have made since the last release are important enough
to be worth putting in ports, they're probably also important enough to be
worth rolling a release for, so that non-OpenBSD users can get them too.
Re: New: mail/minimalist
If only there were some project with a release cycle you could emulate... :)
On Tue, Jun 18, 2013 at 11:44 AM, Christopher Zimmermann <
madro...@gmerlin.de> wrote:
> On Tue, 18 Jun 2013 18:04:22 +0100
> Stuart Henderson wrote:
>
> > On 2013/06/18 18:46, Peter Hessler wrote:
> > > On 2013 Jun 18 (Tue) at 17:40:06 +0200 (+0200), Christopher
> > > Zimmermann wrote: :Hi,
> > > :
> > > :this has been rotting in openbsd-wip for quite some time now. But
> > > since :some people seem to be actually using it I updated it and
> > > propose it :for inclusion in the official ports tree.
> > > :I adopted this project from Vladimir Litovka who has abandoned it
> > > and :improved it security wise.
> > > :Because I don't plan to add new features, only to fix bugs I have
> > > no :real scheme for releases and versioning numbers, so I figured
> > > it would :probably be best to version it by date. Is this sensible?
> > > OK for commit? :
> > >
> > >
> > > Please use "PKGNAME = minimalist-0.0.${DATE}" so if they ever do
> > > real releases, we don't need EPOCH.
> >
> > Better still Christopher, since you're upstream anyway, how about
> > rolling a real release :-)
>
> I did a release 3.0 and 3.1, but since I will only do bugfixes, what
> sense is there in doing a "release" for every bug I fix?
> This is no rhetorical question. I really am looking for input on this
> matter. If I do releases how do I decide when...
>
Re: New: mail/minimalist
On Tue, 18 Jun 2013 18:04:22 +0100
Stuart Henderson wrote:
> On 2013/06/18 18:46, Peter Hessler wrote:
> > On 2013 Jun 18 (Tue) at 17:40:06 +0200 (+0200), Christopher
> > Zimmermann wrote: :Hi,
> > :
> > :this has been rotting in openbsd-wip for quite some time now. But
> > since :some people seem to be actually using it I updated it and
> > propose it :for inclusion in the official ports tree.
> > :I adopted this project from Vladimir Litovka who has abandoned it
> > and :improved it security wise.
> > :Because I don't plan to add new features, only to fix bugs I have
> > no :real scheme for releases and versioning numbers, so I figured
> > it would :probably be best to version it by date. Is this sensible?
> > OK for commit? :
> >
> >
> > Please use "PKGNAME = minimalist-0.0.${DATE}" so if they ever do
> > real releases, we don't need EPOCH.
>
> Better still Christopher, since you're upstream anyway, how about
> rolling a real release :-)
I did a release 3.0 and 3.1, but since I will only do bugfixes, what
sense is there in doing a "release" for every bug I fix?
This is no rhetorical question. I really am looking for input on this
matter. If I do releases how do I decide when...
pgpRFOSBjCfgl.pgp
Description: PGP signature
Re: New: mail/minimalist
On 2013/06/18 18:46, Peter Hessler wrote:
> On 2013 Jun 18 (Tue) at 17:40:06 +0200 (+0200), Christopher Zimmermann wrote:
> :Hi,
> :
> :this has been rotting in openbsd-wip for quite some time now. But since
> :some people seem to be actually using it I updated it and propose it
> :for inclusion in the official ports tree.
> :I adopted this project from Vladimir Litovka who has abandoned it and
> :improved it security wise.
> :Because I don't plan to add new features, only to fix bugs I have no
> :real scheme for releases and versioning numbers, so I figured it would
> :probably be best to version it by date. Is this sensible? OK for commit?
> :
>
>
> Please use "PKGNAME = minimalist-0.0.${DATE}" so if they ever do real
> releases, we don't need EPOCH.
Better still Christopher, since you're upstream anyway, how about
rolling a real release :-)
Re: New: mail/minimalist
On 2013 Jun 18 (Tue) at 17:40:06 +0200 (+0200), Christopher Zimmermann wrote:
:Hi,
:
:this has been rotting in openbsd-wip for quite some time now. But since
:some people seem to be actually using it I updated it and propose it
:for inclusion in the official ports tree.
:I adopted this project from Vladimir Litovka who has abandoned it and
:improved it security wise.
:Because I don't plan to add new features, only to fix bugs I have no
:real scheme for releases and versioning numbers, so I figured it would
:probably be best to version it by date. Is this sensible? OK for commit?
:
Please use "PKGNAME = minimalist-0.0.${DATE}" so if they ever do real
releases, we don't need EPOCH.
:
:Christopher
:
:
:
:Index: Makefile
:===
:RCS file: Makefile
:diff -N Makefile
:--- /dev/null 1 Jan 1970 00:00:00 -
:+++ Makefile 18 Jun 2013 15:32:15 -
:@@ -0,0 +1,46 @@
:+# $OpenBSD: Makefile.template,v 1.61 2012/03/29 13:41:58 sthen Exp $
:+
:+COMMENT = minimalist mailing list manager written in perl
:+
:+CATEGORIES = mail
:+
:+DATE =20130413
:+HASH =e34248cacab44346175f999b20aa5ac1b81e56da
:+DISTNAME =minimalist-${DATE}
:+
:+DISTFILES = ${HASH}${EXTRACT_SUFX}
:+MASTER_SITES =https://github.com/madroach/minimalist/archive/
:+WRKDIST = ${WRKDIR}/minimalist-${HASH}
:+
:+HOMEPAGE =https://github.com/madroach/minimalist
:+
:+MAINTAINER = Christopher Zimmermann
:+
:+# 2-clause BSD
:+PERMIT_PACKAGE_CDROM =Yes
:+
:+SEPARATE_BUILD = Yes
:+
:+NO_BUILD =Yes
:+NO_TEST = Yes
:+
:+do-install:
:+ ${INSTALL_SCRIPT} ${WRKDIST}/minimalist.pl ${PREFIX}/sbin/
:+ ${INSTALL_DATA_DIR} \
:+
${PREFIX}/share/examples/minimalist/{translations,auth,lists,lists/minimalist-example}/
:+ ${INSTALL_DATA} \
:+ ${WRKDIST}/translations/* \
:+ ${PREFIX}/share/examples/minimalist/translations/
:+ ${INSTALL_DATA} \
:+ ${WRKDIST}/lists/minimalist-example/* \
:+ ${PREFIX}/share/examples/minimalist/lists/minimalist-example/
:+ ${INSTALL_DATA} \
:+ ${WRKDIST}/minimalist.conf \
:+ ${PREFIX}/share/examples/minimalist/
:+ ${INSTALL_DATA_DIR} ${PREFIX}/share/doc/minimalist/
:+ ${INSTALL_DATA} ${WRKDIST}/README ${PREFIX}/share/doc/minimalist/
:+ ${INSTALL_DATA} ${WRKDIST}/CHANGES ${PREFIX}/share/doc/minimalist/
:+
:+
:+
:+.include
:Index: distinfo
:===
:RCS file: distinfo
:diff -N distinfo
:--- /dev/null 1 Jan 1970 00:00:00 -
:+++ distinfo 18 Jun 2013 15:32:15 -
:@@ -0,0 +1,2 @@
:+SHA256 (e34248cacab44346175f999b20aa5ac1b81e56da.tar.gz) =
0vY5PwQSkeCG3BRD6qAWHWqshUfX74y/i8suMkOejlY=
:+SIZE (e34248cacab44346175f999b20aa5ac1b81e56da.tar.gz) = 61237
:Index: patches/patch-minimalist_conf
:===
:RCS file: patches/patch-minimalist_conf
:diff -N patches/patch-minimalist_conf
:--- /dev/null 1 Jan 1970 00:00:00 -
:+++ patches/patch-minimalist_conf 18 Jun 2013 15:32:15 -
:@@ -0,0 +1,28 @@
:+$OpenBSD$
:+--- minimalist.conf.orig Fri Aug 3 10:52:51 2012
: minimalist.conf Fri Aug 3 11:22:12 2012
:+@@ -12,7 +12,7 @@
:+ #
:+ # Defaults to the real uid
:+ #
:+-#user = minimalist
:++user = _minimalist
:+
:+ # Administrator password. It applies to all lists, regardless to
:+ # authentication settings in these lists. For per-list authentication see
:+@@ -53,13 +53,13 @@
:+ #
:+ # Default is no logfile
:+ #
:+-#logfile = /var/log/Minimalist.log
:++logfile = /var/log/minimalist
:+
:+ # Log info about messages, passed through Minimalist. Can be 'yes' or 'no'
:+ #
:+ # Default to 'no'. logfile (see above) to 'none' implies 'no'
:+ #
:+-#log messages = yes
:++log messages = yes
:+
:+ # Run in background. If 'yes', Minimalist uses fork for detach from MTA and
:+ # continues execution in background.
:Index: pkg/DESCR
:===
:RCS file: pkg/DESCR
:diff -N pkg/DESCR
:--- /dev/null 1 Jan 1970 00:00:00 -
:+++ pkg/DESCR 18 Jun 2013 15:32:15 -
:@@ -0,0 +1,26 @@
:+Minimalist is a MINImalist MAiling LIST manager. It is fast, extremely easy
:+to setup and support. It is written in Perl and tested on OpenBSD/OpenSMTPd.
:+However there are no causes not to use Minimalist on any other Unix system,
:+because it doesn't use any system-dependent features.
:+
:+Minimalist has these features:
:+
:+ . subscribe/unsubscribe users by request
:+* including write-only option of subscription
:+ . read-only/closed/mandatory lists
:+ . information about list; users, subscribed to list; lists, to which user
:+subscribed
:+ . per-user options:
:+* read-only (for open lists)
:+* write allow (for read-only lists))
:+* maximum message size
:+ . susped/resume su
New: mail/minimalist
Hi,
this has been rotting in openbsd-wip for quite some time now. But since
some people seem to be actually using it I updated it and propose it
for inclusion in the official ports tree.
I adopted this project from Vladimir Litovka who has abandoned it and
improved it security wise.
Because I don't plan to add new features, only to fix bugs I have no
real scheme for releases and versioning numbers, so I figured it would
probably be best to version it by date. Is this sensible? OK for commit?
Christopher
Index: Makefile
===
RCS file: Makefile
diff -N Makefile
--- /dev/null 1 Jan 1970 00:00:00 -
+++ Makefile18 Jun 2013 15:32:15 -
@@ -0,0 +1,46 @@
+# $OpenBSD: Makefile.template,v 1.61 2012/03/29 13:41:58 sthen Exp $
+
+COMMENT = minimalist mailing list manager written in perl
+
+CATEGORIES = mail
+
+DATE = 20130413
+HASH = e34248cacab44346175f999b20aa5ac1b81e56da
+DISTNAME = minimalist-${DATE}
+
+DISTFILES =${HASH}${EXTRACT_SUFX}
+MASTER_SITES = https://github.com/madroach/minimalist/archive/
+WRKDIST = ${WRKDIR}/minimalist-${HASH}
+
+HOMEPAGE = https://github.com/madroach/minimalist
+
+MAINTAINER = Christopher Zimmermann
+
+# 2-clause BSD
+PERMIT_PACKAGE_CDROM = Yes
+
+SEPARATE_BUILD = Yes
+
+NO_BUILD = Yes
+NO_TEST = Yes
+
+do-install:
+ ${INSTALL_SCRIPT} ${WRKDIST}/minimalist.pl ${PREFIX}/sbin/
+ ${INSTALL_DATA_DIR} \
+
${PREFIX}/share/examples/minimalist/{translations,auth,lists,lists/minimalist-example}/
+ ${INSTALL_DATA} \
+ ${WRKDIST}/translations/* \
+ ${PREFIX}/share/examples/minimalist/translations/
+ ${INSTALL_DATA} \
+ ${WRKDIST}/lists/minimalist-example/* \
+ ${PREFIX}/share/examples/minimalist/lists/minimalist-example/
+ ${INSTALL_DATA} \
+ ${WRKDIST}/minimalist.conf \
+ ${PREFIX}/share/examples/minimalist/
+ ${INSTALL_DATA_DIR} ${PREFIX}/share/doc/minimalist/
+ ${INSTALL_DATA} ${WRKDIST}/README ${PREFIX}/share/doc/minimalist/
+ ${INSTALL_DATA} ${WRKDIST}/CHANGES ${PREFIX}/share/doc/minimalist/
+
+
+
+.include
Index: distinfo
===
RCS file: distinfo
diff -N distinfo
--- /dev/null 1 Jan 1970 00:00:00 -
+++ distinfo18 Jun 2013 15:32:15 -
@@ -0,0 +1,2 @@
+SHA256 (e34248cacab44346175f999b20aa5ac1b81e56da.tar.gz) =
0vY5PwQSkeCG3BRD6qAWHWqshUfX74y/i8suMkOejlY=
+SIZE (e34248cacab44346175f999b20aa5ac1b81e56da.tar.gz) = 61237
Index: patches/patch-minimalist_conf
===
RCS file: patches/patch-minimalist_conf
diff -N patches/patch-minimalist_conf
--- /dev/null 1 Jan 1970 00:00:00 -
+++ patches/patch-minimalist_conf 18 Jun 2013 15:32:15 -
@@ -0,0 +1,28 @@
+$OpenBSD$
+--- minimalist.conf.orig Fri Aug 3 10:52:51 2012
minimalist.confFri Aug 3 11:22:12 2012
+@@ -12,7 +12,7 @@
+ #
+ # Defaults to the real uid
+ #
+-#user = minimalist
++user = _minimalist
+
+ # Administrator password. It applies to all lists, regardless to
+ # authentication settings in these lists. For per-list authentication see
+@@ -53,13 +53,13 @@
+ #
+ # Default is no logfile
+ #
+-#logfile = /var/log/Minimalist.log
++logfile = /var/log/minimalist
+
+ # Log info about messages, passed through Minimalist. Can be 'yes' or 'no'
+ #
+ # Default to 'no'. logfile (see above) to 'none' implies 'no'
+ #
+-#log messages = yes
++log messages = yes
+
+ # Run in background. If 'yes', Minimalist uses fork for detach from MTA and
+ # continues execution in background.
Index: pkg/DESCR
===
RCS file: pkg/DESCR
diff -N pkg/DESCR
--- /dev/null 1 Jan 1970 00:00:00 -
+++ pkg/DESCR 18 Jun 2013 15:32:15 -
@@ -0,0 +1,26 @@
+Minimalist is a MINImalist MAiling LIST manager. It is fast, extremely easy
+to setup and support. It is written in Perl and tested on OpenBSD/OpenSMTPd.
+However there are no causes not to use Minimalist on any other Unix system,
+because it doesn't use any system-dependent features.
+
+Minimalist has these features:
+
+ . subscribe/unsubscribe users by request
+* including write-only option of subscription
+ . read-only/closed/mandatory lists
+ . information about list; users, subscribed to list; lists, to which user
+subscribed
+ . per-user options:
+* read-only (for open lists)
+* write allow (for read-only lists))
+* maximum message size
+ . susped/resume subscription
+ . archiving lists (internal and external), with maximum size of archived
+message
+ . multilanguage support
+ . process MIME-encoded messages
+* including support for local charset (for reports and footer)
+ . hook for bounce processing (using VERP - Variable Envelope Return-Path)
+ . exter
