fyi: ftp.openbsd.org: download connection breaks over slow lines

[Steffen Nurpmeso]

Hello.

'Appeared as forceful breaks, ie, there were no seconds without
any activity, but real breaks from now to then.
Just in case anyone feels the desire to look and tune, or
whatever.

  -rw-rw  1 ports ports461016 Aug 12 19:05 openssh-9.4p1.tar.gz.partial
  $ curl --continue-at - --compressed -O 
https://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-9.4p1.tar.gz
% Total% Received % Xferd  Average Speed   TimeTime Time  
Current
   Dload  Upload   Total   SpentLeft  Speed
   24 1801k   24  448k0 0   7226  0  0:04:15  0:01:03  0:03:12  8000
  curl: (18) transfer closed with 1386342 bytes remaining to read
  $ curl --continue-at - --compressed -O 
https://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-9.4p1.tar.gz
  ** Resuming transfer from byte position 458752
% Total% Received % Xferd  Average Speed   TimeTime Time  
Current
   Dload  Upload   Total   SpentLeft  Speed
   33 1353k   33  448k0 0   7283  0  0:03:10  0:01:02  0:02:08  8000
  curl: (18) transfer closed with 927590 bytes remaining to read
  $ curl --continue-at - --compressed -O 
https://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-9.4p1.tar.gz
  ** Resuming transfer from byte position 917504
% Total% Received % Xferd  Average Speed   TimeTime Time  
Current
   Dload  Upload   Total   SpentLeft  Speed
   49  905k   49  448k0 0   7171  0  0:02:09  0:01:03  0:01:06  4000
  curl: (18) transfer closed with 468838 bytes remaining to read
  $ curl --continue-at - --compressed -O 
https://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-9.4p1.tar.gz
  ** Resuming transfer from byte position 1376256
% Total% Received % Xferd  Average Speed   TimeTime Time  
Current
   Dload  Upload   Total   SpentLeft  Speed
   97  457k   97  448k0 0   7146  0  0:01:05  0:01:04  0:00:01  9364
  curl: (18) transfer closed with 10086 bytes remaining to read
  $ curl ipv4.icanhazip.com
  217.144.132.164
  $ curl --continue-at - --compressed -O 
https://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-9.4p1.tar.gz
  ** Resuming transfer from byte position 1835008
% Total% Received % Xferd  Average Speed   TimeTime Time  
Current
   Dload  Upload   Total   SpentLeft  Speed
  100 10086  100 100860 0   9417  0  0:00:01  0:00:01 --:--:--  9426
  $ ll openssh-9.*
  -rw-rw 1 ports ports 1835850 Jul 19 23:22 openssh-9.3p2.tar.gz
  -rw-rw 1 ports ports  461016 Aug 12 19:05 openssh-9.4p1.tar.gz.partial
  -rw-rw 1 ports ports 1845094 Aug 12 19:12 openssh-9.4p1.tar.gz
  $ rm openssh-9.4p1.tar.gz.partial

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: Minimum install size

[Steffen Nurpmeso]

Stuart Henderson wrote in
 :
 |On 2023-04-29, Theo de Raadt  wrote:
 |> The best way to not lie, is to not say anything at all.
 |
 |agreed, this value always gets out of date, and it's no longer the days
 |when one might be deciding whether to buy a 1/2/4GB CF. better to remove
 |than update now I think.

I had 1.4 GB qcow2 VM image after installing 7.3 this week.
Then some pkg_add and cvs stuff for the ports i maintain, and
i ended up with almost 1.7 GB.
Then i dropped the relink stuff, and used tar to copy over the
entire system to another qcow2 image (realpath error can still be
seen for installboot):

  -rw-r-  1 root vm 1681326080 Apr 29 21:41  .o-0703.qcow2
  -rw-r-  1 root vm  882245632 Apr 29 21:50  o-0703.qcow2

The improvement is even greater than for 7.1, that image ~1.3 GB.

A nice 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)
|~~
|..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: Mail from the command line

[Steffen Nurpmeso]

Rodrigo Readi wrote in
 :
 |2023-02-17 19:16 GMT, Steffen Nurpmeso :
 |>|>> modern requirements (html-mail, attachements).
 |>
 |> These both s-nail can (the former likely via mailcap).
 |
 |Yes, as I did it with BSD mail.
 |
 |But the main problem remains: with s-nail and mutt you have to
 |download all attachments
 |even if you only want to read the text.
 |
 |Alpine source comes with the old (unfortunately unmantained) UW imap,
 |the reference
 |implementation of imap. Alpine client has better imap support.

S-nail surely has the weakest IMAP support of the three.
mutt can for example use IMAP compression.  (Other than that i do
not know much of their sources, even though i track both git's.)
Well.  S-nail can fetch only headers, but if you want to
read/save/xy a message then the entire content is downloaded.

Maybe an idea to keep in mind for (much) later.

For me personally this is uninteresting, i pre-filter on the
server and the rest i fetch from within S-nail via SSH, like that
i do not need an additional IMAP daemon :).
(Actually the development version contains undocumented code to
trim messages, one could store and download the trimmed ones.
This was meant for a mailing-list implemenation hack that yet did
not spring into existence.  Whatever.)

Well i do not know, mostly if i want to read an email as via
looking at the header i need it all; my SMTP server also has
a strict size limit, and moreover do not receive (a lot of)
multimedia attachments.  If, that would surely be a problem.
I find that unfriendly, one sometimes sees that on OpenBSD @misc,
or huge tgz on @ports; i'd rather like to see an external URL
then.  There is even an email standard for that,
message/external-body;access-type=URL (RFC 2017).  But any URL
would do.

 |And xoath2 for gmail is other story. I regret that I began using gmail.
 --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: Mail from the command line

[Steffen Nurpmeso]

Steffen Nurpmeso wrote in
 <20230217191605.lu6ph%stef...@sdaoden.eu>:
 |deich...@placebonol.com wrote in
 | <11709eb8-1507-4c76-a042-4c1d016e4...@placebonol.com>:
 ...
 ||>> And alpine is easier to configure, it works with gmail's xoauth2,

Btw i have written a python3 script that can GMail, Outlook and
Yandex, and possibly can more.  (It is easier to configure than
that mutt script in contrib/, or the one one can find in the
internet for sendmail oauth, and it works with modern Python3,
different to the one that Google provides.  The "template" mode
writes a template with doc comments.)

  curl -u moon:mars --basic -O 
https://git.sdaoden.eu/browse/s-toolbox.git/plain/oauth-helper.py

--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: Mail from the command line

[Steffen Nurpmeso]

deich...@placebonol.com wrote in
 <11709eb8-1507-4c76-a042-4c1d016e4...@placebonol.com>:
 |Also take a look at s-nail, it is not an email application, but a very \
 |useful utility.

It is BSD Mail on steroids i would say in "Theo" mode.
(Though a lot is to be done.  And unveil() and pledge() even
further apart.)

 |diana 

Greetings.

 |On February 17, 2023 9:13:15 AM MST, Andrew Mitchell  \
 |wrote:
 |>Thanks, I'll check it out.
 |>Andrew
 |>
 |>Le ven. 17 févr. 2023 à 15:14, Rodrigo Readi  a écrit :
 |>
 |>> 2023-02-16 13:42 GMT, Andrew :
 |>>> Thanks Crystal for your reply and encouragement,
 |>>> I'll explore all your suggestions and references when I have enough \
 |>>> time.
 |>>
 |>> If you do not have tine, better install and use alpine.
 |>>
 |>> You can read mail from a provider with imap without having to download
 |>> the attachements.
 |>> Mutt is not able to do that.
 |>>
 |>> And alpine is easier to configure, it works with gmail's xoauth2,

That can be done with mutt, too.

 |>> displays html-mail.

This is a MIME (mailcap) handler.

 |>> I like BSD mail program, but unfortunately it is not always (easily)
 |>> usable due to the
 |>> modern requirements (html-mail, attachements).

These both s-nail can (the former likely via mailcap).

--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: Missing dependencies for git-send-email(1)?

[Steffen Nurpmeso]

Abhishek Chakravarti wrote in
 <87h6wrghpq@oberon.taranjali.org>:
 |Steffen Nurpmeso  writes:
 |> This is only the git built-in variant, but git-send-email can make
 |> use of external tools, and i, in fact, _never_ (since before 2015)
 |> used a different variant (for real).  The little MUA i maintain
 |> documents something like
 |>
 |>  [sendemail]
 |>  smtpserver = /usr/local/bin/s-nail
 |>  smtpserveroption = -t
 |>  #smtpserveroption = -Sexpandaddr
 |>  smtpserveroption = -Athe-account-you-need
 |>  ##
 |>  suppresscc = all
 |>  suppressfrom = false
 |>  assume8bitEncoding = UTF-8
 |>  #to = /tmp/OUT
 |>  confirm = always
 |>  chainreplyto = true
 |>  multiedit = false
 |>  thread = true
 |>  quiet = true
 |>  annotate = true
 |>
 |>Newer git(1) versions (v2.33.0) added the option sendmailCmd.
 |>
 |> You could also "simply" send format-patch output with anything you
 |> wanted, including OpenBSD base tools (i presume .. but never tried
 |> it).
 |
 |Thank you very much for your detailed response to my query! I did not
 |realise that we could use a local external tool with git-send-email. The
 |configuration with /usr/bin/s-nail looks like a neat approach---I'll try
 |it out.

