Dear postfix users group,
Sorry if this is the wrong place to ask, or if this is a nonsensical
question.
But it seems to me that discarding the exact end-user device IP from
e-mails sent via any authenticated path is going to be a common scenario
in today's more privacy aware age.
Yet, it
On 2/4/25 4:15 AM, Wietse Venema via Postfix-users wrote:
Ellie via Postfix-users:
The submission configurations as distributed have
smtpd_recipient_restrictions=permit_sasl_authenticated,reject
which will reject mail without SASL login.
Wietse
Thank you so much for the
On 2/3/25 11:56 PM, Wietse Venema via Postfix-users wrote:
master.cf:
submission .. .. .. .. .. .. .. smtpd
-o { header_checks = pcre:{{/^Received:/ IGNORE}} }
...other -o options...
submissions .. .. .. .. .. .. .. smtpd
-o { header_checks = pcre:{{/^Receive
On 2/3/25 11:56 PM, Wietse Venema via Postfix-users wrote:
If this is for messages submitted on port 587 (submission) or 465
(smtps or submissions), then you can simply delete all Received:
message headers, because there shuold be only one.
Thanks so much for your helpful response! I wonder, does
On 2/4/25 2:25 AM, Viktor Dukhovni via Postfix-users wrote:
Though one might want to be prepared to encounter more friction for
outbound mail lacking all upstream Received headers. These tend to
be classed more "spammy".
This made me curious, and I've checked a bunch of incoming mail. Many
m
On 2/4/25 4:50 PM, Wietse Venema via Postfix-users wrote:
Yes you did. You forgot to start line 16 with a space or tab.
Wietse
Oops, how silly, sorry! Okay, I think I got it:
smtp inet n - n - - smtpd
-o smtpd_tls_security_level=encrypt
-o { header_checks=regexp:/etc/postfix/header
On 2/4/25 7:07 PM, Ellie via Postfix-users wrote:
Sorry for me perhaps bugging this again! I pondered how I could possibly
be using the wrong file, but I can't think of anything.
To rule out that pcre is the issue, I installed all versions of pcre and
pcre2 both 16 and 32 that Alpine
On 2/4/25 7:00 PM, Wietse Venema via Postfix-users wrote:
You forgot to "postfix reload", or you edited the wrong master.cf
file.
What is the output from:
postconf -Mf submission/inet
It should show the new header_checks setting.
These master.cf sttings override main.cf so no need to del
On 2/4/25 19:48, Wietse Venema via Postfix-users wrote:
What did Postfox log at 18:06:46 - postfix/submission/smtpd or postfix/smtpd?
Wietse
I sent a test mail to a throwaway account now, and found the according
log entry! The one you wanted was gone since I happened to have reboot
On 2/5/25 12:29 AM, postfix--- via Postfix-users wrote:
I might have misunderstood the point of this as im jumping in late, but
there is both `header_checks` and `smtp_header_checks`.
That seems very promising, I tried to put it into practice right now:
smtp inet n - n - - smtpd
-o smtpd_tls
On 2/5/25 5:57 PM, Wietse Venema via Postfix-users wrote:
The following is now part of Postfix 3.10, which is back in the
code freeze stage.
Thank you so much for working on this, this is amazing!!
Regards,
ell1e
___
Postfix-users mailing list -- p
Thank you so much for the in-depth response!!
On 2/6/25 7:10 PM, Wietse Venema via Postfix-users wrote:
You should not prepend the header with multi-recipient deliveries,
because that is a privacy problem.
I wonder, what happens with your config in this case? Would it omit the
X-Original-To hea
Dear postfix users community,
Sorry for asking another beginner question. I've seen solutions online
for this, but only one with caveats.
One of my setups involves a forwarding SMTP that handles external
domains, that then forwards them to some other internal mailbox on a
different machine.
On 2/6/25 7:10 PM, Wietse Venema via Postfix-users wrote:
You can force this witH;
/etc/postfix/master.cf
relay .. .. .. .. .. .. smtp
flags=O
/etc/postfix/main.cf:
relay_destination_recipient_limit = 1
transport_maps = hash:/etc/postfix/transport
/etc/postfix/transport
14 matches
Mail list logo
