Bug 9800

Is it still the case today ?

CC: (none) => boklm

It's not still delaying messages, no.  It sounds like if the form in Comment 0 could be filled out by a Mageia sysadmin, it could help prevent this from happening again.

The URL linked to above is only available to persons with a yahoo account. Sounds like a lot of hoops for us to jump through to address configuration stupidity on yahoo's end.

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX

Then if someone could give me the information it asks for, I could fill it in.  While they're not delaying messages now, lately they have been filtering a lot of them as spam.

Status: RESOLVED => REOPENED
Resolution: WONTFIX => (none)

What information does it ask for? (I won't register a yahoo account to check)

Name *

Your role at the company *

Email address *

Company name *

Company website URL *

Company postal address *

Company phone number *

Mailing information for each active mail server *
    IP address, reverse DNS record, and associated domain associated. One mail server entry per line.

Do you use an Email Service Provider (ESP)? *
- We are an ESP sending email for our clients
- No-we send our own email
- Yes

If you do use an ESP, which one?

Do you use dedicated or shared IP addresses? or both? *

Do you sign emails with DomainKeys/DKIM? *
- DomainKeys only
- DKIM only
- Both
- Neither

What type of emails are sent from your IP addresses? *
    Example: marketing, transactional, forum postings, newsletters, personal, other

What subscription process do you use? *
    Example: confirmed/double opt in, single opt in, opt out, co-registration, affiliate marketing, other

How many subscribers do you currently have? *

How many emails do you send each month? *

Privacy Policy URL *

Subscription Form URL *

Do you remove bouncing email addresses from your subscription list? *

When you get an unsubscribe request, how long does it take to remove an email from your list? *
- Within 1 week
- Within 10 days
- Within 1 month
- Longer than 1 month

Additional information

Not everything fits in the choices given, but I'd say:

- First questions to contain your / Mageia's details.
- Mageia postal address:
Registrant Street: 8b rue de la Terrasse
Registrant City:Paris
Registrant Postal Code:75017
Registrant Country:FR
Registrant Phone:+33.614226713

- Maybe give this bug report as "company website";
- Mailing information (reverse DNS is equal to forward DNS unless indicated):
alamut.mageia.org.     212.85.158.146
alamut.mageia.org.     2a02:2178:2:7::2
krampouezh.mageia.org. 95.142.164.207 (reverse: xvm-164-207.ghst.net)
krampouezh.mageia.org. 2001:4b98:dc0:51:216:3eff:fe6b:4ea9 (reverse: xvm6-fe6b-4ea9.ghst.net)

I'm not sure if other servers send email. Might provide a note to that effect under "Additional information", but alamat.* should be the bulk of it all.

- No-we send our own email
- Dedicated IP-addresses
- On signing, that's a bit tricky. We have DKIM on our mailinglists, but not on bugzilla mail for example. Safe answer would be 'Neither'?
- Types of email: Mailing lists, forum notifications, bugzilla notifications
- Subscription process: confirmed/double opt in
- Number of subscribers: I don't know. < 10000?
- How many emails do you send each month: Depends on one's definition. What do they count anyways? Number of unique message-id's, or messages*subscribers? Either way, I don't know the answer. My guess would be between 50000 and 1000000.
- Privacy Policy URL: https://wiki.mageia.org/en/Privacy_policy
- Subscription form URL: https://identity.mageia.org/register / https://ml.mageia.org/l/home
- Remove bouncing email addresses? Yes
- Unsubscribe requests? Within 1 week

I may not be extensive enough here, but this is what I could come up with right now. New servers/IP-addresses, are not up to sysadm's to update IMHO.

Thanks, form filled out and submitted.

Ugh, this is the response I got.  I guess there's nothing else we can do right now.



Hello David,

Thank you for contacting Yahoo. 
 

If you're not the administrator for the mail server(s) affected, we ask that you contact the administrator so they can provide the information needed to effectively troubleshoot the issue.

Without any specific SMTP error message, we're unable to effectively troubleshoot the issue.

Occasionally, interruptions or disruptions in email transmissions over the Internet will render a message undeliverable. While this is very rare, it does happen. If you continue to experience this delivery issue, in order to troubleshoot it, we'd appreciate it if you could provide a full SMTP thread that represents the connection that resulted in the delivery failure.

Provide the following information in your response:

    Detailed description of the problem (including when it started).
    The sending IP(s) affected.
    What types of emails are being sent from the affected IP(s)?
    The output of a manual SMTP test with telnet from your mail server to our servers showing the SMTP conversation leading up to, and including, the rejection message.
        Telnet to this host "mta5.am0.yahoodns.net" (i.e., "telnet mta5.am0.yahoodns.net 25").
    Log messages from your mail server showing which IP you connected to and what responses you got from the remote server at the time you received the failures.

Without the requested information, we'll be unable to investigate the problem.

We look forward to your response and looking in to this further for you.
Regards, 

April
Yahoo Customer Care

I guess if we have problems in the future delivering mail *to* yahoo.com, I can reply to that e-mail with the needed information.  Closing this for now.

Status: REOPENED => RESOLVED
Resolution: (none) => OLD

That response from Yahoo is exceedingly useless indeed. Ah well, at least we tried, and we'll hope there won't be delays in the future.