Well i have not tried it in many years actually.  Now that i do..
I personally use format-patch and have wrapper scripts around it
(like with --output-directory and --cover-letter, and then
iterating over the output) -- this used to work about ~11 years
ago already.
git send-email fiddles with MIME and all which the mailer really
wants to do itself.  (It is original BSD "Mail" in that -t cannot
take readily prepared MIME emails yet.)  So adding
"transferEncoding = 8bit" to the above seems a good thing todo,
but with that it should make it.
(Of course simply piping the ready thing into any MTA like say
postfix or what .. aka sendmail(1), is likely even easier.)

--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: Missing dependencies for git-send-email(1)?

[Steffen Nurpmeso]

Hello.

Abhishek Chakravarti wrote in
 <87y1q9w5w1@oberon.taranjali.org>:
 |
 |Running a fresh install of OpenBSD 7.2 GENERIC.MP#758 amd64 in a VM.
 |The git-send-email(1) tool is available when pkg_add git is
 |done. However, when attempting to use it, git-send-email fails reporting
 |an out-of-date IO::Socket::SSL. After installing the following packages
 |with pkg_add I was able to get git-send-email to work:
 |  - p5-IO-Socket-SSL
 |  - p5-MIME-tools
 |  - p5-Authen-SASL
 |
 |Should these packages not be part of the git package? Perhaps I'm wrong;
 |if so I would welcome being corrected.
 |
 |Thank you for your time and consideration.

This is only the git built-in variant, but git-send-email can make
use of external tools, and i, in fact, _never_ (since before 2015)
used a different variant (for real).  The little MUA i maintain
documents something like

 [sendemail]
 smtpserver = /usr/local/bin/s-nail
 smtpserveroption = -t
 #smtpserveroption = -Sexpandaddr
 smtpserveroption = -Athe-account-you-need
 ##
 suppresscc = all
 suppressfrom = false
 assume8bitEncoding = UTF-8
 #to = /tmp/OUT
 confirm = always
 chainreplyto = true
 multiedit = false
 thread = true
 quiet = true
 annotate = true

   Newer git(1) versions (v2.33.0) added the option sendmailCmd.

You could also "simply" send format-patch output with anything you
wanted, including OpenBSD base tools (i presume .. but never tried
it).

--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: mailx in pipeline mode: add fields to the EMail header?

[Steffen Nurpmeso]

Jon Fineman wrote in
 <20230103112509.ndhkuetedhnsw...@ryzen.jonjfineman.com>:
[resort]
 |On Tue, Jan 03, 2023 at 08:33:22AM +0100, Harald Dunkel wrote:
 |>is there some way for OpenBSD's mailx (reading an EMail to send from
 |>stdin) to add fields to the EMail header, e.g.

"s-nail" from ports (maintainer here) is a little bit more feature
rich mailx, it can do this in several ways.

 |> Auto-Submitted: auto-generated
 |>
 |>for generated EMails, according to the recommendation in RFC 3834?

I .. do not know this RFC.  Will download when i am online again.

  ...
 |>This could help to avoid a lot of unnecessary vacation responses,

I hope i will never emit one of those.

 |>support automatic filtering, etc.
 |>
 |>The mailx command line could be
 |>
 |> echo hello | \
 |> mailx -s hello -a "Auto-Submitted: auto-generated" j...@example.com

But not -a, this adds an attachment.
You could use -C Auto-Submitted:auto-generated.  (-C links to
other possibilities.)

  $ echo Harry|mail -:/ -Smta=test -C 'Schrubben:Rücken' e...@am.ple
  From steffen Tue Jan  3 21:29:44 2023
  Date: Tue, 03 Jan 2023 21:29:44 +0100
  To: e...@am.ple
  User-Agent: mailx v14.9.24
  Schrubben: =?utf-8?Q?R=C3=BCcken?=
  MIME-Version: 1.0
  Content-Type: text/plain; charset=us-ascii
  
  Harry

It is far from complete and v14.10 is waiting for three years (i
hope for Easter this year), but the v15 that will bring major
improvements not before 2024.  But a bit usable it is already.

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: "cdio cddbinfo" broken?

[Steffen Nurpmeso]

gwes wrote in
 :
 |On 7/25/22 13:53, Erling Westenvik wrote:
 |> On Mon, Jul 25, 2022 at 11:40:30AM -0400, Nick Holland wrote:
 |>> I noticed that the cdio(1) cddbinfo command seem to no longer
 |>> work.  I don't think this is a snapshot breakage -- I upgraded
 ...
 |>> For some CDs, it returns an accurate title:
 |>>$ cdio cddbinfo
 |>>Van Halen / Van Halen II (rock)
 |>>
 |>> but not the track listing it used to show.
 ...
 |tcpdump shows a query to port 8880
 |
 | From https://gnudb.org/howtognudb.php
 |
 |  For new applications do not use the cddbp protocol (port 8880),
 |  it is only left for compatibility with old programs,
 |  all cddbp access to gnudb is actually converted to http requests.
 |
 |  The preferred protocol level is 6, most gnudb cddb entries are 
 |converted to utf-8
 |
 |The query part of cdio needs to be rewritten using the new format.
 |That should probably be stolcopied from some other program.
 |I'll take a quick look around to see if there's anything obvious
 |with an acceptable license.
 |   geoff steckel

If anyone feels to pimp cdio with the MusicBrainz DB that seems to
be in use more and more, you could extract and adapt the "package
CDInfo::InfoSource::MusicBrainz;" from my s-cdda-to-db that is in
ports.  It is anyway a good starting point that works with my
(granted restricted) use cases of it.  The needed HTTP::Tiny and
XML::Parser are there anyway iirc.  (TLS is often no good,
i stopped using its TLS because of that.  And the JSON output did
not work for the needed query alone once i implemented it, thus
the XML one.)  I think they get money from Microsoft, but this is
not a problem for you, is it.

(If someone does extract it, it needs the "sub _calc_mb_discid"
result in order to do the query, and shall someone find errors,
i am happy to fix them.  I.e., this is perl, but doing _that_
dance in C is i think a nuisance, just parse the output of the
perl thing seems better.)

--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: OpenBSD ports require xbase set - still true?

[Steffen Nurpmeso]

Theo de Raadt wrote in
 <74991.1652133...@cvs.openbsd.org>:
 |I looked very closely, it started like this
 |
 |  "Just a rant"
 |
 |And I knew the email was coming from a self-centered individual who is
 |unhappy with the entirely volunteer work done by others, yet not unhappy
 |enough to quit OpenBSD and switch to another operating sytem where
 |there will be similar unhappiness because those other systems also won't
 |do precisely what you want.

You could have adjusted this a bit after pasting it.  ..mumble..

 |Your email is not appropriate.  If you don't like OpenBSD, use something

Yes that is true, i really do apologise for the yelling.
(I do recognize that some people can make a living from OpenBSD.)

 |else, because noone deserves an email which starts with those 3 words
 |you chose, and the following complaint is such horseshit in a world
 |where disk drives are cheap.  I started OpenBSD a quarter of a century

Oh i have 5GB download per 28 days, with max of ~2.7 MB/sec, but
often less.  The next two weeks practically nothing now, there are
so many wars, you do not know where to look first.

 |ago by spending $3500 for a 300MB drive and ate noodles and tuna for

By then i also ate tuna.  I apologise very, very much.  Even our
Russian grocery here had to increase prices by 50 percent now,
peas 1,79€/800G, buckwheat 2,89€/800G, and they use a new recipe
for the ice!  That is a real shame.  Rice and peas i mean, add
fish sauce and a Vietcong would have been your life long friend.
The times they are a-ch-ch-changing.
The Italiens at least kill the tuna by hand, once a year, in that
terrible slaughter session, "Mattanza".  That is minimal respect
compared to artificial robotic slaughter experience.  Maybe.

 |many months to make up for that, and we do not live in a world where you
 |get to moan about 55MB, relative to whatever it takes to ease the compli\
 |cate
 |work undertaken by the ports developers.

