Re: s-nail-14.8.2

[Steffen Nurpmeso]

j...@wxcvbn.org (Jérémie Courrèges-Anglas) wrote:
 |Steffen Nurpmeso sdao...@yandex.com writes:
 | Jeremie Courreges-Anglas j...@wxcvbn.org wrote:
 ||here's an update to the latest release.
 ||Test reports / comments / oks welcome.

 | Please note that any v14.8 including v14.8.2 has a really severe
 | file locking bug and should not be used -- i will release v14.8.3
 | by the end of the week!
 |
 |I don't see a valid reason to push for an update until v14.8.3 is out.

Ok.

 |(and I am not the maintainer of the port anyway)

Yep.

 | Btw…  Since OpenBSD ships with -lreadline, how about using
 | WANT_READLINE=yes instead of
 |
 ||WANT_EDITLINE=1
 |
 | since it is so much more comfortable?
 |
 |I thought that readline and editline proposed more or less the same
 |features, why would one be more comfortable than the other? (Disclaimer:

Oh, mostly tab-completion, and it is likely i haven't changed my
.inputrc for many, many years and got used to it.
I don't know, i'm not using this after implementing it:
EL_PROMPT_ESC is still broken?  Maybe editline(3) becomes
interesting again when there is a new internal tab-completion
function available that can be used for NCL (the builtin editor)
and editline(3).  Until then editline(3) cannot do that much, if
anything more than the builtin NCL, but which is builtin and
i guess faster. 

 |apart from a few tests most of my uses of s-nail are non-interactive).

Sure.  v14.8 has a completely new MIME parameter handling that is
now compliant (also to RFC 2231) and can thus also deal with
filenames with spaces; your use cases should be safe in the
future.

 |Anyway, since libreadline is under GPLv2+ (base system libreadline) or

It's in the base system, right.  Works out of the box.

 |GPLv3+ (ports libreadline) I don't think that would be a good move.
 |
 | Otherwise the builtin
 | command line editor may be worth looking at, but maybe without
 | tabulator expansion (WANT_TABEXPAND=no) to not use wordexp(3).
 | Yes, it is simple since it lets the terminal deal with the line
 | (instead of implementing a visible viewpoint like e.g. ksh(1)),
 | but i think doing so is still more comfortable than editline(3),
 | especially regarding history handling.  Just a suggestion.
 |
 |I'll leave that discussion to others. :)

Of course.  Keep on going.  ._.
Ciao,

--steffen

Re: [update] s-nail-14.8.3 (was: Re: s-nail-14.8.2)

[Steffen Nurpmeso]

Jeremie Courreges-Anglas j...@wxcvbn.org wrote:
 |So here's the update to s-nail-14.8.3.

No maintainer could do that any better!
We yearn for someone like you!
(I think we don't pine, though.)

 |This release brings an additional executable to perform dot-locking
 |against mailboxes.  Since by default on OpenBSD /var/mail belongs to
 |root:wheel, mode 755 there is no way for that (setgid) executable to
 |work, so I removed it from the build (WANT_PRIVSEP=0).

You and William could also use the attached patch, feel free and
use any possible combination of PRIVSEP_USER= and PRIVSEP_GROUP=,
e.g., you may do

  WANT_PRIVSEP=yes PRIVSEP_USER=root PRIVSEP_GROUP=

It is on the [master] branch now.
Ciao, and thanks again!

--steffen
commit 8296012
Author: Steffen (Daode) Nurpmeso sdao...@users.sf.net
Date:   2015-07-07 00:56:08 +0200

WANT_PRIVSEP: add optional PRIVSEP_USER, try setuid(2) if given
---
 make.rc   |  5 +
 mk-mk.in  | 15 +--
 privsep.c | 42 ++
 3 files changed, 52 insertions(+), 10 deletions(-)

diff --git a/make.rc b/make.rc
index 130f333..da31ccf 100644
--- a/make.rc
+++ b/make.rc
@@ -205,8 +205,13 @@ WANT_COLOUR=yes
 # SETGID that has the sole purpose and functionality of managing this dotlock.
 # WANT_PRIVSEP enables this mini dotlock program, which will be installed in
 # LIBEXECDIR SETGID to the group PRIVSEP_GROUP.
+# If you set PRIVSEP_USER to any value then the binary will be installed
+# SETUID and will try to change user identity.
+# You can define _GROUP and _USER and have it installed SETUID *and* SETGID.
+# But note nothing prevents you from giving two empty values.
 WANT_PRIVSEP=yes
 PRIVSEP_GROUP=mail
+PRIVSEP_USER=
 
 ## PATHS AND PROGRAMS ##
 
diff --git a/mk-mk.in b/mk-mk.in
index 4fb6537..3fe411b 100644
--- a/mk-mk.in
+++ b/mk-mk.in
@@ -220,8 +220,19 @@ install: _install_echoes mk.mk mkman.1 mkrc.rc
 	if [ -n $(OPTIONAL_PRIVSEP) ]; then \
 		__mkdir $(DESTDIR)$(LIBEXECDIR);\
 		__stripfile $(PRIVSEP);\
-		__copychownfile 2555 :$(PRIVSEP_GROUP) $(PRIVSEP) \
-			$(DESTDIR)$(LIBEXECDIR)/$(PRIVSEP);\
+		m='o=rx' o=;\
+		if [ -n $(PRIVSEP_GROUP) ]; then \
+			m=g=rxs,$${m} o=:$(PRIVSEP_GROUP);\
+		else \
+			m=g=rx,$${m};\
+		fi;\
+		if [ -n $(PRIVSEP_USER) ]; then \
+			m=u=rxs,$${m} o=$(PRIVSEP_USER)$${o};\
+		else \
+			m=u=rx,$${m};\
+		fi;\
+		__copychownfile $${m} $${o} $(PRIVSEP) \
+$(DESTDIR)$(LIBEXECDIR)/$(PRIVSEP);\
 	fi;\
 	__mkdir $(DESTDIR)$(MANDIR)/man1;\
 	__copyfile 0444 ./mkman.1 $(DESTDIR)$(MANDIR)/man1/$(UAGENT).1;\
diff --git a/privsep.c b/privsep.c
index fb1e47c..83ebf97 100644
--- a/privsep.c
+++ b/privsep.c
@@ -34,9 +34,6 @@ _ign_signal(int signum)
nact.sa_handler = SIG_IGN;
sigemptyset(nact.sa_mask);
nact.sa_flags = 0;
-#ifdef SA_RESTART
-   nact.sa_flags |= SA_RESTART;
-#endif
sigaction(signum, nact, oact);
 }
 
@@ -47,7 +44,7 @@ main(int argc, char **argv)
char const *name, *hostname, *randstr;
size_t pollmsecs;
enum dotlock_state dls;
-   gid_t gid, egid;
+   bool_t anyid;
 
