Viktor Dukhovni via Postfix-users wrote in
:
|On Sat, Jun 08, 2024 at 07:12:01PM -0400, Wietse Venema via Postfix-users \
|wrote:
|>>|> Jun 7 23:41:16 outwall/smtpd[19222]: warning: run-time library \
|>>|> vs. compile-time header version mismatch: OpenSSL 3.3.0 may not \
|>>|> be
Wietse Venema via Postfix-users wrote in
<4vxyjs1khtzj...@spike.porcupine.org>:
|> ...
|>|> Jun 7 23:41:16 outwall/smtpd[19222]: warning: run-time library \
|>|> vs. compile-time header version mismatch: OpenSSL 3.3.0 may not \
|>|> be compatible with OpenSSL 3.2.0
|> ...
|>|[.]
Jeffrey Walton (who is noloader at gmail) pointed out an
interesting point regarding some postfix log message that can be
seen on AlpineLinux edge (again).
--- Forwarded from Steffen Nurpmeso ---
Date: Sat, 08 Jun 2024 02:44:46 +0200
Author: Steffen Nurpmeso
...
Subject: Re: ssl update needs
Alexander Leidinger via Postfix-users wrote in
:
|Am 2024-05-22 01:22, schrieb Greg Sims via Postfix-users:
|> TLS connection reuse is being used. About 10% of the connections are
|> reused for large volume ISPs. Small volume ISPs do not see connection
|> reuse. I believe this is as
Benny Pedersen via Postfix-users wrote in
:
|Jos Chrispijn via Postfix-users skrev den 2024-05-15 11:25:
|> Can someone explain why bl.spamcop.net reverses the ipv6 ip, thus not
|> recognizing it like postscreen?
This is the usual way to do reverse lookups. RFC 1034 from 1987:
2. Host
Wietse Venema via Postfix-users wrote in
<20240513204918.ga80...@spike.porcupine.org>:
|This discussion seems of-topic for the postfix-users mailing list.
Yes, i apologise, and am silent now.
|If you feel strongly about how email is authenticated, I suggest
|that you join the relevant
postfix-users@postfix.org wrote in
:
|On Sun, May 12, 2024 at 03:59:27AM +0200, Steffen Nurpmeso via Postfix-u\
|sers wrote:
...
|> v0.6.1, 2024-05-12:
|> - Adds the algorithm big_ed-sha256 which effectively is RFC 8463
|> (aka ed25519-sha256), but performs thr
I promise this is the last one.
s-postgray by the end of the *next* week.
Good night!
--- Forwarded from Steffen Nurpmeso ---
Subject: [S-announce] [ANN]ounce of s-dkim-sign v0.6.1
Hello people.
Well here i am indeed back again, to announce
v0.6.1, 2024-05-12:
- Adds the algorithm
Yet another "forward", very unfortunate, sorry!
In short: s-dkim-sign generates *correct* Ed25519 signatures,
despite what your DKIM verifier *may* say.
No new release will happen (now, and due to this, at least).
Steffen Nurpmeso wrote in
<20240509012805.7jdxCPXC@steffen%sdaoden
last usage time cannot be represented are kept, and only (as
many as needed of) those will be garbage collected (unless that is
not enough). I thought that is a good addition.)
Sorry for the inconvience, shall you have downloaded and used
(a ed25519- key with) s-dkim-sign (already).
--- Forwarded fr
Wietse Venema via Postfix-users wrote in
<4vvgyx1yynzj...@spike.porcupine.org>:
|Wietse Venema via Postfix-users:
|> 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
Hello.
I hope it is acceptable to forward this.
Maybe someone finds it of value.
Thank you for postfix, and thank you all. This list gives very
helpful non-fooling information, and i am grateful it exists.
--- Forwarded from Steffen Nurpmeso ---
...
Tonight i finally uploaded the first
Wietse Venema via Postfix-users wrote in
<4vtb9v00wbzj...@spike.porcupine.org>:
|Steffen Nurpmeso via Postfix-users:
|> But one thing is plain, if lines get folded "artificially" to
|> satisfy line length limits, then this is a whitespace
Wietse Venema via Postfix-users wrote in
<4vtlbf3vz0zj...@spike.porcupine.org>:
|Postfix does not store line endings internally, because different
|environments have different line ending conventions (for example
|SMTP has while UNIX has ). Postfix strips line endings
|on input, and adds
John Levine wrote in
<20240430015342.8DF9C89B9BE7@ary.local>:
|It appears that Steffen Nurpmeso via Postfix-users \
|said:
|W> |I did not want to insult you!
|>|In mind i had these canon..py snippets
|>|
|>| def strip_trailing_whitespace(content):
|>|return re.su
Steffen Nurpmeso via Postfix-users wrote in
<20240429215451.hPgOZwzc@steffen%sdaoden.eu>:
|Scott Kitterman via Postfix-users wrote in
| <53d75fd8-e109-4712-ba9c-4ea07aa2b...@kitterman.com>:
||On April 29, 2024 9:27:20 PM UTC, Steffen Nurpmeso via Postfix-users \
|| wrote:
||&g
Wietse Venema via Postfix-users wrote in
<4vstkr2gkhzj...@spike.porcupine.org>:
|Steffen Nurpmeso via Postfix-users:
|> Wietse Venema via Postfix-users wrote in
|> <4vsq5f6q3nzj...@spike.porcupine.org>:
|>|Tim Coote via Postfix-users:
|> ..
|>|>
Scott Kitterman via Postfix-users wrote in
<53d75fd8-e109-4712-ba9c-4ea07aa2b...@kitterman.com>:
|On April 29, 2024 9:27:20 PM UTC, Steffen Nurpmeso via Postfix-users \
| wrote:
|>Tim Coote via Postfix-users wrote in
|> :
...
|>|That’s why I formed a hypothesis that (my) Post
Tim Coote via Postfix-users wrote in
:
|Thanks very much for the detailed response. My original issue was why \
|dkim signatures were failing on some emails from email lists when arriving \
|at my Postfix based domain (postfix-3.4.10-1.fc30.x86_64 - I know it \
|needs updating: and that may
Wietse Venema via Postfix-users wrote in
<4vsq5f6q3nzj...@spike.porcupine.org>:
|Tim Coote via Postfix-users:
..
|> SMTP headers are often 'folded' as they flow through MTAs. The
|> standard approach to folding and unfolding is covered in rfcs 5322
...
|3) Lines that exceed 998 bytes (not
Wietse Venema via Postfix-users wrote in
<4vqwxx2jpbzj...@spike.porcupine.org>:
|> * For smfi_chgheader, filter order is important. Later
|>filters will see the header changes made by earlier ones.
|
|Yes, that is fundamental to the way that the Milter API works. Each
|Milter
Hello.
I am still writing my DKIM signer (or, actually, for over six
weeks, i got distracted and ran away due to header remove code,
and realization that all RFCs written after Y2K seem to introduce
their own syntax rules instead of simply going for *822 or 2045,
etc etc etc; including DKIM :().
Wietse Venema via Postfix-users wrote in
<4vkgxb47fdzj...@spike.porcupine.org>:
|Mr. Peng via Postfix-users:
|> I saw this configuration in our master.cf as follows.
|>
|> What's the difference between the option "smtpd_relay_restrictions" and
|> "smtpd_recipient_restrictions"? In my
Wietse Venema via Postfix-users wrote in
<4trq1c66rlzj...@spike.porcupine.org>:
|Steffen Nurpmeso via Postfix-users:
|> What if i would have multiple smtpd listening on different xy and
|> each needs different settings? Would i need different main.cf's
|> for each of those?
Dan Mahoney via Postfix-users wrote in
<56abb6d4-e690-4f94-aadb-2f646a6d1...@prime.gushi.org>:
|> On Mar 6, 2024, at 16:52, Wietse Venema via Postfix-users @postfix.org> wrote:
|> Alex via Postfix-users:
|>> Hi,
|>> I have a few postfix systems on fedora38 with nearly identical
|>>
Geert Hendrickx via Postfix-users wrote in
:
|On Thu, Mar 07, 2024 at 00:22:31 +0100, Steffen Nurpmeso via Postfix-users \
|wrote:
|> Thanks to the README i got it going with
|>
|> masquerade_domains = $mydomain
|> local_header_rewrite_clients = permit_mynetworks,permit_tls
Wietse Venema via Postfix-users wrote in
<4tqsmy5jfczj...@spike.porcupine.org>:
|Wietse Venema via Postfix-users:
|> Again, Postfix does not store line terminators, not when email comes
|> from UNIX tool with \n, via SMTP with \r\n, or encapsulated as
|> netstrings which uses neither.
|>
Claus Assmann via Postfix-users wrote in
<20240307053606.ga48...@veps.esmtp.org>:
|On Wed, Mar 06, 2024, Wietse Venema via Postfix-users wrote:
|
|>> Again, Postfix does not store line terminators, not when email comes
|>> from UNIX tool with \n, via SMTP with \r\n, or encapsulated as
|>>
Wietse Venema via Postfix-users wrote in
<4tqsmy5jfczj...@spike.porcupine.org>:
|Wietse Venema via Postfix-users:
|> Again, Postfix does not store line terminators, not when email comes
|> from UNIX tool with \n, via SMTP with \r\n, or encapsulated as
|> netstrings which uses neither.
|>
Hello.
One more i just had forgotten. I tried to enable easy
One. Last. Message. Of mine.
And sorry for all this mostly off-topic noise.
Steffen Nurpmeso wrote in
<20240306214948.V5gSjSiU@steffen%sdaoden.eu>:
|Steffen Nurpmeso via Postfix-users wrote in
| <20231030191124.5ou-x%stef...@sdaoden.eu>:
||It seems to me there is not much inte
Steffen Nurpmeso via Postfix-users wrote in
<20231030191124.5ou-x%stef...@sdaoden.eu>:
|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
Steffen Nurpmeso via Postfix-users wrote in
<20240306200252.7CXzMIAH@steffen%sdaoden.eu>:
|Steffen Nurpmeso via Postfix-users wrote in
| <20240306195734.nj_iAyWy@steffen%sdaoden.eu>:
||A last check.
||Thank you, postfix-users@.
I am deeply sorry and am now stopping this,
Hello Scott Kitterman.
Scott Kitterman via Postfix-users wrote in
:
..
|As far as I know, we're doing it mostly correctly I'm dkimpy (see below). \
| It's used in lots of ways that have nothing to do with postfix, so \
|I am strongly inclined to believe it's right or there would have been \
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
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
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
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
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
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
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
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
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
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 sys
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
|>
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
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
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
|>
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
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
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
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
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
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
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
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.
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
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
||
||S
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
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
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
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
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
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
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
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 wh
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
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?
|>
|>
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
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:
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
...
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
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 s
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
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:
|>
|>
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:
||
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
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
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 DKI
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
|> ver
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
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.)
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 pr
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
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 (subm
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
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
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
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
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
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
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.
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
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
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
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
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
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
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
,
setrlimit(2) everywhere, but on top specifics for OpenBSD,
FreeBSD, and Linux.
Thank you, and Ciao! already here.
--- Forwarded from Steffen Nurpmeso ---
Date: Wed, 19 Apr 2023 23:36:06 +0200
...
Hey, and hello,
With "Many Thanks!" to Jens Schleusener and his cron job i start
1 - 100 of 198 matches
Mail list logo
