On 2026-06-08 at 22:01:54 UTC-0400 (Mon, 08 Jun 2026 22:01:54 -0400)
Al <[email protected]>
is rumored to have said:
On 08/06/2026 12:24 pm, Bill Cole via Postfix-users wrote:
On 2026-06-08 at 11:55:03 UTC-0400 (Mon, 08 Jun 2026 11:55:03 -0400)
Al via Postfix-users <[email protected]>
is rumored to have said:
Hi,
I keep getting disabled on [email protected] mailing list. I
have resubscribed many times. Is there a problem with my
configuration? What can I do to fix this?
You need to stop rejecting mail from the list. That could be because
you've chose strict DMARC enforcement, which is incompatible with
most discussion mailing lists.
I am not using DMARC.
That makes the situation less obvious. Examine your logs to find the
rejections, which should give you a hint as to why they are happening.
I am using:
smtpd_recipient_restrictions =
permit_mynetworks,
check_client_access cidr:/usr/local/etc/postfix/client_checks,
An entry in that file which gives an "OK" result for list.sys4.de and/or
45.90.5.195 will prevent rejections of list mail by this restriction
list.
check_sender_access hash:/usr/local/etc/postfix/sender_checks,
check_sender_access hash:/usr/local/etc/postfix/sender_access,
An entry in either of those giving an OK result for
[email protected] will prevent bounces of messages for
this list without generally trusting the whole sending host.
reject_unknown_sender_domain,
Always good.
reject_unknown_reverse_client_hostname,
reject_unknown_client_hostname,
Keep the former, remove the latter. reject_unknown_client_hostname
unfortunately has a lot of false positives.
reject_invalid_helo_hostname,
reject_non_fqdn_helo_hostname,
reject_non_fqdn_hostname,
reject_non_fqdn_sender,
reject_non_fqdn_recipient,
reject_unknown_helo_hostname,
All useful, but be aware that because HELO name checking is expressly
discourage by the relevant RFCs, there's very little diligence of
keeping it always correct.
reject_unknown_reverse_client_hostname,
reject_unknown_client_hostname,
Duplicated above. remove for clarity.
reject_unauth_pipelining,
reject_invalid_hostname,
reject_unauth_destination,
All fine.
reject_unknown_sender_domain,
Duplicated above. remove for clarity.
reject_unknown_recipient_domain,
reject_rbl_client zen.spamhaus.org,
reject_rbl_client psbl.surriel.com,
permit
Can I add something to make sure that postfix.org emails are not
rejected?
See above. Blessing the client host and/or the sender address will do
the trick of shielding postfix-users mail from the
smtpd_recipient_restrictions.
However, the other smtpd_*_restrictions lists may be involved, or there
may be other things in your config causing the issue.
For less uncertain analysis, it would help to have the full "postconf
-nf" output (listing explicitly set non-default configs) and the
relevant log lines reporting the failures.
OR: If you are forwarding the messages from the list to anywhere that
has strict DMARC enforcement: STOP DOING THAT.
I don't forward any of my own emails anywhere, I really like to use
pine email client on the server myself, but this is not for everyone.
What is funny is everyone asked for webmail, but now that I have it
working, everyone wants theirs forwarded. I think I am the only one
using roundcube.
Feel good about getting Roundcube working, your users may one day find
it more attractive than forwarding to Yahoo or other behemoths.
Forwarding to any large mailbox provider is problematic if your users
are on discussion mailing lists like this one or if you fail to catch
spam before forwarding it. Over time the problems with forwarding have
only gotten worse.
--
Bill Cole
[email protected] or [email protected]
(AKA @[email protected] and many *@billmail.scconsult.com
addresses)
Please keep discussion mailing list replies *on-list*
Not Currently Available For Hire
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