/* We're a dumb helper, ensure as much as we can noone else uses us */
if (argc != 10 ||
@@ -74,11 +71,40 @@ main(int argc, char **argv)
randstr = argv[7];
pollmsecs = (size_t)strtoul(argv[9], NULL, 10);
 
-   /* Try to change our group identity; to catch faulty installations etc.
+   /* Try to change our identity; to catch faulty installations etc.
+* don't baild if UID==EUID or setuid() fails, but simply continue,
 * don't baild if GID==EGID or setgid() fails, but simply continue */
-   gid = getgid();
-   egid = getegid();
-   if (gid == egid || setgid(egid)) {
+   anyid = FAL0;
+
+   if (PRIVSEP_USER[0] != '\0') {
+  uid_t uid = getuid(), euid = geteuid();
+
+  if (uid != euid) {
+ if (setuid(euid)) {
+dls = DLS_PRIVFAILED;
+if (UICMP(z, write(STDOUT_FILENO, dls, sizeof dls), !=,
+  sizeof dls))
+   goto jerr;
+ }
+ anyid = TRU1;
+  }
+   }
+
+   if (PRIVSEP_GROUP[0] != '\0') {
+  gid_t gid = getgid(), egid = getegid();
+
+  if (gid != egid) {
+ if (setgid(egid)) {
+dls = DLS_PRIVFAILED;
+if (UICMP(z, write(STDOUT_FILENO, dls, sizeof dls), !=,
+  sizeof dls))
+   goto jerr;
+ }
+ anyid = TRU1;
+  }
+   }
+
+   if (!anyid) {
   dls = DLS_PRIVFAILED;
   if (UICMP(z, write(STDOUT_FILENO, dls, sizeof dls), !=, sizeof dls))
  goto jerr;

Re: s-nail-14.8.2

[Steffen Nurpmeso]

Hello!

Jeremie Courreges-Anglas j...@wxcvbn.org wrote:
 |here's an update to the latest release.
 |Test reports / comments / oks welcome.

This is great, thank you very much for your interest and efforts!

  v14.8+ brings in over six months of fulltime development, and is
  the first version of the nail/Heirloom mailx/S-nail BSD Mail
  codebase branch that is capable message roundtripping without
  causing possible message splitting due to faulty From_ line
  detection.  v14.8 also had a Coverity.com defect density of
  0.0 (fwiw).

  And for the first time we start to reap the fruit of all that
  labour: e.g., it was finally and easily possible to implement
  and offer a *ssl-method-HOST* variable, where HOST is the
  address (/port) to connect to.  It was really hard to get there.

Hmhm, sorry for the noise.  ^.^
But now this.

Please note that any v14.8 including v14.8.2 has a really severe
file locking bug and should not be used -- i will release v14.8.3
by the end of the week!

Optionally it is possible to use the attached patch (that was also
send to the list[1]).  Because i really hack many changes into
v14.8.3 (the name has to be Startled Chicken because of that
bug) without any forerun -- the opposite of the rest of v14.8! --
you may prefer this more conservative route instead?

  [1] http://article.gmane.org/gmane.mail.s-nail.user/276

 |Note that s-nail gained a few tests since its import in the ports tree.

Yes, dropping NO_TEST is due.  (Tests are still a real dark corner
beside that, especially expect-fail cases etc.  Sigh.  So to say.)

Btw…  Since OpenBSD ships with -lreadline, how about using
WANT_READLINE=yes instead of

 |WANT_EDITLINE=1

since it is so much more comfortable?  Otherwise the builtin
command line editor may be worth looking at, but maybe without
tabulator expansion (WANT_TABEXPAND=no) to not use wordexp(3).
Yes, it is simple since it lets the terminal deal with the line
(instead of implementing a visible viewpoint like e.g. ksh(1)),
but i think doing so is still more comfortable than editline(3),
especially regarding history handling.  Just a suggestion.

Thanks again, and Ciao! from sunny Germany right before leap,

--steffen
commit 7f8ebc0
Author: Steffen (Daode) Nurpmeso sdao...@users.sf.net
Date:   2015-06-29 13:52:34 +0200

dotlock.c:_dot_dir_access(): fix return value (Martin Neitzel)..

It seems that during the rewrite i changed the control flow twice,
and did not carefully enough adjust the return value accordingly,
effectively setting a true value to true again instead of
assigning false in the other case, and another similar case.
---
 dotlock.c | 9 +
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/dotlock.c b/dotlock.c
index df81fd7..43a1cbc 100644
--- a/dotlock.c
+++ b/dotlock.c
@@ -125,11 +125,12 @@ _dot_dir_access(char const *fname)
 
if ((rv = is_dir(path))) {
   for (;;)
- if (!access(path, R_OK | W_OK | X_OK)) {
-rv = TRU1;
+ if (!access(path, R_OK | W_OK | X_OK))
 break;
- } else if (errno != EINTR)
+ else if (errno != EINTR) {
+rv = FAL0;
 break;
+ }
}
 
ac_free(path);
@@ -328,7 +329,7 @@ dot_lock(char const *fname, int fd, size_t pollmsecs)
   rv = (create_exclusive(path) == 0);
   olderrno = errno;
   sigprocmask(SIG_SETMASK, oset, NULL);
-  if (!rv)
+  if (rv)
  goto jleave;
 
   while (!_dot_fcntl_lock(fd, FLOCK_UNLOCK))

Re: [update] s-nail-14.8.3

[Steffen Nurpmeso]

Hello,

j...@wxcvbn.org (Jérémie Courrèges-Anglas) wrote:
 |Thanks for the quick fix, however we'll go with 14.8.3 without patches.
 |(I just committed the update).  The dotlock will be dealt with in an
 |upcoming update (v14.x?  v15?).

Sourceforge is up again and i was able to release v14.8.4: it
turned the privilege-separated helper into a SETUID program that
gives dotlock files the same UID and GID that the mailbox they are
supposed to lock has.

Thanks for beating me to it!
Ciao,

--steffen

Re: [update] s-nail-14.8.3

[Steffen Nurpmeso]

j...@wxcvbn.org (Jérémie Courrèges-Anglas) wrote:
 |Steffen Nurpmeso sdao...@yandex.com writes:
 | Jeremie Courreges-Anglas j...@wxcvbn.org wrote:

 ||This release brings an additional executable to perform dot-locking
 ||against mailboxes.  Since by default on OpenBSD /var/mail belongs to
 ||root:wheel, mode 755 there is no way for that (setgid) executable to
 ||work, so I removed it from the build (WANT_PRIVSEP=0).
 |
 | You and William could also use the attached patch, feel free and

 |Thanks for the quick fix, however we'll go with 14.8.3 without patches.

Yes, that is better; i have commented on and #if 0 the code out
again on the [master] branch for now, simply doing
setuid(CONFIGURED-UID) cannot be the answer here.  At least not
a satisfying one, that is to say.

 |(I just committed the update).  The dotlock will be dealt with in an
 |upcoming update (v14.x?  v15?).

Many thanks for the update!

And short: yes, of course, but i have to think about it first
[1]..  And then i'm now doing some S-roff to have a nice little
summer break.
Which i wish you too.

Ciao!

[1] So i have to do something about that.  That is clear.  Even
with SETGID the situation is suboptimal already because of
Mail(1)s / POSIX mailx(1)s possibility to open any system mailbox
of a USER via %USER, and $USER / -u USER there is too.  Yet we are
running as A and may dotlock as B, so there is A-B-C, and then
%USER is just a string that gets lost once it is expanded to
MAILSPOOL/user unless we have the object-based v15 environment.
So i think i will end up adding a global bypass for the next
subminor in order not to loose the knowledge that we are working
on %USER and thus should perform dotlocking in addition to normal
file locking.  But i have to think about that.

--steffen

UPDATE mail/s-nail

[Steffen Nurpmeso]

Hello.

Update to v14.9.11 ("Tit family enjoying a bath") with many many
bugfixes and some new features like message info "from the front":

  ? digmsg create 1 -;digmsg 1 header show from; digmsg remove 1

Ciao!

Index: Makefile
===
RCS file: /cvs/ports/mail/s-nail/Makefile,v
retrieving revision 1.20
diff -u -p -r1.20 Makefile
--- Makefile4 May 2018 14:07:27 -   1.20
+++ Makefile9 Aug 2018 20:26:20 -
@@ -2,7 +2,7 @@
 
 COMMENT=   SysV mail/BSD Mail/POSIX mailx: send and receive mail
 
-DISTNAME=  s-nail-14.9.10
+DISTNAME=  s-nail-14.9.11
 CATEGORIES=mail
 HOMEPAGE=  https://www.sdaoden.eu/code.html\#s-mailx
 
Index: distinfo
===
RCS file: /cvs/ports/mail/s-nail/distinfo,v
retrieving revision 1.14
diff -u -p -r1.14 distinfo
--- distinfo4 May 2018 14:07:27 -   1.14
+++ distinfo9 Aug 2018 20:26:20 -
@@ -1,2 +1,2 @@
-SHA256 (s-nail-14.9.10.tar.gz) = h63nu+sRAlCvzoIhsrtVOj2WYTJ9/KP2IplPsBfEnMs=
-SIZE (s-nail-14.9.10.tar.gz) = 895283
+SHA256 (s-nail-14.9.11.tar.gz) = J5ICaHQJuOe08mfheK7RvUxot5wBwQuA8HGX8vc9ZpU=
+SIZE (s-nail-14.9.11.tar.gz) = 926261
Index: patches/patch-obs-imap_c
===
RCS file: patches/patch-obs-imap_c
diff -N patches/patch-obs-imap_c
--- patches/patch-obs-imap_c4 May 2018 14:07:27 -   1.1
+++ /dev/null   1 Jan 1970 00:00:00 -
@@ -1,58 +0,0 @@
 obs-imap.c
-+++ obs-imap.c
-@@ -246,10 +246,9 @@ static enum okay  imap_list(struct mailbox *mp, const 
char *base, int strip,
- static enum okay  imap_copy1(struct mailbox *mp, struct message *m, int n,
-  const char *name);
- static enum okay  imap_copyuid_parse(const char *cp,
-- unsigned long *uidvalidity, unsigned long *olduid,
-- unsigned long *newuid);
-+ ui64_t *uidvalidity, ui64_t *olduid, ui64_t *newuid);
- static enum okay  imap_appenduid_parse(const char *cp,
-- unsigned long *uidvalidity, unsigned long *uid);
-+ ui64_t *uidvalidity, ui64_t *uid);
- static enum okay  imap_copyuid(struct mailbox *mp, struct message *m,
-  const char *name);
- static enum okay  imap_appenduid(struct mailbox *mp, FILE *fp, time_t t,
-@@ -3465,16 +3464,16 @@ imap_copy(struct message *m, int n, const char *name)
- }
-
- static enum okay
--imap_copyuid_parse(const char *cp, unsigned long *uidvalidity,
--   unsigned long *olduid, unsigned long *newuid)
-+imap_copyuid_parse(const char *cp, ui64_t *uidvalidity, ui64_t *olduid,
-+   ui64_t *newuid)
- {
--   char *xp, *yp, *zp;
-+   char const *xp, *yp, *zp;
-enum okay rv;
-NYD_ENTER;
-
--   *uidvalidity = strtoul(cp, , 10);
--   *olduid = strtoul(xp, , 10);
--   *newuid = strtoul(yp, , 10);
-+   n_idec_ui64_cp(uidvalidity, cp, 10, ); /* TODO errors */
-+   n_idec_ui64_cp(olduid, xp, 10, ); /* TODO errors */
-+   n_idec_ui64_cp(newuid, yp, 10, ); /* TODO errors */
-rv = (*uidvalidity && *olduid && *newuid && xp > cp && *xp == ' ' &&
-   yp > xp && *yp == ' ' && zp > yp && *zp == ']');
-NYD_LEAVE;
-@@ -3482,15 +3481,14 @@ imap_copyuid_parse(const char *cp, unsigned long 
*uidvalidity,
- }
-
- static enum okay
--imap_appenduid_parse(const char *cp, unsigned long *uidvalidity,
--   unsigned long *uid)
-+imap_appenduid_parse(const char *cp, ui64_t *uidvalidity, ui64_t *uid)
- {
--   char *xp, *yp;
-+   char const *xp, *yp;
-enum okay rv;
-NYD_ENTER;
-
--   *uidvalidity = strtoul(cp, , 10);
--   *uid = strtoul(xp, , 10);
-+   n_idec_ui64_cp(uidvalidity, cp, 10, ); /* TODO errors */
-+   n_idec_ui64_cp(uid, xp, 10, ); /* TODO errors */
-rv = (*uidvalidity && *uid && xp > cp && *xp == ' ' && yp > xp &&
-   *yp == ']');
-NYD_LEAVE;

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Hey.

Steffen Nurpmeso wrote in <20180809203425.2sjei%stef...@sdaoden.eu>:
 |Update to v14.9.11 ("Tit family enjoying a bath") with many many
 |bugfixes and some new features like message info "from the front":
 |
 |  ? digmsg create 1 -;digmsg 1 header show from; digmsg remove 1

In no way i wanna push forward anything, 'just want to mention
that, last time i tried, "set mta-no-receiver-arguments" in some
.mailrc was helpful; this was introduced in October 2017
specifically to deal with OpenSMTPD 6.0.2p1, because i found it
"joins command line arguments onto receivers given in the message,
which can result in multiple deliveries to the same addressee".
In case someone stumbles upon this.

Have a nice weekend and Ciao! Ciao! Ciao!

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Hello Stuart, all.

Stuart Henderson <s...@spacehopper.org> wrote:
 |On 2018/03/09 18:39, Steffen Nurpmeso wrote:
 |> Stuart Henderson <s...@spacehopper.org> wrote:
 |>|On 2018/03/08 17:35, Steffen Nurpmeso wrote:
 |>|> This brings in two and a half years of development and bug fixes.
 |>|> It has really improved, though a long road is ahead still.
 |>|> Changelog etc. at: https://www.sdaoden.eu/code-nail-ann.html
 ...
 |>|It picks up idn2 in preference to idn if present at build, so
 |>|WANTLIB/LIB_DEPENDS needs fixing.
 |> 
 |> ..Ok.. hmm.  I must say i dislike the entire IDN stuff very very
 |> much (if 25 years ago the DNS had some extensions to support
 |> longer labels UTF-8 could be it; even globally), so instead i have
 |> changed the configuration to prefer IDN over IDN2, and added the
 |> changeset as a patch for the OpenBSD port.  I really would prefer
 |> this approach and have no IDN2 around, if possible. ?
 |
 |Hm - I haven't been keeping close track of IDN, but don't some
 |DNS registrars (like .de) require IDNA 2008 (i.e. libidn2)?
 |There was a CVE in curl relating to this a couple of years ago.

Yes.  They use this backward incompatible stuff and also seem to
promote DNSSEC (instead of DNS/DTLS and/or DNS/TCP/TLS, imho).
Isn't it absurd that instead of using UTF-7 for internationalized
DNS with an extension bit to support longer names they have chosen
that mysterious algorithm to provide backward compatible somewhat
shorter-than-UTF-7 ASCII representations, and then just break
compatibility with already existing names with a shrug.  No.

Heck, whatever you say.  It is much larger, of course.  It took
two hours to compile here...  And noone uses it. :)
So how about adding an "idna" FLAVOR!?!

(For the future i have implemented an any_of mechanism, so we can
say VAL_IDNA="idn2 idnkit" in the future.
Thanks for pointing this out (it tips the scale in fact,
i wondered just last week how to allow users and the test to
choose the used PRG implementation, and have added non-generic
OPT_SSL_RANDOM, this has to go again).  Credits went to you.)

  ...
 |> Running "make test" does not work because we verify $HOME is an
 |> accessible directory, which the port framework does not provide.
  ...
 |Funnily enough this came up in another list post today.
 |You can either set PORTHOME as a port Makefile variable, or set
 |HOME as an environment variable for test. Using ${WRKDIR} for
 |this is often a good choice.

Ah, ok, i did not find anything in FAQ, and then refrained
from asking.  Now am seeing it in bsd.port.mk(5).
Did the first, ok?

Fine, so with a corrected patch (was not a double free indeed,
kept on wondering), and a patch for that false printf(1) in the
test, IDN2 patch removed and IDN2 dependency added for a new idna
FLAVOR (thus not using the .xz tarball since only IDN2 brings xz;
unfortunately there is no zstd(1) packaging around yet, nor is it
in the OpenBSD base system), all tests work and we end up as
pasted below.

Thanks Stuart for the comments and suggestions, a nice weekend
i wish you, and all,
Ciao already here,

Index: Makefile
===
RCS file: /cvs/ports/mail/s-nail/Makefile,v
retrieving revision 1.19
diff -u -p -r1.19 Makefile
--- Makefile8 Dec 2017 01:04:14 -   1.19
+++ Makefile10 Mar 2018 21:56:02 -
@@ -1,45 +1,51 @@
 # $OpenBSD: Makefile,v 1.19 2017/12/08 01:04:14 espie Exp $
 
-COMMENT=   enhanced, MIME capable Berkeley Mail
+COMMENT=   SysV mail/BSD Mail/POSIX mailx: send and receive mail
 
-DISTNAME=  s-nail-14.8.16
-CATEGORIES=mail
-HOMEPAGE=  https://www.sdaoden.eu/code.html\#s-mailx
-FIX_EXTRACT_PERMISSIONS=Yes
+DISTNAME=  s-nail-14.9.9
+CATEGORIES=mail
+FLAVORS=   idna
+HOMEPAGE=  https://www.sdaoden.eu/code.html\#s-mailx
+MAINTAINER=Dmitrij D. Czarkoff <czark...@openbsd.org>
 
+MASTER_SITES=  https://ftp.sdaoden.eu/
 # BSD
-PERMIT_PACKAGE_CDROM=  Yes
-
-WANTLIB += c crypto iconv idn ssl
-
-MASTER_SITES=  https://www.sdaoden.eu/downloads/
-MAINTAINER=Dmitrij D. Czarkoff <czark...@openbsd.org>
+PERMIT_PACKAGE_CDROM=Yes
+# XXX remove FIX_EXTRACT_PERMISSIONS with update to version >14.9.9
+FIX_EXTRACT_PERMISSIONS=Yes
 
-MAKE_FILE= makefile
-MAKE_FLAGS=CC="${CC}" \
-   CFLAGS="${CFLAGS}" \
-   C_INCLUDE_PATH="${LOCALBASE}/include" \
-   LDFLAGS="${LDFLAGS}" \
-   LD_LIBRARY_PATH="${LOCALBASE}/lib" \
-   MANDIR="${PREFIX}/man" \
-   SYSCONFDIR="${SYSCONFDIR}" \
-   WANT_AUTOCC=0 \
-   WANT_EDITLINE=0 \
-   WANT_NCL=1 \
-  

UPDATE mail/s-nail

[Steffen Nurpmeso]

This brings in two and a half years of development and bug fixes.
It has really improved, though a long road is ahead still.
Changelog etc. at: https://www.sdaoden.eu/code-nail-ann.html
Thank you.

Index: Makefile
===
RCS file: /cvs/ports/mail/s-nail/Makefile,v
retrieving revision 1.19
diff -u -p -r1.19 Makefile
--- Makefile8 Dec 2017 01:04:14 -   1.19
+++ Makefile8 Mar 2018 16:26:49 -
@@ -1,45 +1,41 @@
 # $OpenBSD: Makefile,v 1.19 2017/12/08 01:04:14 espie Exp $
 
-COMMENT=   enhanced, MIME capable Berkeley Mail
+COMMENT=   SysV mail/BSD Mail/POSIX mailx: send and receive mail
 
-DISTNAME=  s-nail-14.8.16
-CATEGORIES=mail
-HOMEPAGE=  https://www.sdaoden.eu/code.html\#s-mailx
-FIX_EXTRACT_PERMISSIONS=Yes
+DISTNAME=  s-nail-14.9.9
+CATEGORIES=mail
+HOMEPAGE=  https://www.sdaoden.eu/code.html\#s-mailx
 
+FIX_EXTRACT_PERMISSIONS=Yes
 # BSD
-PERMIT_PACKAGE_CDROM=  Yes
+PERMIT_PACKAGE_CDROM=Yes
 
-WANTLIB += c crypto iconv idn ssl
+WANTLIB += c crypto curses iconv idn ssl
 
-MASTER_SITES=  https://www.sdaoden.eu/downloads/
-MAINTAINER=Dmitrij D. Czarkoff 
+MASTER_SITES=  https://ftp.sdaoden.eu/
+MAINTAINER=Dmitrij D. Czarkoff 
 
-MAKE_FILE= makefile
-MAKE_FLAGS=CC="${CC}" \
-   CFLAGS="${CFLAGS}" \
-   C_INCLUDE_PATH="${LOCALBASE}/include" \
-   LDFLAGS="${LDFLAGS}" \
-   LD_LIBRARY_PATH="${LOCALBASE}/lib" \
-   MANDIR="${PREFIX}/man" \
-   SYSCONFDIR="${SYSCONFDIR}" \
-   WANT_AUTOCC=0 \
-   WANT_EDITLINE=0 \
-   WANT_NCL=1 \
-   WANT_DOTLOCK=0 \
-   SID=
+MAKE_FILE= makefile
+MAKE_FLAGS=C_INCLUDE_PATH="${LOCALBASE}/include" \
+   LD_LIBRARY_PATH="${LOCALBASE}/lib" \
+   VAL_MANDIR="${PREFIX}/man" \
+   VAL_SYSCONFDIR="${SYSCONFDIR}" \
+   VAL_SID= \
+   \
+   OPT_AUTOCC=no \
+   OPT_DOTLOCK=no \
 
 .if !empty(DEBUG)
-MAKE_FLAGS+=   WANT_DEBUG=1
-FAKE_FLAGS+=   WANT_DEBUG=1
+MAKE_FLAGS+=   OPT_DEBUG=yes
+FAKE_FLAGS+=   OPT_DEBUG=yes
 .endif
 
-MAKE_ENV=  VERBOSE=Yes
+MAKE_ENV=  VERBOSE=anynonempty
 
-LIB_DEPENDS=   converters/libiconv \
-   devel/libidn
+LIB_DEPENDS=   converters/libiconv \
+   devel/libidn
 
-INSTALL_TARGET=packager-install
+INSTALL_TARGET=install
 
 post-install:
${INSTALL_DATA_DIR} ${PREFIX}/share/examples/nail
Index: distinfo
===
RCS file: /cvs/ports/mail/s-nail/distinfo,v
retrieving revision 1.13
diff -u -p -r1.13 distinfo
--- distinfo29 Jan 2017 06:08:51 -  1.13
+++ distinfo8 Mar 2018 16:26:49 -
@@ -1,2 +1,2 @@
-SHA256 (s-nail-14.8.16.tar.gz) = xpt0+0scKhokHVOfVTFUpx53TocSI+6AjoY5Zl2bTMo=
-SIZE (s-nail-14.8.16.tar.gz) = 604423
+SHA256 (s-nail-14.9.9.tar.gz) = zb0ni2NPMt+A8i0KP8flmw1fPUGhn+9GOO/LbC0ZhJA=
+SIZE (s-nail-14.9.9.tar.gz) = 885904
Index: patches/patch-nail_rc
===
RCS file: patches/patch-nail_rc
diff -N patches/patch-nail_rc
--- patches/patch-nail_rc   20 Oct 2016 10:49:23 -  1.5
+++ /dev/null   1 Jan 1970 00:00:00 -
@@ -1,14 +0,0 @@
-$OpenBSD: patch-nail_rc,v 1.5 2016/10/20 10:49:23 czarkoff Exp $
-
 nail.rc.orig   Wed Oct  5 12:04:53 2016
-+++ nail.rcSat Oct  8 03:38:20 2016
-@@ -43,6 +43,9 @@ set ask
- # *header* on a per-folder basis (it is meaningless unless *header* is set)
- set bsdannounce
- 
-+# Use the traditional BSD Mail interface style.
-+set bsdcompat
-+
- # Uncomment this in order to get coloured output in $PAGER.
- # (Coloured output is only used if $TERM is either found in *colour-terms*
- # or includes the string "color")
Index: pkg/DESCR
===
RCS file: /cvs/ports/mail/s-nail/pkg/DESCR,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 DESCR
--- pkg/DESCR   29 Mar 2013 03:54:34 -  1.1.1.1
+++ pkg/DESCR   8 Mar 2018 16:26:49 -
@@ -1,5 +1,4 @@
-S-nail is a fork of Heirloom mailx, formerly known as nail.  It is a mail user
-agent derived from Berkeley Mail 8.1 and is intended to provide the
-functionality of the POSIX.2 mailx command with additional support for MIME
-messages, Maildir, POP3, IMAP, SMTP, threading, spam control, and other
-features.
+S-nail provides a simple and friendly environment for sending and receiving
+mail.  It is intended to provide the functionality of the POSIX mailx(1)
+command, but is MIME capable and optionally offers extensions for line 

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Hello Stuart!

Thanks for looking into this.

Stuart Henderson <s...@spacehopper.org> wrote:
 |On 2018/03/08 17:35, Steffen Nurpmeso wrote:
 |> This brings in two and a half years of development and bug fixes.
 |> It has really improved, though a long road is ahead still.
 |> Changelog etc. at: https://www.sdaoden.eu/code-nail-ann.html
 ...
 |> +FIX_EXTRACT_PERMISSIONS=Yes
 |
 |You're upstream aren't you - is there a reason for the unusual
 |permissions in the tar file?

In a future release i will thus create the balls with a different
umask(1) so this should then no longer be necessary.
I gave the credit William (finally) and you (thanks).

 |It picks up idn2 in preference to idn if present at build, so
 |WANTLIB/LIB_DEPENDS needs fixing.

..Ok.. hmm.  I must say i dislike the entire IDN stuff very very
much (if 25 years ago the DNS had some extensions to support
longer labels UTF-8 could be it; even globally), so instead i have
changed the configuration to prefer IDN over IDN2, and added the
changeset as a patch for the OpenBSD port.  I really would prefer
this approach and have no IDN2 around, if possible. ?

 |$ make port-lib-depends-check
 |s-nail-14.9.9(mail/s-nail):
 |Missing lib: idn2.1 (/usr/local/bin/nail) (NOT REACHABLE)
 |Extra:  idn.17

Should work now.

Also i add a fix for a double-free that sneaked into the codebase,
unfortunately.  We have builtin double-free detection, terrible ...

Running "make test" does not work because we verify $HOME is an
accessible directory, which the port framework does not provide.
(The message is "nail: $HOME is not a directory or not accessible:
/s-nail-14.9.9_writes_to_HOME", but we do not write, we only
verify because $HOME is indeed target for several standardized
files which we possibly would need to address.)  Due to that the
error messages invalidate the test checksums.

Running the regression test manually succeeds:

  ?0[steffen@obsd s-nail-14.9.9]$ pwd
  /usr/ports/pobj/s-nail-14.9.9/s-nail-14.9.9
  ?0[steffen@obsd s-nail-14.9.9]$ make test
  /bin/sh ./cc-test.sh --check-only ./nail
...

except for t_behave_attachments which fails because i once again
have made it and escaped a newline in a printf(1) statement (and
did not retest on all platforms after doing so).
Ciao,

Index: Makefile
===
RCS file: /cvs/ports/mail/s-nail/Makefile,v
retrieving revision 1.19
diff -u -p -r1.19 Makefile
--- Makefile8 Dec 2017 01:04:14 -   1.19
+++ Makefile9 Mar 2018 17:31:14 -
@@ -1,45 +1,43 @@
 # $OpenBSD: Makefile,v 1.19 2017/12/08 01:04:14 espie Exp $
 
-COMMENT=   enhanced, MIME capable Berkeley Mail
+COMMENT=   SysV mail/BSD Mail/POSIX mailx: send and receive mail
 
-DISTNAME=  s-nail-14.8.16
-CATEGORIES=mail
-HOMEPAGE=  https://www.sdaoden.eu/code.html\#s-mailx
-FIX_EXTRACT_PERMISSIONS=Yes
+DISTNAME=  s-nail-14.9.9
+CATEGORIES=mail
+HOMEPAGE=  https://www.sdaoden.eu/code.html\#s-mailx
+MAINTAINER=Dmitrij D. Czarkoff <czark...@openbsd.org>
 
 # BSD
-PERMIT_PACKAGE_CDROM=  Yes
-
-WANTLIB += c crypto iconv idn ssl
+PERMIT_PACKAGE_CDROM=Yes
 
-MASTER_SITES=  https://www.sdaoden.eu/downloads/
-MAINTAINER=Dmitrij D. Czarkoff <czark...@openbsd.org>
+MASTER_SITES=  https://ftp.sdaoden.eu/
+# XXX remove FIX_EXTRACT_PERMISSIONS with update to version >14.9.9
+FIX_EXTRACT_PERMISSIONS=Yes
 
-MAKE_FILE= makefile
-MAKE_FLAGS=CC="${CC}" \
-   CFLAGS="${CFLAGS}" \
-   C_INCLUDE_PATH="${LOCALBASE}/include" \
-   LDFLAGS="${LDFLAGS}" \
-   LD_LIBRARY_PATH="${LOCALBASE}/lib" \
-   MANDIR="${PREFIX}/man" \
-   SYSCONFDIR="${SYSCONFDIR}" \
-   WANT_AUTOCC=0 \
-   WANT_EDITLINE=0 \
-   WANT_NCL=1 \
-   WANT_DOTLOCK=0 \
-   SID=
+WANTLIB=   c crypto curses iconv idn ssl
+LIB_DEPENDS=   converters/libiconv \
+   devel/libidn
+# xxx Verifies an accessible $HOME, which "make test" does not provide
+NO_TEST=   Yes
+
+MAKE_FILE= makefile
+MAKE_FLAGS=C_INCLUDE_PATH="${LOCALBASE}/include" \
+   LD_LIBRARY_PATH="${LOCALBASE}/lib" \
+   VAL_MANDIR="${PREFIX}/man" \
+   VAL_SYSCONFDIR="${SYSCONFDIR}" \
+   VAL_SID= \
+   \
+   OPT_AUTOCC=no \
+   OPT_DOTLOCK=no \
+   OPT_SPAM_SPAMC=yes \
+   OPT_SSL_RANDOM=no
 
 .if !empty(DEBUG)
-MAKE_FLAGS+=   WANT_DEBUG=1
-FAKE_FLAGS+=   WANT_DEBUG=1
+MAKE_FLAGS+=   OPT_DEBUG=yes
+FAKE_FLAGS+=   OPT_DEBUG=yes
 .endif
 
-MAKE_EN

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Hello,

i wrote:
 |i wrote:
 ||Stuart Henderson <s...@spacehopper.org> wrote:
 |||On 2018/03/09 18:39, Steffen Nurpmeso wrote:
 |||> Stuart Henderson <s...@spacehopper.org> wrote:
 |||>|On 2018/03/08 17:35, Steffen Nurpmeso wrote:
 |||>|> This brings in two and a half years of development and bug fixes.
 |||>|> It has really improved, though a long road is ahead still.
 |||>|> Changelog etc. at: https://www.sdaoden.eu/code-nail-ann.html
 | ...
 |
 |I have released v14.9.10, the 40th BSD Mail anniversary version.
 |Find below the updated recipe.

four weeks have passed -- is anyone from ports interested in this
(as such that is)?  Or is anything not right, is anything missing?
It is not bad from the feature side, it is stable, and it is
getting better.  Suggestions and bug reports are always welcome.
Would be very much cooler to finally install 6.3 and have a binary
package at a fingertip!

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Oh, hello again Stuart.

Stuart Henderson <s...@spacehopper.org> wrote:
 |On 2018/04/23 18:09, Steffen Nurpmeso wrote:
 |> i wrote:
 |>|i wrote:
 |>||Stuart Henderson <s...@spacehopper.org> wrote:
 |>|||On 2018/03/09 18:39, Steffen Nurpmeso wrote:
 |>|||> Stuart Henderson <s...@spacehopper.org> wrote:
 |>|||>|On 2018/03/08 17:35, Steffen Nurpmeso wrote:
 |>|||>|> This brings in two and a half years of development and bug fixes.
 |>|||>|> It has really improved, though a long road is ahead still.
 |>|||>|> Changelog etc. at: https://www.sdaoden.eu/code-nail-ann.html
 |>| ...
 |>|
 |>|I have released v14.9.10, the 40th BSD Mail anniversary version.
 |>|Find below the updated recipe.
 |> 
 |> four weeks have passed -- is anyone from ports interested in this
 ...
 |Just given this a try (4 weeks ago we were tying up release IIRC,
 |never a good time to send updates if you want them picked up ;)

Yes, i have seen that, then.  Of course, sure.  Thank you.

 |I see it is ignoring CFLAGS and setting its own optimizer levels,
 |this should be under control of ports.

Well, but many autotools based things do so, as well as others.
And it is setting all security related compiler flags it finds
that i know of, except for meltdown/spectre (the latter of) which
does not matter for us as far as i can tell.

But, ok, if the OpenBSD port wants to replace that with a custom
set, all that is needed is to reinclude OPT_AUTOCC=no.  I have
edited this directly into the latter patch.  You know, this box is
so restricted, doing the complete cycle takes hours, i hope it
flies like that.

Index: Makefile
===
RCS file: /cvs/ports/mail/s-nail/Makefile,v
retrieving revision 1.19
diff -u -p -r1.19 Makefile
--- Makefile8 Dec 2017 01:04:14 -   1.19
+++ Makefile26 Mar 2018 18:45:48 -
@@ -1,48 +1,56 @@
 # $OpenBSD: Makefile,v 1.19 2017/12/08 01:04:14 espie Exp $
 
-COMMENT=   enhanced, MIME capable Berkeley Mail
+COMMENT=   SysV mail/BSD Mail/POSIX mailx: send and receive mail
 
-DISTNAME=  s-nail-14.8.16
-CATEGORIES=mail
-HOMEPAGE=  https://www.sdaoden.eu/code.html\#s-mailx
-FIX_EXTRACT_PERMISSIONS=Yes
+DISTNAME=  s-nail-14.9.10
+CATEGORIES=mail
+FLAVORS=   idna
+HOMEPAGE=  https://www.sdaoden.eu/code.html\#s-mailx
+MAINTAINER=Dmitrij D. Czarkoff <czark...@openbsd.org>
 
+MASTER_SITES=  https://ftp.sdaoden.eu/
 # BSD
-PERMIT_PACKAGE_CDROM=  Yes
+PERMIT_PACKAGE_CDROM=Yes
 
-WANTLIB += c crypto iconv idn ssl
-
-MASTER_SITES=  https://www.sdaoden.eu/downloads/
-MAINTAINER=Dmitrij D. Czarkoff <czark...@openbsd.org>
-
-MAKE_FILE= makefile
-MAKE_FLAGS=CC="${CC}" \
-   CFLAGS="${CFLAGS}" \
-   C_INCLUDE_PATH="${LOCALBASE}/include" \
-   LDFLAGS="${LDFLAGS}" \
-   LD_LIBRARY_PATH="${LOCALBASE}/lib" \
-   MANDIR="${PREFIX}/man" \
-   SYSCONFDIR="${SYSCONFDIR}" \
-   WANT_AUTOCC=0 \
-   WANT_EDITLINE=0 \
-   WANT_NCL=1 \
-   WANT_DOTLOCK=0 \
-   SID=
+FLAVOR?=
+WANTLIB=   c crypto curses iconv ssl
+LIB_DEPENDS=   converters/libiconv
+
+CONFIG_ADDS=
+
+.if ${FLAVOR:Midna}
+WANTLIB+=  idn2
+LIB_DEPENDS+=  devel/libidn2
+CONFIG_ADDS+=  OPT_IDNA=yes VAL_IDNA=idn2
+.else
+CONFIG_ADDS+=  OPT_IDNA=no
+.endif
 
 .if !empty(DEBUG)
-MAKE_FLAGS+=   WANT_DEBUG=1
-FAKE_FLAGS+=   WANT_DEBUG=1
+CONFIG_ADDS+=  OPT_DEBUG=yes
+FAKE_FLAGS+=   OPT_DEBUG=yes
 .endif
 
-MAKE_ENV=  VERBOSE=Yes
-
-LIB_DEPENDS=   converters/libiconv \
-   devel/libidn
-
-INSTALL_TARGET=packager-install
+PORTHOME=  ${WRKDIR}
+MAKE_FILE= makefile
+MAKE_ENV=  VERBOSE=anynonempty
+MAKE_FLAGS=C_INCLUDE_PATH="${LOCALBASE}/include" \
+   LD_LIBRARY_PATH="${LOCALBASE}/lib" \
+   VAL_MANDIR="${PREFIX}/man" \
+   VAL_SYSCONFDIR="${SYSCONFDIR}" \
+   VAL_SID= \
+   \
+   OPT_ALWAYS_UNICODE_LOCALE=yes \
+   OPT_AGENT=no \
+   OPT_AUTOCC=no OPT_DOTLOCK=no \
+   OPT_GSSAPI=no \
+   \
+   VAL_RANDOM=arc4 \
+   \
+   ${CONFIG_ADDS}
 
 post-install:
${INSTALL_DATA_DIR} ${PREFIX}/share/examples/nail
-   mv ${DESTDIR}${SYSCONFDIR}/nail.rc ${PREFIX}/share/examples/nail
+   mv ${DESTDIR}${SYSCONFDIR}/nail.rc ${PREFIX}/share/examples/nail/
 
 .include 
Index: distinfo

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Stuart Henderson <s...@spacehopper.org> wrote:
 |On 2018/04/23 19:36, Steffen Nurpmeso wrote:
 |> Stuart Henderson <s...@spacehopper.org> wrote:
 |>|On 2018/04/23 18:09, Steffen Nurpmeso wrote:
 |>|> i wrote:
 |>|>|i wrote:
 |>|>||Stuart Henderson <s...@spacehopper.org> wrote:
 |>|>|||On 2018/03/09 18:39, Steffen Nurpmeso wrote:
 |>|>|||> Stuart Henderson <s...@spacehopper.org> wrote:
 |>|>|||>|On 2018/03/08 17:35, Steffen Nurpmeso wrote:
 |>|>|||>|> This brings in two and a half years of development and bug fixes.
 |>|>|||>|> It has really improved, though a long road is ahead still.
 |>|>|||>|> Changelog etc. at: https://www.sdaoden.eu/code-nail-ann.html
 |>|>| ...
 |>|>|
 |>|>|I have released v14.9.10, the 40th BSD Mail anniversary version.
 |>|>|Find below the updated recipe.
 |>|> 
 |>|> four weeks have passed -- is anyone from ports interested in this
 ...
 |>|I see it is ignoring CFLAGS and setting its own optimizer levels,
 |>|this should be under control of ports.
 |> 
 |> Well, but many autotools based things do so, as well as others.
 |
 |Yes, and we usually patch them out where we notice them.

Yes, fine; 'just want to mention you could overwrite any
last-occurrence-wins flag by setting EXTRA_CFLAGS, for example
EXTRA_CFLAGS=-Os.

 |> And it is setting all security related compiler flags it finds
 |> that i know of, except for meltdown/spectre (the latter of) which
 |> does not matter for us as far as i can tell.
 |
 |The ones that are generally reliable on an arch are already enabled
 |by default in the compiler, some arches have problems with certain
 |of these features and in those cases the default is not to use them.

hmhmm.  hm :)

 |> But, ok, if the OpenBSD port wants to replace that with a custom
 |> set, all that is needed is to reinclude OPT_AUTOCC=no.  I have
 |> edited this directly into the latter patch.  You know, this box is
 |> so restricted, doing the complete cycle takes hours, i hope it
 |> flies like that.
 |
 |Here's an updated version that puts back most of the unnecessary
 |changes to Makefile (ordering, whitespace etc).
 |
 |Dmitrij, are you around? Want to test or shall I just go ahead?

Thank you for taking action!

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

i wrote:
 |Stuart Henderson <s...@spacehopper.org> wrote:
 ||On 2018/03/09 18:39, Steffen Nurpmeso wrote:
 ||> Stuart Henderson <s...@spacehopper.org> wrote:
 ||>|On 2018/03/08 17:35, Steffen Nurpmeso wrote:
 ||>|> This brings in two and a half years of development and bug fixes.
 ||>|> It has really improved, though a long road is ahead still.
 ||>|> Changelog etc. at: https://www.sdaoden.eu/code-nail-ann.html
 ...

I have released v14.9.10, the 40th BSD Mail anniversary version.
Find below the updated recipe.
Thanks already here, your

Index: Makefile
===
RCS file: /cvs/ports/mail/s-nail/Makefile,v
retrieving revision 1.19
diff -u -p -r1.19 Makefile
--- Makefile8 Dec 2017 01:04:14 -   1.19
+++ Makefile26 Mar 2018 18:45:48 -
@@ -1,48 +1,56 @@
 # $OpenBSD: Makefile,v 1.19 2017/12/08 01:04:14 espie Exp $
 
-COMMENT=   enhanced, MIME capable Berkeley Mail
+COMMENT=   SysV mail/BSD Mail/POSIX mailx: send and receive mail
 
-DISTNAME=  s-nail-14.8.16
-CATEGORIES=mail
-HOMEPAGE=  https://www.sdaoden.eu/code.html\#s-mailx
-FIX_EXTRACT_PERMISSIONS=Yes
+DISTNAME=  s-nail-14.9.10
+CATEGORIES=mail
+FLAVORS=   idna
+HOMEPAGE=  https://www.sdaoden.eu/code.html\#s-mailx
+MAINTAINER=Dmitrij D. Czarkoff <czark...@openbsd.org>
 
+MASTER_SITES=  https://ftp.sdaoden.eu/
 # BSD
-PERMIT_PACKAGE_CDROM=  Yes
+PERMIT_PACKAGE_CDROM=Yes
 
-WANTLIB += c crypto iconv idn ssl
-
-MASTER_SITES=  https://www.sdaoden.eu/downloads/
-MAINTAINER=Dmitrij D. Czarkoff <czark...@openbsd.org>
-
-MAKE_FILE= makefile
-MAKE_FLAGS=CC="${CC}" \
-   CFLAGS="${CFLAGS}" \
-   C_INCLUDE_PATH="${LOCALBASE}/include" \
-   LDFLAGS="${LDFLAGS}" \
-   LD_LIBRARY_PATH="${LOCALBASE}/lib" \
-   MANDIR="${PREFIX}/man" \
-   SYSCONFDIR="${SYSCONFDIR}" \
-   WANT_AUTOCC=0 \
-   WANT_EDITLINE=0 \
-   WANT_NCL=1 \
-   WANT_DOTLOCK=0 \
-   SID=
+FLAVOR?=
+WANTLIB=   c crypto curses iconv ssl
+LIB_DEPENDS=   converters/libiconv
+
+CONFIG_ADDS=
+
+.if ${FLAVOR:Midna}
+WANTLIB+=  idn2
+LIB_DEPENDS+=  devel/libidn2
+CONFIG_ADDS+=  OPT_IDNA=yes VAL_IDNA=idn2
+.else
+CONFIG_ADDS+=  OPT_IDNA=no
+.endif
 
 .if !empty(DEBUG)
-MAKE_FLAGS+=   WANT_DEBUG=1
-FAKE_FLAGS+=   WANT_DEBUG=1
+CONFIG_ADDS+=  OPT_DEBUG=yes
+FAKE_FLAGS+=   OPT_DEBUG=yes
 .endif
 
-MAKE_ENV=  VERBOSE=Yes
-
-LIB_DEPENDS=   converters/libiconv \
-   devel/libidn
-
-INSTALL_TARGET=packager-install
+PORTHOME=  ${WRKDIR}
+MAKE_FILE= makefile
+MAKE_ENV=  VERBOSE=anynonempty
+MAKE_FLAGS=C_INCLUDE_PATH="${LOCALBASE}/include" \
+   LD_LIBRARY_PATH="${LOCALBASE}/lib" \
+   VAL_MANDIR="${PREFIX}/man" \
+   VAL_SYSCONFDIR="${SYSCONFDIR}" \
+   VAL_SID= \
+   \
+   OPT_ALWAYS_UNICODE_LOCALE=yes \
+   OPT_AGENT=no \
+   OPT_DOTLOCK=no \
+   OPT_GSSAPI=no \
+   \
+   VAL_RANDOM=arc4 \
+   \
+   ${CONFIG_ADDS}
 
 post-install:
${INSTALL_DATA_DIR} ${PREFIX}/share/examples/nail
-   mv ${DESTDIR}${SYSCONFDIR}/nail.rc ${PREFIX}/share/examples/nail
+   mv ${DESTDIR}${SYSCONFDIR}/nail.rc ${PREFIX}/share/examples/nail/
 
 .include 
Index: distinfo
===
RCS file: /cvs/ports/mail/s-nail/distinfo,v
retrieving revision 1.13
diff -u -p -r1.13 distinfo
--- distinfo29 Jan 2017 06:08:51 -  1.13
+++ distinfo26 Mar 2018 18:45:48 -
@@ -1,2 +1,2 @@
-SHA256 (s-nail-14.8.16.tar.gz) = xpt0+0scKhokHVOfVTFUpx53TocSI+6AjoY5Zl2bTMo=
-SIZE (s-nail-14.8.16.tar.gz) = 604423
+SHA256 (s-nail-14.9.10.tar.gz) = h63nu+sRAlCvzoIhsrtVOj2WYTJ9/KP2IplPsBfEnMs=
+SIZE (s-nail-14.9.10.tar.gz) = 895283
Index: patches/patch-nail_rc
===
RCS file: patches/patch-nail_rc
diff -N patches/patch-nail_rc
--- patches/patch-nail_rc   20 Oct 2016 10:49:23 -  1.5
+++ /dev/null   1 Jan 1970 00:00:00 -
@@ -1,14 +0,0 @@
-$OpenBSD: patch-nail_rc,v 1.5 2016/10/20 10:49:23 czarkoff Exp $
-
 nail.rc.orig   Wed Oct  5 12:04:53 2016
-+++ nail.rcSat Oct  8 03:38:20 2016
-@@ -43,6 +43,9 @@ set ask
- # *header* on a per-folder basis (it is meaningless unless *header* is set)
- set bsdannounce
- 
-+# Use the traditional BSD Mail interface style.
-+set bsdcompat
-+
- # Unc

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

P.S.: unplanned but nice coincidence: according to marc.info this
was message 444 on openbsd-ports@ this month.. which is the very
number of the S-nail project on Coverity.com!

Ciao,

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Hello.

Steffen Nurpmeso wrote in <20180817153001.krprc%stef...@sdaoden.eu>:
 |Steffen Nurpmeso wrote in <20180809203425.2sjei%stef...@sdaoden.eu>:
 ||Update to v14.9.11 ("Tit family enjoying a bath") with many many
 ||bugfixes and some new features like message info "from the front":
 ||
 ||  ? digmsg create 1 -;digmsg 1 header show from; digmsg remove 1
 |
 |In no way i wanna push forward anything, 'just want to mention
 |that, last time i tried, "set mta-no-receiver-arguments" in some
 |.mailrc was helpful; this was introduced in October 2017
 |specifically to deal with OpenSMTPD 6.0.2p1, because i found it
 |"joins command line arguments onto receivers given in the message,
 |which can result in multiple deliveries to the same addressee".
 |In case someone stumbles upon this.

Today is the 65th anniversary of the Kinsey report, and i thought
that could be a good time to contact OpenBSD, ..and ask whether
someone would be so kind and rubber-stamp this update.
Thanks and Ciao,

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Landry Breuil wrote in <20180915075116.gj46...@twilight.rhaalovely.net>:
 |On Fri, Sep 14, 2018 at 10:26:06PM +0100, Stuart Henderson wrote:
 |> I think it might be a good idea if Steffen takes over as MAINTAINER \
 |> for this port ..
 |
 |In the meantime ive pushed the update - but sure :)
 --End of <20180915075116.gj46...@twilight.rhaalovely.net>

Thank you very much, Stuart and Landry!
Will update accordingly next time.
Ciao, and a nice Sunday everybody,

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

UPDATE mail/s-nail

[Steffen Nurpmeso]

Hello and a good Friday evening,

please find below an update to S-nail v14.9.13.
It appeared to me that it would be ok to take maintainership,
i have thus adjusted that line.

Many bugfixes, long options, -Y aka --cmd "is" user input (see
NEWS for more); backward incompatible changes, but with a lot of
legacy support (until v15; -v or even -d show warnings).

Ciao!

Index: Makefile
===
RCS file: /cvs/ports/mail/s-nail/Makefile,v
retrieving revision 1.21
diff -u -p -r1.21 Makefile
--- Makefile14 Sep 2018 17:52:08 -  1.21
+++ Makefile8 Mar 2019 20:52:13 -
@@ -2,7 +2,7 @@
 
 COMMENT=   SysV mail/BSD Mail/POSIX mailx: send and receive mail
 
-DISTNAME=  s-nail-14.9.11
+DISTNAME=  s-nail-14.9.13
 CATEGORIES=mail
 HOMEPAGE=  https://www.sdaoden.eu/code.html\#s-mailx
 
@@ -12,7 +12,7 @@ PERMIT_PACKAGE_CDROM= Yes
 WANTLIB += c crypto curses iconv ssl
 
 MASTER_SITES=  https://ftp.sdaoden.eu/
-MAINTAINER=Dmitrij D. Czarkoff 
+MAINTAINER=        Steffen Nurpmeso 
 
 FLAVORS=   idna
 FLAVOR?=
Index: distinfo
===
RCS file: /cvs/ports/mail/s-nail/distinfo,v
retrieving revision 1.15
diff -u -p -r1.15 distinfo
--- distinfo14 Sep 2018 17:52:08 -  1.15
+++ distinfo8 Mar 2019 20:52:13 -
@@ -1,2 +1,2 @@
-SHA256 (s-nail-14.9.11.tar.gz) = J5ICaHQJuOe08mfheK7RvUxot5wBwQuA8HGX8vc9ZpU=
-SIZE (s-nail-14.9.11.tar.gz) = 926261
+SHA256 (s-nail-14.9.13.tar.gz) = bP7tVRuqERax0pXjwHATRFl/rxKpdHqDYwkrgJZK5Gg=
+SIZE (s-nail-14.9.13.tar.gz) = 1005355

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Stuart Henderson wrote in <2019040606.gf19...@symphytum.spacehopper.org>:
 |On 2019/04/10 23:39, Steffen Nurpmeso wrote:
 |> Ingo Schwarze wrote in <20190410160613.gb73...@athene.usta.de>:
 |>|Steffen Nurpmeso wrote on Wed, Apr 10, 2019 at 05:39:38PM +0200:
 |>|> Steffen Nurpmeso wrote in <20190308210521.7ybvy%stef...@sdaoden.eu>:
 |>|
 |>|>> please find below an update to S-nail v14.9.13.
 |>|
 |>|> would someone be so kind an wave that through, please?
 |>|
 |>|No, absolutely not.  The trees are locked for release.
 |> 
 |> Oh, c rap.
 |> 
 |> Then we have to wait some more.
 |> (Except v14.9.13 is better than v14.9.11.  Hm.)
 |
 |It's OK, we don't plan to stop at 6.5.

It would be a pity otherwise.  Now that i have this supercomputer
with NVME and 8 GB RAM etc. i expect to be able to simply hit
return after installation, instead of going through painful ed
experiences to comment out further kernel relinking.

 --End of <2019040606.gf19...@symphytum.spacehopper.org>

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Ingo Schwarze wrote in <20190410160613.gb73...@athene.usta.de>:
 |Steffen Nurpmeso wrote on Wed, Apr 10, 2019 at 05:39:38PM +0200:
 |> Steffen Nurpmeso wrote in <20190308210521.7ybvy%stef...@sdaoden.eu>:
 |
 |>> please find below an update to S-nail v14.9.13.
 |
 |> would someone be so kind an wave that through, please?
 |
 |No, absolutely not.  The trees are locked for release.

Oh, c rap.

Then we have to wait some more.
(Except v14.9.13 is better than v14.9.11.  Hm.)

 --End of <20190410160613.gb73...@athene.usta.de>

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Hello Solene!

Solene Rapenne wrote in <20190417175408.6ps6zdcv4pmozj34@solene.perso.local>:
 |On 2019/04/10 23:39, Steffen Nurpmeso wrote:
 |> Ingo Schwarze wrote in <20190410160613.gb73...@athene.usta.de>:
 |>|Steffen Nurpmeso wrote on Wed, Apr 10, 2019 at 05:39:38PM +0200:
 |>|> Steffen Nurpmeso wrote in <20190308210521.7ybvy%stef...@sdaoden.eu>:
 |>|
 |>|>> please find below an update to S-nail v14.9.13.
 |>|
 |>|> would someone be so kind an wave that through, please?
 |>|
 |>|No, absolutely not.  The trees are locked for release.
 |> 
 |> Oh, c rap.
 |> 
 |> Then we have to wait some more.
 |> (Except v14.9.13 is better than v14.9.11.  Hm.)
 |
 |builds fine, flavor builds fine.

Thanks for trying out!

 |Seems to work from the quick tests I did.

I hope so.

Fun fact: this very morning i have seen the first (several)
Roman snails here in Germany/Hessen/Darmstadt!

 |ok solene@

Great.

 --End of <20190417175408.6ps6zdcv4pmozj34@solene.perso.local>

Have a good time, ciao,

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Hello OpenBSD.

Steffen Nurpmeso wrote in <20190308210521.7ybvy%stef...@sdaoden.eu>:
 |Hello and a good Friday evening,
 |
 |please find below an update to S-nail v14.9.13.

would someone be so kind an wave that through, please?
We don't want to stand back. ^_^

 |It appeared to me that it would be ok to take maintainership,
 |i have thus adjusted that line.
 |
 |Many bugfixes, long options, -Y aka --cmd "is" user input (see
 |NEWS for more); backward incompatible changes, but with a lot of
 |legacy support (until v15; -v or even -d show warnings).

And it really fixes and improves a lot, visible or not.

Thank you all.

  ...
 |Index: Makefile
 |===
 |RCS file: /cvs/ports/mail/s-nail/Makefile,v
 |retrieving revision 1.21
 |diff -u -p -r1.21 Makefile
 |--- Makefile  14 Sep 2018 17:52:08 -  1.21
 |+++ Makefile  8 Mar 2019 20:52:13 -
 |@@ -2,7 +2,7 @@
 | 
 | COMMENT= SysV mail/BSD Mail/POSIX mailx: send and receive mail
 | 
 |-DISTNAME=s-nail-14.9.11
 |+DISTNAME=s-nail-14.9.13
 | CATEGORIES=  mail
 | HOMEPAGE=https://www.sdaoden.eu/code.html\#s-mailx
 | 
 |@@ -12,7 +12,7 @@ PERMIT_PACKAGE_CDROM=   Yes
 | WANTLIB += c crypto curses iconv ssl
 | 
 | MASTER_SITES=https://ftp.sdaoden.eu/
 |-MAINTAINER=  Dmitrij D. Czarkoff 
 |+MAINTAINER=  Steffen Nurpmeso 
 | 
 | FLAVORS= idna
 | FLAVOR?=
 |Index: distinfo
 |===
 |RCS file: /cvs/ports/mail/s-nail/distinfo,v
 |retrieving revision 1.15
 |diff -u -p -r1.15 distinfo
 |--- distinfo  14 Sep 2018 17:52:08 -  1.15
 |+++ distinfo  8 Mar 2019 20:52:13 -
 |@@ -1,2 +1,2 @@
 |-SHA256 (s-nail-14.9.11.tar.gz) = J5ICaHQJuOe08mfheK7RvUxot5wBwQuA8HGX8v\
 |c9ZpU=
 |-SIZE (s-nail-14.9.11.tar.gz) = 926261
 |+SHA256 (s-nail-14.9.13.tar.gz) = bP7tVRuqERax0pXjwHATRFl/rxKpdHqDYwkrgJ\
 |ZK5Gg=
 |+SIZE (s-nail-14.9.13.tar.gz) = 1005355
 ...
 --End of <20190308210521.7ybvy%stef...@sdaoden.eu>

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Steffen Nurpmeso wrote in <20190819163311.iyjzz%stef...@sdaoden.eu>:
  ...
 |  followup-to-add-cc variable that this message will stress,

You need to set it, of course.

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Hello ports@!

Please find below an update to S-nail v14.9.15, the (likely) last
in the v14.9 series.
You get test parallelization if you use -j with a number (greater
than 1 say), or no -j at all.

Fixes a bug present in all BSD Mails and Unix v10 mail regarding
handling of invalid MBOX database files: in cmd2.c:save1(), after
sendmessage() (and once initially) "mbox_prepare_append()" must be
called (separation must be ensured).

  EXTERNANON authentication to overcome deficient EXTERNAL server
  implementations (the web is broken!), GSS-API for POP3, nice
  followup-to-add-cc variable that this message will stress,
  automatic "name" to "name@host" expansion with
  expandaddr=namehostex etc.
  Note on-account-cleanup hook now runs even on-program-exit.

Thanks for your consideration.

Index: Makefile
===
RCS file: /cvs/ports/mail/s-nail/Makefile,v
retrieving revision 1.24
diff -u -p -r1.24 Makefile
--- Makefile29 Jul 2019 20:23:41 -  1.24
+++ Makefile19 Aug 2019 16:07:37 -
@@ -2,12 +2,12 @@
 
 COMMENT=   SysV mail/BSD Mail/POSIX mailx: send and receive mail
 
-DISTNAME=  s-nail-14.9.14
+DISTNAME=  s-nail-14.9.15
 CATEGORIES=mail
 HOMEPAGE=  https://www.sdaoden.eu/code.html\#s-mailx
 
 # BSD
-PERMIT_PACKAGE=Yes
+PERMIT_PACKAGE_CDROM=  Yes
 
 WANTLIB += c crypto curses iconv ssl
 
Index: distinfo
===
RCS file: /cvs/ports/mail/s-nail/distinfo,v
retrieving revision 1.17
diff -u -p -r1.17 distinfo
--- distinfo29 Jul 2019 20:23:41 -  1.17
+++ distinfo19 Aug 2019 16:07:37 -
@@ -1,2 +1,2 @@
-SHA256 (s-nail-14.9.14.tar.gz) = 8OMnUnTJPzdW+6bFjKU/Bbn6L4m624Z4YIs3LZPqUQw=
-SIZE (s-nail-14.9.14.tar.gz) = 1033460
+SHA256 (s-nail-14.9.15.tar.gz) = TEux2uD9btq/HSaKxqR23pqrPBW0u+IUFUmhHb8rrnM=
+SIZE (s-nail-14.9.15.tar.gz) = 1036102

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Hello Stuart.

Stuart Henderson wrote in <20190820095908.gy32...@symphytum.spacehopper.org>:
 |On 2019/08/19 18:33, Steffen Nurpmeso wrote:
 |> Please find below an update to S-nail v14.9.15, the (likely) last
 |> in the v14.9 series.
 ...
 |> Index: Makefile
 |> ===
 |> RCS file: /cvs/ports/mail/s-nail/Makefile,v
 |> retrieving revision 1.24
 |> diff -u -p -r1.24 Makefile
 |> --- Makefile29 Jul 2019 20:23:41 -  1.24
 |> +++ Makefile19 Aug 2019 16:07:37 -
 |> @@ -2,12 +2,12 @@
 |>  
 |>  COMMENT=   SysV mail/BSD Mail/POSIX mailx: send and receive mail
 |>  
 |> -DISTNAME=  s-nail-14.9.14
 |> +DISTNAME=  s-nail-14.9.15
 |>  CATEGORIES=mail
 |>  HOMEPAGE=  https://www.sdaoden.eu/code.html\#s-mailx
 |>  
 |>  # BSD
 |> -PERMIT_PACKAGE=Yes
 |> +PERMIT_PACKAGE_CDROM=  Yes
 |
 |That needs to stay.

Ok.  It was just that i got myriads of

  The licensing info for s-nail-14.9.15 is incomplete. (in mail/s-nail)
  The licensing info for s-nail-14.9.15 is incomplete. (in mail/s-nail)
  Please notify the OpenBSD port maintainer: (in mail/s-nail)

which lead me to bsd.port.mk and the change above.
And since my update script always does

  (cd ports && cvs -q up $VERSION -PR infrastructure) || exit 5

Ah, maybe i just have to create a -current VM for further package
updates, instead of going $VERSION, it is hacky anyway to update
a package in that 6.5 release environment, i'd say.

 |I'll commit the rest shortly.

Great, thank you Stuart.

Ciao,

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

UPDATE mail/s-nail

[Steffen Nurpmeso]

Hello.

Please find below an update to S-nail v14.9.14.

Fixes GSSAPI for IMAP, adds XOAUTH2/OAUTHBEARER, and for OpenBSD
in particular it fixes long standing (must be) race conditions
regarding child processes and their I/O setup, revealed by my new
hardware (i stepped a decade of hardware improvements).

  Funnily the problem (child descriptors were closed by the parent
  before the fork(2)ed childs had the opportunity to dup(2)licate
  their file descriptors) reminded me of a message of the german
  computer magazine c't, maybe around 2001/2002, when OpenBSD
  improved their fork(2) performance in a day or two after having
  appeared declassified in a comparison with other OSes.
  (Of course it was nothing but our own fault to not synchronize on
  the child, but blindly assuming that a fork(2) child gets the
  opportunity to run immediately.)

Also the tests now take care for OSs which favour the foreground
exec flow, and waits for async files to appear as necessary (since
*sendwait* now set by default and meaning-extended, not much
remained necessary here, though).

Thanks for your consideration, and
Ciao!


Index: Makefile
===
RCS file: /cvs/ports/mail/s-nail/Makefile,v
retrieving revision 1.23
diff -u -p -r1.23 Makefile
--- Makefile12 Jul 2019 20:47:37 -  1.23
+++ Makefile29 Jul 2019 16:32:41 -
@@ -2,7 +2,7 @@
 
 COMMENT=   SysV mail/BSD Mail/POSIX mailx: send and receive mail
 
-DISTNAME=  s-nail-14.9.13
+DISTNAME=  s-nail-14.9.14
 CATEGORIES=mail
 HOMEPAGE=  https://www.sdaoden.eu/code.html\#s-mailx
 
Index: distinfo
===
RCS file: /cvs/ports/mail/s-nail/distinfo,v
retrieving revision 1.16
diff -u -p -r1.16 distinfo
--- distinfo17 Apr 2019 19:43:32 -  1.16
+++ distinfo29 Jul 2019 16:32:41 -
@@ -1,2 +1,2 @@
-SHA256 (s-nail-14.9.13.tar.gz) = bP7tVRuqERax0pXjwHATRFl/rxKpdHqDYwkrgJZK5Gg=
-SIZE (s-nail-14.9.13.tar.gz) = 1005355
+SHA256 (s-nail-14.9.14.tar.gz) = 8OMnUnTJPzdW+6bFjKU/Bbn6L4m624Z4YIs3LZPqUQw=
+SIZE (s-nail-14.9.14.tar.gz) = 1033460

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Stuart Henderson wrote in <20190729202349.ge12...@symphytum.spacehopper.org>:
 |On 2019/07/29 18:56, Steffen Nurpmeso wrote:
 |> Hello.
 |> 
 |> Please find below an update to S-nail v14.9.14.
 |
 |Thanks, committed.

Oh, wow wow, not that i get cardiac dysrhythmia because it is all
too sudden!!

  ...
 |>   Funnily the problem (child descriptors were closed by the parent
 |>   before the fork(2)ed childs had the opportunity to dup(2)licate
 |>   their file descriptors) reminded me of a message of the german

What i meant was, the file gets unlinked, and so the child reads
an immediate EOF.

Really fantastic, thank you very much, Stuart!
Ciao!

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: NEW: mb2md

[Steffen Nurpmeso]

Todd C. Miller wrote in :
 |mb2md is a utility to convert mbox mailboxes to Maildir format.
 |Since there has been talk of changing the default mailbox format
 |for smtpd, it would be nice to have a conversion program in ports.
 |
 |I've included patches from debian and created a basic man page from
 |the documentation in the script itself.  I'm not really interested
 |in taking the time to make the man page beautiful.  If someone else
 |is so inclined, more power to them...

Btw., you could also use s-nail, which is already in ports:

  s-nail -Rf#:/ \
-Y 'copy * maildir:///tmp/f.mdir;xit' \
mbox:///tmp/f.mbox

The mbox:// in the latter is optional, the maildir:// not really.
(Depends.)

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

UPDATE mail/s-nail

[Steffen Nurpmeso]

Hello again,

update to v14.9.17, mostly due to two fixes and a general review
of key-`bind'ings.

Thanks for your consideration!

Index: Makefile
===
RCS file: /cvs/ports/mail/s-nail/Makefile,v
retrieving revision 1.27
diff -u -p -r1.27 Makefile
--- Makefile31 Dec 2019 22:51:41 -  1.27
+++ Makefile3 Feb 2020 17:47:00 -
@@ -2,15 +2,15 @@
 
 COMMENT=   SysV mail/BSD Mail/POSIX mailx: send and receive mail
 
-DISTNAME=  s-nail-14.9.16
+DISTNAME=  s-nail-14.9.17
 REVISION=  0
 CATEGORIES=mail
 HOMEPAGE=  https://www.sdaoden.eu/code.html\#s-mailx
 
 # BSD
-PERMIT_PACKAGE=Yes
+PERMIT_PACKAGE=Yes
 
-WANTLIB += c crypto curses iconv ssl
+WANTLIB+=  c crypto curses iconv ssl
 
 MASTER_SITES=  https://ftp.sdaoden.eu/
 MAINTAINER=Steffen Nurpmeso 
Index: distinfo
===
RCS file: /cvs/ports/mail/s-nail/distinfo,v
retrieving revision 1.19
diff -u -p -r1.19 distinfo
--- distinfo31 Dec 2019 22:50:05 -  1.19
+++ distinfo3 Feb 2020 17:47:00 -
@@ -1,2 +1,2 @@
-SHA256 (s-nail-14.9.16.tar.gz) = 6tdv3+YquK8P2w3a2fi4QZeqsYge0V6y+mVFcqjLvu0=
-SIZE (s-nail-14.9.16.tar.gz) = 1075490
+SHA256 (s-nail-14.9.17.tar.gz) = +U7rZKnp6Do28QM3eh7zFQcOpjiKiq70palD/SZg3yY=
+SIZE (s-nail-14.9.17.tar.gz) = 1077377
Index: patches/patch-include_su_code_h
===
RCS file: patches/patch-include_su_code_h
diff -N patches/patch-include_su_code_h
--- patches/patch-include_su_code_h 31 Dec 2019 22:50:05 -  1.1
+++ /dev/null   1 Jan 1970 00:00:00 -
@@ -1,39 +0,0 @@
-$OpenBSD: patch-include_su_code_h,v 1.1 2019/12/31 22:50:05 sthen Exp $
-
-commit 0eb2314c
-Author: Steffen Nurpmeso 
-AuthorDate: 2019-12-31 20:34:34 +0100
-Commit: Steffen Nurpmeso 
-CommitDate: 2019-12-31 20:34:52 +0100
-
-FIX clang: not inlining with <-O2; comment out _Alignof() usage

- include/su/code.h | 8 +---
- 1 file changed, 5 insertions(+), 3 deletions(-)
-
-diff --git a/include/su/code.h b/include/su/code.h
-index 6e6cd74c..af1e5a30 100644
 include/su/code.h
-+++ include/su/code.h
-@@ -470,8 +470,9 @@ do{\
- #define su_INLINE static inline
- #define su_SINLINE static inline
- #   else
--#define su_INLINE inline
--#define su_SINLINE static inline
-+ /* clang does not like inline with <-O2 */
-+#define su_INLINE inline __attribute__((always_inline))
-+#define su_SINLINE static inline __attribute__((always_inline))
- #   endif
- #  else
- #   define su_INLINE static __inline
-@@ -534,7 +535,8 @@ do{\
- #define su_ROUND_UP2(X,BASE) (((X) + ((BASE) - 1)) & (~((BASE) - 1)))
- 
- /* Alignment.  Note: su_uz POW2 asserted in POD section below! */
--#if defined __STDC_VERSION__ && __STDC_VERSION__ +0 >= 201112L
-+/* Commented out: "_Alignof() applied to an expression is a GNU extension" */
-+#if 0 && defined __STDC_VERSION__ && __STDC_VERSION__ +0 >= 201112L
- # include 
- # define su_ALIGNOF(X) _Alignof(X)
- #else

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Hello.

Steffen Nurpmeso wrote in
<20200203180923.xuph6%stef...@sdaoden.eu>:
 |update to v14.9.17, mostly due to two fixes and a general review
 |of key-`bind'ings.

You would also get the new reply-to-swap-in[=mlist] variable which
help with all those "x via y" mailing-lists.  (Which i really,
really hate.)
Ah, and Coverity.com we have filled the gap and are on par with
sudo's 0.00!

 |Thanks for your consideration!

Juu-huuu!

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Hello Solene, Stuart, all,

Steffen Nurpmeso wrote in <20200101185504.oa5hk%stef...@sdaoden.eu>:
 |Solene Rapenne wrote in <20191231233617.31a04...@t400.my.domain>:
 ||Le Tue, 31 Dec 2019 20:55:02 +0100,
 ||Steffen Nurpmeso  a écrit :
 ||> An update to v14.9.16.  Mailcap support etc., many fixes.
 | ...
 ||hi, portcheck(1) reports this error but I'm unsure why
 ...
 |Stuart Henderson wrote in <20191231225753.GC70067@symphytum.spacehopper.\
 |org>:
 ...
 ||good catch,
 ...
 ||
 ||The second LIB_DEPENDS with = not += hides the first one. (see
 ||"make show=LIB_DEPENDS").
 |
 |!!  Indeed.  Fixed in the below.
 |
 ||The "Missing library" is because there's no valid dependency path to the
 ||idn2 entry in WANTLIB.
 ||
 ||portcheck's "masked by RUN_DEPENDS" message is bogus but that's not really
 ||unusual :)
 |
 |This i do not understand.  What can i do to address this?
 |
 |Anyway, the idna flavour also does compile and test fine with the
 |below.