I do not even know whether it is still true, i could not find the
"not installed" i remembered when grepping infrastructure/.
It expands to quite a bit more, the OpenBSD VM ended up as a 1.1GB
image (kernel relink objects removed).

It actually came out like 2.5GB first (!; no games etc.), so
i created a second disk and copied over, leaving off the relink
package.  This was quite an experience, i thought about sending
a patch to tech@ that shows up the sequence

  fdisk -iy /dev/rsd1c
  disklabel -F xx -E /dev/sd1c
  newfs /dev/rsd1c
  installboot -r XROOT /dev/rsd1a
  ...copy...

in one of the manual pages of the mentioned programs, i had to
read FAQ on the web to get this together.
Especially "installboot -r", when called from the new volume
mounted to /mnt, did not do what i thought or could deduce from my
(fast, superficial) glance at the manual, it complained about
a readlink failure if i recall correctly (maybe empty path;
unfortunately my tmux history of the ncurses qemu output is
sketchy, i think some terminal sequences cause clearance at times,
for example i have

  starting RPC daemons:.
  savecore: no core dump
  checking quotas: done.
  clearing /tmp
So that from boot still
  o-0701# installboot -v -r /dev/sd
This must be later, but without meaning
  8025728d100b2db6.a / ffs rw,wxallowed 1 1
And this is a cat of the generated file

Again i am wasting your time only, of course).

 |In short, Steffen, you need to shut up.

Yeah.  Well i am from Hessen and back when we Germans were not
cloned Americans but Germanen the name of our tribe here was
Chatten, and i am afraid this could ring a bell, ne?  I do have
watched interviews with you and i know you are prowd of your
sensors ('wish i had some, but you know the ones sit at the front
and the others in the back, and so one group just had bad luck).
But our neighbours from Baden-Württemberg produced a nice animated
film of Chatten i think twenty years ago[1], if you like sensors
mayby this could be a nice 5 minute fun.  (Sufficient download
provided.)  Warning: people named "Tucker" should be careful.
"Hessi James"[1] of Badesalz, voila.

  [1] https://www.youtube.com/watch?v=akfz5Fw-pZI=de

 |Steffen Nurpmeso  wrote:

Scary top posting everywhere.  At least on OpenBSD people seem to
be free enough to no only inject lots of exhaust in toposphere or
where those fly, but also can freely choose their email client and
use plain-text only, which on other BSDs seems to get rare, maybe
$DAYJOB imposed, of course.  All those nice HTML mails.

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: OpenBSD ports require xbase set - still true?

[Steffen Nurpmeso]

Theo de Raadt wrote in
 <36104.1652132...@cvs.openbsd.org>:
 |The people who do the work make the decisions.

Ok i will at least look what i was talking about.

 |Steffen Nurpmeso  wrote:
 |
 |> Hello.
 |> 
 |> Just a rant, not for ports@.
 |> I am installing OpenBSD 7.1 right now; this is only a VM, and
 |> i want to create / manage ports there.
 |> Until now whenever i wanted to do this i had to install xbase,
 |> otherwise the port makefile complained some.  (I am afraid i have
 |> forgotten the details.)  Is this still true?  I know i once
 |> "hacked" it because for my ports it really was not needed, at
 |> least not really.  Hm.  I think i even posted about this quite
 |> some years ago.  I have installed xbase now, maybe i even will use
 |> it (OpenBSD X is always super proper, i cheered this often; CRUX
 |> also, but of course not base-integrated).  If not then 55 MB for
 |> a file is quite an act.
 |> 
 |> --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)
 |> 
 --End of <36104.1652132...@cvs.openbsd.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: time drift in OpenBSD in proxmox (qemu-kvm) guest

[Steffen Nurpmeso]

Stuart Henderson wrote in
 :
 |On 2022/04/15 22:02, Tom Smyth wrote:
 ...
 |Thanks for the suggestions - since the change I made in the last mail
 |("I've changed mine to acpihpet0 and it seems much happier", i.e. setting
 |the kern.timecounter.hardware sysctl to acpihpet0, based on Stefan's
 |pointer) the time has stayed in sync.
 |
 |The machine is on what looks like the closest thing to "power saving"
 |(option in machine config is "best experience") - since I leave this
 |machine turned on, at around 0.30GBP/kWh power cost, and often with
 |only ~50% of power generation where I live being low carbon unless
 |it's particularly windy (https://www.carbonintensity.org.uk/#regional,
 |https://www.gridwatch.templar.co.uk/) I'd like to keep it like that
 |if possible :)

That is great.
But i find the focusing on Carbon quite misleading, as it is about
biodiversity and more, as possibly HM Prince Charles would say :)
Anyhow looking at this western-eye-polished mess at [2] i still
find that Germany will now buy liquid gas from the dirtiest
country of the world, that USA and Canada are in the top ten of
the dirtiest and have passed their overshoot day almost two months
ago, that Germany did so last week and that U.K. will in ten days.

  [1] https://www.footprintnetwork.org/our-work/earth-overshoot-day/
  [2] 
https://www.overshootday.org/content/uploads/2022/04/Country_Overshoot_Days_2022_v2_sm.jpg

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

OpenBSD ports require xbase set - still true?

[Steffen Nurpmeso]

Hello.

Just a rant, not for ports@.
I am installing OpenBSD 7.1 right now; this is only a VM, and
i want to create / manage ports there.
Until now whenever i wanted to do this i had to install xbase,
otherwise the port makefile complained some.  (I am afraid i have
forgotten the details.)  Is this still true?  I know i once
"hacked" it because for my ports it really was not needed, at
least not really.  Hm.  I think i even posted about this quite
some years ago.  I have installed xbase now, maybe i even will use
it (OpenBSD X is always super proper, i cheered this often; CRUX
also, but of course not base-integrated).  If not then 55 MB for
a file is quite an act.

--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: mail -r option problem

[Steffen Nurpmeso]

Austin Hook wrote in
 :
 |On Sat, 30 Jan 2021, Rudolf Sykora wrote:
 |> I tried to use the -r option with the mail program, but whenever I use
 |> the option I get a error like this:
 |> 
 |> odin$ mail -r abcd -s abcd rudolf.syk...@cvut.cz
 |> a
 |> EOT
 |> odin$ sendmail: command failed: 550 Invalid recipient:  ut.cz>
 |> 
 |> 
 |> odin$ mail -s abcd rudolf.syk...@cvut.cz 
 |> sdas
 |> EOT
 |> odin$
 |> 
 |> 
 |> can anybody help me understand why? 

 |When you look at the full headers of the email received, having sent it
 |without the -r option, double check what the originating domain info 
 |looks like.
 |
 |Then try with -r set to the same full qualified originating email 
 |address.  That way mail doesn't have to figure out what domain to add to 
 |the abcd.
 |
 |If that works then somehow mail is not appending you originating domain 
 |address the way you want, and perhaps the target mail handler at cvut.cz 
 |is really complaining about the sender, and not the recipient.
 |
 |(I am not any kind of expert at this -- just wondering.)

I have no idea of your boxes really (i did not even know OpenBSD
Mail supports -r), but my Mail clone (s-)nail documents (note
especially last paragraph; bit silly since standouts are missing):

 -r from-addr, --from-address=..
   The RFC 5321 reverse-path used for relaying and delegating mes-
   sages to its destination(s), for example to report delivery er-
   rors, is normally derived from the address which appears in the
   from header (or, if that contains multiple addresses, in
   sender).  A file-based aka local executable mta (Mail-Transfer-
from,sender,mta: variables
   Agent), however, instead uses the local identity of the initi-
   ating user.

   When this command line option is used the given single ad-
   dressee from-addr will be assigned to the internal variable
   from, but in addition the command line option -f from-addr will
