Re: [mmh] Accept header lines of exactly 998 characters

2018-07-19 Thread Vasilii Kolobkov
I've split the last patch and updated it according to your feedback. Hopefully whitout having lost anything while in transit :) What do you say? From 899eac2cee69e32abe2813735ee7ff0870f5ebd1 Mon Sep 17 00:00:00 2001 From: Vasilii Kolobkov Date: Thu, 19 Jul 2018 11:56:11 +0200 Subject: [PATCH 1/4

Re: [mmh] Accept header lines of exactly 998 characters

2018-07-19 Thread Vasilii Kolobkov
[2018-07-19 10:02 +0200] markus schnalke > [2018-07-19 03:24] Philipp Takacs > > [2018-07-18 23:13] Vasilii Kolobkov > > > Yet two of them do fail, but that'd be another patch. The ali tests > > > for the blind lists fail - it's the first time i came to know of >

Re: [mmh] Accept header lines of exactly 998 characters

2018-07-19 Thread Vasilii Kolobkov
Thanks for the comments, Philipp! [2018-07-19 03:24 +0200] Philipp Takacs > [2018-07-18 23:13] Vasilii Kolobkov > > +pseq() { > > I'm not sure, if we realy nead this funktion, because it's used on > two places. In the one place it's easy to remove. On the other place > I

Re: [mmh] Accept header lines of exactly 998 characters

2018-07-18 Thread Vasilii Kolobkov
as well? Cheers, Vasilii p.s. i prefixed all the portable functions with p* so to not shadown the system ones just in case. ---8<--- From 204ae88524838063493242f012a1b1fe2fcf2d05 Mon Sep 17 00:00:00 2001 From: Vasilii Kolobkov Date: Sun, 15 Jul 2018 23:05:09 +0200 Subj

Re: [mmh] Accept header lines of exactly 998 characters

2018-07-16 Thread Vasilii Kolobkov
[2018-07-16 21:45 +0200] markus schnalke > [2018-07-16 20:56] Vasilii Kolobkov > > [2018-07-16 12:23 +0200] markus schnalke > > > Although $((...)) ist part of POSIX. I'd like to avoid it, if > > > possible. All uses of $((...)) in our test cases can be easily > &

Re: [mmh] Accept header lines of exactly 998 characters

2018-07-16 Thread Vasilii Kolobkov
[2018-07-16 14:17 +0200] Philipp Takacs > [2018-07-16 09:20] Vasilii Kolobkov > > [2018-07-16 03:18 +0200] Philipp Takacs > > > What a strange BSD are you using, maybe OpenBSD ;-)? seq is part of Net, > > > Free and DragonflyBSD. Ok, the awk bug/missing

Re: [mmh] Accept header lines of exactly 998 characters

2018-07-16 Thread Vasilii Kolobkov
Good evening folks! [2018-07-16 12:23 +0200] markus schnalke > [2018-07-15 23:29] Vasilii Kolobkov > > 1. Generate sequences vi shell script as BSDs lack seq(1) > > That's unfortunate, as seq(1) is such a great tool. It's not part > of POSIX though. (It originated in Rese

Re: [mmh] Accept header lines of exactly 998 characters

2018-07-16 Thread Vasilii Kolobkov
[2018-07-16 03:18 +0200] Philipp Takacs > What a strange BSD are you using, maybe OpenBSD ;-)? seq is part of Net, > Free and DragonflyBSD. Ok, the awk bug/missing feature is also in FreeBSD. There's no hiding from you, Philipp! I thought those issues to be rather common in BSD-land and am

Re: [mmh] Accept header lines of exactly 998 characters

2018-07-15 Thread Vasilii Kolobkov
ost of the show(1) tests, and i'll be fixing the rest should you deem it useful. Cheers, Vasilii ---8<--- From a8035ca600799e10b1aab2fd9f1b9fe97e2f9aad Mon Sep 17 00:00:00 2001 From: Vasilii Kolobkov Date: Sun, 15 Jul 2018 23:05:09 +0200 Subject: [PATCH] Make show/test-longline

Re: [mmh] Accept header lines of exactly 998 characters

2018-07-14 Thread Vasilii Kolobkov
Hey Philipp! [2018-07-14 14:16 +0200] Philipp Takacs > I have two follow up patches. The first one fixes crlf handling for > long lines in m_getfld2. The secound fix the simular length checking > bug in sposts. Great, i did notice the LF/CRLF discrepancy too, but was too lazy to fix it :) > By

[mmh] Accept header lines of exactly 998 characters

2018-07-11 Thread Vasilii Kolobkov
Holla mmh folks, hope you're doing fine! Lately I've been getting issues with messages containing header lines of 998 characters. This patch fixes it. ---8<--- From ee20b90a40bfa483008fdb7caa7c9e023d519870 Mon Sep 17 00:00:00 2001 From: Vasilii Kolobkov Date: Wed, 11

[mmh] archiving encrypted mail

2017-09-01 Thread Vasilii Kolobkov
Hello mmh folks! Does anybody here save their outgoing encrypted mail unencrypted? Any ideas on how would be best to handle this? Cheers, Vasilii