At http://www.postfix.org/postconf.5.html :
smtpd_reject_unlisted_recipient (default: yes)
Request that the Postfix SMTP server rejects mail for unknown recipient
addresses, even when no explicit reject_unlisted_recipient access restriction
is specified. This prevents the Postfix queue fro
On 5/7/22 13:18, Wietse Venema wrote:
James Feeney:
At http://www.postfix.org/postconf.5.html :
smtpd_reject_unlisted_recipient (default: yes)
Request that the Postfix SMTP server rejects mail for unknown
recipient addresses, even when no explicit reject_unlisted_recipient
access
On 5/10/22 16:47, Wietse Venema wrote:
With this setting, mail will be ACCEPTED when the recipient
address:
Sorry, that is incorrect.
Postfix features of the form "reject_" cannot promise
that a recipient (or sender, client, helo) will be accepted when
their predicate is false.
They can't pro
On 5/11/22 09:56, Wietse Venema wrote:
Please do not reply to the list AND my address.
Ah! I was wondering why I was not being copied directly. My "postfix-users"
mail gets filtered into a separate folder, and I have to go looking there, to see if
there has been a response. Your work-flow
Reading at http://www.postfix.org/MILTER_README.html, and wondering what
results from Postfix interacting with multiple milters, we see, paraphrasing,
in part:
1) There can be more than one Milter application.
2) Milters "are applied in the order [as] specified".
3) "The first Milter applicatio
On 5/23/22 13:51, post...@ptld.com wrote:
Rejects a command is if something in that milter returns a reject response code
like 4xx or 5xx. If dkim runs first before dmarc, and dkim issues a 5xx reject
causing the email to be rejected by postfix, then that's it, ...
Yes, of course. That's not
On 5/24/22 06:09, Matus UHLAR - fantomas wrote:
On 24.05.22 06:38, Wietse Venema wrote:
Hmm... I thought that SPF (and by implication SRS) are concerned
with ENVELOPE addresses?
originally, yes.
I have customer where incoming messages have the
"message was received from external source"
banne
On 5/24/22 03:36, Matus UHLAR - fantomas wrote:
On 23.05.22 19:31, James Feeney wrote:
My understanding has been that a milter can also *modify* a mail message, including both
the message body and the message headers. And then, what version of a mail message will
a subsequent milter &quo
On 5/24/22 08:24, Viktor Dukhovni wrote:
Milters learn about the role of the requesting MTA via a macro. Thus
in the stock master.cf for the submission-related ports:
-o milter_macro_daemon_name=ORIGINATING
Ah! Interesting. Thanks.
Yet note that this term "ORIGINATING" is nowhere to
On 5/25/22 13:36, Wietse Venema wrote:
James Feeney:
Is that what actually happens, between Postfix and a milter,
literally "sending" and "receiving" mail messages, using SMTP? If
anyone actually knows the form of that conversation between Postfix
and a milter, and what
If I am now understanding correctly:
The "smtpd_sasl_auth_enable=yes" configuration parameter for accessing "smtpd
submissions", in master.cf, is *entirely distinct* from the
"smtpd_relay_restrictions = permit_sasl_authenticated" configuration parameter,
which subsequently allows access to
On Tue, 2024-10-22 at 15:30 -0400, Wietse Venema via Postfix-users
wrote:
> James Feeney via Postfix-users:
> > If I am now understanding correctly:
> >
> >
> > The "smtpd_sasl_auth_enable=yes" configuration parameter for
> > accessing "smtpd s
On Tue, 2024-10-22 at 22:23 -0400, Wietse Venema via Postfix-users
wrote:
>
> That is incorrect. Any SMTP client is allowed to send mail to
> Postfix, but RELAYING is restricted with permit_mynetworks,
> permit_sasl_authenticated, and the like.
>
> > And that note in the log message is useless wh
13 matches
Mail list logo
