Re: append_dot_mydomain, how to make it work

Viktor / Wietse, Thanks a million for this. It seems to work great in my test lab. I'm going to move it forward on a secondary server before going to prod w/ it. Sean From: owner-postfix-us...@postfix.org on behalf of Viktor Dukhovni Sent: Sunday, January 29,

Re: smtpd_reject_unlisted_recipient and reject_unlisted_recipient behavior

post...@ptld.com: > >> Or does reject_unlisted_recipient get disabled completely > >> when smtpd_reject_unlisted_recipient=no? > > > > You can then use "reject_unlisted_recipient" explicitly at > > the appropriate stage in the recipient restrictions. > > > Okay, I understand why doing any of

Re: smtpd_reject_unlisted_recipient and reject_unlisted_recipient behavior

Or does reject_unlisted_recipient get disabled completely when smtpd_reject_unlisted_recipient=no? You can then use "reject_unlisted_recipient" explicitly at the appropriate stage in the recipient restrictions. Okay, I understand why doing any of this in DATA is bad and I should have

Re: 'queue file write error' in only very specific instances

> On Wed, 1 Feb 2023, Wietse Venema wrote: > > > post...@fongaboo.com: > >> Jan 31 20:06:15 h6lix postfix/smtp[6552]: 7128C4089C: > >> to=, relay=50.75.172.140[50.75.172.140]:25, > >> delay=2.5, delays=0.64/0.01/1.6/0.23, dsn=4.3.0, status=deferred > >> (host 50.75.172.140[50.75.172.140] said:

Re: 'queue file write error' in only very specific instances

So those log snippets are from the logs on 50.75.172.140 (my postfix server). What more might I be looking for? On Wed, 1 Feb 2023, Wietse Venema wrote: post...@fongaboo.com: Jan 31 20:06:15 h6lix postfix/smtp[6552]: 7128C4089C: to=, relay=50.75.172.140[50.75.172.140]:25, delay=2.5,

Re: 'queue file write error' in only very specific instances

post...@fongaboo.com: > Jan 31 20:06:15 h6lix postfix/smtp[6552]: 7128C4089C: > to=, relay=50.75.172.140[50.75.172.140]:25, > delay=2.5, delays=0.64/0.01/1.6/0.23, dsn=4.3.0, status=deferred > (host 50.75.172.140[50.75.172.140] said: 451 4.3.0 Error: queue > file write error (in reply to end of

'queue file write error' in only very specific instances

First off does "queue file write error (in reply to end of DATA command))" indicate a write error on my server, or on the receiver's server? Best I can tell from grepping the logs, this is happening only with two addresses: Feb 1 07:36:36 h6lix postfix/smtp[22140]: 8F6544089C: to=,

Re: how does postfix determine hostnames in 'received' header?

Michael skrev den 2023-02-01 10:50: [1]: i don't like this solution. instead i'd like to configure dnsmasq to return the fully qualified hostname of the DNS server host, but that's OT here... 127.0.0.1 fqdn.example.com fqdn ::1 fqdn.example.com fqdn add nore data in this file for external

Re: how does postfix determine hostnames in 'received' header?

On Tuesday, 31 January 2023 16:25:05 CET, Matus UHLAR - fantomas wrote: do you have local DNS for 10.0.0.2 range? or, do you use dnsmasq? On 01.02.23 10:59, Michael wrote: great guess! :) that was the logical explanation why you would dns name without dots at that place. the host in

Re: how does postfix determine hostnames in 'received' header?

hey, i already solved it. everything is now as i expect it. thanks. greetings...

Re: how does postfix determine hostnames in 'received' header?

matus, On Tuesday, 31 January 2023 16:25:05 CET, Matus UHLAR - fantomas wrote: do you have local DNS for 10.0.0.2 range? or, do you use dnsmasq? great guess! :) the host in question was the local DNS server and returned its internal hostname, totally unknown to me, instead of the fully

Re: how does postfix determine hostnames in 'received' header?

viktor, thank you very much for your input. it helped me to understand the issue and then solve it. since this 'special' host is the local DNS server (dnsmasq), a reverse lookup returned this weird hostname. so i had to add the DNS server to the mailhub's /etc/hosts, and the issue is