Beiträge von alixxweb

Offenbar trifft tatsächlich keine IP-basierte Ratenlimitierung zu:

Zitat

On 2/10/22 09:56:

Dear Deliverability Support Team,

As you suggested, I just tried again sending a test email to '<mytest>@outlook.com 34h after your last message. Unfortunately, the error is still the same: The email is accepted by your mailserver with 250 2.1.5 but does not get delivered into the inbox/junk folder.

I enclosed the DMARC report that just arrived. It also does not indicate any errors.

I cannot see any error on my end. Also for other big ESPs (gmail.com, yahoo.com, ...) no mail delivery errors are reported by our users.

Vielen Dank! Einige der Themen habe ich schon gesehen. Aber ich denke, es schadet sicherlich nicht, wenn das Problem mehr Öffentlichkeit bekommt. Evtl. bekommen wir ja ein eigenes Unterforum.

Hi,

wir betreiben mittlerweile seit vielen Jahren einen Mailserver. Dieser läuft völlig Problemlos - mit Ausnahme von Mails in Richtung Microsoft.

In unregelmäßigen Abständen gibt es mit dem Mail-Netzwerk von Microsoft Probleme. In der Vergangenheit wurden Mails abgelehnt, mit der Begründung, dass das IP-Netz auf einer Blockliste gelandet sei. In der Regel lässt sich das lösen, indem man einige E-Mails mit dem Postmaster-Support von MS hin- und herschreibt.

Dieses Mal gibt es etwas ganz Neues: E-Mails werden ohne Fehlermeldung angenommen, aber nie ausgeliefert (gibt es dazu ein RFC?).

Da das ganze mittlerweile absurde Züge annimmt, möchte ich in diesem Thema die Konversation mit dem Outlook.com Deliverability Support Team (zu Unterhaltungszwecken) aufzeichnen.

Standardantwort:

Zitat

On 2/8/22 14:22,

WINLV.EDFS.WW.00.EN.MSF.RMD.TS.T01.SPT.00.EM@css.one.microsoft.com wrote:

Dear *human*

Please note that your ticket number is in the subject line of this mail.

45.83.106.*

Note: Errors are unlikely, however, if an error is indicated, please

resubmit the specific IP or IP range.

Thank you,

Outlook.com Deliverability Support

Please do not reply to this message as it is from an unattended

mailbox. Any replies to this email will not be responded to or

forwarded. This service is used for outgoing emails only and cannot

respond to inquiries.

Alles anzeigen

Zitat

Sent : Tuesday, February 8, 2022 1:25:26 PM UTC

To : "WINLV.EDFS.WW.00.EN.MSF.RMD.TS.T01.SPT.00.EM@css.one.microsoft.com"

Subject : [EXTERNAL] Re: Reported deliverability problem to Outlook.com

Dear Outlook.com Deliverability Support,

I hereby confirm that the error persists as initially described. Please

check.

IP: 45.83.106.*

Alles anzeigen

Zitat

On 2/8/22 15:35, Hotmail Sender Support wrote:

Hello,

My name is Chander and I work with the Outlook.com Sender Support Team.

I do not see anything offhand with IP: (45.83.106.*) that would be preventing your mail from reaching our customers.

You may be able to find additional information on common delivery questions at the Outlook.com Postmaster Site found at https://mail.live.com/mail/postmaster.aspx I would like to highlight some key areas that I believe are appropriate to your company.

- Outlook.com has created the Smart Network Data Services (SNDS) program. This is a service that helps legitimate email senders work with their customers and partners to reduce spam originating from their IP. To register, please go to http://postmaster.msn.com/snds/ This program allows a sender to monitor the 'health' of their IPs.

- Monitor user complaints. Outlook.com also has a sender complaint feedback loop program called the Junk Email Reporting Program (JMRP). Enrolment in this free program will benefit you as a sender as it will keep your email lists updated and populated with interested Outlook.com customers. This program will help you to remove those Outlook.com customers who do not want to receive emails from your company. If you are interested in joining this program, please visit https://postmaster.live.com/snds/JMRP.aspx?wa=wsignin1.0.

While using the SNDS tool and enrolment in the JMRP will not allow emails from your mail servers to bypass our filters, these are in place to help legitimate companies deliver their emails to Outlook.com customers.

Apply for IP Certification by Return Path, a Validity Product?

