dkim-filter fails to work if it cannot open a TCP connection to nameserver port DNS
Bug #387171 reported by
Emilio Lucena
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dkim-milter (Ubuntu) |
Confirmed
|
Low
|
Unassigned |
Bug Description
I noticed that when running ubuntu 8.04 Server edition, dkim-filter will work properly if it can not open a TCP connection to the nameserver port DNS. So if, for some reason, your namserver only responds to DNS UDP, you will get an
can't configure DKIM library; continuing
error message. And after that, you will always get an error like:
can't read SMFIC_EOH reply packet header
Maybe dkim-filter should not try to open TCP connection to the nameserver. Instead it should make its queries via UDP.
Changed in dkim-milter (Ubuntu): | |
status: | New → Confirmed |
To post a comment you must log in.
Actually, I meant to say that the dkim-filter will not work properly if ....