<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Marco d'Itri wrote: <blockquote cite="mid20050428225505.GB13826@wonderland.linux.it" type="cite"> <pre wrap="">On Apr 29, Niall O'Reilly <a class="moz-txt-link-rfc2396E" href="mailto:niall.oreilly@ucd.ie"><niall.oreilly@ucd.ie></a> wrote: </pre> <blockquote type="cite"> <pre wrap="">Yet, I get the following in response to my update request. abuse-mailbox: Contact for SPAM <a class="moz-txt-link-rfc2396E" href="mailto:abuse@ucd.ie"><abuse@ucd.ie></a> ***Error: Syntax error in "Contact for SPAM <a class="moz-txt-link-rfc2396E" href="mailto:abuse@ucd.ie"><abuse@ucd.ie></a>" abuse-mailbox: Contact for other abuse <a class="moz-txt-link-rfc2396E" href="mailto:security@ucd.ie"><security@ucd.ie></a> ***Error: Syntax error in "Contact for other abuse <a class="moz-txt-link-rfc2396E" href="mailto:security@ucd.ie"><security@ucd.ie></a>" </pre> </blockquote> <pre wrap=""> I suppose that the parser only accepts an addr-spec and not complete addresses with comments. I really really hope that this will not be changed, because the purpose of abuse-mailbox is to help stupid people who write simple-minded autocomplaints scripts, and asking them to implement a full RFC 2822 parser is a recipe for troubles. </pre> </blockquote> That is exactly right. It is possible to use comments to indicate which mailboxes are for which type of abuse, by using the "remarks:" attribute: <tt>remarks: Contact for SPAM abuse-mailbox: <a class="moz-txt-link-abbreviated" href="mailto:abuse@ucd.ie">abuse@ucd.ie</a> remarks: Contact for other abuse abuse-mailbox: <a class="moz-txt-link-abbreviated" href="mailto:security@ucd.ie">security@ucd.ie</a> </tt> Alternately, using the end-of-line comments: <tt>abuse-mailbox: <a class="moz-txt-link-abbreviated" href="mailto:abuse@ucd.ie">abuse@ucd.ie</a> # contact for SPAM reports abuse-mailbox: <a class="moz-txt-link-abbreviated" href="mailto:security@ucd.ie">security@ucd.ie</a> # contact for other abuse </tt> As a side issue, we don't really implement a full RFC 2822 parser. E-mail can look like: <tt><a class="moz-txt-link-abbreviated" href="mailto:some.&#$%~.?+mess@example.com">some.&#$%~.?+mess@example.com</a> "pretty much anything except chr(34) or chr(64)"@ripe.net </tt> We require two names in the part after the '@', because AFAIK there are no TLD's that accept e-mail. The actual rules allow only up to 80 characters, and match this regular expression: <tt>^((([A-Z0-9~#$%&'*+=?^_`{|}~/-]+\.)*[A-Z0-9~#$%&'*+=?^_`{|}~/-]+)|("[^"@\\]+"))@([A-Z0-9-]+(\.[A-Z0-9-]+)+)$</tt> -- Shane </body> </html>