I see now it was already committed by then!
Thank you all, and

Ciao,

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Stuart Henderson wrote in <20200103132436.ge11...@symphytum.spacehopper.org>:
 |Since you have a script anyway, it would be worth adding "make port-lib-\
 |depends-check",

Ok.

 |and tests for FLAVOR=idna.

"With this box i can do this."  (At first i did not realize that
"pkg_add MYDEP" and "cvs checkout ports/MYDEP" is enough,
i thought the the port had to be build, too.  And building libidn2
took many hours on my former box.  So that.)

Will do!  (Will read first.o)

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

UPDATE mail/s-nail

[Steffen Nurpmeso]

Hello ports@.

An update to v14.9.16.  Mailcap support etc., many fixes.

Now really parallelizes tests even on OpenBSD even without -j
make flag.  Unfortunately needs a patch since i broke clang
(non-) inlining for levels <-O1 (that "rework that false INLINE
sauce" was .. false).  But i assumed OpenBSD does not like
OPT_AUTOGCC still, even if it enables a lot of security related
compile time flags :).

Thanks for your consideration, and a hopefully

Happy new year 2020.

Ciao from Germany!

Index: Makefile
===
RCS file: /cvs/ports/mail/s-nail/Makefile,v
retrieving revision 1.25
diff -u -p -r1.25 Makefile
--- Makefile20 Aug 2019 09:59:59 -  1.25
+++ Makefile31 Dec 2019 19:46:16 -
@@ -2,7 +2,7 @@
 
 COMMENT=   SysV mail/BSD Mail/POSIX mailx: send and receive mail
 
