[P-U] Re: Postfix lists are migrating to a new list server

2023-03-07 Thread Steffen Nurpmeso via Postfix-users
The nice thing about this new list server is that it plays very well with gray listing (without causing the immediate "retry storms" that sometimes can be seen, especially with German service providers which do nothing but themselve perform address verification, and are unfortunately used very ofte

[P-U] Re: Postfix lists are migrating to a new list server

2023-03-07 Thread Steffen Nurpmeso via Postfix-users
Steffen Nurpmeso wrote in <20230307214046.ajvsx%stef...@sdaoden.eu>: |The nice thing about this new list server is that it plays very The ugly that it uses this terrible "Who via LIST " stuff even if the sender does not (granted: yet) uses DKIM. --steffen | |Der Kragenbaer,The m

[P-U] Re: Postfix lists are migrating to a new list server

2023-03-09 Thread Steffen Nurpmeso via Postfix-users
Michael wrote in <0d3709b8-72ae-4e54-a8a5-5a82f3b09...@hemathor.de>: |On Thursday, 9 March 2023 15:29:01 CET, Wietse Venema via Postfix-users |wrote: |> Let me help remind you that your email address has been out there |> for a while. Here are some samples from the postfix-users list: | |i

[P-U] Re: New List Host and Reply-to Header

2023-03-09 Thread Steffen Nurpmeso via Postfix-users
Wietse Venema via Postfix-users wrote in <4pxdmb1f8fzj...@spike.porcupine.org>: |postfix--- via Postfix-users: |> Is it the best idea to add a reply-to header to the author on mailing \ |> list emails? |> The problem I see is many people will hit reply in their email client \ |> which will cr

[P-U] Re: New List Host and Reply-to Header

2023-03-09 Thread Steffen Nurpmeso via Postfix-users
Jaroslaw Rafa wrote in <20230309195933.ga16...@rafa.eu.org>: |Dnia 9.03.2023 o godz. 13:34:39 postfix--- via Postfix-users pisze: |> Is it the best idea to add a reply-to header to the author on mailing \ |> list emails? |> The problem I see is many people will hit reply in their email client

[P-U] Re: New List Host and Reply-to Header

2023-03-09 Thread Steffen Nurpmeso via Postfix-users
Gerald Galster wrote in <4339792b-b58d-4c42-a836-1e71e0eb6...@gcore.biz>: |> This list uses Mailman configuration settings, not handcrafted code. |> If people believe that it is worthwhile to change the Mailman |> implementation or the DMARC spec, then I suggest that they work |> with the peop

[P-U] Re: New List Host and Reply-to Header

2023-03-09 Thread Steffen Nurpmeso via Postfix-users
Steffen Nurpmeso wrote in <20230309210623.0mekl%stef...@sdaoden.eu>: ... |This is the crux with email as it is, if they would have invented |something MIME-alike at the very beginning, and messages would |really be enveloped entirely, and enveloped entirely, etc., as in |old times, where each

[P-U] Re: New List Host and Reply-to Header

2023-03-09 Thread Steffen Nurpmeso via Postfix-users
Jaroslaw Rafa wrote in <20230309222044.ga19...@rafa.eu.org>: |Dnia 9.03.2023 o godz. 21:39:10 Steffen Nurpmeso via Postfix-users pisze: |>|With changing From: to point to the list itself and adding Reply-To: |>|pointing to the author this behaviour hasn't changed. I'm s

[pfx] Re: [P-U] Re: The joke writes itself.

2023-03-10 Thread Steffen Nurpmeso via Postfix-users
Matthias Fechner wrote in : |Am 10.03.2023 um 13:01 schrieb Patrick Ben Koetter via Postfix-users: |> In the old days I used the tags to filter my messages and place them \ |> in the |> right mailbox. With the advent of DMARC I stopped that and turned \ |> to using |> List-Id:-headers as fil

[pfx] Re: milter-reject: END-OF-MESSAGE

2023-03-10 Thread Steffen Nurpmeso via Postfix-users
Gerald Galster wrote in : In my postgray thing i have "allow .dhl.de" (surely for a reason). --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) __

[pfx] sender address verification: easy bypass for myhostname/mydomain?

2023-03-10 Thread Steffen Nurpmeso via Postfix-users
Hello. I see a thread for "double-bounce check applied to itself" from February 2021, but it does not exactly fit this bill (i think): Mar 11 01:10:36 postfix/smtpd[2936]: connect from AWS-OUTLOOK.TOP[85.31.45.162] Mar 11 01:10:37 postfix/smtpd[2936]: Anonymous TLS connection established fr

[pfx] milter: could it splice (, somehow)?

2023-03-10 Thread Steffen Nurpmeso via Postfix-users
Hello. Imagine the DKIM standard would be revised and extended a bit (to get rid of DMARC and ARC, even, could it be) to - sign the entire message as for now, - but include a "cramped=1" tag that signals that all receivers are actually covered by the DKIM signature, so - for any "RCPT TO:<>"

[pfx] mailman mangling (Was: Re: milter: could it splice (, somehow)?)

2023-03-10 Thread Steffen Nurpmeso via Postfix-users
Steffen Nurpmeso wrote in <20230311005401.bynjz%stef...@sdaoden.eu>: ... |>From [.] And i know it is not popular among UNIX people, who like it that way, but this "From_" quoting was introduced by mailman (i presume) when it mangled my quoted-printable to something non-reversible. I do not kno

[pfx] Re: mailman mangling (Was: Re: milter: could it splice (, somehow)?)

