[pfx] Re: mail.log questions

2024-11-20 Thread Wietse Venema via Postfix-users
Hua Y via Postfix-users: > Hello > > I sent a subscribe request to debian-list, and got this info in > mail.log: > > Nov 21 06:05:18 cloud postfix/smtpd[2395479]: connect from > bendel.debian.org[82.195.75.100] > Nov 21 06:05:19 cloud policyd-spf[2395481]: prepend Received-SPF: None > (no SPF

[pfx] mail.log questions

2024-11-20 Thread Hua Y via Postfix-users
Hello I sent a subscribe request to debian-list, and got this info in mail.log: Nov 21 06:05:18 cloud postfix/smtpd[2395479]: connect from bendel.debian.org[82.195.75.100] Nov 21 06:05:19 cloud policyd-spf[2395481]: prepend Received-SPF: None (no SPF record) identity=helo; client-ip=82.195.7

[pfx] Re: Docs: Improve delay_logging_resolution_limit

2024-11-20 Thread Wietse Venema via Postfix-users
Thomas Landauer via Postfix-users: > When setting it to 6, I'm getting this in my logfile: > > > delays=0.12/0.00058/0/0.023 The 0 is consistent with the text that says "delay values below the delay_logging_resolution_limit are logged as 0". The 0.12, 0.023, and 0.00058 have two significant digi

[pfx] Re: from and return-path

2024-11-20 Thread Matus UHLAR - fantomas via Postfix-users
On 20.11.24 11:48, natan via Postfix-users wrote: I have a specific problem - yes, I can solve it with opendmarc and opendkim, and score in spamassassin but that's out of the question - I only need to domain in "return-patch" and "From" for one specific domain and if it's different, then reject

[pfx] Re: from and return-path

2024-11-20 Thread Ralph Seichter via Postfix-users
* natan via Postfix-users: > If @domain.ltd in return-path and from: is dfferend then Reject "non > allowed" That kind of rejection can be realised easily using milter-regex [1]. Simply combine "envfrom" and "header" tests in a custom rule. -Ralph [1] https://www.benzedrine.ch/milter-regex.html

[pfx] Re: from and return-path

2024-11-20 Thread Matus UHLAR - fantomas via Postfix-users
On 20.11.24 11:48, natan via Postfix-users wrote: I have a specific problem - yes, I can solve it with opendmarc and opendkim, and score in spamassassin but that's out of the question - I only need to domain in "return-patch" and "From" for one specific domain and if it's different, then reject

[pfx] from and return-path

2024-11-20 Thread natan via Postfix-users
Hi I have a specific problem - yes, I can solve it with opendmarc and opendkim, and score in spamassassin but that's out of the question - I only need to domain in "return-patch" and "From" for one specific domain and if it's different, then reject. I thought about doing something at the milte

[pfx] Re: from and return-path

2024-11-20 Thread natan via Postfix-users
W dniu 20.11.2024 o 12:53, Matus UHLAR - fantomas via Postfix-users pisze: On 20.11.24 11:48, natan via Postfix-users wrote: I have a specific problem - yes, I can solve it with opendmarc and opendkim, and score in spamassassin but that's out of the question - I only need to domain in "return-p

[pfx] Re: from and return-path

2024-11-20 Thread Ralph Seichter via Postfix-users
* natan via Postfix-users: > > That kind of rejection can be realised easily using milter-regex [1]. > > Simply combine "envfrom" and "header" tests in a custom rule. > > Thenx for replay but this is not for postfix - without corrections and > reinventing the wheel Frankly, you are very wrong. Mi

[pfx] Re: from and return-path

2024-11-20 Thread natan via Postfix-users
W dniu 20.11.2024 o 12:06, Ralph Seichter via Postfix-users pisze: * natan via Postfix-users: If @domain.ltd in return-path and from: is dfferend then Reject "non allowed" That kind of rejection can be realised easily using milter-regex [1]. Simply combine "envfrom" and "header" tests in a cus

[pfx] Docs: Improve delay_logging_resolution_limit

2024-11-20 Thread Thomas Landauer via Postfix-users
Hi, please clarify the following explanation at http://www.postfix.org/postconf.5.html#delay_logging_resolution_limit Large delay values are rounded off to an integral number of seconds; delay values below the delay_logging_resolution_limit are logged as "0", and delay values under 100s are lo

[pfx] Re: Can I log that an smtp sesion is NOT encrypted?

2024-11-20 Thread Bryan K. Walton via Postfix-users
On Tue, Nov 19, 2024 at 04:34:22PM -0500, Wietse Venema wrote: > Bryan K. Walton via Postfix-users: > > are TLS encrypted. But is there a way to log when an smtp session is > > specifically not encrypted? > > main.cf: > smtpd_data_restrictions = warn_if_reject reject_plaintext_session > > Th

[pfx] Re: dns confusion?

2024-11-20 Thread Marvin Renich via Postfix-users
* Randy Bush via Postfix-users [241120 23:52]: > Debian 12 > mail_version = 3.7.11 > unbound > > note third line "hostname mon1.rg.met does not resolve to address > 2001:418:1::35:" > > 2024-11-20T18:41:31.875723+00:00 m0 postfix/postscreen[24315]: CONNECT > from [2001:418:1::35]:51410 to

[pfx] dns confusion?

2024-11-20 Thread Randy Bush via Postfix-users
Debian 12 mail_version = 3.7.11 unbound note third line "hostname mon1.rg.met does not resolve to address 2001:418:1::35:" 2024-11-20T18:41:31.875723+00:00 m0 postfix/postscreen[24315]: CONNECT from [2001:418:1::35]:51410 to [2001:418:3807::22]:25 2024-11-20T18:41:31.875965+00:00 m0 pos

[pfx] Re: dns confusion?

2024-11-20 Thread Randy Bush via Postfix-users
> Your PTR points to a different name. Typo in ".met"? aha! thank you. randy ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org

[pfx] Re: dns confusion?

2024-11-20 Thread Pavel Padamatska via Postfix-users
Your PTR points to a different name. Typo in ".met"? On Wed, Nov 20, 2024 at 11:49 PM Randy Bush via Postfix-users < postfix-users@postfix.org> wrote: > Debian 12 > mail_version = 3.7.11 > unbound > > note third line "hostname mon1.rg.met does not resolve to address > 2001:418:1::35:" > > 202