-DISTNAME=  s-nail-14.9.15
+DISTNAME=  s-nail-14.9.16
 CATEGORIES=mail
 HOMEPAGE=  https://www.sdaoden.eu/code.html\#s-mailx
 
@@ -26,10 +26,8 @@ MAKE_FLAGS=  CC="${CC}" \
VAL_SYSCONFDIR="${SYSCONFDIR}" \
VAL_SID= \
OPT_ALWAYS_UNICODE_LOCALE=yes \
-   OPT_AGENT=no \
OPT_AUTOCC=no \
OPT_DOTLOCK=no \
-   OPT_GSSAPI=no \
VAL_RANDOM=arc4
 
 .if ${FLAVOR:Midna}
Index: distinfo
===
RCS file: /cvs/ports/mail/s-nail/distinfo,v
retrieving revision 1.18
diff -u -p -r1.18 distinfo
--- distinfo20 Aug 2019 09:59:59 -  1.18
+++ distinfo31 Dec 2019 19:46:16 -
@@ -1,2 +1,2 @@
-SHA256 (s-nail-14.9.15.tar.gz) = TEux2uD9btq/HSaKxqR23pqrPBW0u+IUFUmhHb8rrnM=
-SIZE (s-nail-14.9.15.tar.gz) = 1036102
+SHA256 (s-nail-14.9.16.tar.gz) = 6tdv3+YquK8P2w3a2fi4QZeqsYge0V6y+mVFcqjLvu0=
+SIZE (s-nail-14.9.16.tar.gz) = 1075490
Index: patches/patch-include_su_code_h
===
RCS file: patches/patch-include_su_code_h
diff -N patches/patch-include_su_code_h
--- /dev/null   1 Jan 1970 00:00:00 -
+++ patches/patch-include_su_code_h 31 Dec 2019 19:46:16 -
@@ -0,0 +1,39 @@
+$OpenBSD$
+
+commit 0eb2314c
+Author: Steffen Nurpmeso 
+AuthorDate: 2019-12-31 20:34:34 +0100
+Commit: Steffen Nurpmeso 
+CommitDate: 2019-12-31 20:34:52 +0100
+
+FIX clang: not inlining with <-O2; comment out _Alignof() usage
+---
+ include/su/code.h | 8 +---
+ 1 file changed, 5 insertions(+), 3 deletions(-)
+
+diff --git a/include/su/code.h b/include/su/code.h
+index 6e6cd74c..af1e5a30 100644
+--- include/su/code.h
 include/su/code.h
+@@ -470,8 +470,9 @@ do{\
+ #define su_INLINE static inline
+ #define su_SINLINE static inline
+ #   else
+-#define su_INLINE inline
+-#define su_SINLINE static inline
++ /* clang does not like inline with <-O2 */
++#define su_INLINE inline __attribute__((always_inline))
++#define su_SINLINE static inline __attribute__((always_inline))
+ #   endif
+ #  else
+ #   define su_INLINE static __inline
+@@ -534,7 +535,8 @@ do{\
+ #define su_ROUND_UP2(X,BASE) (((X) + ((BASE) - 1)) & (~((BASE) - 1)))
+ 
+ /* Alignment.  Note: su_uz POW2 asserted in POD section below! */
+-#if defined __STDC_VERSION__ && __STDC_VERSION__ +0 >= 201112L
++/* Commented out: "_Alignof() applied to an expression is a GNU extension" */
++#if 0 && defined __STDC_VERSION__ && __STDC_VERSION__ +0 >= 201112L
+ # include 
+ # define su_ALIGNOF(X) _Alignof(X)
+ #else

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Solene Rapenne wrote in <20191231233617.31a04...@t400.my.domain>:
 |Le Tue, 31 Dec 2019 20:55:02 +0100,
 |Steffen Nurpmeso  a écrit :
 |> An update to v14.9.16.  Mailcap support etc., many fixes.
 ...
 |hi, portcheck(1) reports this error but I'm unsure why
 |
 |Missing library for idn2>=0.0
 |*** Error 1 in . (/home/ports/infrastructure/mk/bsd.port.mk:3374 'port-w\
 |antlib-args')
 |*** Error 1 in /home/ports/mail/s-nail (/home/ports/infrastructure/mk/bs\
 |d.port.mk:3033 'print-plist-with-depends')
 |in FLAVOR "idna": the following libraries in WANTLIB look like masked \
 |by RUN_DEPENDS: idn2

Thank you.  For what do i have

  (
 echo '(5)'
 cd ports/mail/s-nail || exit 41
 echo Please perform adjustments, then hit RETURN
 read
 export NO_DEPENDS=Yes
 echo '(6)'
 /usr/ports/infrastructure/bin/portcheck
 echo '(7)'
 make makesum
 echo '(8)'
 make checksum
 echo '(9)'
 make extract
 echo '(10)'
 make build
 echo '(12)'
 make fake
 echo '(13)'
 make plist # ignore error?
 echo '(14)'
 make package
  ) || exit 41
  (
 echo '(15)'
 cd ports/mail/s-nail || exit 42
 cvs diff . > /tmp/s-nail.diff
  ) || exit 42

if i do not address the output!

 --End of <20191231233617.31a04...@t400.my.domain>

Stuart Henderson wrote in <20191231225753.gc70...@symphytum.spacehopper.org>:
 |On 2019/12/31 23:36, Solene Rapenne wrote:
 |> hi, portcheck(1) reports this error but I'm unsure why
 |> 
 |> Missing library for idn2>=0.0
 |> *** Error 1 in . (/home/ports/infrastructure/mk/bsd.port.mk:3374 \
 |> 'port-wantlib-args')
 |> *** Error 1 in /home/ports/mail/s-nail (/home/ports/infrastructure/mk/bs\
 |> d.port.mk:3033 'print-plist-with-depends')
 |> in FLAVOR "idna": the following libraries in WANTLIB look like masked \
 |> by RUN_DEPENDS: idn2
 |
 |good catch,
 |
 |: .if ${FLAVOR:Midna}
 |: WANTLIB+=   idn2
 |: LIB_DEPENDS+=   devel/libidn2
 |: [...]
 |: .endif
 |: 
 |: [...]
 |: 
 |: LIB_DEPENDS=converters/libiconv
 |
 |The second LIB_DEPENDS with = not += hides the first one. (see
 |"make show=LIB_DEPENDS").

!!  Indeed.  Fixed in the below.

 |The "Missing library" is because there's no valid dependency path to the
 |idn2 entry in WANTLIB.
 |
 |portcheck's "masked by RUN_DEPENDS" message is bogus but that's not really
 |unusual :)

This i do not understand.  What can i do to address this?

Anyway, the idna flavour also does compile and test fine with the
below.

 --End of <20191231225753.gc70...@symphytum.spacehopper.org>

Thank you both!
Ciao,

Index: Makefile
===
RCS file: /cvs/ports/mail/s-nail/Makefile,v
retrieving revision 1.25
diff -u -p -r1.25 Makefile
--- Makefile20 Aug 2019 09:59:59 -  1.25
+++ Makefile1 Jan 2020 18:27:46 -
@@ -2,7 +2,7 @@
 
 COMMENT=   SysV mail/BSD Mail/POSIX mailx: send and receive mail
 
-DISTNAME=  s-nail-14.9.15
+DISTNAME=  s-nail-14.9.16
 CATEGORIES=mail
 HOMEPAGE=  https://www.sdaoden.eu/code.html\#s-mailx
 
@@ -26,10 +26,8 @@ MAKE_FLAGS=  CC="${CC}" \
VAL_SYSCONFDIR="${SYSCONFDIR}" \
VAL_SID= \
OPT_ALWAYS_UNICODE_LOCALE=yes \
-   OPT_AGENT=no \
OPT_AUTOCC=no \
OPT_DOTLOCK=no \
-   OPT_GSSAPI=no \
VAL_RANDOM=arc4
 
 .if ${FLAVOR:Midna}
@@ -48,7 +46,7 @@ FAKE_FLAGS+=  OPT_DEBUG=yes
 
 MAKE_ENV=  VERBOSE=Yes
 
-LIB_DEPENDS=   converters/libiconv
+LIB_DEPENDS+=  converters/libiconv
 
 post-install:
${INSTALL_DATA_DIR} ${PREFIX}/share/examples/nail
Index: distinfo
===
RCS file: /cvs/ports/mail/s-nail/distinfo,v
retrieving revision 1.18
diff -u -p -r1.18 distinfo
--- distinfo20 Aug 2019 09:59:59 -  1.18
+++ distinfo1 Jan 2020 18:27:46 -
@@ -1,2 +1,2 @@
-SHA256 (s-nail-14.9.15.tar.gz) = TEux2uD9btq/HSaKxqR23pqrPBW0u+IUFUmhHb8rrnM=
-SIZE (s-nail-14.9.15.tar.gz) = 1036102
+SHA256 (s-nail-14.9.16.tar.gz) = 6tdv3+YquK8P2w3a2fi4QZeqsYge0V6y+mVFcqjLvu0=
+SIZE (s-nail-14.9.16.tar.gz) = 1075490
Index: patches/patch-include_su_code_h
===
RCS file: patches/patch-include_su_code_h
diff -N patches/patch-include_su_code_h
--- /dev/null   1 Jan 1970 00:00:00 -
+++ patches/patch-include_su_code_h 1 Jan 2020 18:27:46 -0000
@@ -0,0 +1,39 @@
+$OpenBSD$
+
+commit 0eb2314c
+Author: Steffen Nurpmeso 
+AuthorDate: 2019-12-31 20:34:34 +0100
+Commit: Steffen Nurpmeso 
+CommitDate: 2019-12-31 20:34:52 +0100
+
+FIX clang: not 

UPDATE mail/s-nail

[Steffen Nurpmeso]

Hello.

one more bugfix release of v14.9.*, fixes

  . a mailcap directive combination (mostly binary formats),
  . .smime-* automated password fallback lookup,
  . all filename prompts now use shell-style quoting,
  . $SOCKS5_PROXY environment used when set

Thanks for your consideration!

Index: Makefile
===
RCS file: /cvs/ports/mail/s-nail/Makefile,v
retrieving revision 1.28
diff -u -p -r1.28 Makefile
--- Makefile24 Feb 2020 09:28:35 -  1.28
+++ Makefile18 Apr 2020 23:43:08 -
@@ -2,7 +2,7 @@
 
 COMMENT=   SysV mail/BSD Mail/POSIX mailx: send and receive mail
 
-DISTNAME=  s-nail-14.9.17
+DISTNAME=  s-nail-14.9.18
 CATEGORIES=mail
 HOMEPAGE=  https://www.sdaoden.eu/code.html\#s-mailx
 
Index: distinfo
===
RCS file: /cvs/ports/mail/s-nail/distinfo,v
retrieving revision 1.20
diff -u -p -r1.20 distinfo
--- distinfo24 Feb 2020 09:28:35 -  1.20
+++ distinfo18 Apr 2020 23:43:08 -
@@ -1,2 +1,2 @@
-SHA256 (s-nail-14.9.17.tar.gz) = +U7rZKnp6Do28QM3eh7zFQcOpjiKiq70palD/SZg3yY=
-SIZE (s-nail-14.9.17.tar.gz) = 1077377
+SHA256 (s-nail-14.9.18.tar.gz) = eiWitcvUCi5DzVSI8oXVhoh8rBK9S2qybFw9RIMdZS4=
+SIZE (s-nail-14.9.18.tar.gz) = 1080781

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Hello.

So here is the promised update to v14.9.19.
Bugfixes worth bringing to OpenBSD 6.7 :).

I am really at odds with having to use OPT_AUTOCC=no, the
configuration would enable all known goods, pedantic warnings and
strict checks, stack protectors, noexecstack (well..), pie, etc.,
anything but retpoline/thunk stuff.  If i do "nail -vvXversion\;x"
then i see that the package builder used "cc -DNDEBUG -O2 -pipe".
Just to have noted it.

 |Ciao, and Good luck! from Germany,

Index: Makefile
===
RCS file: /cvs/ports/mail/s-nail/Makefile,v
retrieving revision 1.28
diff -u -p -r1.28 Makefile
--- Makefile24 Feb 2020 09:28:35 -  1.28
+++ Makefile27 Apr 2020 22:00:41 -
@@ -2,7 +2,7 @@
 
 COMMENT=   SysV mail/BSD Mail/POSIX mailx: send and receive mail
 
-DISTNAME=  s-nail-14.9.17
+DISTNAME=  s-nail-14.9.19
 CATEGORIES=mail
 HOMEPAGE=  https://www.sdaoden.eu/code.html\#s-mailx
 
Index: distinfo
===
RCS file: /cvs/ports/mail/s-nail/distinfo,v
retrieving revision 1.20
diff -u -p -r1.20 distinfo
--- distinfo24 Feb 2020 09:28:35 -  1.20
+++ distinfo27 Apr 2020 22:00:41 -
@@ -1,2 +1,2 @@
-SHA256 (s-nail-14.9.17.tar.gz) = +U7rZKnp6Do28QM3eh7zFQcOpjiKiq70palD/SZg3yY=
-SIZE (s-nail-14.9.17.tar.gz) = 1077377
+SHA256 (s-nail-14.9.19.tar.gz) = rPAsHa0jKBV1EHR+EUiS/VTKPqIrf81iwDIlOvd+Vas=
+SIZE (s-nail-14.9.19.tar.gz) = 1081187

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Hello again.

Steffen Nurpmeso wrote in
<20200418234952.auzwf%stef...@sdaoden.eu>:
  ...
 |one more bugfix release of v14.9.*, fixes
 ...
 |-DISTNAME=s-nail-14.9.17
 |+DISTNAME=s-nail-14.9.18

It seems you are in a freeze for 6.7 already?
Anyway, please hold on with this here, i had an iconv (non-)error
report (and have to compatibility work for OpenSSL 3.0), and will
this release yet another v14.9. update as soon as possible, maybe
even already tomorrow.  I'll ring through then.

Ciao, and Good luck! from Germany,

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Hi.

Steffen Nurpmeso wrote in
<20200427220948.ddaqe%stef...@sdaoden.eu>:
 |So here is the promised update to v14.9.19.

 |I am really at odds with having to use OPT_AUTOCC=no, the
 |configuration would enable all known goods, pedantic warnings and
 |strict checks, stack protectors, noexecstack (well..), pie, etc.,
 |anything but retpoline/thunk stuff.  If i do "nail -vvXversion\;x"
 |then i see that the package builder used "cc -DNDEBUG -O2 -pipe".

So now that i am the actual maintainer i finally took the
opportunity and did that.  I also fixed the Makefile so that it
now uses RUN_DEPENDS not LIB_DEPENDS.  I think Stuart mentioned
that somewhen in the past, i do not know what was wrong actually,
i think i got errors when doing that here.  (By then i had no
X installed but hacked the makefiles to get me going nonetheless
i think.)

I still have some problems that i do not understand

  ===>  Updating plist for s-nail-14.9.19
  Reading existing plist for s-nail-14.9.19
  Scanning /usr/ports/pobj/s-nail-14.9.19/fake-i386
  Removing .debug artefacts
  Figuring out tie points
  Tieing loose objects
  Copying objects
  Stripping directories from converters/libiconv
  child running 'make print-plist-with-depends wantlib_args=no-wantlib-args' 
failed: exit(2)
  make: don't know how to make print-plist-with-depends
  Stop in /usr/ports
  Can't look for conflicts, pkglocatedb not installed

