Am 17.01.25 um 15:00 schrieb Florian Piekert via Postfix-users:
I can confirm it works again for me now.
same here, thanks Wietse!
Andreas
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le.
Am 16.01.25 um 21:18 schrieb Wietse Venema via Postfix-users:
diff -ur /var/tmp/postfix-3.10-20250105/src/smtp/smtp_connect.c
src/smtp/smtp_connect.c
--- /var/tmp/postfix-3.10-20250105/src/smtp/smtp_connect.c 2025-01-05
15:09:04.0 -0500
+++ src/smtp/smtp_connect.c 2025-01-16
Am 16.01.25 um 20:56 schrieb A. Schulze via Postfix-users:
Am 16.01.25 um 20:18 schrieb A. Schulze via Postfix-users:
But there is an additional requirement:
- example.ORG receive messages from any senderdomain,
- example.NET should only be reachable for a small set of senderdomains
Am 16.01.25 um 20:18 schrieb A. Schulze via Postfix-users:
But there is an additional requirement:
- example.ORG receive messages from any senderdomain,
- example.NET should only be reachable for a small set of senderdomains
(authenticated by DMARC)
/writing/ the requirement helps...
the
Hello,
I've an MX receiving for example.ORG
Now, this MX should also handle messages for example.NET
that's easy, add it to relay_domains ...
But there is an additional requirement:
- example.ORG receive messages from any senderdomain,
- example.NET should only be reachable for a small set of
Hello,
I'm installing/running any postfix-3.10-* version in a lab environment.
Till -20250103 the TLSRPT-part worked noiseless. But since -20250107
something is broken. My TLSRPT reporting engine no longer receive any data from
postfix.
If I disable the TLSRPT reporting engine, I not even see an
Am 29.12.24 um 06:45 schrieb Ralph Seichter via Postfix-users:
* Steffen Nurpmeso via Postfix-users:
there is this IETF draft which asks for support SMTPS (aka really,
now), that is Implicit TLS via dedicated port for SMTP.
[1] https://datatracker.ietf.org/doc/draft-nurpmeso-smtp-tls-srv/0
Am 01.12.24 um 17:07 schrieb Wietse Venema via Postfix-users:
The remote server announces SMTPUTF8, but Postfix does not request
SMTPUTF8. It is as if the SMTP client has "smtputf8_enable = no".
Hello Wietse,
I don't think it's an SMTPUTF8 issue.
SMTPUTF8 primary handle non-ascii local par
Hello,
The postfix SMTP client can offload TLS to the tlsproxy by setting
"smtp_tls_connection_reuse = yes"
But in this mode, some logging occur always twice:
Nov 15 22:04:29 mta postfix/tlsproxy[27148]: Trusted TLS connection established
to nexthop.example[2001:db8::25]:587: TLSv1.3 with ciph
Benny Pedersen via Postfix-users:
tux ~ # host 45.90.5.195
195.5.90.45.in-addr.arpa domain name pointer list.sys4.de.
mx ~ # host 45.90.5.195
Host 195.5.90.45.in-addr.arpa not found: 2(SERVFAIL)
Hi Benny,
this seems to be a local problem on your side.
But there is probably a glitch on IPv
Am 28.07.24 um 10:03 schrieb Ralph Seichter via Postfix-users:
Yes. The requirement has been specified as early as 1981 in RFC 822, and
in its successors up to and including RFC 5322.
https://datatracker.ietf.org/doc/html/rfc5321#section-4.5.1
5321 btw...
Andreas
__
Am 07.03.24 um 23:06 schrieb postfix--- via Postfix-users:
I have done some research and opendkim is the most recommended, however, other
research states the opendkim has been abandoned by it's maintainers.
well, long story. yes, it //seem// to be abandoned, but you may use it on
production
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 to listen on
/path/to/postfix-chroot/dev/log
(usually /var/spool/postfix/dev/log)
Andreas
__
Am 25.09.23 um 22:11 schrieb Viktor Dukhovni via Postfix-users:
...
So, unfortunate as it may seem, they just increase
opportunities for failure, without adding anything by way of security.
...
Client certificates serve no purpose unless the server requests them and
knows what to do with them.
Hello,
an SMTP Server with strict_mime_encoding_domain=yes blocked some messages
(which was ... unexpected)
# postconf mail_version
mail_version = 3.7.4
# postconf -n
alias_maps =
maillog_file = /dev/stdout
smtpd_recipient_restrictions = defer
strict_mime_encoding_domain = yes
# postconf -M
s
Am 07.03.23 um 20:37 schrieb postfix--- via Postfix-users:
OpenDMARC is segfaulting. That's what 'signal 11' means. Postfix fails to get
an answer to its end-of-body milter call because of the segfault closing the
other end of that socket. That failure results in Postfix sending a 4xx to the
16 matches
Mail list logo