I think sendmail used -r, but that ship sailed long ago.
Do all MTAs support -r still / does OpenBSD mail _do_ pass -f?
   be passed to a file-based mta whenever a message is sent.
   Shall from-addr include a user name the address components will
   be separated and the name part will be passed to a file-based
   mta individually via -F name.  Even though not a recipient the
   `shquote' expandaddr flag is supported.

   If an empty string is passed as from-addr then the content of
   the variable from (or, if that contains multiple addresses,
   sender) will be evaluated and used for this purpose whenever
   the file-based mta is contacted.  By default, without -r that
   is, neither -f nor -F command line options are used when con-
   tacting a file-based MTA, unless this automatic deduction is
   enforced by seting the internal variable r-option-implicit.
All this not OpenBSD for sure.

   Remarks: many default installations and sites disallow overrid-
   ing the local user identity like this unless either the MTA has
   been configured accordingly or the user is member of a group
   with special privileges.  Passing an invalid address will cause
   an error.

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: 019_libssl.patch regression

[Steffen Nurpmeso]

Steffen Nurpmeso wrote in
 <20200812132648.kaxsj%stef...@sdaoden.eu>:
 |Steffen Nurpmeso wrote in
 | <20200812130039.lto3i%stef...@sdaoden.eu>:
 ||Predrag Punosevac wrote in
 || <20200811212622.ugmda%punoseva...@gmail.com>:
 |||This is a regression report for 019_libssl.patch
 | ...
 |||After applying libssl binary patch to 6.7 release s-nail-14.9.19 can no
 |||longer close STARTTLS IPMI session with Gmail server. I recompiled
 | ...
 ||Hmm.  I can reproduce this here indeed.
 | ...
 ||  nail: >>> QUIT
 ||  nail: >>> SERVER: 221 2.0.0 closing connection g9sm1477447ejf.101 \
 ||  - gsmtp
 ||
 ||And here it hangs endlessly.  For now i presume it hangs at
 ||
 || while (!SSL_shutdown(s_tls)) /* XXX proper error handling;signals! */
 ||;
 |
 |I can confirm we have an endless loop in SSL_shutdown() here.

P.S.: this is ugly code.
P.P.S.: new OpenSSL documents that SSL_read() should be used
instead of a second SSL_shutdown().  I will ask about that on
a openssl-user list when i find some head.  But .. will this work
with libressl too??
Thanks.

--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: 019_libssl.patch regression

[Steffen Nurpmeso]

Steffen Nurpmeso wrote in
 <20200812130039.lto3i%stef...@sdaoden.eu>:
 |Predrag Punosevac wrote in
 | <20200811212622.ugmda%punoseva...@gmail.com>:
 ||This is a regression report for 019_libssl.patch
 ...
 ||After applying libssl binary patch to 6.7 release s-nail-14.9.19 can no
 ||longer close STARTTLS IPMI session with Gmail server. I recompiled
 ...
 |Hmm.  I can reproduce this here indeed.
 ...
 |  nail: >>> QUIT
 |  nail: >>> SERVER: 221 2.0.0 closing connection g9sm1477447ejf.101 - gsmtp
 |
 |And here it hangs endlessly.  For now i presume it hangs at
 |
 | while (!SSL_shutdown(s_tls)) /* XXX proper error handling;signals! */
 |;

I can confirm we have an endless loop in SSL_shutdown() here.

--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: 019_libssl.patch regression

[Steffen Nurpmeso]

Hello Predrag, all.

Predrag Punosevac wrote in
 <20200811212622.ugmda%punoseva...@gmail.com>:
 |This is a regression report for 019_libssl.patch
 |
 |predrag@oko$ uname -a
 |OpenBSD oko.int.bagdala2.net 6.7 GENERIC.MP#5 amd64
 |predrag@oko$ syspatch -l
 |001_wscons
 |002_rpki
 |003_ssh
 |004_libssl
 |005_unbound
 |006_smtpd_sockaddr
 |007_perl
 |008_hid
 |009_asr
 |010_x509
 |011_shmget
 |012_tty
 |013_tty
 |014_iked
 |015_rpki
 |016_ximcp
 |017_dix
 |018_ximcp
 |019_libssl
 |
 |After applying libssl binary patch to 6.7 release s-nail-14.9.19 can no
 |longer close STARTTLS IPMI session with Gmail server. I recompiled
 |s-nail and rebooted the machine. After reverting the patch s-nail works
 |as expected. Interestingly enough I can only see this with Gmail
 |servers.  019_libssl.patch doesn't break Hotmail IPMI connection. Patch
 |does break SMTP session with Gmail server in the same fashion as IPMI.
 |It just doesn't terminate cleanly. I don't know enough about the subject
 |to look further into the problem but I am 100% sure this is LibreSSL
 |bug.

Hmm.  I can reproduce this here indeed.

  nail: Resolving host smtp.gmail.com:587 ... done
  nail: Connecting to 108.177.126.109:587 ... connected.
  nail: >>> SERVER: 220 smtp.gmail.com ESMTP g9sm1477447ejf.101 - gsmtp
  nail: >>> EHLO gmail.com
  nail: >>> SERVER: 250-smtp.gmail.com at your service, [109.40.130.60]
  ...
  nail: >>> STARTTLS
  nail: >>> SERVER: 220 2.0.0 Ready to start TLS
  nail: TLS: applying config: CipherString = TLSv1.2:!aNULL:!eNULL
  nail: TLS: applying config: MinProtocol = TLSv1.2
  nail:  Certificate depth 2
  nail:   subject = /OU=GlobalSign Root CA - R2/O=GlobalSign/CN=GlobalSign
  nail:   notBefore = Dec 15 08:00:00 2006 GMT
  nail:   notAfter = Dec 15 08:00:00 2021 GMT
  nail:   issuer = /OU=GlobalSign Root CA - R2/O=GlobalSign/CN=GlobalSign
  nail:  Certificate depth 1
  nail:   subject = /C=US/O=Google Trust Services/CN=GTS CA 1O1
  nail:   notBefore = Jun 15 00:00:42 2017 GMT
  nail:   notAfter = Dec 15 00:00:42 2021 GMT
  nail:   issuer = /OU=GlobalSign Root CA - R2/O=GlobalSign/CN=GlobalSign
  nail:  Certificate depth 0
  nail:   subject = /C=US/ST=California/L=Mountain View/O=Google 
LLC/CN=smtp.gmail.com
  nail:   notBefore = Jul 15 08:33:08 2020 GMT
  nail:   notAfter = Oct  7 08:33:08 2020 GMT
  nail:   issuer = /C=US/O=Google Trust Services/CN=GTS CA 1O1
  nail: Comparing subject_alt_name: need is
  nail: TLS certificate ok
  nail: TLS SHA256 fingerprint: 
7B:2D:63:EC:E2:4C:D5:BB:33:00:A5:65:A0:67:DA:1B:C6:B8:1F:88:6E:6B:67:78:D7:6A:AC:93:94:6E:9F:9F
  nail: TLS connection using ? / AEAD-AES256-GCM-SHA384

This ? is, interesting, the "None" of

  static struct a_xtls_protocol const a_xtls_protocols[] = {
 {"ALL", SSL_OP_NO_SSL_MASK, 0, FAL0, TRU1, FAL0, TRU1, {0}},
 {"TLSv1.3\0", SSL_OP_NO_TLSv1_3, TLS1_3_VERSION, TRU1,TRU1,FAL0,FAL0,{0}},
 {"TLSv1.2", SSL_OP_NO_TLSv1_2, TLS1_2_VERSION, TRU1, TRU1, FAL0, FAL0, 
{0}},
 {"TLSv1.1", SSL_OP_NO_TLSv1_1, TLS1_1_VERSION, TRU1, TRU1, FAL0, FAL0, 
{0}},
 {"TLSv1", SSL_OP_NO_TLSv1, TLS1_VERSION, TRU1, TRU1, FAL0, FAL0, {0}},
 {"SSLv3", SSL_OP_NO_SSLv3, SSL3_VERSION, TRU1, TRU1, FAL0, FAL0, {0}},
 {"SSLv2", SSL_OP_NO_SSLv2, SSL2_VERSION, TRU1, TRU1, FAL0, FAL0, {0}},
 {"None", SSL_OP_NO_SSL_MASK, 0, TRU1, FAL0, TRU1, FAL0, {0}}
  };

after

  ver = SSL_version(sop->s_tls);
  for(xpp = _xtls_protocols[1] /* [0] == ALL */;; ++xpp)
 if(xpp->xp_version == ver || xpp->xp_last){
n_err(_("TLS connection using %s / %s\n"),
   (xpp->xp_last ? n_qm : xpp->xp_name),
   SSL_get_cipher(sop->s_tls));
break;
 }
   }

I have to look there when i have time, maybe!?!

  nail: >>> EHLO gmail.com
  nail: >>> SERVER: 250-smtp.gmail.com at your service, [109.40.130.60]
  ...
  nail: >>> AUTH PLAIN
  nail: >>> SERVER: 334
  ...
  nail: >>> SERVER: 354  Go ahead g9sm1477447ejf.101 - gsmtp
  ...
  nail: >>> .
  nail: >>> SERVER: 250 2.0.0 OK  1597236652 g9sm1477447ejf.101 - gsmtp
  nail: >>> QUIT
  nail: >>> SERVER: 221 2.0.0 closing connection g9sm1477447ejf.101 - gsmtp

And here it hangs endlessly.  For now i presume it hangs at

 while (!SSL_shutdown(s_tls)) /* XXX proper error handling;signals! */
;

Because the final SMTP answer has been successfully received.  But
i am a bit out of ideas at the moment since i need to -KILL it, no
other signal gets through, and our socket_close() does not catch
signals.  I will look a bit.

--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: explicit_bzero vs. alternatives

[Steffen Nurpmeso]

Theo de Raadt wrote in
 <61139.1597087...@cvs.openbsd.org>:
 |Philipp Klaus Krause  wrote:
 |> Am 10.08.20 um 17:00 schrieb Theo de Raadt:
 |>> Philipp Klaus Krause  wrote:
 |>> 
 |>>> OpenBSD has the explicit_bzero function to reliably (i.e. even if not
 |>>> observable in the C abstract machine) overwrite memory with zeroes.
 |>>>
 |>>> WG14 is currently considering adding similar functionality to C2X.
 |>> 
 |>> Then perhaps in the interests of the public they should use the same
 |>> name, but I suspect they won't.
 |> 
 |> The functionality (i.e. some way to reliably overwrite memory) already
 |> exists under different names: explicit_bzero in OpenBSD
 |
 |This one was first.

If i recall correctly others had already started using volatile
pointers to memset(3) before.  'Kind of strange that bcopy
etc. all were thrown away, just to bring back a bzero to
circumvent overoptimization of compilers.  That "reliably
overwrite memory" .. bugs me, i know that ship has sailed, but if
the programmer calls a function then for a reason.
Sorry, the topic concerns me.

--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: .nailrc and Gmail

[Steffen Nurpmeso]

Hello Stuart.

Stuart Henderson wrote in
:
 |On 2020-06-08, Steffen Nurpmeso  wrote:
 |> Pity they did not wave through .19 before freeze, plenty of time
 |> there would have been.
 |
 |"Plenty of time" "But it's just one port!"

And a small and minor one, sure.

 |With dozens of people trying to push through updates to ports they
 |are interested in before tagging too, there is not plenty of time.
 |(you already asked to hold 14.9.18, and nothing in changelog,
 |at least to someone who doesn't use s-nail themselves, really
 |seemed important enough to make an exception).

To me the three weeks in between .18 and the official 6.7
announcement where a long time, it depends on the point of view.
It is clearly a minor port, but for it, anything after v14.9.16
are all pure bugfix releases.  Nothing in changelog, i wonder what
this means?  I do not see per-port changelogs?  .18 had

  . a mailcap directive combination (mostly binary formats),
  . .smime-* automated password fallback lookup,

of which the latter i deem important, at least for those who have
password protected certificates and keys.  (As i no longer have.)
We did not have had a test for this specific case, just as for the
former, which does not bite me in practice either because i have

  application/pdf;\
infile=%s\;\
  trap "rm -f ${infile}" EXIT\;\
  trap "exit 75" INT QUIT TERM\;\
  mupdf "${infile}";\
test = [ -n "${DISPLAY}" ];\
nametemplate = %s.pdf; x-mailx-async; x-mailx-test-once
  application/pdf;\
pdfinfo %s\; pdftotext -layout %s -;\
test = command -v pdfinfo >/dev/null 2>&1; \
copiousoutput; nametemplate=%s.pdf; x-mailx-test-once

in my ~/.mailcap and so we fall through to the last one, since if
PDFs look important i usually `write' them somewhere before mupdf
comes into play.