If i look into the fake/ thing, i see a tremendous amount of
directories too, including ja_JP.EUC and cat* stuff in man/, a lot
of nls/ locales in quite a bit of different languages, and such.
Anyway. Argh the name nail.

All tests run fine.  I hope this now is really the final v14.9.*.
Back with .10. somewhen in Autumn i think.

Ciao from Germany.

Index: Makefile
===
RCS file: /cvs/ports/mail/s-nail/Makefile,v
retrieving revision 1.28
diff -u -p -r1.28 Makefile
--- Makefile24 Feb 2020 09:28:35 -  1.28
+++ Makefile26 May 2020 14:43:08 -
@@ -2,7 +2,7 @@
 
 COMMENT=   SysV mail/BSD Mail/POSIX mailx: send and receive mail
 
-DISTNAME=  s-nail-14.9.17
+DISTNAME=  s-nail-14.9.19
 CATEGORIES=mail
 HOMEPAGE=  https://www.sdaoden.eu/code.html\#s-mailx
 
@@ -26,13 +26,12 @@ MAKE_FLAGS= CC="${CC}" \
VAL_SYSCONFDIR="${SYSCONFDIR}" \
VAL_SID= \
OPT_ALWAYS_UNICODE_LOCALE=yes \
-   OPT_AUTOCC=no \
OPT_DOTLOCK=no \
VAL_RANDOM=arc4
 
 .if ${FLAVOR:Midna}
 WANTLIB+=  idn2
-LIB_DEPENDS+=  devel/libidn2
+RUN_DEPENDS+=  devel/libidn2
 MAKE_FLAGS+=   OPT_IDNA=yes \
VAL_IDNA=idn2
 .else
@@ -46,7 +45,7 @@ FAKE_FLAGS+=  OPT_DEBUG=yes
 
 MAKE_ENV=  VERBOSE=Yes
 
-LIB_DEPENDS+=  converters/libiconv
+RUN_DEPENDS+=  converters/libiconv
 
 post-install:
${INSTALL_DATA_DIR} ${PREFIX}/share/examples/nail
Index: distinfo
===
RCS file: /cvs/ports/mail/s-nail/distinfo,v
retrieving revision 1.20
diff -u -p -r1.20 distinfo
--- distinfo24 Feb 2020 09:28:35 -  1.20
+++ distinfo26 May 2020 14:43:08 -
@@ -1,2 +1,2 @@
-SHA256 (s-nail-14.9.17.tar.gz) = +U7rZKnp6Do28QM3eh7zFQcOpjiKiq70palD/SZg3yY=
-SIZE (s-nail-14.9.17.tar.gz) = 1077377
+SHA256 (s-nail-14.9.19.tar.gz) = rPAsHa0jKBV1EHR+EUiS/VTKPqIrf81iwDIlOvd+Vas=
+SIZE (s-nail-14.9.19.tar.gz) = 1081187

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Stuart Henderson wrote in
<20200526181335.gg4...@symphytum.spacehopper.org>:
 |On 2020/05/26 16:53, Steffen Nurpmeso wrote:
 |> Steffen Nurpmeso wrote in
 |> <20200427220948.ddaqe%stef...@sdaoden.eu>:
 |>|So here is the promised update to v14.9.19.
 ...
 |Committed without the incorrect LIB_DEPENDS changes.

Thanks a lot!  Next time i will read the entire manual once again,
maybe i will get it right.

Ciao, and keep the virus and such off the remote holes!

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Steffen Nurpmeso wrote in
 <20201214225721.xskzo%stef...@sdaoden.eu>:
 |Update to v14.9.20, TLS over *socks-proxy*/$SOCKS5_PROXY, EXTERNAL
 |auth for POP3S? and IMAPS?, stuff.

-Wformat-security, truly OPENSSL_NO_DEPRECATED_3_0 clean, etc.,
what-there-is should just-work-neatless finally (now for real).

Thanks in advance.
"A good slide" (that is happy new year) and keep the virus away,
that rhyme surely a crime,
bye bye my love, bye bye.

Ciao.

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

UPDATE mail/s-nail

[Steffen Nurpmeso]

Hello!

Update to v14.9.20, TLS over *socks-proxy*/$SOCKS5_PROXY, EXTERNAL
auth for POP3S? and IMAPS?, stuff.

Ciao from Germany already here,

Index: Makefile
===
RCS file: /cvs/ports/mail/s-nail/Makefile,v
retrieving revision 1.29
diff -u -p -r1.29 Makefile
--- Makefile26 May 2020 18:13:35 -  1.29
+++ Makefile14 Dec 2020 22:53:13 -
@@ -2,7 +2,7 @@
 
 COMMENT=   SysV mail/BSD Mail/POSIX mailx: send and receive mail
 
-DISTNAME=  s-nail-14.9.19
+DISTNAME=  s-nail-14.9.20
 CATEGORIES=mail
 HOMEPAGE=  https://www.sdaoden.eu/code.html\#s-mailx
 
Index: distinfo
===
RCS file: /cvs/ports/mail/s-nail/distinfo,v
retrieving revision 1.21
diff -u -p -r1.21 distinfo
--- distinfo26 May 2020 18:13:35 -  1.21
+++ distinfo14 Dec 2020 22:53:13 -
@@ -1,2 +1,2 @@
-SHA256 (s-nail-14.9.19.tar.gz) = rPAsHa0jKBV1EHR+EUiS/VTKPqIrf81iwDIlOvd+Vas=
-SIZE (s-nail-14.9.19.tar.gz) = 1081187
+SHA256 (s-nail-14.9.20.tar.gz) = 3uKTILgc9Ti2myKz/54wmkf1xo2Xhlgfd26jrLMneAo=
+SIZE (s-nail-14.9.20.tar.gz) = 1089331

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Steffen Nurpmeso wrote in
 <20201229162620.gwx_7%stef...@sdaoden.eu>:
 |Steffen Nurpmeso wrote in
 | <20201214225721.xskzo%stef...@sdaoden.eu>:
 ||Update to v14.9.20, TLS over *socks-proxy*/$SOCKS5_PROXY, EXTERNAL
 ||auth for POP3S? and IMAPS?, stuff.
 |
 |-Wformat-security, truly OPENSSL_NO_DEPRECATED_3_0 clean, etc.,
 |what-there-is should just-work-neatless finally (now for real).
 |
 |Thanks in advance.
 |"A good slide" (that is happy new year) and keep the virus away,
 |that rhyme surely a crime,
 |bye bye my love, bye bye.

Thank you for committing it, Stuart!

A happy and healthy 2021 from Germany i wish,

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

UPDATE mail/s-nail

[Steffen Nurpmeso]

Hello again.

Well, unfortunately, yes.
I apologise for the inconvenience of yet another bugfix release.
Also one security related SMTP fix.

Index: Makefile
===
RCS file: /cvs/ports/mail/s-nail/Makefile,v
retrieving revision 1.30
diff -u -p -r1.30 Makefile
--- Makefile30 Dec 2020 14:25:09 -  1.30
+++ Makefile21 Jan 2021 23:34:25 -
@@ -2,7 +2,7 @@
 
 COMMENT=   SysV mail/BSD Mail/POSIX mailx: send and receive mail
 
-DISTNAME=  s-nail-14.9.20
+DISTNAME=  s-nail-14.9.21
 CATEGORIES=mail
 HOMEPAGE=  https://www.sdaoden.eu/code.html\#s-mailx
 
Index: distinfo
===
RCS file: /cvs/ports/mail/s-nail/distinfo,v
retrieving revision 1.22
diff -u -p -r1.22 distinfo
--- distinfo30 Dec 2020 14:25:09 -  1.22
+++ distinfo21 Jan 2021 23:34:25 -
@@ -1,2 +1,2 @@
-SHA256 (s-nail-14.9.20.tar.gz) = 3uKTILgc9Ti2myKz/54wmkf1xo2Xhlgfd26jrLMneAo=
-SIZE (s-nail-14.9.20.tar.gz) = 1089331
+SHA256 (s-nail-14.9.21.tar.gz) = U9dfAYj1v6v+uw5JyhCqpoJAHv0viJskxCDg6Lb0cZc=
+SIZE (s-nail-14.9.21.tar.gz) = 1091097

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Steffen Nurpmeso wrote in
 <20210121233913.sovre%stef...@sdaoden.eu>:
 |Well, unfortunately, yes.
 |I apologise for the inconvenience of yet another bugfix release.
 |Also one security related SMTP fix.
 ...
 |-DISTNAME=s-nail-14.9.20
 |+DISTNAME=s-nail-14.9.21

Thanks again, Stuart -- even with a backport to 6.8!  :-)

Ciao from Germany, a nice and healthy weekend i wish!

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: bogofilter with sqlite3 wants lib z

[Steffen Nurpmeso]

Stuart Henderson wrote in
 :
 |On 2021/07/08 08:45, Martin Ziemer wrote:
 ...
 |Let's look at the other flavours.
 |
 |bogofilter-1.2.4p2-qdbm(mail/bogofilter,qdbm):
 |Extra:  qdbm.14
 |
 |bogofilter-1.2.4p2-db4(mail/bogofilter,db4):
 |Extra:  db.5 iconv.7
 |
 |Same problem. Presumably this worked properly before, looking at other OS
 |bogofilter is dynamically linked to db libraries there. The part of the
 |configure script responsible for figuring out how to link to these comes
 |from an ancient copy of gettext-related m4 files in the distro. So let's
 |pick up new ones to replace them. While there we can pick up the 2019
 |update to 1.2.5 that includes various things including fixes for memory
 |leaks, lexer fixes for MIME multipart and HTML tokens, and some others.

Gee, you could really add the LMDB backend.
I use it for years (disclaimer: i wrote it, long before release
1.2.5), the per-entry overhead is smaller, the speed is
tremendous, the library is only ~7.1% of the size of libsqlite3
(here).  With postfix also using LMDB exclusively (needs a patch,
AlpineLinux has it, CRUX has, too) i am all out of DBs but LMDB in
the mail system here, and that is very nice.

There is only one caveat: LMDB has no VACUUM.
So for compaction all you can do is

  bogoutil -d wordlist.lmdb > /tmp/spam.db || exit 2
  mv wordlist.lmdb wordlist.lmdb.save
  bogoutil -l wordlist.lmdb < /tmp/spam.db || {
 mv wordlist.lmdb.save wordlist.lmdb
 exit 3
  }
  rm wordlist.lmdb.save

ie, regenerate the database, whenever you feel the need to do so.

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: bogofilter with sqlite3 wants lib z

[Steffen Nurpmeso]

Stuart Henderson wrote in
 :
 |On 2021/07/08 15:12, Steffen Nurpmeso wrote:
 |> Stuart Henderson wrote in
 |>  :
 |>|On 2021/07/08 08:45, Martin Ziemer wrote:
 |>  ...
 |>|Let's look at the other flavours.
 |>|
 |>|bogofilter-1.2.4p2-qdbm(mail/bogofilter,qdbm):
 |>|Extra:  qdbm.14
 |>|
 |>|bogofilter-1.2.4p2-db4(mail/bogofilter,db4):
 |>|Extra:  db.5 iconv.7
 |>|
 |>|Same problem. Presumably this worked properly before, looking at other OS
 |>|bogofilter is dynamically linked to db libraries there. The part of the
 ...
 |> Gee, you could really add the LMDB backend.
 |
 |And you could really read my diff.

