On Wed, Jul 26, 2017 at 04:22:55PM -0700, Michael wrote:
> You might be going too stringent in that case..
I don't think so. This would allow fred.amazon@ and things that meet
those kinds of use cases, while disallowing amazon@ and amazon.com@.
Note that I don't particularly like this -- years ag
On 7/26/17 5:54 PM, Peter Bowen wrote:
Public certification authorities are allowed to use five mailbox names
when verifying domain control for TLS/SSL certificate issuance. These
are postmaster, hostmaster, webmaster, administrator, and admin.
Meanwhile, new hire Robert Oot was assigned a cor
On Tue, Jul 25, 2017 at 9:59 AM, Kirk MacDonald
wrote:
> In addition to what is mentioned in RFC2142, can anyone offer any resources
> (or "best practices") for what can be considered "restricted" email
> addresses/UIDs for a domain which offers mailbox service to the general
> public? This wou
You might be going too stringent in that case..
For instance, many people create aliases related to the service they are
working with..
Also, a lot of people use 'throwaway' addresses related to the service..
I remember using 'ticketmaster@' once and surprised at how quickly 3rd party
offers came
On Tue, Jul 25, 2017 at 04:59:39PM +, Kirk MacDonald wrote:
> In addition to what is mentioned in RFC2142, can anyone offer any
> resources (or "best practices") for what can be considered "restricted"
> email addresses/UIDs for a domain which offers mailbox service to the
> general public?
In
Not nearly a complete list but somethings that might inspire you, also YMMV
based on your exact needs.
abuse
admin
administration
all
announce
approved
contact
email
events
help
hostmaster
info
information
List-help
Lists
List-subscribe
List-unsubscribe
mailer-daemon
marketing
Moderators
Mods
NoRe
On Tue, 25 Jul 2017 10:49:09 -0700, Brandon Long via mailop
wrote:
>Gmail also restricted all usernames that it's employees used and all
>popular names. More because they figured it would lead to confusion, I
>know the guy who had dave@yahoo and even a decade ago it was nearly useless
>with peop
On common OS names, I have an ISP client who blocks Administrator@ (both in
and out). They claim it reduces a whole load of problems with misconfigured
Exchange / AD servers living on client LANs.
Also make sure messages to abuse@ also feeds into your Abuse dept. as well
as going to your client.
Other things to consider are support/sales/ads or anything that contains
your brand. Guess this depends on whether this is a set of domains that
anyone can sign up for an address on, or whether they own the domain.
Gmail also restricted all usernames that it's employees used and all
popular names
On 17-07-25 09:59 AM, Kirk MacDonald wrote:
In addition to what is mentioned in RFC2142, can anyone offer any resources (or "best practices")
for what can be considered "restricted" email addresses/UIDs for a domain which offers mailbox
service to the general public? This would also be assuming
In addition to what is mentioned in RFC2142, can anyone offer any resources (or
"best practices") for what can be considered "restricted" email addresses/UIDs
for a domain which offers mailbox service to the general public? This would
also be assuming the "restricted" email addresses are otherwi
11 matches
Mail list logo
