On Thu, 2025-01-16 at 08:33 -0500, Wietse Venema via Postfix-users
wrote:
> Tobi via Postfix-users:
> > Hi list
> >
> > we have an issue with mail delivery. We use tlspol to tell postfix
> > if
> > mta-sts or DANE should be used for a recipient domain. Now we have
> > the
> > case that a rcpt doma
A. Schulze via Postfix-users:
>
>
> 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 -05
amp;& !valid_hostaddr(domain, DONT_GRIPE))
smtp_tlsrpt_create_wrapper(state, domain);
else
applied to -20250107 but I didn't note any change
- still no warning about a missing tlsrpt socket
- if the socket is present, no tlsrpt data are written to that socket
like it may be related...
Well it did stop the warning message ;-(
This will be fixed in postfix-3.10-20250116. "TLS-Required: no"
support will be next.
Wietse
diff -ur /var/tmp/postfix-3.10-20250105/src/smtp/smtp_connect.c
src/smtp/smtp_connect.c
--- /var/tmp/postfix-3.10-2
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
(authe
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 f
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
Wietse Venema via Postfix-users wrote in
<4yykn31zfkzj...@spike.porcupine.org>:
|Tobi via Postfix-users:
...
|> we have an issue with mail delivery. We use tlspol to tell postfix if
|> mta-sts or DANE should be used for a recipient domain. Now we have the
...
|That would be unexpected. I'm i
On Thu, Jan 16, 2025 at 08:33:39AM -0500, Wietse Venema via Postfix-users wrote:
> > dane-only to postfix in that case. Now it seems that postfix only tries
> > the first MX, sees that there is no TLSA and defers the message.
That's unexpected, because "deferring" a message is what happens only
Tobi via Postfix-users:
> Hi list
>
> we have an issue with mail delivery. We use tlspol to tell postfix if
> mta-sts or DANE should be used for a recipient domain. Now we have the
> case that a rcpt domain has 3 MX records. The first one with prio 0 has
> **no** TLSA records but the other two (pr
Hello Wietse and all others,
Jan 15 21:38:10 butterfly postfix/local[3652656]: 475F8F8AC4C:
to=, relay=local, delay=2.9,
delays=2.9/0.01/0/0, dsn=2.0.0, status=sent (delivered to file: /dev/null)
You want to ADD a recipient with xxx_rcipient_bcc_maps. Done.
Sometimes that added recipient is
Hi list
we have an issue with mail delivery. We use tlspol to tell postfix if
mta-sts or DANE should be used for a recipient domain. Now we have the
case that a rcpt domain has 3 MX records. The first one with prio 0 has
**no** TLSA records but the other two (prio 10 and 20) have proper TLSA
recor
13 matches
Mail list logo