Oh.  Indeed.  What a shame.  Some defense problems here!
Very much sorry for the noise then.

 --End of 

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Stuart Henderson wrote in
 :
 |On 2021/03/08 21:55, Steffen Nurpmeso wrote:
 |> Steffen Nurpmeso wrote in
 |>  <20210308200314.r794j%stef...@sdaoden.eu>:
 |>|Stuart Henderson wrote in
 |>| :
 |>||On 2021/03/08 18:53, Steffen Nurpmeso wrote:
 |>||> Steffen Nurpmeso wrote in
 |>||>  <20210224143220.o1zwb%stef...@sdaoden.eu>:
 |>||>|Update to v14.9.22 to unbreak a closefrom(2) / close_range(2)
 |>||>|brain damage of mine.
 |>||> 
 |>||> I just got an according bug report from Predrag regarding this.
 |>||> Dependent on what you do, version 14.9.21 is truly _broken_, and
 |>||> 14.9.22 really should replace 14.9.21 wherever possible, please.
 |>| 
 |>||Committed.
 |>|
 |>|Thank you very much for this, Stuart.
 |>|
 |>||Can you advise how to tell the complicated make-config script how to
 |>||respect ports CFLAGS setting for compiler optimization please?
 |>|
 |>|If it is only optimization one could either overwrite it by
 |>|passing an additional EXTRA_CFLAGS=-O1 or similar to overwrite it,
 |>|or instead pass cc_maxopt=[0123] (this i have not tested for years
 |>|hmmm .. but still works).  Note that higher than -O3 is not
 |>|supported, if you want this then you have to go the EXTRA_CFLAGS
 |>|way.  (-Os also not built-in, it also seems badly maintained in,
 |>|granted gcc, upstream and caused inlining problems in the past
 |>|(AlpineLinux package).
 |> 
 |> Well, i mean, selectively picking something out of original
 |> $CFLAGS automatically is not supported, on the other hand.  Does
 |> any build system support that?  I.e., only adding warnings and
 |> hardening flags etc. _onto_ the otherwise unchanged original
 |> $CFLAGS?  Is it that would you mean?  This is i think an
 |> interesting suggestion i will try to address in the future, and
 |> ship with the next update of this package, then.
 ...
 |It's fairly common for software to add warnings/include paths/etc
 |after a provided CFLAGS, or sometimes via another variable (some use
 |COPTFLAGS). Where that's not supported, in most cases it's a simple
 |matter of patching a Makefile to remove -O3 etc but it's a bit more
 |complex here.

Well i mean the package could reinstantiate the OPT_AUTOCC=no that
i think William Yodlowsky introduced years ago, then the builder
is absolutely free to define whatever she desires.  I personally
have always been of the opinion that all the warning options,
stack guards, PIE, let alone the terrible retpoline that i really
refrain from uncommenting, as well as the noexecstack that
i personally could only dig if it were execstack on request,
should not be needed at all in shipout code.  I only ever used
-fno-exceptions -fno-rtti myself, but somehow CPU cycles have to
be wasted it seems.  Sandboxing we do not support yet, it requires
a program redesign.  At least we have OPT_AUTOCC_STACKPROT to get
rid of that, but it is on by default, you know.  Indifference has
won won won.

 |Trying EXTRA_CFLAGS it's nearly what's needed, though it relies on
 |the user setting an alternative -O to override the one added in
 |make-config.sh, you can't e.g. set EXTRA_CFLAGS="" to build with no
 |-O flag at all.
 |
 |Ports on OpenBSD (and I believe also FreeBSD) are generally meant to use
 |OS defaults or user settings via the standard interface e.g. "make
 |CFLAGS=-O0" etc, when building the port. When dealing with a collection
 |of thousands of programs, it's helpful to have standard interfaces like
 |this rather than have to figure out what's needed for each individual
 |port.

By the way, what actual optimization issue do you have.
But yeah, people get understandably frustrated without a -march=,
i apologise.

So i have implemented VAL_AUTOCC=, which for now offers
add_options,bind_now,pie,stackprot,fortify selections, where the
default is bind_now,pie,stackprot,fortify, and i would change the
port to use add_options,bind_now,pie,stackprot when the next
version is released.  We cannot do FORTIFY because that requires
optimization to be enabled, which can no longer be guaranteed.
Thanks for the suggestion Stuart.

Ciao from Germany,

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

UPDATE mail/s-nail

[Steffen Nurpmeso]

Hello ports@.

Update to v14.9.22 to unbreak a closefrom(2) / close_range(2)
brain damage of mine.

Thank you and Ciao from Germany!

Index: Makefile
===
RCS file: /cvs/ports/mail/s-nail/Makefile,v
retrieving revision 1.31
diff -u -p -r1.31 Makefile
--- Makefile22 Jan 2021 11:05:33 -  1.31
+++ Makefile24 Feb 2021 14:21:21 -
@@ -2,7 +2,7 @@
 
 COMMENT=   SysV mail/BSD Mail/POSIX mailx: send and receive mail
 
-DISTNAME=  s-nail-14.9.21
+DISTNAME=  s-nail-14.9.22
 CATEGORIES=mail
 HOMEPAGE=  https://www.sdaoden.eu/code.html\#s-mailx
 
Index: distinfo
===
RCS file: /cvs/ports/mail/s-nail/distinfo,v
retrieving revision 1.23
diff -u -p -r1.23 distinfo
--- distinfo22 Jan 2021 11:05:33 -  1.23
+++ distinfo24 Feb 2021 14:21:21 -
@@ -1,2 +1,2 @@
-SHA256 (s-nail-14.9.21.tar.gz) = U9dfAYj1v6v+uw5JyhCqpoJAHv0viJskxCDg6Lb0cZc=
-SIZE (s-nail-14.9.21.tar.gz) = 1091097
+SHA256 (s-nail-14.9.22.tar.gz) = LAwupEEqdXtgThFpUntC1L42MbqPZDrTxJ+M7YME7DE=
+SIZE (s-nail-14.9.22.tar.gz) = 1090859

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Hello.

Steffen Nurpmeso wrote in
 <20210224143220.o1zwb%stef...@sdaoden.eu>:
 |Hello ports@.
 |
 |Update to v14.9.22 to unbreak a closefrom(2) / close_range(2)
 |brain damage of mine.

I just got an according bug report from Predrag regarding this.
Dependent on what you do, version 14.9.21 is truly _broken_, and
14.9.22 really should replace 14.9.21 wherever possible, please.

The problem is that file descriptors needed for subprocesses will
be closed.  I still have not updated the tests for this, i got
back to school to learn about boxing, WireGuard, better firewall,
etc., and yet existing ones only use the standard set of file
descriptors, and thus did not reveal this.  (And my own use cases
do not either, i turned to use ~/.mailcap and effectively use %s
for all relevant entries.)

Sorry for the inconvenience, and greetings from Germany,
Ciao,

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Steffen Nurpmeso wrote in
 <20210308200314.r794j%stef...@sdaoden.eu>:
 |Stuart Henderson wrote in
 | :
 ||On 2021/03/08 18:53, Steffen Nurpmeso wrote:
 ||> Steffen Nurpmeso wrote in
 ||>  <20210224143220.o1zwb%stef...@sdaoden.eu>:
 ||>|Hello ports@.
 ||>|
 ||>|Update to v14.9.22 to unbreak a closefrom(2) / close_range(2)
 ||>|brain damage of mine.
 ||> 
 ||> I just got an according bug report from Predrag regarding this.
 ||> Dependent on what you do, version 14.9.21 is truly _broken_, and
 ||> 14.9.22 really should replace 14.9.21 wherever possible, please.
 | 
 ||Committed.
 |
 |Thank you very much for this, Stuart.
 |
 ||Can you advise how to tell the complicated make-config script how to
 ||respect ports CFLAGS setting for compiler optimization please?
 |
 |If it is only optimization one could either overwrite it by
 |passing an additional EXTRA_CFLAGS=-O1 or similar to overwrite it,
 |or instead pass cc_maxopt=[0123] (this i have not tested for years
 |hmmm .. but still works).  Note that higher than -O3 is not
 |supported, if you want this then you have to go the EXTRA_CFLAGS
 |way.  (-Os also not built-in, it also seems badly maintained in,
 |granted gcc, upstream and caused inlining problems in the past
 |(AlpineLinux package).

Well, i mean, selectively picking something out of original
$CFLAGS automatically is not supported, on the other hand.  Does
any build system support that?  I.e., only adding warnings and
hardening flags etc. _onto_ the otherwise unchanged original
$CFLAGS?  Is it that would you mean?  This is i think an
interesting suggestion i will try to address in the future, and
ship with the next update of this package, then.

Thanks, and Ciao! from Germany,

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Hello Stuart.

Stuart Henderson wrote in
 :
 |On 2021/03/08 18:53, Steffen Nurpmeso wrote:
 |> Steffen Nurpmeso wrote in
 |>  <20210224143220.o1zwb%stef...@sdaoden.eu>:
 |>|Hello ports@.
 |>|
 |>|Update to v14.9.22 to unbreak a closefrom(2) / close_range(2)
 |>|brain damage of mine.
 |> 
 |> I just got an according bug report from Predrag regarding this.
 |> Dependent on what you do, version 14.9.21 is truly _broken_, and
 |> 14.9.22 really should replace 14.9.21 wherever possible, please.
 
 |Committed.

Thank you very much for this, Stuart.

 |Can you advise how to tell the complicated make-config script how to
 |respect ports CFLAGS setting for compiler optimization please?

If it is only optimization one could either overwrite it by
passing an additional EXTRA_CFLAGS=-O1 or similar to overwrite it,
or instead pass cc_maxopt=[0123] (this i have not tested for years
hmmm .. but still works).  Note that higher than -O3 is not
supported, if you want this then you have to go the EXTRA_CFLAGS
way.  (-Os also not built-in, it also seems badly maintained in,
granted gcc, upstream and caused inlining problems in the past
(AlpineLinux package).

 --End of 

P.S.: just to mention it, this is documented in make.rc and in
full in INSTALL, "1.3 Tests failed!".  Seems like a bad place, hm.
I have never encountered miscompilations with this software?  But
i think i will turn cc_maxopt into a regular option, and document
it in make.rc, better it is.

Ciao!

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

UPDATE mail/s-nail

[Steffen Nurpmeso]

Hello ports@.

Bugfix update to v14.9.23.
Gets Europe/Dublin and other timezones with negativs is-DST
adjustment right, and more.

Dear Stuart,

Steffen Nurpmeso wrote in
 <20210309175203.3umyh%stef...@sdaoden.eu>:
 |Stuart Henderson wrote in
 | :
 ||On 2021/03/08 21:55, Steffen Nurpmeso wrote:
 ||> Steffen Nurpmeso wrote in
 ||>  <20210308200314.r794j%stef...@sdaoden.eu>:
 ||>|Stuart Henderson wrote in
 ||>| :
 ..
 ||>||Can you advise how to tell the complicated make-config script how to
 ||>||respect ports CFLAGS setting for compiler optimization please?
 ...
 |So i have implemented VAL_AUTOCC=, which for now offers
 |add_options,bind_now,pie,stackprot,fortify selections, where the
 |default is bind_now,pie,stackprot,fortify, and i would change the
 |port to use add_options,bind_now,pie,stackprot when the next
 |version is released.  We cannot do FORTIFY because that requires
 |optimization to be enabled, which can no longer be guaranteed.
 |Thanks for the suggestion Stuart.

This is not in v14.9.23, the "next [regular] release" should have
been and then is v14.10, it will contain this.

For now i thus have disabled automatic $CC settings, just for you,
i still wonder why all the security features were not enabled for
OpenBSD s-nail package, until i (as package maintainer) then
turned on automatic $CC settings.  On the other hand i really like
it, i personally never used them but for development purposes as
i think a shipout thing should not put debug burden on users, so
i am really fine with it!  Never triggered in real life in all
this time.

A nice weekend i wish from Germany already here,
Ciao!

Index: Makefile
===
RCS file: /cvs/ports/mail/s-nail/Makefile,v
retrieving revision 1.33
diff -r1.33 Makefile
5c5
< DISTNAME= s-nail-14.9.22
---
> DISTNAME= s-nail-14.9.23
29a30
>   OPT_AUTOCC=no \
Index: distinfo
===
RCS file: /cvs/ports/mail/s-nail/distinfo,v
retrieving revision 1.24
diff -r1.24 distinfo
1,2c1,2
< SHA256 (s-nail-14.9.22.tar.gz) = LAwupEEqdXtgThFpUntC1L42MbqPZDrTxJ+M7YME7DE=
< SIZE (s-nail-14.9.22.tar.gz) = 1090859
---
> SHA256 (s-nail-14.9.23.tar.gz) = Ul7SMxec/CoWluopUpn9jlrbskUQrU4eZDC0SRYvkWs=
> SIZE (s-nail-14.9.23.tar.gz) = 1091503

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Hello ports@.

Steffen Nurpmeso wrote in
 <2023004708.af5oe%stef...@sdaoden.eu>:
 |Bugfix update to v14.9.23.
 |Gets Europe/Dublin and other timezones with negativs is-DST
 |adjustment right, and more.
 ...

Not a widely used port, but would be nice to get the update in.

Ciao from Germany already here,

Index: Makefile
===
RCS file: /cvs/ports/mail/s-nail/Makefile,v
retrieving revision 1.33
diff -r1.33 Makefile
5c5
< DISTNAME= s-nail-14.9.22
---
> DISTNAME= s-nail-14.9.23
29a30
>   OPT_AUTOCC=no \
Index: distinfo
===
RCS file: /cvs/ports/mail/s-nail/distinfo,v
retrieving revision 1.24
diff -r1.24 distinfo
1,2c1,2
< SHA256 (s-nail-14.9.22.tar.gz) = LAwupEEqdXtgThFpUntC1L42MbqPZDrTxJ+M7YME7DE=
< SIZE (s-nail-14.9.22.tar.gz) = 1090859
---
> SHA256 (s-nail-14.9.23.tar.gz) = Ul7SMxec/CoWluopUpn9jlrbskUQrU4eZDC0SRYvkWs=
> SIZE (s-nail-14.9.23.tar.gz) = 1091503


--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Hello again ports@.

Steffen Nurpmeso wrote in
 <20211202214827.ckm95%stef...@sdaoden.eu>:
 |Hello ports@.
 |
 |Steffen Nurpmeso wrote in
 | <2023004708.af5oe%stef...@sdaoden.eu>:
 ||Bugfix update to v14.9.23.
 ||Gets Europe/Dublin and other timezones with negativs is-DST
 ||adjustment right, and more.
 | ...

Please, would anybody be so kind and

  Give back Ireland to the Irish

??  And hey, it was an English Sir who said so first!

(It brings in more fixes/tweaks, 57 changesets all in all, and one
more really bitter one there is, too.)

Thank you in advance, and greetings from Germany!
Ciao,

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Hello Stuart.

Thanks again!

Stuart Henderson wrote in
 :
 |On 2021/12/09 14:50, Steffen Nurpmeso wrote:
 |> Steffen Nurpmeso wrote in
 |>  <20211202214827.ckm95%stef...@sdaoden.eu>:
 |>|Steffen Nurpmeso wrote in
 |>| <2023004708.af5oe%stef...@sdaoden.eu>:
 |>||Bugfix update to v14.9.23.
 ...
 |I have committed with the REVISION line removed.

You put it in with 1.33 in order to pass through specific
optimizations.  I have not consciously recognized that line, 
sorry.  I am not a very sophisticated port maintainer, only
maintaining this thing i even code myself (yikes!); i sometimes
thought about adding at least my s-cdda, or even s-cdda-to-db in
addition, but never have beaten myself to it.  And then there is
always that warning from one of the script steps (likely
/usr/ports/infrastructure/bin/portcheck or make
port-lib-depends-check) that i do not really understand, but it is
just doing it all smoothly the way it is so i really never got
used to wrap my head around it; port systems are complicated
beasts and how often i was banging against a wall that then was
not my fault, but that of others.  Whatever.  Hm.

 |Please could you send diffs with -u and it would be helpful to reinclude

I adjusted the script accordingly.  (I no longer have a ~/.cvsrc!
It had the "diff -Napu" i now added.)

 |the diff (in usable rather than quoted form) if you are prodding, it
 |makes it easier for whoever is committing if they don't have to look in
 |mail archives.

Well as i can because it is easy for this very port, i will.

Thanks again, greetings to an island!
Ciao,

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: UPDATE mail/s-nail

[Steffen Nurpmeso]

Hello.

Stuart Henderson wrote in
 :
 |On 2021/12/09 20:28, Steffen Nurpmeso wrote:
 ...
 |> Stuart Henderson wrote in
 |>  :
 ...
 |>|I have committed with the REVISION line removed.
 |> 
 |> You put it in with 1.33 in order to pass through specific
 |> optimizations.
 |
 |A change affecting the built packages needs the package version number
 |to be increased so that installed copies are updated, if the actual version
 |number of the software didn't change this is done by setting REVISION.
 |When the port is updated to a new version then REVISION is removed again.

Noted.  This is in contrast to the (easy, shell-based) package
system of CRUX-Linux for which i also maintain packages:

elif [ ! "$version" ]; then
error "Variable 'version' not specified in $PKGMK_PKGFILE."
exit $E_PKGFILE
[The program version.]
elif [ ! "$release" ]; then
error "Variable 'release' not specified in $PKGMK_PKGFILE."
exit $E_PKGFILE
[The package release.]

Removing REVISION is a bit more pragmatic than setting release=1!

Thank you, Stuart.

A nice weekend if you can, everybody.
Ciao,

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

UPDATE mail/s-nail

[Steffen Nurpmeso]

Hello ports@, hello Stuart.

This updates to v14.9.24, with a few fixes, including an IMAP
improvement so this MUA should work with Microsoft IMAP servers
(and all servers which treat "untagged" responses seriously).
(In general what seemed "buggy" to "you, user" should now feel
right.)

This is now really and irrefutable the last (bugfix) update of the
v14.9.X branch.  Thanks for your patience.

 <2023004708.af5oe%stef...@sdaoden.eu>:
 |Steffen Nurpmeso wrote in
 | <20210309175203.3umyh%stef...@sdaoden.eu>:
 ||Stuart Henderson wrote in
 || :
 |||On 2021/03/08 21:55, Steffen Nurpmeso wrote:
 |||> Steffen Nurpmeso wrote in
 |||>  <20210308200314.r794j%stef...@sdaoden.eu>:
 |||>|Stuart Henderson wrote in
 |||>| :
 | ..
 |||>||Can you advise how to tell the complicated make-config script how to
 |||>||respect ports CFLAGS setting for compiler optimization please?
 | ...
 ||So i have implemented VAL_AUTOCC=, which for now offers
 ...
 |This is not in v14.9.23, the "next [regular] release" should have
 |been and then is v14.10, it will contain this.
 |
 |For now i thus have disabled automatic $CC settings, just for you,

This continues to be true, thus.

A sedition free time everybody, greetings from Germany (in the
middle of a snow storm (honestly, not April 1st)).

Index: Makefile
===
RCS file: /cvs/ports/mail/s-nail/Makefile,v
retrieving revision 1.35
diff -a -p -u -a -p -u -r1.35 Makefile
--- Makefile11 Mar 2022 19:34:55 -  1.35
+++ Makefile31 Mar 2022 22:15:37 -
@@ -1,6 +1,6 @@
 COMMENT=   SysV mail/BSD Mail/POSIX mailx: send and receive mail
 
-DISTNAME=  s-nail-14.9.23
+DISTNAME=  s-nail-14.9.24
 CATEGORIES=mail
 HOMEPAGE=  https://www.sdaoden.eu/code.html\#s-mailx
 
Index: distinfo
===
RCS file: /cvs/ports/mail/s-nail/distinfo,v
retrieving revision 1.25
diff -a -p -u -a -p -u -r1.25 distinfo
--- distinfo9 Dec 2021 14:07:21 -   1.25
+++ distinfo31 Mar 2022 22:15:37 -
@@ -1,2 +1,2 @@
-SHA256 (s-nail-14.9.23.tar.gz) = Ul7SMxec/CoWluopUpn9jlrbskUQrU4eZDC0SRYvkWs=
-SIZE (s-nail-14.9.23.tar.gz) = 1091503
+SHA256 (s-nail-14.9.24.tar.gz) = Tk24aXkrzcyX+uHbGmZB5mSpOy6F9urFPns6wwXmxYY=
+SIZE (s-nail-14.9.24.tar.gz) = 1105199

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: Tool to scan/watch upstream source for new releases ?

[Steffen Nurpmeso]

Stefan Sperling wrote in
 :
 |On Wed, Jan 26, 2022 at 10:44:50AM +, Yifei Zhan wrote:
 |> On 22/01/26 10:16AM, Laurent Cheylus wrote:
 |>> Hi,
 |>> 
 |>> for Debian Linux distribution, uscan tool is used to scan/watch \
 |>> upstream 
 |>> sources for new releases of software.
 |>> https://manpages.debian.org/bullseye-backports/devscripts/uscan.1.en.htm\
 |>> l
 |>> 
 |>> This tool is used with watchfiles : defines URL for upstream tarball(s) 
 |>> and download it if the upstream tarball have highest version newer than 
 |>> the last upstream version.
 |>> 
 |>> Is there a similar tool for OpenBSD ports ?
 |>> 
 |> 
 |> This might be what you are looking for:
 |> https://portroach.openbsd.org/
 |> 
 |> but now I mostly just use repology.org since they support OpenBSD 
 |> Ports and allow me to do cross reference with other distros.
 |
 |ropology is slow with updating its data for OpenBSD ports.
 |It sometimes lags behind by several days, perhaps by a week.
 |Watch out for this if you really need up-to-date info.

The core group of the CRUX Linux i am contributing ports to installed
some repology json i think it was info on the ports master server;
ie now repology looks at the json data, and this seems to happen
"almost instantly".

I personally like it very much as i do not install things like
ck4up or similar utilities to track upstream changes -- what does
not come in via oss-security or announcement mails (which often
are forgotten, take st: huhu!!!) may linger a bit.

 |For example, for devel/got, repology keeps showing that FreeBSD keeps
 |updating before OpenBSD, which in reality has never happened.
 |https://repology.org/project/got-game-of-trees/history
 --End of 

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: [NEW] mail/s-postgray: postfix graylisting policy server (fast+secure)

[Steffen Nurpmeso]

Stuart Henderson wrote in
 :
 |Please send new ports as tars, they are easier to work with
 |
 |@pkgpath markers should only be used when a port has already been
 |committed but the pkgpath is changed for some reason (either the
 |port directory is renamed, or more likely the port is split from a
 |single package to multipackages), they are used for building a set
 |of possible update candidates

Thanks for the info.  Will do tomorrow.

 --End of 

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: [NEW] audio/s-cdda: access audio CDs (informations and track data)

[Steffen Nurpmeso]

Stuart Henderson wrote in
 :
 |On 2022/05/12 01:43, Steffen Nurpmeso wrote:
 |>   ...
 |>|> +MAKE_FILE= makefile
 |>|
 |>|this is not strictly needed.  make looks also for a file called
 |>|"makefile" by default, so as long as you don't add another "Makefile" in
 |>|the tarball make(1) should do the right thing.
 |> 
 |> Yes it does.  I simply copied over from the S-nail port.  Will do.
 |
 |that one is required; ports uses "-f ${MAKE_FILE}"

ok will check.

 --End of 

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

[NEW] mail/s-postgray: postfix graylisting policy server (fast+secure)

[Steffen Nurpmeso]

Finally that one.

RFC 6647 graylisting policy server, following the recommendet
practice noted in the standard document.  Graylisting defers
message acceptance (for a specific recipient / sender /
client_address value tuple) a configurable number of times via
a standardized SMTP response (see allow(5), RFC 5321), which does
not prevent message delivery from SMTP M(ail) T(ransfer) A(gent)s,
but can help against simple spam producing programs.

s-postgray is started via spawn(8), with the given user
credentials, therefore the built-in DB store path is /tmp --
you surely want to change this.
Note s-postgray changes CWD to the configured --store-path, and
loads most files from therein.

diff -Napru mail.orig/s-postgray/Makefile mail/s-postgray/Makefile
--- mail.orig/s-postgray/Makefile   Thu Jan  1 01:00:00 1970
+++ mail/s-postgray/MakefileThu May 12 01:13:54 2022
@@ -0,0 +1,22 @@
+COMMENT=   postfix graylisting policy server (fast+secure)
+
+DISTNAME=  s-postgray-0.6.0
+#REVISION= 0
+CATEGORIES=mail
+HOMEPAGE=  https://www.sdaoden.eu/code.html\#s-postgray
+
+MASTER_SITES=  https://ftp.sdaoden.eu/
+MAINTAINER=Steffen Nurpmeso 
+
+# ISC
+PERMIT_PACKAGE=Yes
+
+WANTLIB+=  c
+
+MAKE_FILE= makefile
+MAKE_FLAGS=MANDIR="${DESTDIR}${PREFIX}"/man/man8 \
+   VAL_STORE_PATH=/tmp
+
+NO_TEST=   Yes
+
+.include 
diff -Napru mail.orig/s-postgray/distinfo mail/s-postgray/distinfo
--- mail.orig/s-postgray/distinfo   Thu Jan  1 01:00:00 1970
+++ mail/s-postgray/distinfoThu May 12 01:14:48 2022
@@ -0,0 +1,2 @@
+SHA256 (s-postgray-0.6.0.tar.gz) = He6OqMiB1ctjcmFR9RQrX19MS/nHEz2l5xcKzooA0UY=
+SIZE (s-postgray-0.6.0.tar.gz) = 127563
diff -Napru mail.orig/s-postgray/pkg/DESCR mail/s-postgray/pkg/DESCR
--- mail.orig/s-postgray/pkg/DESCR  Thu Jan  1 01:00:00 1970
+++ mail/s-postgray/pkg/DESCR   Thu May 12 01:12:01 2022
@@ -0,0 +1,10 @@
+RFC 6647 graylisting policy server, following the recommendet practice
+noted in the standard document.
+Graylisting defers message acceptance (for a specific recipient / sender
+/ client_address value tuple) a configurable number of times
+via a standardized SMTP response (see allow(5), RFC 5321), which does
+not prevent message delivery from SMTP M(ail) T(ransfer) A(gent)s,
+but can help against simple spam producing programs.
+s-postgray is started via spawn(8), with the given user credentials,
+therefore the built-in DB store path is /tmp -- you surely want to
+change this.
diff -Napru mail.orig/s-postgray/pkg/PLIST mail/s-postgray/pkg/PLIST
--- mail.orig/s-postgray/pkg/PLIST  Thu Jan  1 01:00:00 1970
+++ mail/s-postgray/pkg/PLIST   Thu May 12 01:16:04 2022
@@ -0,0 +1,3 @@
+@pkgpath mail/s-postgray
+@bin libexec/s-postgray
+@man man/man8/s-postgray.8
diff -Napru mail.orig/s-postgray/pkg/PLIST.orig mail/s-postgray/pkg/PLIST.orig
--- mail.orig/s-postgray/pkg/PLIST.orig Thu Jan  1 01:00:00 1970
+++ mail/s-postgray/pkg/PLIST.orig  Thu May 12 00:58:11 2022
@@ -0,0 +1,3 @@
+@pkgpath mail/s-postgray
+libexec/s-postgray
+@man man/man8/s-postgray.8

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

[NEW] audio/s-cdda-to-db: perl program that creates a music database via s-cdda

[Steffen Nurpmeso]

One more.

  Queries content and data of audio CDs through s-cdda(1), collects
  informations (artist, album, song titles, etc.) of desired tracks,
  if possible correlates data with a web query against MusicBrainz,
  then places encoded tracks as well as a human readable and easily
  parseable database in a per-CD directory under a directory tree.
  The audio encoders (and sox(1) without --no-volume-normalize) need
  to be installed separately.

^ Note especially this.  sox(1) is needed by default unless
a command line option is given, yet i did not want to add it to
RUN_DEPENDS?  Just like the audio encoders like faac(1) or
oggenc(1).

  (P.S.: the user will be asked to edit collected informations, and
  will be given a hand for the rather sophisticated, classical music
  aware) database layout while doing so.)

  (P.P.S.: nice foundation for link farms.)

^ Also since as many informations are stored in the files itself
as possible.  The music.db (UTF-8) file is very simple to parse.
(The file names are just the track numbers.)

diff -Napru audio.orig2/s-cdda-to-db/Makefile audio/s-cdda-to-db/Makefile
--- audio.orig2/s-cdda-to-db/Makefile   Thu Jan  1 01:00:00 1970
+++ audio/s-cdda-to-db/Makefile Thu May 12 00:38:29 2022
@@ -0,0 +1,21 @@
+COMMENT=   perl program that creates a music database via s-cdda
+
+DISTNAME=  s-cdda-to-db-0.8.0
+#REVISION= 0
+CATEGORIES=audio
+HOMEPAGE=  https://www.sdaoden.eu/code.html\#s-cdda-to-db
+
+MASTER_SITES=  https://ftp.sdaoden.eu/
+MAINTAINER=Steffen Nurpmeso 
+
+# ISC
+PERMIT_PACKAGE=Yes
+
+RUN_DEPENDS=   audio/s-cdda textproc/p5-XML-Parser
+
+MAKE_FILE= makefile
+MAKE_FLAGS=MANDIR="${DESTDIR}${PREFIX}"/man/man1
+
+NO_TEST=   Yes
+
+.include 
diff -Napru audio.orig2/s-cdda-to-db/distinfo audio/s-cdda-to-db/distinfo
--- audio.orig2/s-cdda-to-db/distinfo   Thu Jan  1 01:00:00 1970
+++ audio/s-cdda-to-db/distinfo Thu May 12 00:38:55 2022
@@ -0,0 +1,2 @@
+SHA256 (s-cdda-to-db-0.8.0.tar.gz) = 
fhk86RwPCsO+/W5rGfV8wrFhwjd7b14TJayTMuE59hI=
+SIZE (s-cdda-to-db-0.8.0.tar.gz) = 32519
diff -Napru audio.orig2/s-cdda-to-db/pkg/DESCR audio/s-cdda-to-db/pkg/DESCR
--- audio.orig2/s-cdda-to-db/pkg/DESCR  Thu Jan  1 01:00:00 1970
+++ audio/s-cdda-to-db/pkg/DESCRThu May 12 00:29:11 2022
@@ -0,0 +1,11 @@
+Queries content and data of audio CDs through s-cdda(1), collects
+informations (artist, album, song titles, etc.) of desired tracks,
+if possible correlates data with a web query against MusicBrainz,
+then places encoded tracks as well as a human readable and easily
+parseable database in a per-CD directory under a directory tree.
+The audio encoders (and sox(1) without --no-volume-normalize) need
+to be installed separately.
+(P.S.: the user will be asked to edit collected informations, and
+will be given a hand for the rather sophisticated, classical music
+aware) database layout while doing so.)
+(P.P.S.: nice foundation for link farms.)
diff -Napru audio.orig2/s-cdda-to-db/pkg/PLIST audio/s-cdda-to-db/pkg/PLIST
--- audio.orig2/s-cdda-to-db/pkg/PLIST  Thu Jan  1 01:00:00 1970
+++ audio/s-cdda-to-db/pkg/PLISTThu May 12 00:41:28 2022
@@ -0,0 +1,3 @@
+@pkgpath audio/s-cdda-to-db
+bin/s-cdda-to-db
+@man man/man1/s-cdda-to-db.1

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: [NEW] audio/s-cdda: access audio CDs (informations and track data)

[Steffen Nurpmeso]

Hello Omar.

Omar Polo wrote in
 <2HRCV4TLLPQOH.3C2ED8QH9XY1T@venera>:
 |Steffen Nurpmeso  wrote:
 |> My first from-scratch port, maybe of interest.
 ...
 |> diff -Napru audio.orig/s-cdda/Makefile audio/s-cdda/Makefile
 |
 |for new ports, please send a tarball.

Ok.  Ok will do that then for the three, tomorrow, ok?

 |while here thought, a few minor nits inline.  It looks good, but I can't
 |try it since I don't have any cdrom or the hardware to read them ^^
 |
 |> --- audio.orig/s-cdda/Makefile  Thu Jan  1 01:00:00 1970
 |> +++ audio/s-cdda/Makefile   Tue May 10 23:57:08 2022
 |> @@ -0,0 +1,21 @@
 |> +COMMENT=   access audio CDs (informations and track data)
 |
 |I'd probably drop the parenthesis

Ok.

 |> +
 |> +DISTNAME=  s-cdda-0.8.5
 |> +#REVISION= 0
 |
 |and the commented revision.  it's correct to not have a REVISION line
 |for new submission and updates that bumps a version.  (revision starts
 |empty, then goes 0, 1, ... and is reset upon every version change.)

'Thing is i am afraid i will forget it when i need it :)
But ok will do.

  ...
 |> +MAKE_FILE= makefile
 |
 |this is not strictly needed.  make looks also for a file called
 |"makefile" by default, so as long as you don't add another "Makefile" in
 |the tarball make(1) should do the right thing.

Yes it does.  I simply copied over from the S-nail port.  Will do.

  ...
 |> +++ audio/s-cdda/pkg/PLIST  Tue May 10 23:10:58 2022
 |> @@ -0,0 +1,3 @@
 |> +@pkgpath audio/s-cdda
 |
 |the @pkgpath is not needed to be set explicitly as it's the default
 |already.

Will remove it.

Thank you.

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: [NEW] mail/s-postgray: postfix graylisting policy server (fast+secure)

[Steffen Nurpmeso]

Omar Polo wrote in
 <3S1VORZPMKQPR.2D6JRDSHUPVF3@venera>:
 |Steffen Nurpmeso  wrote:
 |> Stuart Henderson wrote in
 |>  :
 |>|s/recommendet/recommended in DESCR, ok
 |> 
 |> Fixed in tarball.  (Permissions adjusted anyhow, too.)
 |> (And compiler flags as in other message.)
 |
 |imported with a minor tweak, thanks!

Oh, thank you. :)

(But i added the same "mechanism" for this one, and instead
removed these "newish" += for CFLAGS and LDFLAGS which somehow
exist in this makefile.)

There will be a s-postgray 0.7.0 somewhen, it has a better manual
after feedback from some people that saw the announcement on
postfix-users, --test-mode will output a valid resource file
(affects --allow etc only), and adds --msg-{allow,block,defer}
(and obsoletes "falsely named" --defer-msg -- but keeps its).
I do not expect changes other than that (a simple program).

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: [NEW] audio/s-cdda: access audio CDs (informations and track data)

[Steffen Nurpmeso]

Hello Omar.

