Yahoo Whitelist Requests

Yahoo Applications for White Lists:

URL to request

Mandatory abuse contact information in RIPE region started with phase 1.

RIPE Anti-Abuse 

Phase 1 of ripe-563 "Abuse Contact Management in the RIPE Database" is
now being implemented, as announced on 19 March 2013.

According to ripe-563, all resources allocated or assigned by the RIPE
NCC will need to have an abuse contact email address included in their
RIPE Database registration. During the first six months of
implementation (phase 1), all Local Internet Registries (LIRs) must add
an abuse contact attribute ("abuse-c:") to their LIR's ORGANISATION
object to provide abuse contact information for all of the allocated
address space under their LIR.

Since the initial announcement two weeks ago, we are pleased to report
that 24.8% of the RIPE NCC's allocated IPv4 address space is already
covered with an abuse contact. More statistics will be sent to the RIPE
Anti-Abuse Working Group mailing list.

In phase 1, we will send notifications to LIRs that haven't added abuse
contact information to their LIR's ORGANISATION object. If this
information is not added by the LIR by the end of phase 1, we will
automatically add the LIR's contact email address (which is already
publicly listed at: <https://www.ripe.net/membership/indices/>) as their
abuse contact. LIRs can always change this information as needed.

More information on the implementation plan, including phase 2 (covering
PI space and ASNs) is available on RIPE Labs at:
<https://labs.ripe.net/Members/kranjbar/implementation-details-of-policy-2011-06>

How to add "abuse-c"

An explanation of how to add "abuse-c:" to an LIR's ORGANISATION object
as well as how to fine-tune abuse contact information for
sub-allocations and assignments is outlined here:
<https://labs.ripe.net/Members/denis/creating-and-finding-abuse-contacts-in-the-ripe-database>

Please kindly consider adding abuse contact information as soon as
possible to the ORGANISATION object(s) you control or maintain in the
RIPE Database.

Kind Regards,

Kaveh Ranjbar,
RIPE NCC Database Group Manager

Domains you might have missed

Sometimes the little domains don't get attention.

Here is a short list of revenue generating domains that you should pay attention to.

Domains	Value
me.com	11.12%
frontiernet.net	10.11%
windstream.net	9.30%
cfl.rr.com	8.62%
optonline.net	7.69%
cs.com	6.01%
yahoo.co.uk	5.78%
wi.rr.com	4.01%
neo.rr.com	3.42%
mchsi.com	3.33%
myway.com	2.88%
satx.rr.com	2.83%
yahoo.fr	2.82%
suddenlink.net	2.73%
imonmail.com	2.51%
austin.rr.com	2.22%
hawaiiantel.net	2.22%
ec.rr.com	2.15%
epix.net	1.53%
tds.net	1.29%
centurytel.net	1.28%
embarqmail.com	1.26%
yahoo.co.in	1.25%
wmconnect.com	1.08%
wildblue.net	0.89%
localnet.com	0.84%
copper.net	0.82%

AOL Mail Servers

Inspecting AOL's mail server cluster.

This graph represents the mail servers host names.

65K messages were sent in the period of 10 days.

Not all of AOL mail servers behaved the same, some accepted more emails than others.


All emails were sent from 1 ip address, and all had an equal amounts of mail delivered from them to an equal amount of hostnames MX records for AOL.

MX for aol.com

• hostname : mtain-dg.r1000.mx.aol.com
• IP address: 205.188.146.193

This one mx record above would accept 10% more mail than the other MX records for aol.com

Earthlink is opening up their feedback loop to ESPs.

Earthlink is opening up their feedback loop to ESPs.

To take advantage of this, requests should be sent to fblrequest@abuse.earthlink.net with the following information:

• mail server range(s) (IPs/CIDRs)
• FBL address (where complaints are directed)
• technical contact email
• ESP name and contact info

Everyone has delivery issues

Check out my confirmation email from returnpath.com

It too is not immune to the junk folder.

Why does this matter to you?

If you're in the email delivery space, every piece of email matters.

email delivery rates

It's all about email isn't it?

Here are the current delivery rates of sending mail to the major ISP's.

 NOTE: X axis are number of ips trying to connect and send email.

To undertand the graph a little better I'll explain in a little more detail:


You can tell if you're trying to send SMTP to Earthlink. There is little to no ramping period. They don't throttle you to prevent email traffic. It's either an OK ip address, or a REJECTED ip address.

Yahoo has a ramping period before near 100% acceptance. A very short ramp to 45% success and you're okay to keep sending mail. Then there is a looooong ramp up period. You should adjust your ramping for small increments on messages to send per min. The next plateau to hit is 88% success delivery, and then a shorter ramp to 100% success

The configuration for delivering to each ISP changes as acceptance of emails do. The number of emails per connection, the number of connections per ip, the number of retries per minute, the number of emails per min, and add infinitude.

There is no magical formula for all. A consultant is needed, the likes of a

John Caldwell

www.linkedin.com/in/jacaldwell/ is a good start.






Remember, in order of importance for best delivery:
1. subscriber engagement, time viewing emails(YES!), clicks, opens
2. spam trap hits
3. abuse complaints
4. bounce rates