Re: [exim] Misleading message "clamd: failed to connect to …

Startseite
Nachricht löschen
Nachricht beantworten
Autor: Jeremy Harris
Datum:  
To: exim-users
Alte Treads: Re: [exim] Misleading message "clamd: failed to connect to 127.0.0.1: couldn't connect to any host: Connection refused" ?
Betreff: Re: [exim] Misleading message "clamd: failed to connect to 127.0.0.1: couldn't connect to any host: Connection refused" ?
On 10/07/14 23:05, Phil Pennock wrote:
> On 2014-07-09 at 11:26 +0200, Marcin Mirosław wrote:
>> W dniu 02.07.2014 03:43, Phil Pennock pisze:
>>> Sorry, that's misleading, yes. What it means is "for the hostname or IP
>>> address given, couldn't connect to any host matching that hostname". If
>>> you had specified "localhost 3310" on an IPv6 system, then it would have
>>> tried 127.0.0.1 and ::1 both before reporting that error.
>>>
>>> So when Exim is working through the list of possible targets, in random
>>> order now, each item is tried in turn; when they're IP addresses instead
>>> of hostnames, then the message is misleading.
>>
>> Should I fill bug for this?
>
> Yes, I think so.
>
> It's not trivial to fix, since the code is "working" and working well,
> and it's reuse of code which is geared for another context (finding a
> mail-server to connect to), but bad diagnostic messages waste human time
> and should count as an issue to be addressed.


Simple change to the message added as attachment to bug 1505.
The issue is whether we're liable to break anyone doing log-parsing,
and how much we care?

The testsuite runs through clean, without any modification.
--
Cheers,
Jeremy