Wietse:

> Did you build Postfix or OpenDKIM yourself?

I installed them with the xbps package manager on Void Linux (x86_64-musl).

Postfix: https://github.com/void-linux/void-packages/tree/master/srcpkgs/postfix

OpenDKIM: 
https://github.com/void-linux/void-packages/tree/master/srcpkgs/opendkim



Bill & L.P.H:

Oh I'm definitely following an old guide: 
https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-dkim-with-postfix-on-debian-wheezy
 (2014).

My main.cf now reads:

> milter_protocol = 6

But the issue still persists.

If I remove this directive altogether the issue also still occurs.



Andrey & Viktor:

My configuration now reads:

> smtpd_milters = inet:[127.0.0.1]:12301
> non_smtpd_milters = inet:[127.0.0.1]:12301

The warning still shows up, just with a new address:

> postfix/cleanup[20180]: warning: milter inet:[127.0.0.1]:12301: can't read 
> SMFIC_EOH reply packet header: Invalid argument



Thanks all for the debugging help so far.

Best,
Noah Huppert

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Wednesday, February 13, 2019 10:09 AM, Viktor Dukhovni 
<postfix-us...@dukhovni.org> wrote:

> > On Feb 13, 2019, at 9:48 AM, Andrey Repin anrdae...@yandex.ru wrote:
>
> > > > milter_default_action = accept
> > > > smtpd_milters = inet:localhost:12301
> > > > non_smtpd_milters = inet:localhost:12301
> >
> > inet:[localhost]:…
> > Save a roundtrip to DNS server for MX lookup. It's not needed, nor going to 
> > be
> > successful here.
>
> For the record, there are no MX lookups involved in resolving the TCP endpoint
> for a milter. To avoid DNS lookups here, use:
>
> inet:[127.0.0.1]:12301
>
> instead. With hostnames the [] are optional and usually not used. With IPv4
> address literals, the [] are also optional, but preferred. With IPv6, they're
> required:
>
> inet:[::1]:12301
>
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>     Viktor.
>


Reply via email to