dkim-dev
[Top] [All Lists]

Re: [dkim-dev] dkim and email list software - potential solution

2009-09-30 03:52:21
Douglas,

Thanks for replying,

On Wednesday 30 September 2009 11:00:26 Douglas Otis wrote:
There are no good solutions.

which do you think is the better^Wleast bad one?

This feature was intended to cause
messages with their signatures damaged or missing to not end up in
someone's mailbox.

odd - this is not mentioned in rfc5016

Any domain making an ADSP discard assertion should
expect the domain will become usable on mailing lists.  Such domains
should be limited to handling transactional emails.

s/usable/unusable/

Unfortunately, this view might lead to more phishing exploits whenever
alternative domains are then used by the same organization.

or just as likely, prevent dkim=discardable on high value domains like irs.gov 
to prevent where staff use email as well as wanting to prevent phishing 
associated with it.

When there is nothing good to be said, perhaps the better choice is to say 
nothing.

sounds saner that suggesting 'no good' ideas.

 Perhaps there should be a standardization for transactional
sub-domains and stringent requirements where ADSP transactions then
become superfluous. Where subdomains like secure, or
signed.somedomain.com versus somedomain.com might be used as a way to
establish a visual convention.

I'm not sure what subdomain protection has to do with intermediaries breaking 
ADSP validation.

-- 
Daniel Black
Infrastructure Administrator
CAcert

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
dkim-dev mailing list
dkim-dev(_at_)mipassoc(_dot_)org
http://mipassoc.org/mailman/listinfo/dkim-dev