2023-03-11 Thread Steffen Nurpmeso via Postfix-users
Wietse Venema wrote in <4pyjz55tpdzj...@spike.porcupine.org>: |Wietse Venema via Postfix-users: |> Steffen Nurpmeso via Postfix-users: |>> Steffen Nurpmeso wrote in |>> <20230311005401.bynjz%stef...@sdaoden.eu>: |>> ... |>>|>From [.] |> |>

[pfx] Re: milter: could it splice (, somehow)?

2023-03-11 Thread Steffen Nurpmeso via Postfix-users
postfix-users@postfix.org wrote in : |On Sat, Mar 11, 2023 at 01:54:01AM +0100, Steffen Nurpmeso via Postfix-u\ |sers wrote: | |> - sign the entire message as for now, | |You're confusing the message and the envelope. ..no? No. |> - but include a "cramped=1" tag that signals that all rec

[pfx] Re: milter: could it splice (, somehow)?

2023-03-11 Thread Steffen Nurpmeso via Postfix-users
Scott Kitterman wrote in <4d53bd64-1672-49c5-adca-487f320f8...@kitterman.com>: .. |>But i treat your answer as if milters will not do that. | |If you want to talk about DKIM replay, the IETF DKIM working group \ |was just rechartered to work on that exact thing: ietf-d...@ietf.org . Maybe a

[pfx] Re: sender address verification: easy bypass for myhostname/mydomain?