I soon asked for holding it then, because there was one more
problem to fix, it is really superficial (was never seen in real
life), but since i also made the software OpenSSL 3.0 ready
i wanted to make another release, and it made no sense to update
to .18 and then .19, with all the machinery there is involved.

Nothing wild, it is just that as the maintainer of this thing
i would like to see that the best aka newest version is available
to whoever wants to fiddle around with this thing.  That's all.

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: [S-mailx] .nailrc and Gmail

[Steffen Nurpmeso]

Hello Predrag.

Predrag Punosevac wrote in
<20200607193905.3ndsv%punoseva...@gmail.com>:
 |Predrag Punosevac  wrote:
 ...
 |I apologize for cross posting. After upgrading my laptop to 

I took ports off ok, i'd feel ashamed to keep it in. ^_^

 |predrag@oko-mobile$ uname -a
 |OpenBSD oko-mobile.int.bagdala2.net 6.7 GENERIC.MP#2 amd64
 |
 |I felt it was the time for me to jump the ship and finally go with
 |s-nail from the official ports tree. 
 |
 |predrag@oko-mobile$ pkg_info s-nail
 |Information for inst:s-nail-14.9.17

Pity they did not wave through .19 before freeze, plenty of time
there would have been.

 |I got to the bottom of all "issues" I originally reported 
 |
 |https://www.mail-archive.com/s-mailx@lists.sdaoden.eu/msg00948.html
 |
 |in the thread. I used quotation marks around issues as in the hindsight
 |there was really only one. All other issues were due to the fact that I
 |didn't realize that you have completely rewritten s-nail and there is
 |really not much in common with the original Heirloom mailx

Nah, not true.  Almost all extensions or replacements until now.
The entire I/O and MIME layer rewrite is waiting still.  That is
ridiculous, i have written much more code in less than half the
time i am maintaining this.  In the past.

 |http://heirloom.sourceforge.net/mailx.html
 |
 |which I used for at least 15 years. That is not to say that the things
 |don't work or they are worse. They just work different. It took me two
 |full days of dicking with it to get a to get a hang of it.

Hm.  A problem is surely that IMAP search expressions must now be
shell-escaped, we do warn a bit but all that primitive.  I got
reports, but people are so silent, hm.

I personally do not regret moving all over to shell syntax with
v15-compat=y that will be default in v14.10.* somewhen in autumn.
We loose strict POSIX compatibility with this, but then again it
should not really hurt if this software is used POSIX compatibly.
It offers so much more possibilities.  Still we are much too
restricted.

 |First thing first you really trough me off the board with Ctrl+D instead
 |of next line and a dot to sent the email. I have not read the code, and
 |even if I did I don't have sufficient programming background to
 |understand design decession but I am using dot to sent emails since
 |circa 1989 and that is a hard pill to swallow. That is why I kept
 |reporting that sending email doesn't work. 
 |
 |I noticed that 14.9.17 on 6.7 doesn't report that annoying message
 |
 |There are new messages in the error message ring (denoted by ERROR),
 |nail:   which can be managed with the `errors' command
 |ERROR# ? 

It would if there would be errors. :)

 |I really like new configuration grammar. This is my not so minimal
 |working example

Just the same grammar. :)

 |predrag@oko-mobile$ more .mailrc 
 |set ask
 |set crt
 |ignore message-id received date fcc status resent-date resent-message-id
 |resent-from in-reply-to
 |
 |set mailx-extra-rc=~/.nailrc

This is new, it was NAIL_EXTRA_RC, but we are moving all over to
mailx all over the software.

 |and this is dotnailrc file
 |
 |account gmail {
 | set inbox=imaps://usern...@imap.gmail.com
 | set imap-use-starttls

Not needed with imaps.

 | set password="secret"
 | set folder=imaps://usern...@imap.gmail.com record="+[Gmail]/Sent Mail"

That this works in practice, you have a good internet connection.
This software still has a very bad error recovery when that would
happen.  With `disconnect' / and `connect' much of this is
handable however.  Hm.  Don't you get automatic copies in "Sent
Mail" when you use SMTPS in GMail?

 | set from="Predrag Punosevac " \
 | mta=smtp://usern...@smtp.gmail.com:587 \
 | set smtp-use-starttls 

You should be able to use

  set mta=smtps://smtp.gmail.com:465

