Hi Matus!
I have just found out about the socket and changed it accordingly.
Spamassassin does its job, but amavis refuses the connection. I get the
following error message:
2024-12-24T09:32:42.431446-06:00 axum postfix/amavis/smtp[2894]: connect
to 127.0.0.1[127.0.0.1]:10026: Connection re
I have to correct myself. If I only add the no_milters here, a DKIM
signature is added and the header check also works, it looks like, but
for the body is reported:
127.0.0.1:10025 inet n - n - - smtpd
-o syslog_name=postfix/10025
[ ... ]
-o
receive_override_optio
Steffen Nurpmeso via Postfix-users:
> |If there is demand, then support for that syntax can be added later.
> |Hint: I don't find any instances of such syntax in my email archive.
>
> Oh! That is easy to get, you only need a non-US-ASCII attachment
> filename.
It is not relevant for Postfix.
If your content filter makes chnages to the content then that
invalidates a DKIM signature.
Best practice therefore is to verify signatures before making content
changes, and to add signatures after making content changes.
Wietse
___
Postfix-use
Hi Matus,
As suggested by Wietse and you, I want to add the DKIM signature to
amavis in conjunction with OpenDKIM, but I'm not yet where I need to be
with the configuration.
I manage to get a signature added, but there are problems with the
socket. The following is configured in /etc/opendki
Sorry, for the previous mail. Hit the wrong button!
Here the excerpt from mail.log:
2024-12-24T08:25:12.029798-06:00 axum postfix/submission/smtpd[2060]:
warning: connect to Milter service local:opendkim/opendkim.sock: No such
file or directory
2024-12-24T08:25:12.668707-06:00 axum postfix/sub
Hello,
Postfix logs TLS status details before it logs delivery status details.
...
With plaintext delivery, that first line will not be logged.
I know.
In both cases the logging shows the SMTP client process name and
process ID, and the remote SMTP server name, IP address, and port.
With
On 24.12.24 09:08, Andreas Kuhlen via Postfix-users wrote:
I have to correct myself. If I only add the no_milters here, a DKIM
signature is added and the header check also works, it looks like, but
for the body is reported:
127.0.0.1:10025 inet n - n - - smtpd
-o sysl
Dirk St?cker via Postfix-users:
> Hello,
>
> > Postfix logs TLS status details before it logs delivery status details.
>
> ...
>
> > With plaintext delivery, that first line will not be logged.
>
> I know.
>
> > In both cases the logging shows the SMTP client process name and
> > process ID, a
On Tue, Dec 24, 2024 at 12:33:04PM -0800, Randy Bush via Postfix-users wrote:
> why is the actual mail not transferred. how to debug?
>
> 2024-12-24T20:27:05.074565+00:00 m0 postfix/smtpd[188336]: connect from
> mail-koreacentralazon11023102.outbound.protection.outlook.com[40.107.44.102]
> 2024-
> Randy, I'm disappointed
and i embarrassed. clearly i blew it when creating the new mx target.
i just regenerated it with
m0.rg.net:/home/randy# openssl x509 -in
/etc/letsencrypt/live/m0.rg.net/fullchain.pem -noout -pubkey | openssl pkey
-pubin -outform DER | openssl sha256
SHA2-256(stdin)=
On Tue, Dec 24, 2024 at 09:08:41PM -0800, Randy Bush via Postfix-users wrote:
> > Randy, I'm disappointed
>
> And I embarrassed. clearly I blew it when creating the new mx target.
I am glad you took the friendly jibe in stride.
> > I' like to suggest some serious attention to monitoring
>
> b
On Tue, Dec 24, 2024 at 12:50:04PM +0100, Dirk Stöcker via Postfix-users wrote:
> > Postfix logs TLS status details before it logs delivery status details.
>
> ...
>
> > With plaintext delivery, that first line will not be logged.
>
> I know.
>
> > In both cases the logging shows the SMTP clie
why is the actual mail not transferred. how to debug?
2024-12-24T20:27:05.074565+00:00 m0 postfix/smtpd[188336]: connect from
mail-koreacentralazon11023102.outbound.protection.outlook.com[40.107.44.102]
2024-12-24T20:27:05.482255+00:00 m0 postfix/smtpd[188336]: setting up TLS
connection from
m
> Of course it whined.
> You have a different setting at line 67 that overrides the new setting.
> Remove it.
caught that and did.
still not getting outlook mail
randy
2024-12-24T23:07:05.736325+00:00 m0 postfix/smtpd[1343]: disconnect from
mail-dm6nam10lp2040.outbound.protection.outlook.com[
and without 1.3
2024-12-24T23:09:17.812720+00:00 m0 postfix/smtpd[1379]: connect from
mail-eastasiaazrln102210001.outbound.protection.outlook.com[2a01:111:f403:e400::1]
2024-12-24T23:09:18.164836+00:00 m0 postfix/smtpd[1379]: setting up TLS
connection from
mail-eastasiaazrln102210001.outbound.p
also getting a few of these
2024-12-24T23:19:14.030432+00:00 m0 postfix/smtpd[1414]: connect from
mdpmta-as-1p-177349-txn.sys.comcast.net[96.103.94.54]
2024-12-24T23:19:14.100806+00:00 m0 postfix/smtpd[1414]: setting up TLS
connection from mdpmta-as-1p-177349-txn.sys.comcast.net[96.103.94.54]
20
Randy Bush via Postfix-users:
> > Maybe this will work around the problem:
> > smtpd_tls_protocols = >=TLSv1 !TLSv1.3
>
> because of all the warnings, i `systemctl restart`ed postfix. still whined.
>
> 2024-12-24T21:55:54.219911+00:00 m0 postfix/master[189212]: warning:
> /etc/postfix/main.
Randy Bush via Postfix-users:
> why is the actual mail not transferred. how to debug?
The TLS handshake completes, and then the Microsoft client drops
the connections, before or afte sending the post-handshake EHLO.
This appears to be a bug in the Microsoft TLSv1.3 support.
Maybe this will work
> Maybe this will work around the problem:
> smtpd_tls_protocols = >=TLSv1 !TLSv1.3
because of all the warnings, i `systemctl restart`ed postfix. still whined.
2024-12-24T21:55:54.215806+00:00 m0 postfix/postfix-script[189210]: starting
the Postfix mail system
2024-12-24T21:55:54.219911+00:
fwiw, i tried
smtpd_tls_session_cache_timeout = 0
and
smtpd_tls_session_cache_timeout = ridiculous
both with and without `!TLSv1.3`
no mail transfer
randy
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email
On 2024-12-24 at 18:10:24 UTC-0500 (Tue, 24 Dec 2024 15:10:24 -0800)
Randy Bush via Postfix-users
is rumored to have said:
and without 1.3
[...]
2024-12-24T23:09:18.525130+00:00 m0 postfix/smtpd[1379]: Anonymous TLS
connection established from
mail-eastasiaazrln102210001.outbound.protection
Randy Bush via Postfix-users:
> fwiw, i tried
> smtpd_tls_session_cache_timeout = 0
> and
> smtpd_tls_session_cache_timeout = ridiculous
>
> both with and without `!TLSv1.3`
>
> no mail transfer
This will have to wait until Viktor reads this thread. This
is a failure that happens after t
Bill Cole via Postfix-users:
> On 2024-12-24 at 18:10:24 UTC-0500 (Tue, 24 Dec 2024 15:10:24 -0800)
> Randy Bush via Postfix-users
> is rumored to have said:
>
> > and without 1.3
> >
> [...]
> > 2024-12-24T23:09:18.525130+00:00 m0 postfix/smtpd[1379]: Anonymous TLS
> > connection established fr
joker should be a pretty reliable well configured site, but
2024-12-25T00:41:26.540567+00:00 m0 postfix/smtpd[2063]: connect from
mailout1.joker.csl.de[194.245.148.146]
2024-12-25T00:41:26.771343+00:00 m0 postfix/smtpd[2063]: setting up TLS
connection from mailout1.joker.csl.de[194.245.148.146]
Hello!
Here are my so far unsuccessful attempts to link opendkim with amavis in
order to add or verify the DKIM signature to mails.
_*/etc/opendkim.conf*_
Canonicalization relaxed/simple
Mode sv
SubDomains no
AutoRestart yes
AutoR
26 matches
Mail list logo
