Apologies for using this as a 'Please contact me' list, but can a postmaster
from AOL please give me a call? Our outbound mail has (again) mysteriously
started getting bounced, even while having a 30-day temporary whitelist on
this server.
Calls to the NOC line receive a fast busy after the automated prompter.
Thus spake Damian Gerow (damian@sentex.net) [17/10/03 11:09]:
Apologies for using this as a 'Please contact me' list, but can a postmaster
from AOL please give me a call? Our outbound mail has (again) mysteriously
started getting bounced, even while having a 30-day temporary whitelist on
this server.Calls to the NOC line receive a fast busy after the automated prompter.
Thanks to AOL for an amazingly quick response. Much appreciated.
I've had so many people over the past few weeks ask me for an update
as to how Email Deliverability Summit II went that I thought I really
ought to at least point to some links, which is exactly what I'm
going to do, in the interest of not taking up list bandwidth.
In short, it was absolutely amazing. Twenty CEOs or other executive
decision-makers from ISPs, spam-filtering companies, and other email
receivers (some of them on this list), and twenty from large email
sending companies, in a room at a roundtable for 8 solid hours - and
we got a *lot* accomplished.
Those accomplishments include the promulgation and announcement of 5
new industry standards for both email senders and receivers (this is
up at http://www.isipp.com/standards.php), the presentation of EDDB -
which is a receivers/senders contact information database (it was
actually Damian's request which reminded me to post about this - EDDB
allows participants to log in and get the appropriate contact
information for the sender or receiver in question - information
about EDDB is at http://www.isipp.com/eddb.php), and the announcement
of a new cross-industry working group - the Email Processing Industry
Alliance (EPIA), which will carry on with the work started at Summits
I and II (if you'd like information about being involved as a
receiver, contact Mark Herrick of RoadRunner at markh@va.rr.com, or
Craig Hughes of SpamAssassin Open Source at craig-hughes@isipp.com;
senders should contact Ian Oxman at oxmani@rappdigital.com).
Finally, ISIPP announced it's upcoming Spam and the Law conference
(http://www.isipp.com/events.php).
I'd also like to take this opportunity to mention that independent of
ISIPP I am working on a new email deliverability product which allows
senders and receivers to preauthorize and prevalidate (and even
preschedule) the senders' legitimate bulk mailings. We're currently
in beta, and I'd welcome any of you to participate in the beta test
(which of course is free, and once we get into commercial production
we expect to offer *deep* discounts to beta testers). Anyone who
would like more information should contact me directly.
Anne
Anne P. Mitchell, Esq.
President & CEO
Institute for Spam and Internet Public Policy
Anne,
Those accomplishments include the promulgation and announcement of 5
new industry standards for both email senders and receivers (this is
up at http://www.isipp.com/standards.php), the presentation of EDDB -
which is a receivers/senders contact information database (it was
This is excellent work!
A question is: how best to proceed?
Email has rather complex dynamics. As Verisign has shown us for the DNS
-- which has arguably simpler dynamics -- small changes can have big and
unexpected effects. Usually those effects are nasty.
Consequently, I am hoping that your group intends to bring these
proposed standards to a venue that does open standards development and
adoption, to ensure that the specifications are subject to broad review
and commentary.
d/
Dave - the problem with basic email is that is has no assured delivery
capabilities or receipt processes. These have always been its failings
relative to commercial transactional messaging and until they are resolved
there is NO hope that email will be usable for anything other than casual
messaging - and if you have any doubts see the ABA's recommendation on email
security and use.
Todd Glassey
Dave - the problem with basic email is that is has no assured delivery
capabilities or receipt processes.
To that end, and to Dave's question (and some I've received off-list)
- these are not particularly *technical* standards - they are
practical standards, having to do more with email industry process
and practice - and while they are framed as ISIPP's standards, they
were formed, refined and adopted unanimously by:
RoadRunner
AOL
Microsoft
Outblaze
SpamAssassin
Cloudmark
Ironport
Everyone.net
MSN/TV
SamSpade
Cyphertrust
Word to the Wise
ReturnPath
Mailshell
MessageFire
MailFrontier
Cable & Wireless
ePrivacyGroup
Cheetahmail
Digital Impact
Yesmail
RappDigital Innovyx
Digital River
Silverpop
Socketware
Atriks and TheMail.com
WhatCounts
Digital Connexxions
e-Dialog
Uptilt
ExactTarget
Captaris
Experian
Acquireweb
SubscriberMail
NetCreations
iVillage
CNET
..and, indeed, many of these orgs have already put them into
practice. They are based on a dialogue between senders and
receivers, in which the senders basically said "tell us what we have
to do to get our mail delivered", the receivers said "this is what
you have to do, and what can we do to help you do that?"..and this is
the result. It's not the law.. but when several of the top ISPs and
spam filters say "do this", senders listen.
Anne