without smtp-use-starttls.  Saves round-trips.

 | set smtp-auth="login" 
 |# IMAP SHORTCUTS SECTION for standard Gmail folders
 | shortcut allmail +[Gmail]/All\ Mail
 | shortcut sent +[Gmail]/Sent\ Mail
 | shortcut spam +[Gmail]/Spam
 | shortcut trash +[Gmail]/Trash
 |}
 |account cmu {
 | set inbox=imaps://username%40andrew.cmu@imap.gmail.com
 | set imap-use-starttls

Not needed with IMAPS.
| set password="secret"
 | set from="Predrag Punosevac " \
 | mta=smtp://username%40andrew.cmu@smtp.gmail.com:587 \
 | set smtp-use-starttls 
 | set smtp-auth="login" 
 |# IMAP SHORTCUTS SECTION for standard Gmail folders
 | shortcut allmail +[Gmail]/All\ Mail
 | shortcut sent +[Gmail]/Sent\ Mail
 | shortcut spam +[Gmail]/Spam
 | shortcut trash +[Gmail]/Trash
 |}
 |account hotmail {

Looked around that, found on [1] via Firefox

  Office-Support
  Produkte
  Geräte
  Neuerungen
  Office installieren
  Konto  Abrechnung

Oops.

  Vorlagen
  Mehr Unterstützung 

  [1] 
https://support.office.com/de-de/article/pop-imap-und-smtp-einstellungen-f%C3%BCr-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040

 | set inbox=imaps://username%40hotmail@imap-mail.outlook.com
 | set 

Re: qemu/kvm viornd0 problems with OpenBSD 6.7

[Steffen Nurpmeso]

Hello once again.

Steffen Nurpmeso wrote in
<20200525221543.zdgwt%stef...@sdaoden.eu>:
 |Ya, thanks!, i am doing my OpenBSD 6.7 today!
 |
 |I have switched to use "-device virtio-rng-pci" in qemu not too
 |long ago after figuring out it works quite nice and almost
 |everybody seems to support it.  It is detected just fine for
 |OpenBSD 6.4 .. 6.6, but OpenBSD 6.7 causes qemu/kvm to abort with
 |a libgcrypt error: "Fatal: no entropy gathering module detected".
 |It works fine if i do not use this -device.

Ok, once i started doing food for the animals (just fyi) i had the
idea that the "-chroot ." i use might be the problem.  I have no
idea .. it seems mknod might no longer do what it is supposed to
on Linux, hm, random and urandom however i supplied without any
positive effects.

Anyhow, i can confirm that OpenBSD 6.7 boots regulary with that
virtio-rng if i do not chroot qemu!
(So maybe i have to supply --bind mounts for dev etc.  Hm.)

Good night,

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

qemu/kvm viornd0 problems with OpenBSD 6.7

[Steffen Nurpmeso]

Hello!

Ya, thanks!, i am doing my OpenBSD 6.7 today!

I have switched to use "-device virtio-rng-pci" in qemu not too
long ago after figuring out it works quite nice and almost
everybody seems to support it.  It is detected just fine for
OpenBSD 6.4 .. 6.6, but OpenBSD 6.7 causes qemu/kvm to abort with
a libgcrypt error: "Fatal: no entropy gathering module detected".
It works fine if i do not use this -device.

I can tell you this happens with qemu 4.2.0 and on qemu 5.0.0, on
Linux 4.19.{117,123,124}, yep, and it seems to make qemu/kvm
shiver.  4.19.117 even could no longer shutdown the computer
correctly, i seem to recall the last message before the hang being
"kvm: exiting hardware virtualization".  This never happened
before, once i was using this kernel actively.

I also get

  starting network daemons: sshd smtpd sndiod(failed).

for my 

  o-0607-x86# cat /etc/rc.conf.local
  library_aslr=no
  sndiod_flags=no

which feels wrong.  It is still sndiod_flags in rc.conf.
(I also got a "reordering libraries" on the first boot, i think,
even though the file was already in place.  No problem here no
more, however.)

Out in the forest now.  It seems i have to reprepare my MUA port
tomorrow thus, will post it to ports@.

Thank you, 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: Nail viewing HTML messages

[Steffen Nurpmeso]

Hello.

Jon Fineman wrote in <20191224111506.mxv_o%...@fineman.me>:
 |I am having trouble viewing an HTML message. Nail natively seems to \
 |work with
 |simple HTML messages that I create and email to myself. However commerci\
 |ally
 |created emails with multi-part doesn't render in lynx.

Hmm, whether i use the simple builtin HTML viewer, or the better
lynx, it works for me?

 |I have nail version v14.9.15, 2019-08-17 (built for OpenBSD) and I \
 |am working
 |through the example in the man page below (without the ? marks). The second
 |part viewing PDFs works fine. The first part to view a fancy HTML doesn't \
 |work.

 |I installed lynx. I think the issue is with mathml which I don't quite
 |understand what that is doing with regard to the first part of defining \
 |a pipe
 |to lynx. I don't see anything related to mathml in the packages.

That mathml thing is really only an example of how a new MIME type
can be created from within the application itself, without some
mime.types(5) on the system.

 |When I view an HTML message with the "p" command it views the text \
 |displayable
 |version, as expected. When I use the mimeview command it just displays \
 |a blank
 |or two of lines and no text.

The mimeview command is for now only "a crux" to be able to access
those MIME parts which cannot be displayed inline alongside other
MIME parts.  Or, in ~/.mailcap terms, those MIME parts which are
not "copiousoutput" enabled.  When using the mimeview command on
So

 |? if [ "$features" !% +filter-html-tagsoup ]
 |?   #set pipe-text/html='?* elinks -force-html -dump 1'
 |?   set pipe-text/html='?* lynx -stdin -dump -force_html'
 |?   # Display HTML as plain text instead
 |?   #set pipe-text/html=?
 |? endif

  if "$features" !% +filter-html-tagsoup

So if the builtin simple HTML filter is not available (% is
substring match, case sensitively, =% and !%, as opposed to == and
!= which are an exakt match, just like in the shell)

set pipe-text/html='?* lynx -stdin -dump -force_html'

Then install lynx has a HTML viewer.  The "?*" tells S-nail that
this is "copiousoutput" in .mailcap terms, that is, the output
that lynx produces can be reintegrated in the normal output that
S-nail produces, and thus ends in less(1) (likely), or directly on
the terminal (depending on the setting of "crt", how many lines
the terminal height is, and how large the final output).

  endif
 mimetype ? application/mathml+xml mathml

Register a new MIME type.  The ? is again a modifier, an extension
tag, it tells S-nail that it should treat MIME parts of this type
as plain text by default, if no explicit handler is available.

 |? wysh set pipe-application/pdf='?&=? \
 |trap "rm -f \"${MAILX_FILENAME_TEMPORARY}\"" EXIT;\
 |trap "trap \"\" INT QUIT TERM; exit 1" INT QUIT TERM;\
 |mupdf "${MAILX_FILENAME_TEMPORARY}"'
 |
 |Am I misunderstanding how this macro works?

Well "mimeview" is for now really only a crux.  In the original
code any MIME part which has a handler installed was simply being
executes when the mail has been viewed (via "t"ype
a.k.a. "p"rint), which was really a bad thing.  So now the view
command only prints what can be viewed directly and on the
terminal, and as a whole; S-nail prepares that output, and sends
it to the $PAGER as necessary.  All other MIME types, like PDF in
the thing above, have to go over mimeview, and mimeview will ask
you for each part in turn whether you want to have the handler
invoked.  The above PDF handler for example will run
asynchronously in the background, with a temporary file being
filled in.

It is very primitive yet, it would be much nicer if you could
address MIME parts directly, as in "mimeview 13.2", and we would
also need a MIME parts overview display, like we now have
a "headers" overview display, as in "mimetree" or whatever.
Then, with the right key "bind"ings you could use the cursor keys
to move up and down and maybe have one to invoke a mimeview which
invokes the handler for the part the cursor is over.  But that not
yet.

 |Thanks.

I hope this helps, a nice rest-Christmas and
Ciao from Germany,

 |Jon
 --End of <20191224111506.mxv_o%...@fineman.me>

--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: s-nail copying deleted imap messages to trash

[Steffen Nurpmeso]

Jon Fineman wrote in <20191224012038.4azmy%...@fineman.me>:
 |Steffen Nurpmeso  wrote:
 |
 |> Even better would be
 |> 
 |>   \copy "$@" /tmp/undelete.mbox
 |>   \delete `
 |> 
 |> since the messages are collected only once.
 |
 |Thanks.
 |
 |I was focused on searching for a built in similiar to the way sent uses
 |"record", that I didn't consider creating a function.

Or really just "commandalias delete move" or so?  You can prefix \
if you want the real "delete", without commandalias expansion.

S-nail v14.9.10, hopefully before next summer, will bring some
updates also to the IMAP code.  For v15 IMAP however has to go, at
least temporary, until our network code no longer uses blocking
I/O and signal(3) caused siglongjmp(3), really.  But during that
the v14.10.* series will be maintained, at least a little.

Ciao!

 |Jon
 --End of <20191224012038.4azmy%...@fineman.me>

--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: s-nail copying deleted imap messages to trash

[Steffen Nurpmeso]

Steffen Nurpmeso wrote in <20191223200257.kp4kp%stef...@sdaoden.eu>:
 |Jon Fineman wrote in <20191223153845.kcdii%...@fineman.me>:
 ||For current s-nail is there a way with an imap account to copy messages \
 ||that I
 ||delete to my ISPs trash folder like the set record=+Sent command copies \
 ||sent
 ||message to my sent folder?
 ||
 ||Currently they are being permanently deleted.
 |
 |I would say there are multiple possibilities, if i understand your
 |desire correctly.  The easiest would likely be a function plus
 |a commandalias (or even a key binding).
 |
 |  define my_delete {
 |\copy "$@" /tmp/undelete.mbox
 |\delete "$@"

Even better would be

  \copy "$@" /tmp/undelete.mbox
  \delete `

since the messages are collected only once.

 |}
 |  commandalias d '\call my_delete'
 |
 |And then you say "d *" as before.  Just replace my_delete with
 |whatever is your desire, but note that this is inefficient unless
 |you stay under the same IMAP account (for a while).  You could
 |also just use \move instead of \copy, which is likely very much

