RFC2142 tells you that abuse@ must exist as well. Cheers, D
On Dec 15, 2011, at 4:48 PM, Ted Cabeen wrote: > The only address that MUST exist by the RFCs is [email protected] (RFC > 2821). When we've had an abuse email, it's usually gone to the Systems and > Network team so the user/account causing the problem can be identified. From > there, it's usually passed to Desktop/Customer Support for resolution. > > --Ted > > On 12/15/2011 10:40 AM, Jim Hickstein wrote: >> Who handles your abuse@ mailbox? Where does that >> person/group/organization report into, at the executive level? If >> there's a requirement to publish such a contact, who says so? (ARIN >> comes to mind, but is it from higher up, or does each region have their >> own rules, for IP address space. And for domains?) >> >> Someone asked me what I knew about this, and I realized I didn't know >> much. So I'm polling LOPSA. Googling finds lots of abuse contacts, but >> not so much metadata about them, in particular best practices. (Not >> without needing half a dozen more search terms like "-substance".) >> > _______________________________________________ > Discuss mailing list > [email protected] > https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss > This list provided by the League of Professional System Administrators > http://lopsa.org/ _______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
