Noah Huppert:
> I have a Postfix send only server setup.
> 
> I am attempting to integrate OpenDKIM to mitigate the possibility of being 
> blacklisted.
> 
> Whenever I send a message I see the following warning in the syslog:
> 
> > postfix/cleanup[19960]: warning: milter inet:localhost:12301: can't read 
> > SMFIC_EOH reply packet header: Invalid argument

Postfix was unable to receive end-of-header packet size, which is
a 32-bit number. On the Postfix side we're talking about code that
has not changed in some 10 years and that is being used world-wide.

Did you build Postfix or OpenDKIM yourself?

        Wietse

static int milter8_read_resp(MILTER8 *milter, int event, unsigned char *command,
                                     ssize_t *data_len)
{
    UINT32_TYPE len;
        ...
    /*
     * Receive the packet length.
     */
    if ((vstream_fread(milter->fp, (void *) &len, UINT32_SIZE))
        != UINT32_SIZE) {
        smfic_name = str_name_code(smfic_table, event);
        msg_warn("milter %s: can't read %s reply packet header: %m",
                 milter->m.name, smfic_name != 0 ?
                 smfic_name : "(unknown MTA event)");


> Messages are still sent by Postfix, however the emails do not appear to have 
> any DKIM related headers in them. I suspect that the warning above indicates 
> that OpenDKIM is not communicating with Postfix correctly and as a result 
> messages are not being signed.
> 
> I setup Postfix to use OpenDKIM in the Postfix main.cf file:
> 
> > milter_protocol = 2
> > milter_default_action = accept
> > smtpd_milters = inet:localhost:12301
> > non_smtpd_milters = inet:localhost:12301
> 
> The output of postconf -n and postconf -Mf are in this GitHub Gist: 
> https://gist.github.com/Noah-Huppert/0e8160dd6a12e0c62292d1c3f5a262b8
> 
> This Gist also contains what I believe to be the relevant OpenDKIM 
> configuration.
> 
> My efforts to debug this issue have mainly been centered around figuring out 
> what the SMFIC_EOH error code means. However I have had no luck. Any help 
> figuring out what this error code means or how to fix this issue would be 
> greatly appreciated.
> 
> Best,
> Noah Huppert
> 

Reply via email to