North American Network Operators Group
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: the authors of RFC 2317 have a question for at&t worldnet

  • From: Al Iverson
  • Date: Thu Feb 01 13:23:38 2007
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=iPBidQ3IuHUwwW6JrtXKbY/StWstgW/5J9VrQL0CgZ5At8wTUFhAfAYilKSn415TMO3p3F7zSpQ10c41QCf7UKcD88qPPYC4YYhUO8tw55M+Ygciv7WlCr30D4yqbNQGaJQAMJ/5lgGtxu2oFGiI5lcAG62PLSN7edTHJIZumvQ=

On 2/1/07, Paul Vixie <[email protected]> wrote:

(and btw, if you're going to block inbound e-mail, you need to give senders
some idea of how to get unblocked.  not for fairness, just for practicality.
and this parenthesized paragraph is why i count this screed as not-off-topic.)


Putting on my sender hat, I see that the URL you link to leads one to:
http://www.att.net/general-info/mail_info/block_admin.html

I've had some client issues in the past that have necessitated use of
that process. I have found that AT&T is fairly responsive regarding
sender blocking issues. There are many other ISPs whom I wish were as
good at publishing info and offering a contact channel.

Al Iverson

--
Al Iverson on Spam and Deliverabilty, see http://www.spamresource.com
Message copyright 2007 by Al Iverson. For posts to SPAM-L, permission
is granted only to this lists's owners to redistribute to their sub-
scribers and to archive this message on site(s) under their control.