And "move" is likely what you really want.

 |more efficient than the above.  But there is no automatic and
 |builtin way to say, for example, "just let delete do x and y", no.
 |
 ||Thanks.
 |
 |Hope this help.
 |Merry Christmas ;) i wish 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: s-nail copying deleted imap messages to trash

[Steffen Nurpmeso]

Hello.

Jon Fineman wrote in <20191223153845.kcdii%...@fineman.me>:
 |For current s-nail is there a way with an imap account to copy messages \
 |that I
 |delete to my ISPs trash folder like the set record=+Sent command copies \
 |sent
 |message to my sent folder?
 |
 |Currently they are being permanently deleted.

I would say there are multiple possibilities, if i understand your
desire correctly.  The easiest would likely be a function plus
a commandalias (or even a key binding).

  define my_delete {
\copy "$@" /tmp/undelete.mbox
\delete "$@"
  }
  commandalias d '\call my_delete'

And then you say "d *" as before.  Just replace my_delete with
whatever is your desire, but note that this is inefficient unless
you stay under the same IMAP account (for a while).  You could
also just use \move instead of \copy, which is likely very much
more efficient than the above.  But there is no automatic and
builtin way to say, for example, "just let delete do x and y", no.

 |Thanks.

Hope this help.
Merry Christmas ;) i wish from Germany,
Ciao,

 |Jon
 |
 |
 --End of <20191223153845.kcdii%...@fineman.me>

--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: mail sign/encrypt

[Steffen Nurpmeso]

Hello again Rudolf.

Rudolf Sykora  wrote:
 |I'd like to be able to optionally
 |- sign my email,
 |- encrypt the email.
 |
 |I have a certificate in the .p12 form,
 |containing my private key and two certificates,
 |one of them mine.
 |
 |I want to prepare mail locally, i.e. to use
 |some simple locally installed MUA.
 |
 |Is there a way with the default "mail" program,
 |or do I have to install some more powerful MUA?

S-nail can do that indeed, and once v14.9.10 finally really gets
included in ports (and brings in 30+ months of what i call
development), then you could even do at least some useful things
with the on-compose-..  hooks that you have suggested over two
years ago, too.

And i see potential for improvement, also of the manual.  Thanks.

--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: S-nail, ssh, and vi

[Steffen Nurpmeso]

Good morning Predrag.

Predrag Punosevac  wrote:
 |mar...@martinbrandenburg.com wrote:
 ..
 |>> Can anybody help me understand what am I seeing. Namely I am trying to 
 |>> send an e-mail using S-nail 14.8.12 (the last one which cleanly compiles
 |>> on OpenBSD). Actual package is 14.8.9. Ever since I upgraded to 6.1 I

I still have not found the time to back OPT_ALWAYS_UNICODE_LOCALE
(true on OpenBSD) with real functionality, iconv(3) will remain
a dependency of IMAP in v14.9 (i promised you to try hard to
reinstantiate the IMAP code).  Sorry.

 |>> noticed that if I try to use ~v in order to load my e-mail into vi from
 |>> the base for editing I have normal behaviour if the existing message is
 |>> empty but if I had started typing I see
 |>>
 |>>
 |>> ~v [LogLevel VERBOSE]
 |>> ~v [LogLevel DEBUG]
 ...
 |> It's coming from ssh.  If you type an escape sequence immediately after
 |> a newline ssh might recognize it.  Type return followed by ~? in ssh for
 |> more information.
 ...
 |> ~. will kill a stuck session.
 ...
 |> In short, type ~~v for vi when running mail in ssh.
 |
 |Works for me! I only run mail in ssh when I am away from my home to
 |bypass worning messages from my mail providers. I have never seen this
 |before. 

I (finally) set the *escape* variable to ! to avoid this (after
having been disconnected quite some times after typing ~., and
having to reload all the SSH keys):

  set escape=!

and then type !v in compose mode (it is !e or truly now F1 due to

  !:bind compose
  bind compose :kf1 !e

for me).

--steffen

Re: 6.0/i386 memcpy(3) causes crash if DST < SRC, because of overlap

[Steffen Nurpmeso]

"Theo de Raadt"  wrote:
  ...
 |> If your code triggers the memcpy() log+abort, then the code only works 
 |> elsewhere because the compiler isn't smart enough.  Yet.
 |
 |How about undefined behaviour such as the following:
 |
 |if (backwards) {
 | fprintf(stderr, " --\n");
 | fprintf(stderr, "/  \\\n");
 | fprintf(stderr, "   /REST\\\n");
 | fprintf(stderr, "  /  IN  \\\n");
 | fprintf(stderr, " / PEACE  \\\n");
 | fprintf(stderr, "/  \\\n");
 | fprintf(stderr, "| Steffen  |\n");
 | fprintf(stderr, "|   0 Au   |\n");
 | fprintf(stderr, "|   killed by a|\n");
 | fprintf(stderr, "|backward  |\n");
 | fprintf(stderr, "|  memcpy  |\n");
 | fprintf(stderr, "|   2017   |\n");
 | fprintf(stderr, "   *| *  *  *  | *\n");
 | fprintf(stderr, "  _)/_//(\\/(/\\)/\\//\\/|_)___\n");

(HA-HA-HA!)

 | reboot(RB_NOSYNC);
 | abort();
 |}

..so slowly goes the night.

--steffen

Re: 6.0/i386 memcpy(3) causes crash if DST < SRC, because of overlap

[Steffen Nurpmeso]

Philip Guenther <guent...@gmail.com> wrote:
 |On Tue, 21 Feb 2017, Steffen Nurpmeso wrote:
 |...
 |> But mind you, it is true that i still think it is funny that this 
 |> happened on a BSD system, the origin of bcopy(3).  To me memcpy(3) never 
 ...
 |If your code triggers the memcpy() log+abort, then the code only works 
 |elsewhere because the compiler isn't smart enough.  Yet.

Yes.  Lover, lover go by...

--steffen

Re: 6.0/i386 memcpy(3) causes crash if DST < SRC, because of overlap

[Steffen Nurpmeso]

"Theo de Raadt"  wrote:
  ...
 |>|the point is to make memcpy a strict API.
 |> 
 |> It turned out not to be too problematic for myself (i hope i have
 |> found all occurrences).  The commit message reads
 |> 
 |>   Avoid memcpy(3) crash due to strict standard compliance..
 |
 |So you are saying strict standard compliance made your program buggy?

I have changed it to appease you and the weird english it was:

  Avoid crash due to a strictly standard compliant memcpy(3)..

 |> Luckily this happened before the release!
 ...
 |Then why did you use memcpy, if you knew it required strict ordering?
 |You should have used memmove in the first place, which is bcopy with
 |the arguments swapped.

Yes.

--steffen

Re: 6.0/i386 memcpy(3) causes crash if DST < SRC, because of overlap

[Steffen Nurpmeso]

Theo de Raadt  wrote:
 |>> There's got to be a performance cost, not using the .S versions.
 |>
 |>What is the average size of the copy please?
 |
 |Average in what?  In base, or in chrome?
 |
 |>Years ago, I did a whole lot of tests with this. I was so disappointed 
 |>with memcpy that I NEVER use memcpy these days, only 'memmove'. I grew
 |>up with 'bcopy' so I tend to think in terms of safe overlapped copies.
 |
 |Well we don't control the entire ecosystem to follow such practices.

But he is right that moving backwards was very much faster on old
x86 hardware, which i (who never read hardware system manuals, let
alone processor-family specifics) never understood, since the
range was available via repz regardless of the direction.  I read

   // on both, my Athlon 1600+ and my old Cyrix 166+, simple backward
   // copying via REPZ MOVSL is as fast, or up to ~5 percent faster, than
   // the perfectly thought through MMX+SSE optimized forward copy is.
   // (which is not available on the Cyrix.  there Move is somewhat 300
   // percent faster than Copy anyway.)

Moving backwards much appreciated.

  ..
 |the point is to make memcpy a strict API.

It turned out not to be too problematic for myself (i hope i have
found all occurrences).  The commit message reads

  Avoid memcpy(3) crash due to strict standard compliance..

Luckily this happened before the release!
But mind you, it is true that i still think it is funny that this
happened on a BSD system, the origin of bcopy(3).  To me memcpy(3)
never has been anything but an optimization for cases where you
know it is save, so that the tests, the move to the end to start
there etc., can be avoided.  This was at least nine (9) cycles
iirc on the above CPUs that can be saved, and that almost
sufficient to copy a small string!
Ciao.

--steffen

6.0/i386 memcpy(3) causes crash if DST < SRC, because of overlap

[Steffen Nurpmeso]

Hey,

