Mark Sapiro writes: > At 05:00 local time this morning my Mailman installation sent password > reminders to 65 comcast.net addresses. Of these, exactly 1 bounced with > > 550 5.1.1 <u...@comcast.net> Account not available (in reply to RCPT TO > command)
OK, so we know Comcast will admit that a user doesn't exist. Is this a personalized list? Maybe Comcast does something different with a multiple recipient RCPT TO that contains multiple invalid users? Also, note that this message, presumably a quote from comcast.net up to the open paren, includes an extended status code whereas the OP's error did not. I wonder if his MTA was actually talking to comcast.net? Maybe somebody gave him a "comcast.com" address by mistake or something like that? ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org