2023-03-11 Thread Steffen Nurpmeso via Postfix-users
Steffen Nurpmeso wrote in <20230311003215.yvtaf%stef...@sdaoden.eu>: |I see a thread for "double-bounce check applied to itself" from |February 2021,[.] ... |Is there an easy (non-DNS etc) way to say that @sdaoden.eu (or |even @(.+\.)?sdaoden\.eu MUST NOT come from the outside, so Forget abo

[pfx] Re: sender address verification: easy bypass for myhostname/mydomain?

2023-03-12 Thread Steffen Nurpmeso via Postfix-users
Steffen Nurpmeso wrote in <20230312003030.4aldj%stef...@sdaoden.eu>: |Steffen Nurpmeso wrote in | <20230311003215.yvtaf%stef...@sdaoden.eu>: ||I see a thread for "double-bounce check applied to itself" from ||February 2021,[.] | ... ||Is there an easy (non-DNS etc) way to say that @sdaoden.e

[pfx] Re: use object storage as message store

2023-03-12 Thread Steffen Nurpmeso via Postfix-users
Postfix users wrote in <4pzsd16nkpzj...@spike.porcupine.org>: ... |Postfix must wait for fsync() to complete (or whatever its Cloud |equivalent is), before it can take responsibility for delivery of (postfix does not support FULLFSYNC on MacOS.) --steffen | |Der Kragenbaer,The

[pfx] Re: Allow TLSv1 only for internal senders

2023-03-18 Thread Steffen Nurpmeso via Postfix-users
Jaroslaw Rafa wrote in <20230318191215.gb30...@rafa.eu.org>: |Dnia 18.03.2023 o godz. 14:54:15 Gerd Hoerst via Postfix-users pisze: |> I setup my postfix for the clients to use only  protocols > TLSv1 with |> |> smtpd_tls_mandatory_protocols = !SSLv2, !SSLv3, !TLSv1 |> smtpd_tls_protocols   

[pfx] Re: Allow TLSv1 only for internal senders

2023-03-18 Thread Steffen Nurpmeso via Postfix-users
Jaroslaw Rafa wrote in <20230318203334.ga31...@rafa.eu.org>: |Dnia 18.03.2023 o godz. 21:08:17 Steffen Nurpmeso via Postfix-users pisze: |> I still have no problems with |> |> smtpd_tls_mandatory_protocols = >=TLSv1.2 |> smtpd_tls_protocols = $smtpd_tls_mandatory_pr

[pfx] Fwd: Re: Re: Allow TLSv1 only for internal senders

2023-03-18 Thread Steffen Nurpmeso via Postfix-users
GP: id=EE19E1C1F2F7054F8D3954D8308964B51883A0DD; url=https://ftp.sdaoden.eu/steffen.asc; preference=signencrypt Peter wrote in <29591811-f04e-b667-d5df-3e3223e7d...@pajamian.dhs.org>: |On 19/03/23 09:08, Steffen Nurpmeso via Postfix-users wrote: |> I still have no problems with |> |>smtpd_tls_mandatory_

[pfx] Re: Allow TLSv1 only for internal senders

2023-03-20 Thread Steffen Nurpmeso via Postfix-users
Jaroslaw Rafa wrote in <20230318234124.ga32...@rafa.eu.org>: |Dnia 18.03.2023 o godz. 23:54:28 Steffen Nurpmeso via Postfix-users pisze: |> Eh, no. I do not do either. (Granted i use PayPal one, two times |> a month, but my bank account is not online-enabled.) |> I _never_

[pfx] Re: Allow TLSv1 only for internal senders

2023-03-22 Thread Steffen Nurpmeso via Postfix-users
Jaroslaw Rafa wrote in <20230322104345.ga10...@rafa.eu.org>: |Dnia 20.03.2023 o godz. 21:46:59 Steffen Nurpmeso via Postfix-users pisze: |> Luckily here a couple of shops remain, even for clothes and |> electronics (mostly household). It is much uglier a bit further |[...] | |

[pfx] Re: Allow TLSv1 only for internal senders

2023-03-22 Thread Steffen Nurpmeso via Postfix-users
Steffen Nurpmeso wrote in <2023030559.mn7ux%stef...@sdaoden.eu>: |Jaroslaw Rafa wrote in | <20230322104345.ga10...@rafa.eu.org>: ||Dnia 20.03.2023 o godz. 21:46:59 Steffen Nurpmeso via Postfix-users pisze: ||> Luckily here a couple of shops remain, even for clothes and

[pfx] Re: Allow TLSv1 only for internal senders

2023-03-23 Thread Steffen Nurpmeso via Postfix-users
Jaroslaw Rafa wrote in <20230322230223.ga17...@rafa.eu.org>: |Dnia 22.03.2023 o godz. 23:05:59 Steffen Nurpmeso via Postfix-users pisze: |> I have very strict firewall rules, and you have become blocked for |> last access + 84000 seconds. |> Should work again. | |I again got

[pfx] Re: Allow TLSv1 only for internal senders

2023-03-24 Thread Steffen Nurpmeso via Postfix-users
Bernardo Reino wrote in <79552717-5p3o-8q26-r963-124or6r66...@oozx.bet>: |On Thu, 23 Mar 2023, Steffen Nurpmeso via Postfix-users wrote: ... |> (That is pretty off-topic for postfix; except maybe for fun |> posting my SMTP related firewall ... |> add_ru

[pfx] Re: Allow TLSv1 only for internal senders

2023-03-24 Thread Steffen Nurpmeso via Postfix-users
Steffen Nurpmeso wrote in <20230324175540.o_vn-%stef...@sdaoden.eu>: |Bernardo Reino wrote in | <79552717-5p3o-8q26-r963-124or6r66...@oozx.bet>: ||On Thu, 23 Mar 2023, Steffen Nurpmeso via Postfix-users wrote: | ... ||> (That is pretty off-topic for postfix; except maybe for f

[pfx] Re: Allow TLSv1 only for internal senders

2023-03-24 Thread Steffen Nurpmeso via Postfix-users
gt;: ||>|On Thu, 23 Mar 2023, Steffen Nurpmeso via Postfix-users wrote: ||> ... ||>|> (That is pretty off-topic for postfix; except maybe for fun ||>|> posting my SMTP related firewall ||> ... ||>|> add_rule -p tcp --src ${addr}${mask} \ ||&g

[pfx] Re: Allow TLSv1 only for internal senders

2023-03-24 Thread Steffen Nurpmeso via Postfix-users
Ahem, .. i however have to add one more sentence.. Steffen Nurpmeso wrote in <20230324193739.s-qco%stef...@sdaoden.eu>: ... ||reading, programming, and nature impressions, four to five hours ||a day, all in all, for caring for the (other) animal friends ||alone, sorry. Please .. that "other

[pfx] Re: pf snap 3.8-20230402 mem corruption issues

2023-04-06 Thread Steffen Nurpmeso via Postfix-users
Wietse Venema wrote in <4pshgn4l8vzj...@spike.porcupine.org>: |Wietse Venema via Postfix-users: |> I have some, starting after I updated from 3.8-202304331 to 3.8-2023040\ |> 2. There are snapshots, there is source access beyond regular releases? ... |> There are two changes, one in util/

[pfx] Re: pf snap 3.8-20230402 mem corruption issues

2023-04-06 Thread Steffen Nurpmeso via Postfix-users
Wietse Venema wrote in <4psxbn1frczj...@spike.porcupine.org>: |Steffen Nurpmeso via Postfix-users: |> Wietse Venema wrote in |> <4pshgn4l8vzj...@spike.porcupine.org>: |>|Wietse Venema via Postfix-users: |>|> I have some, starting after I updated from 3.8-202304

[pfx] Re: pf snap 3.8-20230402 mem corruption issues

2023-04-06 Thread Steffen Nurpmeso via Postfix-users
postfix-users@postfix.org wrote in : |On Thu, Apr 06, 2023 at 11:20:17PM +0200, Steffen Nurpmeso via Postfix-u\ |sers wrote: | |> It seems so square to have a need to use the C library resolver, |> or external library, or even code something yourself, in order to |> implement a policy or mil

[pfx] Re: SPF: HELO does not publish an SPF Record

2023-04-12 Thread Steffen Nurpmeso via Postfix-users
Matus UHLAR - fantomas wrote in : |On 12.04.23 12:41, Fourhundred Thecat via Postfix-users wrote: ... |>Does it mean that I should either: |> |> 1) create SPF record for mail.mydomain.com ... |I would do the first: | |fantomas.fantomas.sk descriptive text "v=spf1 a -all" Interesting thi

[pfx] Fwd: [ANN]ounce of S-postgray v0.8.1 ("Something Gray on Bicycle-Day")

2023-04-19 Thread Steffen Nurpmeso via Postfix-users
Hello. Unlike promised there had to be another release, and i still hope it is ok to forward the announcement here. (Bicycle-Day has passed in the meantime, however.) This fixes some bugs, even non-developers can now see --verbose logging, for example. Out of interest i implemented sandboxing, s

[pfx] 3.8.0: spawn says "command time limit exceeded"

2023-04-19 Thread Steffen Nurpmeso via Postfix-users
Hello. On 3.8.0 services managed via spawn(8) now produce Apr 19 01:03:04 postfix/spawn[8485]: warning: /usr/libexec/s-postgray: process id 8486: command time limit exceeded Apr 19 14:43:56 postfix/spawn[19651]: warning: /usr/libexec/s-postgray: process id 19755: command time limit exceeded

[pfx] Re: 3.8.0: spawn says "command time limit exceeded"

2023-04-20 Thread Steffen Nurpmeso via Postfix-users
Wietse Venema wrote in <4q21sp16m7zj...@spike.porcupine.org>: |Steffen Nurpmeso via Postfix-users: |> On 3.8.0 services managed via spawn(8) now produce |> |> Apr 19 01:03:04 postfix/spawn[8485]: warning: /usr/libexec/s-postgray: \ |> process id 8486: command t

[pfx] Re: 3.8.0: spawn says "command time limit exceeded"

2023-04-20 Thread Steffen Nurpmeso via Postfix-users
Wietse Venema wrote in <4q2khr57flzj...@spike.porcupine.org>: |Steffen Nurpmeso: |> Wietse Venema wrote in |> <4q21sp16m7zj...@spike.porcupine.org>: |>|Steffen Nurpmeso via Postfix-users: |>|> On 3.8.0 services managed via spawn(8) now produce |>|> |&g

[pfx] Re: smtpcheck

2023-04-20 Thread Steffen Nurpmeso via Postfix-users
natan wrote in : |Hi |I use keepalived and easy check like: | |vrrp_script chk_myscript { |     script "/usr/bin/postfix-check.sh" |     interval    4 |     fall    2 |     weight  10 |     user root |} | |... |#!/bin/bash |echo "ehlo localhost" | /bin/nc -w 1 "127.0.0.1"

[pfx] Re: 3.8.0: spawn says "command time limit exceeded"

2023-04-20 Thread Steffen Nurpmeso via Postfix-users
Wietse Venema via Postfix-users wrote in <4q2l0p03svzj...@spike.porcupine.org>: |Steffen Nurpmeso: |> Wietse Venema wrote in |> <4q2khr57flzj...@spike.porcupine.org>: |>|Steffen Nurpmeso: |>|> Wietse Venema wrote in |>|> <4q21sp16m7zj...@spike.porcup

[pfx] Re: working around crypto policies turned up to 11

2023-05-10 Thread Steffen Nurpmeso via Postfix-users
postfix-users@postfix.org wrote in : |On Mon, May 08, 2023 at 06:13:25PM -0400, Wietse Venema via Postfix-users \ |wrote: |> We're thinking of adding a few new settings to the stable Postfix |> releases that allow Postfix to regain some control over crypto |> policies that do not necessarily

[pfx] Re: Postfix: running a script on authentication failure

2023-06-22 Thread Steffen Nurpmeso via Postfix-users
Robert Schetterer wrote in : |Am 22.06.2023 um 13:58 schrieb André Rodier via Postfix-users: ... |> Shortly after it has been setup, I see brute force attacks (not |> surprising) from a whole /24 network (more surprising). ... |> Is there any way, with postfix, to run a script on authentica

[pfx] Re: LOST mails in /var/mail/

2023-06-26 Thread Steffen Nurpmeso via Postfix-users
Matus UHLAR - fantomas wrote in : |On 26.06.23 10:32, Tan Mientras via Postfix-users wrote: |>On Mon, Jun 26, 2023 at 10:28 AM Matus UHLAR - fantomas via Postfix-users \ |>postfix-users@postfix.org> wrote: |> |>> If there's not much of them, you can copy them to maildir using \ |>> e.g. mutt

[pfx] Re: local sending

2023-07-11 Thread Steffen Nurpmeso via Postfix-users
Wietse Venema wrote in <4r0ss907yqzj...@spike.porcupine.org>: |Ken Gillett via Postfix-users: |> I disagree about Apple. In this respect they most definitely ARE |> idiots. Email addresses do NOT require anything after the @. That |> simply means the user of that name on the current host. If t

[pfx] Re: email being flagged a spam for using localhost [127.0.0.1] as first hop

2023-08-09 Thread Steffen Nurpmeso via Postfix-users
Michel Verdier via Postfix-users wrote in <87fs4s49y5@free.fr>: |On 2023-08-09, Fourhundred Thecat via Postfix-users wrote: | |> do you think this would be OK, or does the hostname and IP (be it |> localhost.local) have to be there ? | |Why don't you remove completely this header in your

[pfx] Re: email being flagged a spam for using localhost [127.0.0.1] as first hop

2023-08-09 Thread Steffen Nurpmeso via Postfix-users
Michel Verdier via Postfix-users wrote in <87jzu4c5qi@free.fr>: |On 2023-08-09, Steffen Nurpmeso via Postfix-users wrote: | |> 192.0.2.1:submission inet n - n - - smtpd |> -o syslog_name=vpnsub |> -o smtpd_sasl_auth_enable=no

[pfx] [off-topic] Lua searches ML host

2023-08-18 Thread Steffen Nurpmeso via Postfix-users
Hello. The Lua scripting language, which recently celebrated its 30th anniversary, is usable standalone or as an embedded interpreter, and used by many programs and operating-systems, even in-kernel, or as a bootloader, searches a new mailing-list hoster. I was just thinking, maybe some reader of

[pfx] Re: [off-topic] Lua searches ML host

2023-08-19 Thread Steffen Nurpmeso via Postfix-users
Benny Pedersen via Postfix-users wrote in : |Steffen Nurpmeso via Postfix-users skrev den 2023-08-19 02:30: ... |> (And sorry for being off-topic.) | |postfix have not lua support yet, maybe it will come ? Outsourcing parsing (and dumping) of configuration files to Lua could significan

[pfx] Re: How can I set up a very simple postfix server

2023-08-22 Thread Steffen Nurpmeso via Postfix-users
Peter via Postfix-users wrote in <5080e33a-0d10-d028-d59e-0481024e3...@pajamian.dhs.org>: |On 22/08/23 15:42, Bruce Dubbs via Postfix-users wrote: |> I have built postfix-3.8.1 from source and want to use it only on the |> local system. That is, I really only want it to receive messages from

[pfx] Re: How can I set up a very simple postfix server

2023-08-22 Thread Steffen Nurpmeso via Postfix-users
Wietse Venema via Postfix-users wrote in <4rvkgl4lfyzj...@spike.porcupine.org>: |Steffen Nurpmeso via Postfix-users: |> "But" postfix's sendmail reads the postfix configuration, it will |> not work otherwise, at least once i tried last. |> Going over SMTP (s

[pfx] Re: How can I set up a very simple postfix server

2023-08-23 Thread Steffen Nurpmeso via Postfix-users
Peter via Postfix-users wrote in <8b2661ea-5560-af5a-e674-d2fb10094...@pajamian.dhs.org>: |On 23/08/23 11:58, Steffen Nurpmeso via Postfix-users wrote: |> "The problem" (i have given up and did not try it for long) is the |> configuration directory. Does this work

[pfx] Re: How can I set up a very simple postfix server

2023-08-23 Thread Steffen Nurpmeso via Postfix-users
Wietse Venema via Postfix-users wrote in <4rw8mh2rcwzj...@spike.porcupine.org>: |Steffen Nurpmeso via Postfix-users: |>|Alls you need is to 'mount' the maildtop directory into a container |>|with read/write permission, and install the Postfix sendmail and |>|postdrop

[pfx] Re: Recommendation for dkim signing

2023-10-30 Thread Steffen Nurpmeso via Postfix-users
It seems to me there is not much interest of mail operators in stepping to ed25519, reducing the payload of DNS and email? I know dkimpy supports it (and more -- but is python, uuuh!) for long, but OpenDKIM is unchanged for eight years. (At least my sf.net import from 2017-09-23 still stands.) Bt

[pfx] Re: Recommendation for dkim signing

2023-10-30 Thread Steffen Nurpmeso via Postfix-users
postfix-users@postfix.org wrote in : |On Mon, Oct 30, 2023 at 10:06:46AM +0100, Jens Hoffrichter via Postfix-u\ |sers wrote: | |> We are looking into implementing DKIM signing for one of our services, |> and there are multiple ways to implement that. |> |> So far I have found that you can

[pfx] Re: Recommendation for dkim signing

2023-11-01 Thread Steffen Nurpmeso via Postfix-users
Hello. Jens Hoffrichter via Postfix-users wrote in : |On Mon, Oct 30, 2023 at 8:12 PM Steffen Nurpmeso via Postfix-users | wrote: ... |> Btw i would wonder: why do -- as email operators -- still use DKIM |> at all, since there is ARC and it also offers signatures and |> verificat

[pfx] Re: Recommendation for dkim signing

2023-11-02 Thread Steffen Nurpmeso via Postfix-users
Matus UHLAR - fantomas via Postfix-users wrote in : |>Jens Hoffrichter via Postfix-users wrote in |> : |>|On Mon, Oct 30, 2023 at 8:12 PM Steffen Nurpmeso via Postfix-users |>| wrote: |> ... |>|> Btw i would wonder: why do -- as email operators -- still use DKIM |>|

[pfx] Re: Recommendation for dkim signing

2023-11-07 Thread Steffen Nurpmeso via Postfix-users
Benny Pedersen via Postfix-users wrote in <9d22bd4f4b3f203609d2d676306e8...@junc.eu>: |Noel Butler via Postfix-users skrev den 2023-11-05 04:53: |> On 03/11/2023 10:22, Steffen Nurpmeso via Postfix-users wrote: ... |> DKIM, was a problem, but for several years now mailman can do t

[pfx] Re: Replacing ancient Qmail with Postfix.

2023-11-10 Thread Steffen Nurpmeso via Postfix-users
Matus UHLAR - fantomas via Postfix-users wrote in : |On 09.11.23 15:27, Shaun Erickson via Postfix-users wrote: |> We use a fake (internal, externally-unregistered) domain, for our |> division’s servers. Let’s call it fakedomain.com or fd.com, for short. | |Just FYI, there are domain names

[pfx] Re: Recommendation for dkim signing

2023-11-15 Thread Steffen Nurpmeso via Postfix-users
P.S.: Steffen Nurpmeso wrote in <20231103002256.iibfi%stef...@sdaoden.eu>: |Matus UHLAR - fantomas via Postfix-users wrote in | : ||>Jens Hoffrichter via Postfix-users wrote in ||> : ||>|On Mon, Oct 30, 2023 at 8:12 PM Steffen Nurpmeso via Postfix-users ||>| wrote: ||

[pfx] Re: Recommendation for dkim signing

2023-11-15 Thread Steffen Nurpmeso via Postfix-users
Jaroslaw Rafa via Postfix-users wrote in <20231115204142.ga1...@rafa.eu.org>: |Dnia 15.11.2023 o godz. 20:02:44 Steffen Nurpmeso via Postfix-users pisze: |> Funnily i just now got while sending a mail to not more than about |> i think two dozen gmail accounts: |> |>

[pfx] Re: Return-path: == From:

2023-11-17 Thread Steffen Nurpmeso via Postfix-users
Testeur via Postfix-users wrote in <083b817e-2bf9-4307-9484-e5acf678a...@starinux.org>: ... |I'd want that the return-path be the same that the From sender. |Is there a mean to do that with a postfix mean (eg. with rewriting \ |headers) ? Should be -f (and -F) to sendmail if i understood you

[pfx] Re: Return-path: == From:

2023-11-17 Thread Steffen Nurpmeso via Postfix-users
Wietse Venema via Postfix-users wrote in <4sx8x207tzzj...@spike.porcupine.org>: |Viktor Dukhovni via Postfix-users: |> On Fri, Nov 17, 2023 at 07:19:31PM +0100, Steffen Nurpmeso via Postfix-u\ |> sers wrote: |> |>>Remarks: many MTA installations and sites disallow setting an |>>

[pfx] Re: How to temporarily pause virtual mail delivery?

2023-11-22 Thread Steffen Nurpmeso via Postfix-users
Matthias Nagel via Postfix-users wrote in <12336799.O9o76ZdvQC@matthias-pc>: |Am Mittwoch, 22. November 2023, 19:01:23 CET schrieb postfix--- via \ |Postfix-users: |>> I am looking for an option to temporarily pause delivery via LMTP \ |>> and defer mail while the Dovecot mailboxes are being b

[pfx] Re: Exposing the Postfix-generated Received: header to Milters

2023-12-13 Thread Steffen Nurpmeso via Postfix-users
Wietse Venema via Postfix-users wrote in <4sr8hc44p7zj...@spike.porcupine.org>: |Currently, Postfix does not send the Postfix-generated Received: |header to Milters, because that is how Sendmail works, that is what ... |This information would improve the Milter's analysis. Untrusted ... |Th

[pfx] Re: Exposing the Postfix-generated Received: header to Milters

2023-12-13 Thread Steffen Nurpmeso via Postfix-users
Wietse Venema via Postfix-users wrote in <4srcnm0d3jzj...@spike.porcupine.org>: |Steffen Nurpmeso via Postfix-users: |> Wietse Venema via Postfix-users wrote in |> <4sr8hc44p7zj...@spike.porcupine.org>: |>|Currently, Postfix does not send the Postfix-generated Received:

[pfx] Re: 25 years today

2023-12-14 Thread Steffen Nurpmeso via Postfix-users
Wietse Venema via Postfix-users wrote in <4srxyy1hslzj...@spike.porcupine.org>: |As a few on this list may recall, it is 25 years ago today that the |"IBM secure mailer" had its public beta release. This was accompanied |by a nice article in the New York Times business section. | |There is so

[pfx] Re: omitting the X-Google-Original-From header

2023-12-18 Thread Steffen Nurpmeso via Postfix-users
Bill Cole via Postfix-users wrote in <6039ed61-2c8f-4a12-b736-994d32632...@billmail.scconsult.com>: |On 2023-12-17 at 09:27:36 UTC-0500 (Sun, 17 Dec 2023 06:27:36 -0800 |(PST)) |saunders.nicholas--- via Postfix-users |is rumored to have said: | |> How is this header populated? |> |> X-Go

[pfx] Re: Postfix using proxy protocol outbound?

2023-12-19 Thread Steffen Nurpmeso via Postfix-users
Wietse Venema via Postfix-users wrote in <4svjy117ywzj...@spike.porcupine.org>: ... |I expect that a SOCKS5 client would not use much code, compared to |the code that was needed with HaProxy. Gaetan Bisson (former ArchLinux, a very smart math professor Tahiti) has written a small LD_PRELOAD SO

[pfx] Re: omitting the X-Google-Original-From header

2023-12-22 Thread Steffen Nurpmeso via Postfix-users
Hallo. Lars Kollstedt via Postfix-users wrote in <5d6f30a5-9401-47e7-90a9-627bd6447...@man-da.de>: |on 18.12.23 um 23:15 Steffen Nurpmeso wrote via Postfix-users: |>|> X-Google-Original-From:nicho...@mordor.saundersconsulting.tech |>| |>|By Google. Exactly what their algorithm is for it is no

[pfx] Re: Postfix stopped logging lines with sender IP addresses after upgrade

2024-01-02 Thread Steffen Nurpmeso via Postfix-users
A. Schulze via Postfix-users wrote in <8c5873ea-137e-4938-8b77-2194fd757...@andreasschulze.de>: |Am 02.01.24 um 20:44 schrieb Vince Heuser via Postfix-users: |> smtp   inet  n   -   y   -   -   smtpd | |Hi, | |the smtp server run chroot. You need to configure syslog t

[pfx] milter: how about a SMFIP_NOQUIT?

2024-01-30 Thread Steffen Nurpmeso via Postfix-users
Hello. I am currently writing my first ever milter, a yet postfix-only DKIM sign-only one. I want to do "that" (well: actually DKIM, not milter) for years but could not because i had "no I-M-F aka RFC 822/2822/5322 parser of acceptable quality". That has changed (quite a bit), but i will

[pfx] Re: milter: how about a SMFIP_NOQUIT?

2024-01-31 Thread Steffen Nurpmeso via Postfix-users
Wietse Venema via Postfix-users wrote in <4tpmnz1dqyzj...@spike.porcupine.org>: |Postfix has to be compatible with libmilter, the reference |implementation from Sendmail. It absolutely makes no sends for me |to unilaterally add features. If you wish to propose libmilter API |changes, such as c

[pfx] Re: Are multiple white spaces allowed in a date in headers?

2024-01-31 Thread Steffen Nurpmeso via Postfix-users
Michael Storz via Postfix-users wrote in <0cf37c59789c8be39a442926261d2...@lrz.de>: |Am 2024-01-31 15:09, schrieb David Bürgin via Postfix-users: |> Michael Storz: |>> FWS =   ([*WSP CRLF] 1*WSP) /  obs-FWS |>> |>> A FWS can be a single WSP or a folded line. |>> |>> Therefore

[pfx] milter8.c: please support SMFIC_QUIT_NC (Was: Re: milter: how about a SMFIP_NOQUIT?)

2024-01-31 Thread Steffen Nurpmeso via Postfix-users
postfix-users@postfix.org wrote in <20240131155624.ga51...@veps.esmtp.org>: |> SMFIP_NOQUIT would |> be a good protocol extension in general | |"Use the source, Luke." | |You mean something like |SMFIC_QUIT_NC |? I did, i have that symbol (like MDS256..), yes. So maybe, yes. This is one

[pfx] Re: milter: how about a SMFIP_NOQUIT?

2024-01-31 Thread Steffen Nurpmeso via Postfix-users
Wietse Venema via Postfix-users wrote in <4tq7t76ypkzj...@spike.porcupine.org>: |Claus Assmann via Postfix-users: |>> SMFIP_NOQUIT would |>> be a good protocol extension in general |> |> "Use the source, Luke." |> |> You mean something like |> SMFIC_QUIT_NC |> ? | |And... Postfix 'kn

[pfx] Re: milter: how about a SMFIP_NOQUIT?

2024-01-31 Thread Steffen Nurpmeso via Postfix-users
Wietse Venema via Postfix-users wrote in <4tqc213rcwzj...@spike.porcupine.org>: |So you're suggesting that as long as an MTA-to Milter connection |is not in an error state, sending | |SMFIC_QUIT_NC | |and later sending | |SMTIC_CONNECT | |are sufficient to make a Milter fully f

[pfx] Re: milter: how about a SMFIP_NOQUIT?

2024-01-31 Thread Steffen Nurpmeso via Postfix-users
Steffen Nurpmeso wrote in <20240131203248.XtHi_6Do@steffen%sdaoden.eu>: |Wietse Venema via Postfix-users wrote in | <4tqc213rcwzj...@spike.porcupine.org>: ||So you're suggesting that as long as an MTA-to Milter connection ||is not in an error state, sending || ||SMFIC_QUIT_NC || ||and

[pfx] Re: milter: how about a SMFIP_NOQUIT?

2024-01-31 Thread Steffen Nurpmeso via Postfix-users
Wietse Venema via Postfix-users wrote in <4tqfyk4qzqzj...@spike.porcupine.org>: |Steffen Nurpmeso via Postfix-users: |> Wietse Venema via Postfix-users wrote in |> <4tqc213rcwzj...@spike.porcupine.org>: |>|So you're suggesting that as long as an MTA-to Milter c

[pfx] Re: milter: how about a SMFIP_NOQUIT?

2024-02-01 Thread Steffen Nurpmeso via Postfix-users
Wietse Venema via Postfix-users wrote in <4tqkyr4p2zzj...@spike.porcupine.org>: |Looks like there is sufficient basis to make SMTPD_QUIT_NC rerquests |thts from Postfix. Just need to figure out how to enable/disable |this particular command based on the Postfix and Milter protocol |versions. T

[pfx] Re: postscreen segfault since 3.8.4

2024-02-05 Thread Steffen Nurpmeso via Postfix-users
Christophe Kalt via Postfix-users wrote in : |no crash over the past day, so something must indeed be off with the |packages, disappointing, oh well. On the bright side, I no longer depend on |these getting updated. There were often problems with the -s they use. Especially before they starte

[pfx] Re: Potential bug in milter interface, can't change first header field

2024-02-21 Thread Steffen Nurpmeso via Postfix-users
Taco de Wolff via Postfix-users wrote in : |While writing a milter for use with Postfix, I was unable to change the |first header field and instead of changing it, Postfix appends it to the |end of the header. Incidentally, as I believed this was a bug with the insheader with index 0 worked fo

[pfx] Re: Potential bug in milter interface, can't change first header field

2024-02-21 Thread Steffen Nurpmeso via Postfix-users
Taco de Wolff via Postfix-users wrote in : |Thanks Wietse and Steffen, I forgot to mention that I'm using Postfix |3.5.8, but it appears the bug is thus still present in the latest version. |Looking forward to the fix :-) | |@Steffen, that is genius and hadn't thought of it. I can confirm tha

[pfx] Re: success! Re: Re: removing Authentication-Results, how?

2024-02-22 Thread Steffen Nurpmeso via Postfix-users
Matus UHLAR - fantomas via Postfix-users wrote in : ... |I can now also say that these milters: | |pyspf-milter |opendkim |opendmarc | |(at least their versions in Debian 12) | |do NOT remove existing Authentication-Results: and thus this ste is |necessary to avoid possible confusion o

[pfx] Re: Configuration Settings for TLS 1.2 and 1.3 with No Weak Ciphers

2024-02-29 Thread Steffen Nurpmeso via Postfix-users
postfix-users@postfix.org wrote in : |On Thu, Feb 29, 2024 at 06:36:09AM -0500, Scott Hollenbeck wrote: | |> Sorry, context is important. This server needs to pass a Payment Card |> Industry (PCI) compliance scan. Their definition of weak: "key lengths of |> less than 112 bits, or else use th

[pfx] Re: Configuration Settings for TLS 1.2 and 1.3 with No Weak Ciphers

2024-03-01 Thread Steffen Nurpmeso via Postfix-users
Viktor Dukhovni via Postfix-users wrote in : |On Fri, Mar 01, 2024 at 12:26:33AM +0100, Steffen Nurpmeso wrote: | |> i still use the |> |> # super modern, forward secrecy TLSv1.2 / TLSv1.3 selection.. |> tls_high_cipherlist = EECDH+AESGCM:EECDH+AES256:EDH+AESGCM:CHACHA20 | |I don't re

[pfx] Escaping of braces {} in configuration (master(5))

2024-03-04 Thread Steffen Nurpmeso via Postfix-users
Hello. Is it possible to escape braces in resource files? I am currently testing an hm early beta of my thing and did lb = { rb = } in main.cf to be able to say dkim-sign unix - n n - - spawn user=_postfix_xlocal argv=/tmp/s-dkim-sign --milter-macro-sign ${lb}daemon_name${rb},sign

[pfx] Re: Escaping of braces {} in configuration (master(5))

2024-03-04 Thread Steffen Nurpmeso via Postfix-users
Wietse Venema via Postfix-users wrote in <4tpc280nhvzj...@spike.porcupine.org>: |Steffen Nurpmeso via Postfix-users: |> Hello. |> |> Is it possible to escape braces in resource files? |> I am currently testing an hm early beta of my thing and did |> |> lb = {

[pfx] Re: Escaping of braces {} in configuration (master(5))

2024-03-04 Thread Steffen Nurpmeso via Postfix-users
Steffen Nurpmeso wrote in <20240305004501.fwAHTulV@steffen%sdaoden.eu>: |Wietse Venema via Postfix-users wrote in | <4tpc280nhvzj...@spike.porcupine.org>: ||Steffen Nurpmeso via Postfix-users: ||> Is it possible to escape braces in resource files? ... ||What happens w

[pfx] Re: Escaping of braces {} in configuration (master(5))

2024-03-04 Thread Steffen Nurpmeso via Postfix-users
Wietse Venema via Postfix-users wrote in <4tpcly5z0dzj...@spike.porcupine.org>: |Steffen Nurpmeso via Postfix-users: |> Steffen Nurpmeso wrote in |> <20240305004501.fwAHTulV@steffen%sdaoden.eu>: |>|Wietse Venema via Postfix-users wrote in |>| <4tpc280n

[pfx] Re: SOLVED: Escaping of braces {} in configuration (master(5))

2024-03-05 Thread Steffen Nurpmeso via Postfix-users
Hello Wietse Venema! Wietse Venema via Postfix-users wrote in <4tq1wl2k2czj...@spike.porcupine.org>: |Wietse Venema via Postfix-users: |> With this in master.cf: |> |> dkim-sign unix - n n - 0 spawn |> user=_postfix_xlocal argv=/tmp/s-dkim-sign |>

[pfx] Re: SOLVED: Escaping of braces {} in configuration (master(5))

2024-03-05 Thread Steffen Nurpmeso via Postfix-users
Steffen Nurpmeso via Postfix-users wrote in <20240306000454.itbj3nHU@steffen%sdaoden.eu>: Authentication-Results: list.sys4.de; dkim=fail header.d=sdaoden.eu; arc=none (Message is not ARC signed); dmarc=none Received: from sdaoden.eu (sdaoden.eu [217.144.132.164]) Why does sys4 fa

[pfx] Re: SOLVED: Escaping of braces {} in configuration (master(5))

2024-03-05 Thread Steffen Nurpmeso via Postfix-users
Steffen Nurpmeso via Postfix-users wrote in <20240306000832.cK3_SjGH@steffen%sdaoden.eu>: |Steffen Nurpmeso via Postfix-users wrote in | <20240306000454.itbj3nHU@steffen%sdaoden.eu>: | | Authentication-Results: list.sys4.de; dkim=fail header.d=sdaoden.eu; | arc=none (Messag

[pfx] Re: SOLVED: Escaping of braces {} in configuration (master(5))

2024-03-06 Thread Steffen Nurpmeso via Postfix-users
Wietse Venema via Postfix-users wrote in <4tqwct4jgczj...@spike.porcupine.org>: |Wietse Venema via Postfix-users: |> The text should have said: |> |> Other command-line arguments |> Specify "{" and "}" around command arguments that must start |> with "{" or that must contain whitespace

[pfx] Re: SOLVED: Escaping of braces {} in configuration (master(5))

2024-03-06 Thread Steffen Nurpmeso via Postfix-users
Wietse Venema via Postfix-users wrote in <4tqh100n6pzj...@spike.porcupine.org>: |Are you trying to say that Postfix represents a multiline message |header as text with \n instead of \r\n? Yes. |That is very well possible. Postfix strips \n and \r\n line terminators |on input, and the MIME pa

[pfx] Re: Milter multiline header formatting

2024-03-06 Thread Steffen Nurpmeso via Postfix-users
Hello Wietse Venema :) Wietse Venema via Postfix-users wrote in <4tqhxw0ksyzj...@spike.porcupine.org>: |Steffen Nurpmeso via Postfix-users: |> Wietse Venema via Postfix-users wrote in |> <4tqh100n6pzj...@spike.porcupine.org>: |>|Are you trying to say that Postfix r

[pfx] Re: Milter multiline header formatting

2024-03-06 Thread Steffen Nurpmeso via Postfix-users
Steffen Nurpmeso via Postfix-users wrote in <20240306193747.mAtzRjYs@steffen%sdaoden.eu>: ... |My milter now treats LF and CR not in a CRLF as real whitespace. |The email i just sent was accepted by Google, this one should also |wrap, and we see what this software does (rspamd is it i

[pfx] Re: SOLVED: Escaping of braces {} in configuration (master(5))

2024-03-06 Thread Steffen Nurpmeso via Postfix-users
Ah, please. Let me please reply to this thread once more, to be sure. (The other did not have folded.) (Pressing thumbs!) --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

[pfx] Short subject (Was Re: ...)

2024-03-06 Thread Steffen Nurpmeso via Postfix-users
Steffen Nurpmeso via Postfix-users wrote in <20240306194657.5KGvOP2Q@steffen%sdaoden.eu>: |Ah, please. |Let me please reply to this thread once more, to be sure. (The |other did not have folded.) |(Pressing thumbs!) That failed. But i replied to that again to a Google account, and

[pfx] Re: SOLVED: Escaping of braces {} in configuration (master(5))

2024-03-06 Thread Steffen Nurpmeso via Postfix-users
A last check. Thank you, postfix-users@. --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) ___ Postfix-users ma

[pfx] Re: SOLVED: Escaping of braces {} in configuration (master(5))

2024-03-06 Thread Steffen Nurpmeso via Postfix-users
Hello. Steffen Nurpmeso via Postfix-users wrote in <20240306195734.nj_iAyWy@steffen%sdaoden.eu>: |A last check. |Thank you, postfix-users@. Authentication-Results: list.sys4.de; dkim=pass header.d=sdaoden.eu; arc=none (Message is not ARC signed); dmarc=none So it seems to me

  1   2   3   >