* Steve Holden <st...@holdenweb.com>: > [definitely not urgent] > > OK, how does this look? And if it looks OK, how come I'm still getting > bounced at pythoncraft.com? > > """ Technical details of permanent failure: Google tried to deliver > your message, but it was rejected by the recipient domain. We recommend > contacting the other email provider for further information about the > cause of this error. The error that the other server returned was: 550 > 550 5.1.0 <st...@holdenweb.com>: Sender address rejected: User unknown > in virtual alias table (state 14). """
This looks like the recipient domain does sender address verification and the mailserver for the sender reported "User unknown in virtual alias table" (and maybe that data is old, but cached) st...@holdenweb.com is definitely being valid ( :) ) and (I just tested this) being accepted by every MX host. Thus I'm assuming that the MXes for pythoncraft.com (which are using postfix) cached the negative verification result. The default settings are: address_verify_negative_cache = yes address_verify_negative_expire_time = 3d address_verify_negative_refresh_time = 3h Meaning that it may take up to 3 days for the wrong data to expire. How old is that report (I took the weekend off :) ) -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de _______________________________________________ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
