HELO command rejected

scottu

How can I disable the need for a fully qualified hostname? I am using CDO in an access database, and it is only sending the machine name as hostname.

DocFraggle

scottu You can whitelist the IP of your host running the access database in the mailcow UI

scottu

I added it to the forwarding hosts section, but same error occurs. Is there a different place I need to add it to?

DocFraggle

scottu I added it to the forwarding hosts

This is the way… it should work afaik…

scottu

Here is logs showing it is whitelisted, but still requiring fq hostname

Look up 10.180.1.41 on whitelist, result 200 PERMIT

NOQUEUE: reject: RCPT from unknown[10.180.1.41]: 504 5.5.2 <PRDABSTCRW04>: Helo command rejected: need fully-qualified hostname; from=titleabstract@xxxxx.com to=susnick@xxxxx.com proto=ESMTP helo=<PRDABSTCRW04>

scottu

i removed “,reject_non_fqdn_helo_hostname” from the master.cf configuration file, and it works fine now. Anyway to override this for when i update at some point?

esackbauer

https://docs.mailcow.email/manual-guides/Postfix/u_e-postfix-extra_cf/

a-teece

esackbauer This doesn’t work because the value is defined in master.cf, which overrides main.cf.

We faced the same issue and I’ve logged a bug mailcow/mailcow-dockerizedissues/5830, referencing this little thread.

marshalleq

I’ve finally figured out this issue is causing my AP not to email status updates. Anyone know if there’s an official way to resolve this now? Forwarding host doesn’t work. Thanks.

esackbauer

@marshalleq
https://docs.mailcow.email/manual-guides/Postfix/u_e-postfix-postscreen_whitelist/

marshalleq

Thanks so that’s the official solution and it survives container upgrades? I was thinking for an official solution they would put it in the gui.

Also, just tried it and it doesn’t work. 192.168.43.1/24. permit still gets Helo command rejected: need fully-qualified hostname and it does have a FQDN I checked. So who knows really.

esackbauer

marshalleq and it survives container upgrades?

Yes, thats the reason why it is in official documentation 😉

marshalleq it doesn’t work.

Did you add the IP address also to the forwarding hosts under “Options”?

I can tell you it works for me…