Thursday, March 7, 2024, 3:58:26 PM, Viktor Dukhovni via Postfix-users wrote:
> On Thu, Mar 07, 2024 at 01:06:53PM +1100, Phil Biggs via Postfix-users wrote:
>> Today I noticed that, occasionally, I see a syslog message stating "blocked
>> using zen.spamhaus..." but no matching "DNSBL rank
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
> > netstrings which uses neither.
> In headers that Postfix sends to a milter. I may want to
On Wed, Mar 06, 2024 at 07:30:01PM -0500, Christophe Kalt via Postfix-users
wrote:
> Hi,
>
> The two options I've seen for implementing SRS are milter and
> [sender_]canonical_maps but it seems to me that neither are a good fit when
> rewriting the envelope From as they happen early on (smtpd
On Thu, Mar 07, 2024 at 01:06:53PM +1100, Phil Biggs via Postfix-users wrote:
> Today I noticed that, occasionally, I see a syslog message stating "blocked
> using zen.spamhaus..." but no matching "DNSBL rank ..." message.
>
> A couple of examples from the past two days:
>
>
On Wed, Mar 06, 2024 at 07:30:01PM -0500, Christophe Kalt via Postfix-users
wrote:
> The two options I've seen for implementing SRS are milter and
> [sender_]canonical_maps but it seems to me that neither are a good fit when
> rewriting the envelope From as they happen early on (smtpd and
On Wed, Mar 6, 2024 at 8:18 PM Wietse Venema via Postfix-users <
postfix-users@postfix.org> wrote:
> This location in the message flow seems right to me. And we already
> have an example for implementing an address rewriting _classes
> feature. This can even be configured in master.cf if one also
Today I noticed that, occasionally, I see a syslog message stating "blocked
using zen.spamhaus..." but no matching "DNSBL rank ..." message.
A couple of examples from the past two days:
postfix/postscreen 84893 - - CONNECT from [43.157.61.211]:30092 to
[192.168.11.2]:25
postfix/dnsblog
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.
>
> Instead, Postfix generates line terminators upon output, and until
> now they are always
Christophe Kalt via Postfix-users:
> Hi,
>
> The two options I've seen for implementing SRS are milter and
> [sender_]canonical_maps but it seems to me that neither are a good fit when
> rewriting the envelope From as they happen early on (smtpd and cleanup
> specifically) and before Postfix
> On Mar 6, 2024, at 16:52, Wietse Venema via Postfix-users
> wrote:
>
> Alex via Postfix-users:
>> Hi,
>> I have a few postfix systems on fedora38 with nearly identical
>> configurations. I'd like to be able to push changes to them from a third
>> system without having to login to them
Alex via Postfix-users:
> Hi,
> I have a few postfix systems on fedora38 with nearly identical
> configurations. I'd like to be able to push changes to them from a third
> system without having to login to them directly to do so. What's the
> best/most secure way to do this?
>
> For example, I'd
On Wed, Mar 06, 2024 at 07:12:18PM -0500, Alex via Postfix-users wrote:
> I have a few postfix systems on fedora38 with nearly identical
> configurations. I'd like to be able to push changes to them from a third
> system without having to login to them directly to do so. What's the
> best/most
Hi,
The two options I've seen for implementing SRS are milter and
[sender_]canonical_maps but it seems to me that neither are a good fit when
rewriting the envelope From as they happen early on (smtpd and cleanup
specifically) and before Postfix knows where the mail is going.
That's a bit of a
Hi,
I have a few postfix systems on fedora38 with nearly identical
configurations. I'd like to be able to push changes to them from a third
system without having to login to them directly to do so. What's the
best/most secure way to do this?
For example, I'd like to push the recipient access file
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 interest of mail
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
|long, but
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, but somehow the
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 the ML
On March 6, 2024 7:37:47 PM UTC, Steffen Nurpmeso via Postfix-users
wrote:
>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
> |>
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
Google
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 think).
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 represents a multiline
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
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
Are you trying to say that Postfix represents a multiline message
header as text with \n instead of \r\n?
That is very well possible. Postfix strips \n and \r\n line terminators
on input, and the MIME parser synthesizes multiline headers with
\n boundaries thusly, before they are sent to
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
Alan Munday:
> As of the 22 Feb 2024 I have been seeing invalid MAIL FROM address from
> Microsoft:
>
> In: MAIL FROM: XATTRDIRECT=Originating
> XATTRORGID=xorgid:96f9e21d-a1c4-44a3-99e4-37191ac61848
Wietse:
> When I send the above as one line into Postfix, the response is:
>
> 555
Alan Munday via Postfix-users:
> As of the 22 Feb 2024 I have been seeing invalid MAIL FROM address from
> Microsoft:
>
> In: MAIL FROM: XATTRDIRECT=Originating
> XATTRORGID=xorgid:96f9e21d-a1c4-44a3-99e4-37191ac61848
>
> Clearly an issue with line termination, but one I have yet to find
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 (Postfix 3.0 and
> later). These outer "{" and "}" are removed from the
As of the 22 Feb 2024 I have been seeing invalid MAIL FROM address from
Microsoft:
In: MAIL FROM: XATTRDIRECT=Originating
XATTRORGID=xorgid:96f9e21d-a1c4-44a3-99e4-37191ac61848
Clearly an issue with line termination, but one I have yet to find
reported online.
I have seen a couple
> From: Ralph Seichter via Postfix-users
>
> I heartily recommend milter-regex [1]. It serves me well by allowing me
> to configure all kinds of complex antispam rules.
>
> [1] https://www.benzedrine.ch/milter-regex.html
>
> -Ralph
Thanks Ralph, that looks interesting and it's even Swiss made
35 matches
Mail list logo