Omar Polo wrote in
 <28P1AX08SNCS0.30TJDZ4GTJ8IJ@venera>:
 |Steffen Nurpmeso  wrote:
 |> Stuart Henderson wrote in
 |>  :
 |>|On 2022/05/13 00:22, Steffen Nurpmeso wrote:
 |>|> Since the S-nail port did not honour port CFLAGS for i think
 |>|> years, i hope it is ok to go like this for some time.
 |>|
 |>|That was because nobody had noticed it. Ports policy is to honour CFLAGS.
 |> 
 |> Sigh.  Works just fine on CRUX and Alpine Linux ;)
 |> Well i do not know.  The Python Makefile.inc does a virtuous
 |> dance, CRUX does "make EXTRA_CFLAGS="$CFLAGS"" after doing so (for
 ...
 |well, I can't speak for crux nor alpine, but as a general rule we want
 |to be in control of the CFLAGS the port uses when building.  Sometimes
 |one port slips, but that's the policy.
 |
 |If a compiler changes something (see for example the not too old clang
 |issue regarding -fcommon) you want to be able to fix the fallout by
 |tweaking the various Makefiles, not digging into every port build system
 |and patching things.

OK i understand the desire to add additional flags per se.

 |> Adding onto the environment's $CFLAGS the set of project's CFLAGS
 |> is ok?  I see what i can do tomorrow.  
 |
 |in this case it's as simple as (from the port makefile)
 |
 | MAKE_FLAGS += CFLAGS="${CFLAGS}"

If you would be so kind to add at least -DNDEBUG i would be fine.
In fact i wanted to go the hard way and add an EXTRA_CFLAGS
mechanism, and patch it into the port, but for OpenBSD it is ok.
Note please also do LDFLAGS="${LDFLAGS}" then, because the
built-in ones use -pie, and that requires -fPIE in CFLAGS, which
we then cannot guarantee.
A possible next release of s-cdda will have an EXTRA_CFLAGS
mechanism, already committed.

 |and if you're ok with that and sthen@ doesn't change his mind i'll
 |import it.

Thank you very much.

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: [NEW] mail/s-postgray: postfix graylisting policy server (fast+secure)

[Steffen Nurpmeso]

Stuart Henderson wrote in
 :
 |Please send new ports as tars, they are easier to work with
 |
 |@pkgpath markers should only be used when a port has already been
 |committed but the pkgpath is changed for some reason (either the
 |port directory is renamed, or more likely the port is split from a
 |single package to multipackages), they are used for building a set
 |of possible update candidates

Interestingly after "rm PLIST" "make plist" does not generate
"@bin X" for s-cdda and s-postgray, but does so for s-cdda-to-db?
But @pkgpath is gone for all, thank you.

 --End of 

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: [NEW] audio/s-cdda: access audio CDs (informations and track data)

[Steffen Nurpmeso]

Steffen Nurpmeso wrote in
 <20220510222731.mpq2x%stef...@sdaoden.eu>:
 |My first from-scratch port, maybe of interest.
 |
 |   Access digital audio CDs (TOC, MCN, ISRC, CD-TEXT, audio tracks).
 |   Developed in 2020 on then current operating-systems and hardware.
 |   Not tested with CD-Extra etc (only proofed logically).
 |   Linux and *BSD.
 |
 |This only interacts with SCSI MMC-3 aware cdrom/drivers (thus all
 |should do as of today i think).
 |Note -i (ISRC) and -x (CD-TEXT) (thus -a == all) are SCSI
 |quality-of-service, as said in manual.
 |The output is a bit scary as it is meant for usage by sh(1)ell (or
 |perl(1), in fact) usage.

With all comments from Omar and Stuart fixed, and as a ball.
Thank you!

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)


s-cdda.tar.gz
Description: application/tar-gzip

Re: [NEW] audio/s-cdda-to-db: perl program that creates a music database via s-cdda

[Steffen Nurpmeso]

Steffen Nurpmeso wrote in
 <20220511225516.qecds%stef...@sdaoden.eu>:
 |One more.
 |
 |  Queries content and data of audio CDs through s-cdda(1), collects
 |  informations (artist, album, song titles, etc.) of desired tracks,
 |  if possible correlates data with a web query against MusicBrainz,
 |  then places encoded tracks as well as a human readable and easily
 |  parseable database in a per-CD directory under a directory tree.
 |  The audio encoders (and sox(1) without --no-volume-normalize) need
 |  to be installed separately.
 |
 |^ Note especially this.  sox(1) is needed by default unless
 |a command line option is given, yet i did not want to add it to
 |RUN_DEPENDS?  Just like the audio encoders like faac(1) or
 |oggenc(1).
 |
 |  (P.S.: the user will be asked to edit collected informations, and
 |  will be given a hand for the rather sophisticated, classical music
 |  aware) database layout while doing so.)
 |
 |  (P.P.S.: nice foundation for link farms.)
 |
 |^ Also since as many informations are stored in the files itself
 |as possible.  The music.db (UTF-8) file is very simple to parse.
 |(The file names are just the track numbers.)

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)


s-cdda-to-db.tar.gz
Description: application/tar-gzip

Re: [NEW] mail/s-postgray: postfix graylisting policy server (fast+secure)

[Steffen Nurpmeso]

Steffen Nurpmeso wrote in
 <20220511232320.3wsz8%stef...@sdaoden.eu>:
 |Finally that one.
 |
 |RFC 6647 graylisting policy server, following the recommendet
 |practice noted in the standard document.  Graylisting defers
 |message acceptance (for a specific recipient / sender /
 |client_address value tuple) a configurable number of times via
 |a standardized SMTP response (see allow(5), RFC 5321), which does
 |not prevent message delivery from SMTP M(ail) T(ransfer) A(gent)s,
 |but can help against simple spam producing programs.
 |
 |s-postgray is started via spawn(8), with the given user
 |credentials, therefore the built-in DB store path is /tmp --
 |you surely want to change this.
 |Note s-postgray changes CWD to the configured --store-path, and
 |loads most files from therein.

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)


s-postgray.tar.gz
Description: application/tar-gzip

Re: [NEW] audio/s-cdda: access audio CDs (informations and track data)

[Steffen Nurpmeso]

Hello Omar.

Omar Polo wrote in
 <3G6K68XUPG6J2.2639ZNZN90LGM@venera>:
 |Steffen Nurpmeso  wrote:
 |> Omar Polo wrote in
 |>  <28P1AX08SNCS0.30TJDZ4GTJ8IJ@venera>:
 |>|Steffen Nurpmeso  wrote:
 |>|> Stuart Henderson wrote in
 |>|>  :
 |>|>|On 2022/05/13 00:22, Steffen Nurpmeso wrote:
 ...
 |>|well, I can't speak for crux nor alpine, but as a general rule we want
 |>|to be in control of the CFLAGS the port uses when building.  Sometimes
 |>|one port slips, but that's the policy.
 ...
 |> OK i understand the desire to add additional flags per se.
 |
 |(i forgot to add that this mechanisms is also used to generated debug
 |packages -- see bsd.port.mk for "THE DEBUG_PACKAGES INFRASTRUCTURE --
 |and possibly other things I haven't thought yet.  Oh, and from the POV
 |of a project, it's better to *append*, not prepend, the CFLAGS passed,
 |so users and packagers can effectively control the build process from
 |the outside)

Append is much better yes; the EXTRA_CFLAGS thing will place at
the end.  Reading this, DEBUG_CONFIGURE_ARGS will be needed for
s-nail and later s-postgray, and placing debug symbols in an
external file i had implemented in s-nail, this will be
interesting how it fits into OpenBSD port system then, it does

+ if [ -n "${DEBUG_IN_EXTERNAL_FILE}" ]; then
+${objcopy} --only-keep-debug "${_dst}" "${_dst}".debug
+${strip} -g "${_dst}"
+${objcopy} --add-gnu-debuglink="${_dst}".debug "${_dst}"
+
+${chown} ${_ident} "${_dst}".debug || true
+${chmod} 0644 "${_dst}".debug

But i surely will figure it out, some months to come anyhow.
Thanks for the info, Omar.

  ...
 |> If you would be so kind to add at least -DNDEBUG i would be fine.
 ...
 |imported, thanks!  (and audio/s-cdda-to-db too)

Thank you!

 |I didn't add -fPIE because on OpenBSD clang generates PIE code by
 |default (see clang-local(1) for the OpenBSD-specific behavior of llvm)

Oh, i did not know!
(I wonder where the backing for "See the documentation for the
-fsanitize-minimal-runtime flag" is.)

 |and I didn't add -DNDEBUG because I don't see any calls to assert(3).

That is ok for cdda with its freestanding code base.
(In general i also depend some sorts of inlining upon NDEBUG
because OPTIMIZE is not standardized.  But not yet used.  Well.)

 |if I've missed something please don't hesitate to point it out so that
 |we can fix it!
 |
 |regarding the other port, s-cdda-to-db, I've added NO_BUILD and PKG_ARCH
 |and tweaked a bit pkg/DESCR to avoid the post scriptum and to fix a typo
 |in "informations".

Thank you.

Ciao!

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: [NEW] audio/s-cdda: access audio CDs (informations and track data)

[Steffen Nurpmeso]

Hello Stuart.

Stuart Henderson wrote in
 :
 |oops, op@'s eyes are better than mine - build doesn't respect ports
 |CFLAGS

I do not know where op@ said something, but it is right that these
two Makefiles do not honour anything from the outside.
These are very simple makefiles, they choose the toughest
"compile-time security" they can.  Especially for s-postgray
i posted

  What should definitely change is the build system, it is
  intermediate because of the SU tools used, those are part of the
  S-nail MUA and so need to be "baked in".  Therefore:

Either it builds, then it should run.  Or not.  :-)
I have tested it on GNU and musl Linux, and on all BSDs.
(Solaris needs some build system work, but should do, too.)

I have implemented the part for S-nail, it will be in v14.10,
maybe in Autumn.  (Too much else to do, almost four years
"development" then for that branch, one i could accept.)
Then somewhen i will split the build system so that the SU tools
are a real submodule, and then we could become more "regular".

However quite some programs do not honour outside things as such,
maybe via --debug or so at configuration time.
Since the S-nail port did not honour port CFLAGS for i think
years, i hope it is ok to go like this for some time.

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: [NEW] audio/s-cdda: access audio CDs (informations and track data)

[Steffen Nurpmeso]

Stuart Henderson wrote in
 :
 |s/informations/information/ in COMMENT then it's ok sthen@
 |
 |if someone imports, mind the permissions on the files, the tar
 |has them set quite restrictively and I don't remember what cvs will
 |do with them, so probably safer to chmod -R +rX . by hand first

Is fixed in tarball.

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)


s-cdda.tar.gz
Description: application/gzip

Re: [NEW] audio/s-cdda-to-db: perl program that creates a music database via s-cdda

[Steffen Nurpmeso]

Stuart Henderson wrote in
 :
 |also ok, same comment re perms

Fixed in tarball.

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)


s-cdda-to-db.tar.gz
Description: application/gzip

Re: [NEW] mail/s-postgray: postfix graylisting policy server (fast+secure)

[Steffen Nurpmeso]

Stuart Henderson wrote in
 :
 |s/recommendet/recommended in DESCR, ok

Fixed in tarball.  (Permissions adjusted anyhow, too.)
(And compiler flags as in other message.)

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)


s-postgray.tar.gz
Description: application/gzip

Re: [NEW] audio/s-cdda: access audio CDs (informations and track data)

[Steffen Nurpmeso]

Stuart Henderson wrote in
 :
 |On 2022/05/13 00:22, Steffen Nurpmeso wrote:
 |> Since the S-nail port did not honour port CFLAGS for i think
 |> years, i hope it is ok to go like this for some time.
 |
 |That was because nobody had noticed it. Ports policy is to honour CFLAGS.

Sigh.  Works just fine on CRUX and Alpine Linux ;)
Well i do not know.  The Python Makefile.inc does a virtuous
dance, CRUX does "make EXTRA_CFLAGS="$CFLAGS"" after doing so (for
example 'CFLAGS="${CFLAGS/-O2/-O3} -ffat-lto-objects"', spooky).
You surely have to know what you append to the end of the list of
CFLAGS developers have chosen (if they did).

Adding onto the environment's $CFLAGS the set of project's CFLAGS
is ok?  I see what i can do tomorrow.  

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: [NEW] audio/s-cdda: access audio CDs (informations and track data)

[Steffen Nurpmeso]

Steffen Nurpmeso wrote in
 <20220512230021.bijcj%stef...@sdaoden.eu>:
 |Stuart Henderson wrote in
 | :
 ||On 2022/05/13 00:22, Steffen Nurpmeso wrote:
 ||> Since the S-nail port did not honour port CFLAGS for i think
 ||> years, i hope it is ok to go like this for some time.
 ||
 ||That was because nobody had noticed it. Ports policy is to honour CFLAGS.
 ...
 |Adding onto the environment's $CFLAGS the set of project's CFLAGS
 |is ok?  I see what i can do tomorrow.  

And thanks for looking into this, Stuart.

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: [UPDATE] mail/s-postgray: v0.7.0

[Steffen Nurpmeso]

Omar Polo wrote in
 <3P0JCKN6GHS3U.2CNEOXOGPIFQO@venera>:
 |Steffen Nurpmeso  wrote:
 ...
 |committed, thanks!

Thank you Omar!  That was .. tremendously quick.

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

[UPDATE] mail/s-postgray: v0.7.0

[Steffen Nurpmeso]

Hello ports@.

 |After hearing some voices from postfix-users i was doing an
 |iteration of this one.  (No real _need_ to update from v0.6.0.)
 |I could imagine this to be the last release, except for the
 |build system, which is still intermediate.
 ...
 |  - An iteration that fixes some oddities, and clarifies documentation.
 |(The example configuration is also better.)
 |
 |  - Bug fixes:
 |
 |. -v and -p were not reset for reload, thus fixated once set.
 |
 |. -b and -B were not command-line-parsed by the server, only in
 |  --test-mode (driven by client); usage in resource-file ok, too.
 |
 |  - --test-mode now outputs a normalized resource file.
 |
 |  - New --focus-sender approach which i like better.
 |
 |  [I personally now use --focus-sender mode with --count=1,
 |  --msg-allow=permit and --msg-defer='DEFER 4.2.0 blabla',
 |  and reject_unverified_sender thereafter.  I could imagine
 |  s-postgray to become obsolete if verify(8) would do a once-
 |  then-wait-five-minutes graylisting itself.]
 |
 |  - New --msg-{allow,block}, and --msg-defer for misnamed --defer-msg,
 |which is kept for compatibility.

Index: Makefile
===
RCS file: /cvs/ports/mail/s-postgray/Makefile,v
retrieving revision 1.1.1.1
diff -u -p -a -p -u -r1.1.1.1 Makefile
--- Makefile13 May 2022 17:30:07 -  1.1.1.1
+++ Makefile8 Jun 2022 18:23:56 -
@@ -1,11 +1,10 @@
 COMMENT=   fast and secure postfix graylisting policy server
 
-DISTNAME=  s-postgray-0.6.0
+DISTNAME=  s-postgray-0.7.0
 CATEGORIES=mail
 HOMEPAGE=  https://www.sdaoden.eu/code.html\#s-postgray
 
 MASTER_SITES=  https://ftp.sdaoden.eu/
-FIX_EXTRACT_PERMISSIONS=Yes
 
 MAINTAINER=Steffen Nurpmeso 
 
Index: distinfo
===
RCS file: /cvs/ports/mail/s-postgray/distinfo,v
retrieving revision 1.1.1.1
diff -u -p -a -p -u -r1.1.1.1 distinfo
--- distinfo13 May 2022 17:30:07 -  1.1.1.1
+++ distinfo8 Jun 2022 18:23:56 -
@@ -1,2 +1,2 @@
-SHA256 (s-postgray-0.6.0.tar.gz) = He6OqMiB1ctjcmFR9RQrX19MS/nHEz2l5xcKzooA0UY=
-SIZE (s-postgray-0.6.0.tar.gz) = 127563
+SHA256 (s-postgray-0.7.0.tar.gz) = 3K40FbXtAUyDtcUPtWBW0tHh/toB/rZ4/7Z3vX1uFs0=
+SIZE (s-postgray-0.7.0.tar.gz) = 140144

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

[NEW] audio/s-cdda: access audio CDs (informations and track data)

[Steffen Nurpmeso]

Hello.

My first from-scratch port, maybe of interest.

   Access digital audio CDs (TOC, MCN, ISRC, CD-TEXT, audio tracks).
   Developed in 2020 on then current operating-systems and hardware.
   Not tested with CD-Extra etc (only proofed logically).
   Linux and *BSD.

This only interacts with SCSI MMC-3 aware cdrom/drivers (thus all
should do as of today i think).
Note -i (ISRC) and -x (CD-TEXT) (thus -a == all) are SCSI
quality-of-service, as said in manual.
The output is a bit scary as it is meant for usage by sh(1)ell (or
perl(1), in fact) usage.

diff -Napru audio.orig/s-cdda/Makefile audio/s-cdda/Makefile
--- audio.orig/s-cdda/Makefile  Thu Jan  1 01:00:00 1970
+++ audio/s-cdda/Makefile   Tue May 10 23:57:08 2022
@@ -0,0 +1,21 @@
+COMMENT=   access audio CDs (informations and track data)
+
+DISTNAME=  s-cdda-0.8.5
+#REVISION= 0
+CATEGORIES=audio
+HOMEPAGE=  https://www.sdaoden.eu/code.html\#s-cdda
+
+MASTER_SITES=  https://ftp.sdaoden.eu/
+MAINTAINER=Steffen Nurpmeso 
+
+# ISC
+PERMIT_PACKAGE=Yes
+
+WANTLIB+=  c
+
+MAKE_FILE= makefile
+MAKE_FLAGS=MANDIR="${DESTDIR}${PREFIX}"/man/man1
+
+NO_TEST=   Yes
+
+.include 
diff -Napru audio.orig/s-cdda/distinfo audio/s-cdda/distinfo
--- audio.orig/s-cdda/distinfo  Thu Jan  1 01:00:00 1970
+++ audio/s-cdda/distinfo   Tue May 10 23:43:49 2022
@@ -0,0 +1,2 @@
+SHA256 (s-cdda-0.8.5.tar.gz) = lc1mRRR6wAz8L8pIdNytb3mldUApr2cHg1a7H8fFHNY=
+SIZE (s-cdda-0.8.5.tar.gz) = 17885
diff -Napru audio.orig/s-cdda/pkg/DESCR audio/s-cdda/pkg/DESCR
--- audio.orig/s-cdda/pkg/DESCR Thu Jan  1 01:00:00 1970
+++ audio/s-cdda/pkg/DESCR  Tue May 10 23:12:05 2022
@@ -0,0 +1,3 @@
+s-cdda queries information, like the table-of-contents, from audio CD-ROMs.
+It also reads audio tracks to store them as WAVE audio files.
+It only works with SCSI MMC-3 aware cdrom/drivers.
diff -Napru audio.orig/s-cdda/pkg/PLIST audio/s-cdda/pkg/PLIST
--- audio.orig/s-cdda/pkg/PLIST Thu Jan  1 01:00:00 1970
+++ audio/s-cdda/pkg/PLIST  Tue May 10 23:10:58 2022
@@ -0,0 +1,3 @@
+@pkgpath audio/s-cdda
+@bin bin/s-cdda
+@man man/man1/s-cdda.1

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: [UPDATE] mail/s-postgray: v0.8.0

[Steffen Nurpmeso]

Hello Omar!

Omar Polo wrote in
 <2QQ8HVULYU66Z.2I0646W5TV2VB@venera>:
 |On 2022/09/16 17:11:38 +0200, Steffen Nurpmeso  wrote:
 |> Omar Polo pointed out in private that i indeed had forgotten the
 |> patch, thanks again.  Quite ridiculous.
 |> 
 |> So here the patch in public, too.
 |
 |Sorry for the delay.

Oh please, wonderful, thank you!

 |Committed with two small edits, thanks!
 ...
 |> +DISTNAME=  s-postgray-0.8.0
 |
 |added FIX_EXTRACT_PERMISSIONS for it to build with PORTS_PRIVSEP:
 |different users needs to poke things in the build dir and so lax
 |permissions (644 or the like) are needed.

Ah, my umask again, not fixed for this build "system".
Sorry!

Ciao!!

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: [UPDATE] mail/s-postgray: v0.8.0

[Steffen Nurpmeso]

Hello.

Omar Polo pointed out in private that i indeed had forgotten the
patch, thanks again.  Quite ridiculous.

So here the patch in public, too.

Ciao.

Index: Makefile
===
RCS file: /cvs/ports/mail/s-postgray/Makefile,v
retrieving revision 1.2
diff -u -p -a -p -u -r1.2 Makefile
--- Makefile8 Jun 2022 20:59:10 -   1.2
+++ Makefile16 Sep 2022 14:16:13 -
@@ -1,6 +1,6 @@
 COMMENT=   fast and secure postfix graylisting policy server
 
-DISTNAME=  s-postgray-0.7.0
+DISTNAME=  s-postgray-0.8.0
 CATEGORIES=mail
 HOMEPAGE=  https://www.sdaoden.eu/code.html\#s-postgray
 
@@ -20,6 +20,7 @@ MAKE_FLAGS=   MANDIR="${DESTDIR}${PREFIX}
 # get rid of hardcoded -O2
 MAKE_FLAGS+=   SUFOPT=-I./include
 
-NO_TEST=   Yes
+test:
+   cd ${WRKBUILD} && ./s-postgray-test.sh
 
 .include 
