Marco d'Itri wrote:
On Apr 29, Niall O'Reilly <niall.oreilly@ucd.ie> wrote:
Yet, I get the following in response to my update request.
abuse-mailbox: Contact for SPAM <abuse@ucd.ie> ***Error: Syntax error in "Contact for SPAM <abuse@ucd.ie>" abuse-mailbox: Contact for other abuse <security@ucd.ie> ***Error: Syntax error in "Contact for other abuse <security@ucd.ie>"
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.
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: remarks: Contact for SPAM abuse-mailbox: abuse@ucd.ie remarks: Contact for other abuse abuse-mailbox: security@ucd.ie Alternately, using the end-of-line comments: abuse-mailbox: abuse@ucd.ie # contact for SPAM reports abuse-mailbox: security@ucd.ie # contact for other abuse As a side issue, we don't really implement a full RFC 2822 parser. E-mail can look like: some.&#$%~.?+mess@example.com "pretty much anything except chr(34) or chr(64)"@ripe.net 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: ^((([A-Z0-9~#$%&'*+=?^_`{|}~/-]+\.)*[A-Z0-9~#$%&'*+=?^_`{|}~/-]+)|("[^"@\\]+"))@([A-Z0-9-]+(\.[A-Z0-9-]+)+)$ -- Shane