> > Guess this is a MailEnable bug, but maybe anyone has the possibility to test > > if this patch helps to workaround the problem. > > This is completely a mailenable bug and should be reported to them. > They are assuming that the sending mta can always send the numeric code as one > byte. in fact, they're probably only doing one read and not checking for > any kind of short read.
Spamd should not be changed to cope with their bugs. People who don't do SMTP or TCP or sockets correctly should receive bug reports, and they should then fix their bugs. Year on year, the number of workarounds for buggy software should decrease, not increase. The same thing is happening with giant mailgateway hosts -- increasingly many of them are ensuring that their their re-attempts come from the same IP address. Greylisting is a fact of life now for them, and these giant operations are learning to cope with following the new thing 451 is used for.