Just something funny for in between...
I am now looking over all calls to memcpy() because i got a crash
on OpenBSD on a perfect subject to memcpy(), effectively a string
move forward (i.e., leftwise).  I never would have even thought on
anything else but

// the difference to Copy is that this fn handles overlapping regions,
// i.e., starts at the end if source (_from) LT destination (_to).
// so what we do is easy and thus we just jump off to copy unless we
// can't.  this works because the functions use equal stacks and so.

so that i became a hundred percent used to that.  Yes, now i read
that the standard says "If copying takes place between objects
that overlap, the behavior is undefined", but they don't overlap,
do they -- you have to load before you store.
Have a good night.

--steffen

Re: how to send email via Mail

[Steffen Nurpmeso]

Roderick <hru...@gmail.com> wrote:
 |On Fri, 26 Feb 2016, Steffen Nurpmeso wrote:
 |>|client I feel like.  mail(1) was a bit too tedious and limited for
typical
 |>|use.
 |>
 |> Unfortunately i (as the maintainer of the source) have to agree.
 |> So it is.  Especially regarding interactive use: no way to access
 |> message MIME parts directly, and no OpenPGP support, for example.
 |> S/MIME limited to the OpenSSL MIME parser.  Come back in ten years
 |> from now, perhaps.  ^.^
 |
 |We had this thema before. See:
 |
 |https://marc.info/?t=13800958274=1=2

It seems to me that often only patching a codebase is not a good
thing, but especially if it is a codebase that originates in the
1970s and was developed for the machines of the 70s and the
non-existing standards of the 70s.  Much has changed, and if you
add and add on top of a base that was designed in totally
different circumstances, then at some time the base is dead.
Regarding S-nail 2013 is a long time passing, and it has
a heartbeat.  Again.  It surely would have been better to take
OpenBSD Mail and use that as a starter, for example, but i was
pointed to that one and i did it.  Also i didn't know consciously.
And i'm still alive, no heart attack so far.  And the possible
reasons will vanish.  YES!

 |I agree that mail (1) has its limitations, but in todays form it
 |is coherent with the Unix concept and must stay there. This is
 |similar to the discussion about lpr/lpd.

I disagree.  You need to have MIME to have UTF-8 for example.  If
all you need is a cronjob pure ASCII reporter then use what i have
on small Busybox machine, with (possible) some echo(1)es followed
by cat(1) feeding a (restricted version of) sendmail(1) -t.
Right?  So for S-nail you can say "make CONFIG=MINIMAL" or even
"make CONFIG=NULLI" and you get only the very basic, but with
MIME.  Then give it a few more years and it has been cleaned even
more.  (This is at least what i hope.  Still.)

 |The solution to the limitation is not to inflate it with all kind
 |of cool features, but to use an alternative email program with
 |the wanted cool features and leave mail (1) there as it is.

It is all i need, really.  Or, better, it (S-nail) is all i use
and it would be all i need if it would improve some more.  This
regarding user interface and possibilities on the one hand, and
code quality / density on the other.  It is very stable, i start
it on monday and quit it on saturday for a long time now.

But you are right.  It should effectively be a modularized library
that possibly even has a Lua accessor, with the actual front-end
doing only command-line parsing etc.  That is a long road, but the
topic e-mail involves a lot of standards that need to be and that
you want to become handled correctly and no other mailer i know of
except nmh (which i don't know) and of course the superior Plan9
approach to mail handling offer the possible possibility of using
mail from the command line.

E.g., in the queue i have an idea for a very simple frontend for
mlmmj mailing-list archive handling with searching capabilities.
How do you do that?  Effectively you use a scripting language like
Perl (with a lot of nice and mature but non-default modules) or
Python (urgh!), or you write a program that uses one of the
available mail libraries.  Or you use Plan9 and use grep(1).  Or
you use nmh and parse each message a thousand times (i don't know
nmh).  Or you could use the BSD Mail and its batching
capabilities, *if* you could use the BSD Mail for that.  But you
can't.  And *this* is the problem for me.  (I'll use S-nail for
this, but it is a terrible and ugly hack.)

 |Perhaps in the future we will be able to mount imap mailboxes using
 |fuse. Then we can read imap mailboxes with mail (1) not altering it,

Or use Plan9 today.

 |this is the unix way. For PGP and mime, mail (1) allows to pipe
 |the mail, this is the unix way. Inflating mail (1) and lpr/lpd with

But it's shit.  You cannot say "rawpipe" etc.  It is not flexible,
not configurable, it is dumb and cannot really be used for
anything real, except by outer intelligence (like signature mark
lines which an external program treats as boundaries).  Maybe
NetBSD Mail can do that better, i don't know.  I know that S-nail
really sucks in this area.

 |cool features is perhaps the linux way, but not the unix way.

I disagree, because a mail handling system needs to be able to
handle mail.  I agree with lpr, it is good to have a printer that
understands postscript.  I for one hate cups and all that XML
script foo (once i've looked last).  Maybe because i don't
understand it.  I think it all has become so cheap that a nice
super-simple ARM machine driven by Linux should not only be in the
refrigerator but also in the printer, so that i can feed
postscript/pdf into it directly, and don't need to take care for
the rest.  I'd be willing to spend some Euro more for Postscript.
I kno

Re: how to send email via Mail

[Steffen Nurpmeso]

Артур Истомин  wrote:
 |On Thu, Feb 25, 2016 at 07:54:20PM -0500, Nick Holland wrote:
 |> On 02/25/16 17:01, Jaap Bosman wrote:
 |>> Hallo, I would like to use mail(1) for email client.

Hallo!

 |> No, really, you don't.

It may be that he is right, you know.
But if you really would like to give Mail a chance you may want to
have a look at the S-nail (later S-mailx) derivative i maintain.
There is a port in the OpenBSD tree but for now i think you would
be better off compiling from source - that is easy, on OpenBSD,
just say "make all WANT_READLINE=yes" and then "make install" as
root.  The source is at [1] or [2], and the online manual[3] is
full of hyperlinks which is hopefully a help especially for new
users.  Many improvements are still possible, but in the example
section[4] you should find anything you need; ring through if not,
please.  It is likely that you find interactive usage too
restricted for your daily work, but we'll surely get better as
time goes by.

  [1] https://downloads.sourceforge.net/project/s-nail/s-nail-14_8_6.tar.xz
  [2] https://git.sdaoden.eu/cgit/s-nail.git/snapshot/s-nail-14.8.6.tar.xz
  [3] https://www.sdaoden.eu/code-nail.html
  [4] https://www.sdaoden.eu/code-nail.html#34

 |>> In man mail(1) I read nothing about configure mail to send and receive
 |>> email from outside. I would like to find how to configure mail(1).
 |>
 |> Step 1: you need to read the first few chapters of the Sendmail book.
 |> You can skip all the stuff about sendmail configuration, but you don't
 |> seem to understand how mail works.
 |>
 |> And ... hopefully you realize you don't want to get involved in that
 |> side of the mail system.  Just pay someone to do that for you.
 |
 |With this approach, we will have only one email provider. His name is\
 | Google.

It seems to me it must be very large and fully interweaved; yes.

  https://moderncrypto.org/mail-archive/messaging/2014/000780.html

 |Spam and other black sides of today email system is price we pay for
 |decentralized system. And it's worth it.

Oh yes, flashing advertises improve the simplemost text pages
a lot; i hope the future brain implant doesn't stutter the same
way that my graphical browser does today when i open such a page.
E.g., i hope the route to googleads never hangs when i really need
to go to toilet and the implant wants to provide some
context-sensitive advertising first...  Kind of cali fornication,
if you trust Kundera, at least.

--steffen

Re: how to send email via Mail

[Steffen Nurpmeso]

"trondd"  wrote:
 |On Fri, February 26, 2016 10:55 am, Joel wrote:
 |> Unfortunately, it isn't in the ports tree, but there is a slightly
 |> updated version of mail called heirloom-mail.

That is heirloom-mailx.

 |s-nail is a fork and is in ports.  I went through this same exercise and

The port is unfortunately 20 dozen commits and half a year behind
the latest release, and most of those commits were cherry-picked
stability improvements and/or fixes from the v14.9 development
branch.  Also the OpenBSD port should use readline from the base
system, which is especially nice for normal users.  Imho.

 |quickly switched to IMAP so I can read my mail from anywhere with whatever
 |client I feel like.  mail(1) was a bit too tedious and limited for typical
 |use.

Unfortunately i (as the maintainer of the source) have to agree.
So it is.  Especially regarding interactive use: no way to access
message MIME parts directly, and no OpenPGP support, for example.
S/MIME limited to the OpenSSL MIME parser.  Come back in ten years
from now, perhaps.  ^.^

It is however the best Mail i know of, already today.  And one day
it'll have SysV signal handling on the inside, too.

--steffen