If you are doing all the above and you continue to have deliverability issues, you may wish to consider joining Return Path's IP Certified Mail Program, a third-party program administered by Return Path, a Validity Product. Many legitimate mailers and marketers have qualified and joined this program to improve mail deliverability and decrease email from being filtered to the Junk E-mail Folder. Return Path's IP Certification (https://www.validity.com/products/returnpath/certification/) is the only service to which we subscribe

The troubleshooting steps in this email are recommendations only. Microsoft makes no guarantees that following these steps will guarantee deliverability to MSN, Outlook.com, or Live.com customers.

For more detailed information about best sending practices to Outlook.com users, please review the following white paper: http://download.microsoft.com/…272fb/enhance_deliver.pdf

Sincerely,

Chander

Outlook.com Deliverability Support

Alles anzeigen

Zitat

--- Original Message ---

Sent : Tuesday, February 8, 2022 5:46:24 PM UTC

To : "Hotmail Sender Support"

Subject : Re: [EXTERNAL] Re: Reported deliverability problem to Outlook.com

Hello Chander,

thanks for taking time to carefully review my request. I once again reviewed the sender guidelines and can confirm that technical requirements are met. In particular SPF and DKIM.

However the situation changed:

Emails from the domain I initially reported issues (a.tld) do appear now in the inbox of <mytest>@outlook.com. Thanks for fixing that.

However, emails from other domains (eg. b.tld, c.tld, d.tld, ...) served by the same email server behave now as initially reported when sent to eg. <mytest>@outlook.com: They are accepted with "250 2.1.5" but they neither appear in the mailbox nor in the Junk folder.

I haven't tested the other domains served by our email server, but I suppose that they need the same mitigations that you implemented for a.tld

Logs:

< Logs showing that PR3P193MB0699.EURP193.PROD.OUTLOOK.COM accepted the emails sent to <mytest>@outlook.com from domains listed above with Code 250 2.1.5 >

Alles anzeigen

Zitat

On 2/8/22 20:27, Hotmail Sender Support wrote:

Hello,

My name is Nikitha and I work with the Outlook.com Deliverability Team.

The connection and throttling limitation against your IP (45.83.106.*) has been set to a more appropriate level based on your reputation. Please note that this does not guarantee that your mail will be delivered to a user's inbox, only that it will no longer be subject to the previous thresholds unless your IP/domain reputation degrades (or) until it exceeds its revised thresholds.

The troubleshooting steps in this email are recommendations only. Microsoft makes no guarantees that following these steps will guarantee deliverability to MSN or Outlook.com customers.

For more detailed information about best sending practices to Outlook.com users, please review the following white paper: http://download.microsoft.com/…272fb/enhance_deliver.pdf

I hope that the information I provided you was helpful. You may also find additional information on common delivery questions at the Outlook.com Postmaster site found at http://postmaster.msn.com/

Sincerely,

Nikitha

Outlook.com Deliverability Support

Alles anzeigen

Zitat

Sent : Tuesday, February 8, 2022 10:02:27 PM UTC

To : "Hotmail Sender Support"

Subject : Re: [EXTERNAL] Re: Reported deliverability problem to Outlook.com

Hello,

thanks for looking into our issue. Unfortunately, this also did not solve the issue. I also doubt that any IP-based rate limit applies here, since mails from the domain a.tld (served by the same server) are getting delivered.

I just performed a test from two domains, and the described error persists: Mail is accepted by your end (outlook.com) with 250 2.1.5 but does not get delivered into my test inbox (<mytest>@outlook.com). I would be happy if you could look into it.

Could you trace the mails from the following domains directed to my test inbox (<mytest>@outlook.com)? Maybe you could also check with your collegue Chander and ask what he did, since a.tld faced the same issue earlier today and is now functional.

Logs:

< Logs showing that PR3P193MB0699.EURP193.PROD.OUTLOOK.COM accepted the emails sent to <mytest>@outlook.com from domains listed above with Code 250 2.1.5 >

Alles anzeigen

Zitat

Hello,

My name is Karthikayini and I work with the Outlook.com Deliverability Support Team.

Your IP's [45.83.106.*] has already been mitigated. We request you to try sending emails in the next 24-48 hours and let us know in case you see any errors.

Sincerely,

Karthikayini

Outlook.com Deliverability Support.

Alles anzeigen

Dann bis morgen!

~fc