On 6/9/25 20:54, Mark Sapiro wrote:
On 6/9/25 05:06, Florian Sukup wrote:
The setup has historic reasons. However I can eliminate reverse.rrr.com completely and replace it by host.xxx.com. Right now reverse.rrr.com has an A-record pointing to the host's ip address.
Eliminating reverse.rrr.com completely and replacing it by host.xxx.com would be good. This will help.
First step is done: I replaced reverse.rrr.com by host.xxx.com the DNS zones of all domain I use. Tomorrow I will have the rDNS record be rewritten by my ISP.
Also if I look up the A record for reverse.rrr.com either locally or at aaron.ns.cloudflare.com there isn't one. This will be moot if you replace reverse.rrr.com with host.xxx.com.
reverse.rrr.com is not the real name ...
What is the output from
postconf -n?alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases append_dot_mydomain = no biff = no compatibility_level = 2 inet_interfaces = all inet_protocols = all local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/var/lib/mailman3/data/postfix_lmtp mailbox_size_limit = 0 message_size_limit = 0 mydestination = localhost, localhost.localdomain, arvak
This needs to include $myhostname
I don't want to receive any emails like ...@host.xxx.com . So I thought removing host.xxx.com from $mydestination is a good idea. Is there any other solution for that?
Florian.