All the servers I have been able to identify with this kind of log seem to have the same version number. I guess they don't regard this as a problem but more of a "feature" which is used to prevent spam because they are refusing mails when 1 recipient is wrong. What is funny is that on their page, they claim to verify remote servers SMTP compliance while they are not compliant themselves.
I don't think I will bother modifying my configuration for the small amount of people using this kind of server. After all, they are not SMTP compliant, so I don't see much interest in modifying my config while _they_ should modify theirs. In fact, the biggest trouble I had with this issue is automatically reporting to rfc-ignorant.org wrong domains, due to a reject at "MAIL FROM" time. Now that I know that it's not exim's fault and this can be reproduced, I just modified my rfc-ignorant script. On 2/15/2006, "exim-users-request" <[EMAIL PROTECTED]> wrote: >On 2/13/06 6:37 AM, "Philip Hazel" <[EMAIL PROTECTED]> wrote: > >> SMTP<< 220 digest2.cali.co.uk ESMTP server ready (Alligate >> v1.5.11.16-13.2-0.2) >> > >Alligate. http://www.alligate.com > >A pay for anti-spam front end for Windows servers. > >There is no indication I could see on the web site as to what the current >version is. (That is, the problem could be long-solved. It also, of >course, might not be regarded as a problem.) > >For Renaud, the easy solution would seem to be to avoid the random option on >the callout for this domain (as noted in prior messages), since even if a >later version of Alligate "fixes the problem" the site may not want to >upgrade. > >Note that the software has an element of learning, so too much calling out >with bad addresses might make it impossible to send legitimate email to the >domain using it. > -- ## List details at http://www.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://www.exim.org/eximwiki/
