Class AutomatedMailboxName
- Namespace
- MailFathom.Domain.Contacts.Collection
- Assembly
- MailFathom.Domain.dll
Answers whether an address names a machine, a role, or a mailing list's administration rather than a person.
public static class AutomatedMailboxName
- Inheritance
-
AutomatedMailboxName
- Inherited Members
Remarks
This is the half of collection's bounds an owner does not write. A book is worth having because it holds people, and the addresses below are the ones every mailbox receives from without anybody corresponding with them — so leaving them to a configured exclusion list would mean every deployment discovering the same noise and writing the same list against it.
Each of the three rules is anchored in something published rather than in a survey of what senders happen to use.
The role mailboxes are RFC 2142's, which defines them precisely as names a function is reached at rather than
a person, together with mailer-daemon, the name a transport has reported delivery failures under since RFC
821. The list-administration suffixes are the convention RFC 2142 § 5 states for reaching a list's machinery
instead of its readers. The no-reply prefixes are the one rule with no standard behind them, and they are here
because an address that says in its own name that a reply goes nowhere is stating that nobody corresponds with it.
The comparison is on the address's own comparison form, so the rule is the same rule the book matches addresses by
and a sender's casing decides nothing. What the rule costs is stated rather than hidden: a person whose mailbox is
genuinely news@ or sales@ at their own domain is not collected, and an owner who corresponds with them
writes them down instead — which is the safe direction, since a book that is missing somebody is corrected by
recording them and a book full of machines is not corrected at all.
Methods
- Names(EmailAddress)
Answers whether the address names something other than a person to correspond with.