Index: distinfo
===
RCS file: /cvs/ports/mail/s-postgray/distinfo,v
retrieving revision 1.2
diff -u -p -a -p -u -r1.2 distinfo
--- distinfo8 Jun 2022 20:59:10 -   1.2
+++ distinfo16 Sep 2022 14:16:13 -
@@ -1,2 +1,2 @@
-SHA256 (s-postgray-0.7.0.tar.gz) = 3K40FbXtAUyDtcUPtWBW0tHh/toB/rZ4/7Z3vX1uFs0=
-SIZE (s-postgray-0.7.0.tar.gz) = 140144
+SHA256 (s-postgray-0.8.0.tar.gz) = TR44Q3hUfAx+6KV6u8ZktUmlH7Zo1E4zqZTQJj+V1TI=
+SIZE (s-postgray-0.8.0.tar.gz) = 142362
Index: pkg/DESCR
===
RCS file: /cvs/ports/mail/s-postgray/pkg/DESCR,v
retrieving revision 1.1.1.1
diff -u -p -a -p -u -r1.1.1.1 DESCR
--- pkg/DESCR   13 May 2022 17:30:07 -  1.1.1.1
+++ pkg/DESCR   16 Sep 2022 14:16:13 -
@@ -5,6 +5,11 @@ Graylisting defers message acceptance (f
 via a standardized SMTP response (see allow(5), RFC 5321), which does
 not prevent message delivery from SMTP M(ail) T(ransfer) A(gent)s,
 but can help against simple spam producing programs.
-s-postgray is started via spawn(8), with the given user credentials,
-therefore the built-in DB store path is /tmp -- you surely want to
-change this via configuration file or command line option.
+
+s-postgray clients are started via spawn(8), as shown in the manual.
+The server is started by clients as necessary, but it can be --startup
+also since v0.8.0.
+
+s-postgray needs to be configured as the builtin DB store path is /tmp
+(see manual), user and group settings are inherited from spawn(8) (or
+the environment which uses --startup).

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

[UPDATE] mail/s-postgray: v0.8.0

[Steffen Nurpmeso]

Hello ports@!

  - New --startup mode to allow it to be driven as a standalone daemon.

  - Client no longer exits after five unsuccessful connection attempts.
Instead try as long as postfix is willing to let it.

  - "Fixes a miss": if on server startup the socket yet existed (no
proper shutdown on last run), startup failed and the missing policy
server would cause postfix to refuse acting.
Whereas "rm -f PG-SOCKET" in a postfix-startup-script avoids this,
it was never announced to be necessary, so henceforth automatize this.

  - Robustness against MFILE,NFILE,NOBUF,NOMEM in file/socket open paths.

  - Fixes some oddities, and clarifies documentation.

The port now actually runs the tests.

Except for the intermediate self-knitted build system (and bitrot)
i really do not expect any further release now.

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

[UPDATE] mail/s-postgray: v0.8.1

[Steffen Nurpmeso]

Hello ports@!

"Something Gray on Bicycle-Day" was unfortunately necessary, so
i spent some time and implemented sandboxing.
I expect no "real" further releases.

   postfix(1) graylisting policy daemon.  See its README + manual for more.
   [.]
   * Many, many thanks to Jens Schleusener, and his cron job!
   + Add --status to query server status.
   + Server PID is now stored in the lock file (renamed to VAL_NAME.pid),
 and --startup now waits for server response (like --shutdown does).
   + Add sandboxing: generic setrlimit(2) based, plus an OS-dependent
 strict sandboxing that can be disabled via --untamed.  (Because it may
 require an additional, internally managed, logger process, and may be
 incompatible to (future) C library changes (see makefile).)
 (On OpenBSD configured file paths are now even fixed byte-by-byte.)

^ pledge/unveil: SIGHUP configuration reload requires that
actually used file paths have not changed (byte-wise).

   - FIX memory map return check.
   - FIX possible error path crash during program startup (missing fmt arg).
   - fix: add missing su_log_set_level() and make --verbose work for users!
   - fix: --startup was missing short -@ equivalent.
   - fix: --test-mode did not include "focus-sender", "once" and "verbose".
   - fix: VAL_MSG_* could not be overwritten on make(1) command line.
   - Typos: treshold->threshold.  (Jens Schleusener)
   - (Source code style change spaces/80 -> tab/120+, saves ~12KB; etc.)

Ciao!

Index: Makefile
===
RCS file: /cvs/ports/mail/s-postgray/Makefile,v
retrieving revision 1.4
diff -u -p -a -p -u -r1.4 Makefile
--- Makefile31 Oct 2022 23:14:54 -  1.4
+++ Makefile20 Apr 2023 20:09:55 -
@@ -1,11 +1,10 @@
 COMMENT=   fast and secure postfix graylisting policy server
 
-DISTNAME=  s-postgray-0.8.0
+DISTNAME=  s-postgray-0.8.1
 CATEGORIES=mail
 HOMEPAGE=  https://www.sdaoden.eu/code.html\#s-postgray
 
 MASTER_SITES=  https://ftp.sdaoden.eu/
-FIX_EXTRACT_PERMISSIONS=Yes
 
 MAINTAINER=Steffen Nurpmeso 
 
@@ -19,7 +18,7 @@ MAKE_FLAGS=   MANDIR="${DESTDIR}${PREFIX}
VAL_STORE_PATH=/tmp
 
 # get rid of hardcoded -O2
-MAKE_FLAGS+=   SUFOPT=-I./include
+MAKE_FLAGS+=   SUFOPT="-DNDEBUG -I./include"
 
 do-test:
cd ${WRKBUILD} && ./s-postgray-test.sh
Index: distinfo
===
RCS file: /cvs/ports/mail/s-postgray/distinfo,v
retrieving revision 1.3
diff -u -p -a -p -u -r1.3 distinfo
--- distinfo19 Sep 2022 15:02:29 -  1.3
+++ distinfo20 Apr 2023 20:09:55 -
@@ -1,2 +1,2 @@
-SHA256 (s-postgray-0.8.0.tar.gz) = TR44Q3hUfAx+6KV6u8ZktUmlH7Zo1E4zqZTQJj+V1TI=
-SIZE (s-postgray-0.8.0.tar.gz) = 142362
+SHA256 (s-postgray-0.8.1.tar.gz) = pFwBgDsPo/HUWwj7XjC0uLkkShuMcEwqrvp+SFrLTMg=
+SIZE (s-postgray-0.8.1.tar.gz) = 156386

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: audio/sox unbreak wav gsm

[Steffen Nurpmeso]

Nam Nguyen wrote in
 <877cus7en1.fsf@n.m>:
 |wav gsm playback and encoding is broken because the wav.c patch to avoid
 |division by 0 introduced a regression. Debian has a fix for an older
 |version of sox from Helmut Grohne . This patch
 |is from Steffen Nurpmeso  who applied it
 |against git. I added a tweak to not recalculate wave->numSamples for wav
 |gsm files, which is where division by 0 happens. Apparently, gsm has
 |variable bits_per_sample, so 0 is an acceptable value.

This is total exaggeration.
I had broken gsm, did not look at all, did not care a bit, gave
a crap, then Nam came and fixed it.  Only like so for sure.

  ...

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: [UPDATE] mail/s-postgray: v0.8.1

[Steffen Nurpmeso]

Hello Omar.

Omar Polo wrote in
 <1Z17OUITT1QF6.1YP5V5TQELDRI@venera>:
 |On 2023/05/19 19:10:25 +0200, Steffen Nurpmeso  wrote:
 |> Hello;
 |> 
 |> anyone interested in this?  Works fine.
 |> (The last test runs a bit slow on OpenBSD, it finishes in the
 |> fraction of a second everywhere else.  But its malloc has other
 |> priorities than speed, one should look.)
 |
 |sorry for the delay,
 |committed, thanks! :)

Wonderful, thank you very much!

 --End of <1Z17OUITT1QF6.1YP5V5TQELDRI@venera>

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)
|~~
|..and in spring, hear David Leonard sing..
|
|The black bear,  The black bear,
|blithely holds his own   holds himself at leisure
|beating it, up and down  tossing over his ups and downs with pleasure
|~~
|Farewell, dear collar bear

Re: [UPDATE] mail/s-postgray: v0.8.1

[Steffen Nurpmeso]

Hello;

anyone interested in this?  Works fine.
(The last test runs a bit slow on OpenBSD, it finishes in the
fraction of a second everywhere else.  But its malloc has other
priorities than speed, one should look.)

--- Forwarded from Steffen Nurpmeso  ---
Hello ports@!

"Something Gray on Bicycle-Day" was unfortunately necessary, so
i spent some time and implemented sandboxing.
I expect no "real" further releases.

   postfix(1) graylisting policy daemon.  See its README + manual for more.
   [.]
   * Many, many thanks to Jens Schleusener, and his cron job!
   + Add --status to query server status.
   + Server PID is now stored in the lock file (renamed to VAL_NAME.pid),
 and --startup now waits for server response (like --shutdown does).
   + Add sandboxing: generic setrlimit(2) based, plus an OS-dependent
 strict sandboxing that can be disabled via --untamed.  (Because it may
 require an additional, internally managed, logger process, and may be
 incompatible to (future) C library changes (see makefile).)
 (On OpenBSD configured file paths are now even fixed byte-by-byte.)

^ pledge/unveil: SIGHUP configuration reload requires that
actually used file paths have not changed (byte-wise).

   - FIX memory map return check.
   - FIX possible error path crash during program startup (missing fmt arg).
   - fix: add missing su_log_set_level() and make --verbose work for users!

[^ "That was the thing"; only in development code did logging
work.  Such a mess.]

   - fix: --startup was missing short -@ equivalent.
   - fix: --test-mode did not include "focus-sender", "once" and "verbose".
   - fix: VAL_MSG_* could not be overwritten on make(1) command line.
   - Typos: treshold->threshold.  (Jens Schleusener)
   - (Source code style change spaces/80 -> tab/120+, saves ~12KB; etc.)

Ciao!

Index: Makefile
===
RCS file: /cvs/ports/mail/s-postgray/Makefile,v
retrieving revision 1.4
diff -u -p -a -p -u -r1.4 Makefile
--- Makefile31 Oct 2022 23:14:54 -  1.4
+++ Makefile20 Apr 2023 20:09:55 -
@@ -1,11 +1,10 @@
 COMMENT=   fast and secure postfix graylisting policy server
 
-DISTNAME=  s-postgray-0.8.0
+DISTNAME=  s-postgray-0.8.1
 CATEGORIES=mail
 HOMEPAGE=  https://www.sdaoden.eu/code.html\#s-postgray
 
 MASTER_SITES=  https://ftp.sdaoden.eu/
-FIX_EXTRACT_PERMISSIONS=Yes
 
 MAINTAINER=Steffen Nurpmeso 
 
@@ -19,7 +18,7 @@ MAKE_FLAGS=   MANDIR="${DESTDIR}${PREFIX}
VAL_STORE_PATH=/tmp
 
 # get rid of hardcoded -O2
-MAKE_FLAGS+=   SUFOPT=-I./include
+MAKE_FLAGS+=   SUFOPT="-DNDEBUG -I./include"
 
 do-test:
cd ${WRKBUILD} && ./s-postgray-test.sh
Index: distinfo
===
RCS file: /cvs/ports/mail/s-postgray/distinfo,v
retrieving revision 1.3
diff -u -p -a -p -u -r1.3 distinfo
--- distinfo19 Sep 2022 15:02:29 -  1.3
+++ distinfo20 Apr 2023 20:09:55 -
@@ -1,2 +1,2 @@
-SHA256 (s-postgray-0.8.0.tar.gz) = TR44Q3hUfAx+6KV6u8ZktUmlH7Zo1E4zqZTQJj+V1TI=
-SIZE (s-postgray-0.8.0.tar.gz) = 142362
+SHA256 (s-postgray-0.8.1.tar.gz) = pFwBgDsPo/HUWwj7XjC0uLkkShuMcEwqrvp+SFrLTMg=
+SIZE (s-postgray-0.8.1.tar.gz) = 156386

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)
|~~
|..and in spring, hear David Leonard sing..
|
|The black bear,  The black bear,
|blithely holds his own   holds himself at leisure
|beating it, up and down  tossing over his ups and downs with pleasure
|~~
|Farewell, dear collar bear

Re: [update] www/yt-dlp to 2023.11.16

[Steffen Nurpmeso]

Justin Berthault wrote in
 :
 |On Fri, Nov 17, 2023 at 08:23:58AM +, Stuart Henderson wrote:
 |> When a port has a maintainer, you should CC them, don't rely on
 |> them reading ports@.
 |
 |I included him in the first mail, forgot to cc after that. Sorry. 
 |
 |Still learning the good way to do it.

I maintain that (unfortunately: python!) for a Linux and my recipe

  name=yt-dlp
  version=2023.11.16
  release=1
  source=(https://github.com/${name}/${name}/releases/download/\
  ${version}/${name}.tar.gz)
  renames=(${name}-${version}.tar.gz)

  build() {
  cd ${name} #-${version}

  install -D ${name} "${PKG}"/usr/bin/${name}
  install -D -m 0644 ${name}.1 "${PKG}"/usr/share/man/man1/${name}.1

  if prt-get isinst bash-completion > /dev/null 2>&1; then
  install -D completions/bash/yt-dlp \
  "${PKG}"/usr/share/bash-completion/completions/${name}
  fi
  }

results in

  $ pkginfo -l yt-dlp
  usr/
  usr/bin/
  usr/bin/yt-dlp
  usr/share/
  usr/share/man/
  usr/share/man/man1/
  usr/share/man/man1/yt-dlp.1.gz

  $ file /usr/bin/yt-dlp
  /usr/bin/yt-dlp: a /usr/bin/env python3 script executable (Zip archive)

I find this approach that upstream thankfully provides much nicer
than yours with the thousands of python files that noone but
yt-dlp ever needs.

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: patch dkimproxy: use rsa-sha256 in sample signing config

[Steffen Nurpmeso]

Hello.

Kirill A. Korinsky wrote in
 <5285e80cbc0d1...@mx2.catap.net>:
 |On Fri, 10 May 2024 10:47:43 +0100,
 |Stuart Henderson  wrote:
 |> On 2024/05/10 11:40, Matthieu Herrb wrote:
 |>> Afaict dkimpproxy is not using opendkim but p5-Mail-DKIM. dkimproxy
 |>> itself also hasn't seen a update since many years, but the underlying
 |>> perl lib has been last updated last january (and could use an update
 |>> in the port).
 |>> 
 |>> So unless you imply that because many people use opendkim, ed25519
 |>> based signatures shouldn't be used at all I'm not sure I understand
 |>> what you're saying.
 |> 
 |> ed25519 can be used, but at the moment if you do use it, you probably
 |> want to be double-signing with both that + rsa-sha256.
 |> 
 |
 |I imply that using ed25519 usually leads to malformed signature, and some
 |big hosting providers treat double signature as bad signature if some of
 |them are not RSA-SHA256. A notable example is icloud.com, which delivers \
 |all
 |emails with double signatures to the junk folder. At least that's what they
 |did the last time I checked in December'23.

Then these are not standard compliant.  The DKIM standard 6376
*explicitly* supports multiple signatures.

 |So I suggest to put in README and config exmaple that using anything other
 |than RSA-SHA256 may lead to delivery email to thte junk. Unfortunately, \
 |this
 |includes duble signatures as well.

On the IETF DKIM list there are people which told me they use such
a configuration since 2019 without any issues, and i myself use it
for two months, too, and did not have problems; that cloud thing
i never saw, though.

Btw my postfix-only s-dkim-sign will become a port soon, i only
want to have an update to s-postgray first, and then do all the
ports in one go.  Dunno whether i make it tomorrow, but early next
week for sure.  (It simply compiles, tests and runs on OpenBSD out
of the box.)

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: patch dkimproxy: use rsa-sha256 in sample signing config

[Steffen Nurpmeso]

Hello Kirill.

Kirill A. Korinsky wrote in
 <2fdd33f2325e6...@mx2.catap.net>:
 |On Sat, 11 May 2024 00:21:18 +0100,
 |Steffen Nurpmeso  wrote:
 |> Kirill A. Korinsky wrote in
 |>  <5285e80cbc0d1...@mx2.catap.net>:
 |
 |BTW this is quite wired address which seems like Message-Id

That is what it is.

 |>|I imply that using ed25519 usually leads to malformed signature, and some
 |>|big hosting providers treat double signature as bad signature if some of
 |>|them are not RSA-SHA256. A notable example is icloud.com, which delivers \
 |>|\
 |>|all
 |>|emails with double signatures to the junk folder. At least that's \
 |>|what they
 |>|did the last time I checked in December'23.
 |> 
 |> Then these are not standard compliant.  The DKIM standard 6376
 |> *explicitly* supports multiple signatures.
 |
 |Yes, RFC may imply that but OpenDKMI was released quite a while ago and the
 |last stable release seems that doesn't handle well this case.

OpenDKIM cannot.  I looked at its code in about January and there
is no notion of it.  zdkimfilter as of courier bases upon it, and
supports it.  (Very preprocessor sprinkled crypto code in between
several libraries that uses, though, and the OpenSSL 3.0 thing
even fiddles with openssl parameters which i have *not*
understood from my short glance..)

 |>|So I suggest to put in README and config exmaple that using anything \
 |>|other
 |>|than RSA-SHA256 may lead to delivery email to thte junk. Unfortunately, \
 |>|this
 |>|includes duble signatures as well.
 |> 
 |> On the IETF DKIM list there are people which told me they use such
 |> a configuration since 2019 without any issues, and i myself use it
 |> for two months, too, and did not have problems; that cloud thing
 |> i never saw, though.
 |
 |Here I've sent to some tool which is used to check email configuration a
 |test email with 2 singatures [1] and with 1 [2], the same behaviour \
 |I saw in
 |icloud.com.
 |
 |I've tracked that issue last Decemner and it had status that second
 |signature or non RSA-SHA256 leads to not valid signature and delivery email
 |into junk folder. Probably.
 |
 |Footnotes:
 |[1]  https://mxtoolbox.com/deliverability/8d9efa25-f421-4582-a0fb-652f01\
 |46dfce
 |
 |[2]  https://mxtoolbox.com/deliverability/42b985b2-c8a1-44b2-a9ed-4bf86a\
 |604e54

It does not matter that the Ed25519 code is not understood, the
RFC 6376 is a very, very thought through standard and has all that
foreseen indeed.  From a short look at the first it seems your
real problem why this fails is that *all* signatures are rejected,
and the RSA is because it uses SHA-1, however, SHA-1 was
explicitly forbidden by RFC 8301 as of January 2018:

   Due to the recognized weakness of the SHA-1 hash algorithm (see
   [RFC6194]) and the wide availability of the SHA-256 hash algorithm
   (it has been a required part of DKIM [RFC6376] since it was
   originally standardized in 2007), the SHA-1 hash algorithm MUST NOT
   be used.  This is being done now to allow the operational community
   time to fully shift to SHA-256 in advance of any SHA-1-related
   crisis.

I could very much imagine that if you change to RSA-SHA256 then
your problem will vanish.

 --End of <2fdd33f2325e6...@mx2.catap.net>

Ciao,

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Re: patch dkimproxy: use rsa-sha256 in sample signing config

[Steffen Nurpmeso]

Hello Kirill.

Kirill A. Korinsky wrote in
 <98c1f03bc1d6c...@mx1.catap.net>:
 ...
 |> Kirill A. Korinsky wrote in
 |>  <2fdd33f2325e6...@mx2.catap.net>:
 |>|>|I imply that using ed25519 usually leads to malformed signature, \
 ...
 |>|> Then these are not standard compliant.  The DKIM standard 6376
 |>|> *explicitly* supports multiple signatures.
 |>|
 |>|Yes, RFC may imply that but OpenDKMI was released quite a while ago \
 |>|and the
 |>|last stable release seems that doesn't handle well this case.
 |> 
 |> OpenDKIM cannot.  I looked at its code in about January and there
 |> is no notion of it.  zdkimfilter as of courier bases upon it, and
 |> supports it.  (Very preprocessor sprinkled crypto code in between
 |> several libraries that uses, though, and the OpenSSL 3.0 thing
 |> even fiddles with openssl parameters which i have *not*
 |> understood from my short glance..)
 |
 |And here the issue and my point: until OpenDKIM is supporting anything else
 |than RSA may lead to delivery emails into Junk.

No, Kirill, you are misunderstanding a little bit how DKIM works.

  ...
 |> I could very much imagine that if you change to RSA-SHA256 then
 |> your problem will vanish.
 |
 |Nope, it doesn't
 |
 |See mxtoolbox [1] for the case of RSA-SHA256 and icloud says, let me quote:
 |
 |  Authentication-Results: dkim-verifier.icloud.com; dkim=permerror \
 |  (0-bit key) header.d=korins.ky header.i=@korins.ky header.b=VNwI9oir
 |  Authentication-Results: dkim-verifier.icloud.com; dkim=pass (2048-bit \
 |  key) header.d=korins.ky header.i=@korins.ky header.b=qwDQ6QCD
 |
 |The issue that one of signatures is invalid, and icloud moves mail to the
 |Junk folder.

Because DKIM says that as long as *one* signature passes
correctly, DKIM has succeeded.  The introduction of new algorithms
and key changes etc is quite broadly foreseen in a lot of RFCs
regarding public key infrastructure in the last two decades (my
view is very limited however, but, still..).

 |As soon as I use only RSA signatures, emails are delivered to inbox.

This is broken behaviour of these people, see RFC 6376, 6.1:

  INFORMATIVE NOTE: The rationale of this requirement is to permit
  messages that have invalid signatures but also a valid signature
  to work.
  ...
  the message should succeed even in the presence of the
  known-broken signature.

What they are doing is wrong.  Maybe if you move it out of Junk
a few times their algorithm learns or what, i do not know.
I would start screaming, but normally noone listens anyhow, sure.

 |Footnotes:
 |[1]  https://mxtoolbox.com/deliverability/86e2b0ff-ba95-47f3-b71e-4ead73\
 |653a73

Ah, you, i do not look, this required Javascript and whatnot.

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

[NEW] mail/s-dkim-sign: postfix-only DKIM sign-only milter

[Steffen Nurpmeso]

Hello.

Unfortunately i had messed compatibility with OpenSSL 1.1 and
ReSSL on April 30th it seems (after all that lengthy testing),
which is why there needs to be a patch.

Index: s-dkim-sign/Makefile
===
RCS file: s-dkim-sign/Makefile
diff -N s-dkim-sign/Makefile
--- /dev/null   1 Jan 1970 00:00:00 -
+++ s-dkim-sign/Makefile19 May 2024 00:04:09 -
@@ -0,0 +1,30 @@
+COMMENT=   postfix(1)-only DKIM sign-only milter
+
+DISTNAME=  s-dkim-sign-0.6.1
+CATEGORIES=mail
+HOMEPAGE=  https://www.sdaoden.eu/code.html\#s-dkim-sign
+
+SITES= https://ftp.sdaoden.eu/
+
+MAINTAINER=Steffen Nurpmeso 
+
+# ISC
+PERMIT_PACKAGE=Yes
+
+COMPILER=  base-clang ports-gcc
+COMPILER_LANGS=c
+
+# uses pledge()
+# uses unveil()
+WANTLIB+=  c
+
+MAKE_FILE= makefile
+MAKE_FLAGS=MANDIR="${DESTDIR}${PREFIX}"/man/man8
+
+# get rid of hardcoded -O2
+MAKE_FLAGS+=   SUFOPT="-DNDEBUG -I./include"
+
+do-test:
+   cd ${WRKBUILD} && ./s-dkim-sign-test.sh
+
+.include 
Index: s-dkim-sign/distinfo
===
RCS file: s-dkim-sign/distinfo
diff -N s-dkim-sign/distinfo
--- /dev/null   1 Jan 1970 00:00:00 -
+++ s-dkim-sign/distinfo19 May 2024 00:04:09 -
@@ -0,0 +1,2 @@
+SHA256 (s-dkim-sign-0.6.1.tar.gz) = 
u0qLh+1ijxd3UGGzkBPE7IijdcMWZDi6bXy6SaPQ/X4=
+SIZE (s-dkim-sign-0.6.1.tar.gz) = 185602
Index: s-dkim-sign/patches/patch-s_dkim_sign_c
===
RCS file: s-dkim-sign/patches/patch-s_dkim_sign_c
diff -N s-dkim-sign/patches/patch-s_dkim_sign_c
--- /dev/null   1 Jan 1970 00:00:00 -
+++ s-dkim-sign/patches/patch-s_dkim_sign_c 19 May 2024 00:04:09 -
@@ -0,0 +1,13 @@
+diff --git a/s-dkim-sign.c b/s-dkim-sign.c
+index c92be084e4..81d2da79f9 100644
+--- s-dkim-sign.c
 s-dkim-sign.c
+@@ -112,7 +112,7 @@
+ # define a_PKEY_GET_SIZE(X) EVP_PKEY_get_size(X)
+ #else
+ # undef a_MD_FETCH
+-# define a_PKEY_GET_SIZE(X) EVP_MAX_KEY_LENGTH
++# define a_PKEY_GET_SIZE(X) EVP_PKEY_size(X)
+ #endif
+ 
+ /* milter-protocol.txt {{{ */
Index: s-dkim-sign/pkg/DESCR
===
RCS file: s-dkim-sign/pkg/DESCR
diff -N s-dkim-sign/pkg/DESCR
--- /dev/null   1 Jan 1970 00:00:00 -
+++ s-dkim-sign/pkg/DESCR   19 May 2024 00:04:09 -
@@ -0,0 +1,6 @@
+A postfix(1)-only RFC 6376/[8301]/8463 D(omain)K(eys) I(dentified)
+M(ail) sign-only milter.
+The program is intended to be started via the postfix(1) spawn(8)
+daemon, which takes care of the correct user and group credentials,
+timeouts and stale server garbage collection etc.
+Just see the manual page.
Index: s-dkim-sign/pkg/PLIST
===
RCS file: s-dkim-sign/pkg/PLIST
diff -N s-dkim-sign/pkg/PLIST
--- /dev/null   1 Jan 1970 00:00:00 -
+++ s-dkim-sign/pkg/PLIST   19 May 2024 00:04:09 -
@@ -0,0 +1,4 @@
+@bin libexec/s-dkim-sign
+@man man/man8/s-dkim-sign-key-create.8
+@man man/man8/s-dkim-sign.8
+sbin/s-dkim-sign-key-create

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)