It appears that Peter N. M. Hansteen via mailop <[email protected]> said: >Hi, > >My spamtrap harvesting machinery(1) spotted a weird overlong one this >afternoon (times in CEST), to wit: > >[Fri May 09 18:22:04] peter@skapet:~$ grep >ujtvek_baecn8zeukebbwu_yvpj.5ay0q02j3uqj7-jn61h7zh-lw1awg226-...@bsdly.net >/var/log/spamd >May 9 18:09:34 skapet spamd[16683]: (GREY) 54.217.254.187: ><[email protected]> -> ><ujtvek_baecn8zeukebbwu_yvpj.5ay0q02j3uqj7-jn61h7zh-lw1awg226-...@bsdly.net> >May 9 18:09:34 skapet spamd[42482]: new entry 54.217.254.187 from ><[email protected]> to ><ujtvek_baecn8zeukebbwu_yvpj.5ay0q02j3uqj7-jn61h7zh-lw1awg226-...@bsdly.net>, >helo smtpout23.eu.briteverify.com > >I suspect a naive belief in SMTP callbacks(2) is the main cause, so I would >appreciate if anyone here has useful contact info for admins of origindata.com >or briteverify.com to check what their actual story is.
Briteverify is Validity's listwashing service so my guess would either be that they're washing a stupendously cruddy list, or more likely they're testing to see whether the mail domain has a wildcard that accepts ecerything. My MTA has a special listwash mode which says no to long addresses and yes to short ones, regardless of whether they actually exist. That local part is 64 octets which is indeed the maximum that RFC 5321 allows. R's, John _______________________________________________ mailop mailing list [email protected] https://list.mailop.org/listinfo/mailop
