SOLVED

Outgoing emails marked as SPAM and Phishing emails by O365 servers

%3CLINGO-SUB%20id%3D%22lingo-sub-429311%22%20slang%3D%22en-US%22%3EOutgoing%20emails%20marked%20as%20SPAM%20and%20Phishing%20emails%20by%20O365%20servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-429311%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3CBR%20%2F%3E%3CBR%20%2F%3ESince%20yesterday%2C%20all%20outgoing%20emails%20from%20our%20organization%20using%20Office365%20(fully%20cloud)%20are%20being%20flagged%20as%20either%20spam%20or%20phishing%20email%20by%20Microsoft%20Outbound%20email%20servers.%20Due%20to%20this%20our%20Office365%20user%20accounts%20are%20getting%20blocked%20every%20hour.%20We%20tried%20contacting%20Office365%20support%20but%20they%20said%20they%20cannot%20help%20on%20outbound%20email%20spam%20settings%20as%20they%20do%20not%20have%20any%20control%20over%20the%20configurations.%20I%20spend%20more%20than%20an%20hour%20on%20the%20phone%20with%20the%20support%20person%20and%20at%20the%20end%20was%20asked%20to%20send%205%20sample%20emails%20to%20not_junk%40office365microsoft.com%20and%20wait%20for%2048%20hours.%20I%20told%20O365%20support%20that%20each%20user%20who%20is%20blocked%20sends%20around%20100%20emails%20of%20which%20all%20of%20them%20are%20getting%20flagged%20as%20either%20spam%20or%20phishing%20email%2C%20so%20sending%20random%20samples%20will%20not%20help.%20No%20spam%20or%20phishing%20filter%20settings%20have%20been%20changed%20since%20months%20now%20so%20I%20can%20only%20think%20on%20some%20backend%20updates%20done%20by%20O365%20team%20for%20tightening%20the%20spam%20filters.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20am%20not%20sure%20whom%20to%20contact%20or%20escalate%20this%20case%20now%20so%20I%20am%20posting%20it%20in%20this%20group%20to%20everyone%20expecting%20someone%20who%20might%20have%20experienced%20the%20same%20might%20help.%20Any%20help%20to%20resolve%20this%20issue%20will%20be%20much%20appreciated%20as%20our%20users%20are%20unable%20to%20send%20emails.%3CBR%20%2F%3E%3CBR%20%2F%3EThanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-429311%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-430459%22%20slang%3D%22en-US%22%3ERe%3A%20Outgoing%20emails%20marked%20as%20SPAM%20and%20Phishing%20emails%20by%20O365%20servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-430459%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F252899%22%20target%3D%22_blank%22%3E%40ALV_Work%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20issue%20seems%20quite%20strange.%20How%20did%20you%20know%20that%20MS%20Outbound%20servers%20are%20marking%20your%20emails%20as%20Spam.%20Secondly%20I%20hope%20your%20domain%20is%20still%20able%20to%20send%20emails%20to%20other%20domains%2C%20if%20yes...%20could%20you%20share%20a%20message%20header..%20so%20that%20I%20can%20analyze%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-430692%22%20slang%3D%22en-US%22%3ERe%3A%20Outgoing%20emails%20marked%20as%20SPAM%20and%20Phishing%20emails%20by%20O365%20servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-430692%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F165275%22%20target%3D%22_blank%22%3E%40Robin%20Nishad%3C%2FA%3E%20%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20edited%20the%20default%20Outgoing%20Spam%20rule%20to%20copy%20messages%20flagged%20as%20spam%20to%20one%20of%20our%20internal%20email%20addresses.%20I%20have%20pasted%20the%20header%20from%20one%20such%20email%20(apparently%20we%20receive%20almost%20every%20outgoing%20email%20now)%20as%20requested.%20As%20you%20will%20notice%20that%20the%20Spam%20Confidence%20Level%20is%20set%20to%205%20by%20Microsoft%20and%20the%20Phishing%20Level%20to%208%20for%20this%20outgoing%20email%20from%20Office365.%20We%20do%20have%20even%20have%202FA%20enabled%20for%20most%20users%20and%20never%20had%20any%20issue%20till%20yesterday.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EReceived%3A%20from%20AM6PR0602MB3589.eurprd06.prod.outlook.com%3CBR%20%2F%3E(2603%3A10a6%3A208%3Aaa%3A%3A49)%20by%20AM0PR0602MB3585.eurprd06.prod.outlook.com%20with%3CBR%20%2F%3EHTTPS%20via%20AM0PR06CA0072.EURPRD06.PROD.OUTLOOK.COM%3B%20Wed%2C%2010%20Apr%202019%2017%3A13%3A40%3CBR%20%2F%3E%2B0000%3CBR%20%2F%3EReceived%3A%20from%20VI1PR0601CA0005.eurprd06.prod.outlook.com%3CBR%20%2F%3E(2603%3A10a6%3A800%3A1e%3A%3A15)%20by%20AM6PR0602MB3589.eurprd06.prod.outlook.com%3CBR%20%2F%3E(2603%3A10a6%3A209%3Ae%3A%3A26)%20with%20Microsoft%20SMTP%20Server%20(version%3DTLS1_2%2C%3CBR%20%2F%3Ecipher%3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)%20id%2015.20.1771.19%3B%20Wed%2C%2010%20Apr%3CBR%20%2F%3E2019%2017%3A13%3A39%20%2B0000%3CBR%20%2F%3EReceived%3A%20from%20VE1EUR01FT025.eop-EUR01.prod.protection.outlook.com%3CBR%20%2F%3E(2a01%3A111%3Af400%3A7e01%3A%3A209)%20by%20VI1PR0601CA0005.outlook.office365.com%3CBR%20%2F%3E(2603%3A10a6%3A800%3A1e%3A%3A15)%20with%20Microsoft%20SMTP%20Server%20(version%3DTLS1_2%2C%3CBR%20%2F%3Ecipher%3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384)%20id%2015.20.1792.14%20via%20Frontend%3CBR%20%2F%3ETransport%3B%20Wed%2C%2010%20Apr%202019%2017%3A13%3A39%20%2B0000%3CBR%20%2F%3EReceived%3A%20from%20EUR01-HE1-obe.outbound.protection.outlook.com%20(52.101.129.90)%3CBR%20%2F%3Eby%20VE1EUR01FT025.mail.protection.outlook.com%20(10.152.2.232)%20with%20Microsoft%3CBR%20%2F%3ESMTP%20Server%20(version%3DTLS1_2%2C%20cipher%3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384)%20id%3CBR%20%2F%3E15.20.1771.16%20via%20Frontend%20Transport%3B%20Wed%2C%2010%20Apr%202019%2017%3A13%3A38%20%2B0000%3CBR%20%2F%3EReceived%3A%20from%20DB5EUR01FT040.eop-EUR01.prod.protection.outlook.com%3CBR%20%2F%3E(10.152.4.56)%20by%20DB5EUR01TH003.eop-EUR01.prod.protection.outlook.com%3CBR%20%2F%3E(10.152.4.138)%20with%20Microsoft%20SMTP%20Server%20(version%3DTLS1_2%2C%3CBR%20%2F%3Ecipher%3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384)%20id%2015.20.1750.16%3B%20Wed%2C%2010%20Apr%3CBR%20%2F%3E2019%2017%3A10%3A53%20%2B0000%3CBR%20%2F%3EReceived%3A%20from%20EUR02-AM5-obe.outbound.protection.outlook.com%20(52.101.131.59)%3CBR%20%2F%3Eby%20DB5EUR01FT040.mail.protection.outlook.com%20(10.152.5.25)%20with%20Microsoft%3CBR%20%2F%3ESMTP%20Server%20(version%3DTLS1_2%2C%20cipher%3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384)%20id%3CBR%20%2F%3E15.20.1771.16%20via%20Frontend%20Transport%3B%20Wed%2C%2010%20Apr%202019%2017%3A10%3A53%20%2B0000%3CBR%20%2F%3EAuthentication-Results%3A%20spf%3Dnone%20(sender%20IP%20is%20)%3CBR%20%2F%3Esmtp.mailfrom%3Danna.mandia%40gmsuae.com%3B%3CBR%20%2F%3EReceived%3A%20from%20AM0PR0602MB3554.eurprd06.prod.outlook.com%20(52.133.46.17)%20by%3CBR%20%2F%3EAM0PR0602MB3523.eurprd06.prod.outlook.com%20(52.133.49.30)%20with%20Microsoft%20SMTP%3CBR%20%2F%3EServer%20(version%3DTLS1_2%2C%20cipher%3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)%20id%3CBR%20%2F%3E15.20.1792.14%3B%20Wed%2C%2010%20Apr%202019%2017%3A10%3A45%20%2B0000%3CBR%20%2F%3EReceived%3A%20from%20AM0PR0602MB3554.eurprd06.prod.outlook.com%3CBR%20%2F%3E(%5Bfe80%3A%3A9162%3A6e5e%3A65c1%3A9944%5D)%20by%20AM0PR0602MB3554.eurprd06.prod.outlook.com%3CBR%20%2F%3E(%5Bfe80%3A%3A9162%3A6e5e%3A65c1%3A9944%256%5D)%20with%20mapi%20id%2015.20.1771.014%3B%20Wed%2C%2010%20Apr%202019%3CBR%20%2F%3E17%3A10%3A44%20%2B0000%3CBR%20%2F%3EContent-Type%3A%20application%2Fms-tnef%3B%20name%3D%22winmail.dat%22%3CBR%20%2F%3EContent-Transfer-Encoding%3A%20binary%3CBR%20%2F%3EFrom%3A%20Anna%20Mandia%20%3CANNA.MANDIA%3E%3CBR%20%2F%3ETo%3A%20Calum%20Berkley%20%3CCALUMBERKLEY%3E%2C%20%22reservations%40milansuites.com.sa%22%3CBR%20%2F%3E%3CRESERVATIONS%3E%2C%20%22ayman%40milansuites.com.sa%22%3CBR%20%2F%3E%3CAYMAN%3E%2C%20IBIS%20Abu%20Dhabi%20Gate%20FO3%20%3CH6949-FO3%3E%2C%3CBR%20%2F%3ENOVOTEL%20Abu%20Dhabi%20Gate%20RE1%20%3CH6948-RE1%3E%3CBR%20%2F%3ECC%3A%20Paula%20Cercel%20%3CPAULA.CERCEL%3E%2C%20William%20Escondo%3CBR%20%2F%3E%3CWILLIAM.ESCONDO%3E%2C%20Amit%20Dagar%20%3CAMIT.DAGAR%3E%3CBR%20%2F%3ESubject%3A%20FW%3A%20Calum%20Berkley%2FSharqi%2F12%20Apr%20%5BEmail%20Ref.%20%231457448%5D%3CBR%20%2F%3EThread-Topic%3A%20Calum%20Berkley%2FSharqi%2F12%20Apr%20%5BEmail%20Ref.%20%231457448%5D%3CBR%20%2F%3EThread-Index%3A%20AQHU7g3sNf9KY9rzwEKdxrIlBbZyQaYySW2%2BgAAUiICAAtK0IA%3D%3D%3CBR%20%2F%3EDate%3A%20Wed%2C%2010%20Apr%202019%2017%3A10%3A44%20%2B0000%3CBR%20%2F%3EMessage-ID%3A%20%3CAM0PR0602MB35543E59377335E66B1F11119D2E0%3E%3CBR%20%2F%3EReferences%3A%20%3CAM0PR0602MB35549FA31C962DC1097B472A9D2C0%3E%3CBR%20%2F%3E%3CAM0PR0602MB3554B2DF88EFB2AD15FCC0699D2C0%3E%3CBR%20%2F%3E%26lt%3B46AED3F05A1011E9B957005056BF25F3%40focalscope.com%26gt%3B%3CBR%20%2F%3EIn-Reply-To%3A%20%26lt%3B46AED3F05A1011E9B957005056BF25F3%40focalscope.com%26gt%3B%3CBR%20%2F%3EAccept-Language%3A%20en-GB%2C%20en-US%3CBR%20%2F%3EContent-Language%3A%20en-US%3CBR%20%2F%3EX-MS-Has-Attach%3A%20yes%3CBR%20%2F%3EX-MS-Exchange-Organization-SCL%3A%205%3CBR%20%2F%3EX-MS-TNEF-Correlator%3A%20%3CAM0PR0602MB35543E59377335E66B1F11119D2E0%3E%3CBR%20%2F%3EMIME-Version%3A%201.0%3CBR%20%2F%3EX-MS-Exchange-Organization-MessageDirectionality%3A%20Originating%3CBR%20%2F%3EX-MS-Exchange-Organization-AuthSource%3A%20AM0PR0602MB3554.eurprd06.prod.outlook.com%3CBR%20%2F%3EX-MS-Exchange-Organization-AuthAs%3A%20Internal%3CBR%20%2F%3EX-MS-Exchange-Organization-AuthMechanism%3A%2004%3CBR%20%2F%3EX-Originating-IP%3A%20%5B217.164.74.77%5D%3CBR%20%2F%3EX-MS-Exchange-Organization-Network-Message-Id%3A%201516fec6-bb59-4dad-acf3-08d6bdd77816%3CBR%20%2F%3EX-MS-PublicTrafficType%3A%20Email%3CBR%20%2F%3EReturn-Path%3A%20anna.mandia%40gmsuae.com%3CBR%20%2F%3EX-MS-Exchange-Organization-ExpirationStartTime%3A%2010%20Apr%202019%2017%3A10%3A45.0518%3CBR%20%2F%3E(UTC)%3CBR%20%2F%3EX-MS-Exchange-Organization-ExpirationStartTimeReason%3A%20OriginalSubmit%3CBR%20%2F%3EX-MS-Exchange-Organization-ExpirationInterval%3A%202%3A00%3A00%3A00.0000000%3CBR%20%2F%3EX-MS-Exchange-Organization-ExpirationIntervalReason%3A%20OriginalSubmit%3CBR%20%2F%3EX-MS-Office365-Filtering-Correlation-Id%3A%201516fec6-bb59-4dad-acf3-08d6bdd77816%3CBR%20%2F%3EX-Microsoft-Antispam%3A%20BCL%3A0%3BPCL%3A0%3BRULEID%3A(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600139)(711020)(4605104)(2017052603328)(49563074)(7193020)%3BSRVR%3AAM0PR0602MB3523%3BBCL%3A0%3BPCL%3A8%3BRULEID%3A(3031054)(100001)(3032054)(3034054)%3BSRVR%3ADB5EUR01TH003%3B%3CBR%20%2F%3EX-MS-TrafficTypeDiagnostic%3A%3CBR%20%2F%3EAM0PR0602MB3523%3A%7CAM0PR0602MB3523%3A%7CDB5EUR01TH003%3A%7CDB5EUR01TH003%3A%7CDB5EUR01TH003%3A%7CDB5EUR01TH003%3A%7CDB5EUR01TH003%3A%7CDB5EUR01TH003%3A%7CDB5EUR01TH003%3A%7CDB5EUR01TH003%3A%7CDB5EUR01TH003%3A%7CDB5EUR01TH003%3A%7CDB5EUR01TH003%3A%7CDB5EUR01TH003%3A%7CAM6PR0602MB3589%3A%3CBR%20%2F%3EX-MS-Exchange-PUrlCount%3A%203%3CBR%20%2F%3EX-Microsoft-Antispam-PRVS%3A%20%3CAM0PR0602MB352364002DE092CC23D543D69D2E0%3E%3CBR%20%2F%3EX-Forefront-PRVS%3A%2000032065B2%3CBR%20%2F%3EX-Forefront-Antispam-Report%3A%20SFV%3ASPM%3BSFS%3A(10009020)(136003)(39850400004)(396003)(346002)(366004)(376002)(199004)(189003)(9686003)(3846002)(236005)(52536014)(76176011)(4326008)(606006)(66066001)(25786009)(107886003)(102836004)(53546011)(6506007)(26005)(186003)(11346002)(476003)(71190400001)(66574012)(71200400001)(6116002)(790700001)(68736007)(486006)(44832011)(33656002)(5660300002)(5024004)(446003)(14444005)(97736004)(256004)(81156014)(81166006)(2201001)(54906003)(8936002)(8676002)(508600001)(14454004)(110136005)(7696005)(53946003)(2906002)(6306002)(2473003)(413944005)(99286004)(99936001)(316002)(229853002)(74316002)(7736002)(2501003)(105586002)(6436002)(733005)(106356001)(53936002)(55016002)(86362001)(54556002)(54896002)(59010400001)%3BDIR%3AOUT%3BSFP%3A1501%3BSCL%3A5%3BSRVR%3AAM0PR0602MB3523%3BH%3AAM0PR0602MB3554.eurprd06.prod.outlook.com%3BFPR%3A%3BSPF%3ANone%3BLANG%3Aen%3BPTR%3AInfoNoRecords%3BA%3A1%3BMX%3A1%3B%3CBR%20%2F%3EReceived-SPF%3A%20None%20(protection.outlook.com%3A%20gmsuae.com%20does%20not%20designate%3CBR%20%2F%3Epermitted%20sender%20hosts)%3CBR%20%2F%3EX-MS-Exchange-Organization-ExpirationInterval%3A%200%3A04%3A00%3A00.7865921%3CBR%20%2F%3EX-MS-Exchange-Organization-ExpirationIntervalReason%3A%20SpamEngine%3CBR%20%2F%3EX-MS-Exchange-AtpMessageProperties%3A%20sap%3D1%3Bslp%3D1%3B%3CBR%20%2F%3EX-MS-Exchange-Transport-CrossTenantHeadersStamped%3A%20AM0PR0602MB3523%3CBR%20%2F%3EX-MS-Exchange-Transport-CrossTenantHeadersStripped%3A%20DB5EUR01FT040.eop-EUR01.prod.protection.outlook.com%3CBR%20%2F%3EX-MS-Exchange-Organization-ACSExecutionContext%3A%2004%2F10%2F2019%2017%3A10%3A53%3B04%2F10%2F2019%3CBR%20%2F%3E17%3A13%3A38%3B%7B%22SubmissionInfo%22%3A%7B%22SubmissionToken%22%3A%22PFRva2VuIFRva2VuVHlwZT0iU3VibWlzc2lvblRva2VuIiBJZD0iYjAyN2FkZWYtYjM1Yi1lOTExLWIwNzYtOWNkYzcxNTBlYjYyIiBSb2xlPSJTdWJtaXR0ZXIiIEVuZHBvaW50PSJodHRwczovL0hFMVNFVTA0VFAxMDUuZW9wLXNldTA0LnByb2QucHJvdGVjdGlvbi5vdXRsb29rLmNvbS9zb25hcmFwaS8iIFNpZ25hdHVyZT0iRmg4aFlxVGszUkhDTDQ4S0NpK1haNEFWNlRBPSIgLz4%22%2C%22Identity%22%3A%229960c8bc-7008-4852-a218-286be1ec6672%22%7D%7D%3BSC%3BS%3B0%3B04%2F10%2F2019%3CBR%20%2F%3E17%3A13%3A24%3B0%7C0%7C0%7C1%7C%3B%3CBR%20%2F%3EX-EOPAttributedMessage%3A%200%3CBR%20%2F%3EX-OriginatorOrg%3A%20gmsuae.com%3CBR%20%2F%3EX-MS-Exchange-Organization-SafeAttachmentProcessing%3A%3CBR%20%2F%3EX-MS-Exchange-Transport-EndToEndLatency%3A%2000%3A02%3A55.2749479%3CBR%20%2F%3EX-MS-Exchange-Processed-By-BccFoldering%3A%2015.20.1771.000%3CBR%20%2F%3EX-Microsoft-Antispam-Mailbox-Delivery%3A%3CBR%20%2F%3Eucf%3A0%3Bjmr%3A0%3Bex%3A0%3Bauth%3A0%3Bdest%3AI%3BENG%3A(20160513016)(750119)(520011016)(706158)(944506303)(944610083)%3B%3CBR%20%2F%3EX-Microsoft-Antispam-Message-Info%3A%3CBR%20%2F%3EDAPEWkLz3LKrnttMLdcI98FZqSXR7MZz4OAxsAZSkiO6Gu6jwVcQ8UY2dnhlI4Er0hSFzRtjFw1ahUoSQuNcF8JkUWZwJKBsg22Xejcz94WydHdk%2F2gZ33UC9IjWff1BjQEkPJAxGAHyXXRwia3hCxqrFuM4MkRlX3wyAl%2BK67mNK5XXrlbmJta1I4mm2IRumAgmngf4loOkKGF7eNyYO9VBQEImTYKVEimogNG%2FGb1ZyvX%2B%2FKxix7uGzdtR%2F9HQvQ4cvuIkEjoVIivTdX8XgPt0TH6nwFdG%2FkzjpCD4ufYIAb3HxGjsgrIgX7pGgKRgzg6xVOdyFiihOo9Rr1%2BrxrU2%2FFdhsIbuKHPJM66JC02Yld6Fot5bPkNgOSDDYBicG0HxUwsbDMHbuE81ik85yTQrDCAx0lzwH4X6pWWIKzrCpVkclW79BujtKE1oPIb5WoPVj7n%2BWiNIWDC59kEGqYYjX3BArXj3ohDEkRI2NMmfZMt2Sy6h0i6fPpcL%2FYngqxwQ2%2BpfxDnWFJOCt4wNregwhu4gev2eR7CtduQohvInuqvP%2FrO62VOcX96b5HV5kmnTFZlQwr2OnnHNEKI85GXpIn9qvwxwxlS6g8TFl0EWpN4XRc0F0E8LA%2Bk53Qmj%2FZq64uvKj55GIRE9AF4YmodBgxemEV6NdlF8t3xaM2FVEVC3pXGFthJ10VjUWzi2k5oeJSFYVvmHHleLS61IiPLiwic14OtMTvh8TgKTInvvcOuhxFY6SlQLcrIMEgjsF1KaqPtTbkyrdu%2ByY%2BraGdWajsnFM6lM7GETgaX%2Ff90%3D%3C%2FAM0PR0602MB352364002DE092CC23D543D69D2E0%3E%3C%2FAM0PR0602MB35543E59377335E66B1F11119D2E0%3E%3C%2FAM0PR0602MB3554B2DF88EFB2AD15FCC0699D2C0%3E%3C%2FAM0PR0602MB35549FA31C962DC1097B472A9D2C0%3E%3C%2FAM0PR0602MB35543E59377335E66B1F11119D2E0%3E%3C%2FAMIT.DAGAR%3E%3C%2FWILLIAM.ESCONDO%3E%3C%2FPAULA.CERCEL%3E%3C%2FH6948-RE1%3E%3C%2FH6949-FO3%3E%3C%2FAYMAN%3E%3C%2FRESERVATIONS%3E%3C%2FCALUMBERKLEY%3E%3C%2FANNA.MANDIA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-431299%22%20slang%3D%22en-US%22%3ERe%3A%20Outgoing%20emails%20marked%20as%20SPAM%20and%20Phishing%20emails%20by%20O365%20servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-431299%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F252899%22%20target%3D%22_blank%22%3E%40ALV_Work%3C%2FA%3E%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CDIV%3E%3CDIV%3EThis%20is%20the%20typical%20case%20of%20HRDP%2C%20when%20your%20outbound%20emails%20are%20detected%20as%20spam%20and%20EOP%20tries%20to%20deliver%20it%20to%20recipient%20with%20already%20blacklisted%20ip.%3C%2FDIV%3E%3CDIV%3E%3CBR%20%2F%3Esocial.technet.microsoft.%20com%2Fwiki%2Fcontents%2Farticles%2F36402.exchange-online-troubleshooting-high-risk-delivery-pool.aspx%3C%2FDIV%3E%3CDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%3CDIV%3ELooking%20at%20the%20headers%2C%20it%20seems%20that%20EOP%20IP%2052.101.129.90%20is%20on%20blacklist%3CBR%20%2F%3ETry%20to%20delist%20the%20IP%20on%20sender.office.%26nbsp%3Bcom%3C%2FDIV%3E%3CDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%3CDIV%3ESometimes%20your%20tenant%20gets%20assigned%20a%20blacklisted%20IP%20in%20random.%20You%20can%20contact%20O365CloudExperts%20Support%20if%20you%20need%20more%20help.%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3ERegards%2C%3C%2FDIV%3E%3CDIV%3EAkshay%20M%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-431492%22%20slang%3D%22en-US%22%3ERe%3A%20Outgoing%20emails%20marked%20as%20SPAM%20and%20Phishing%20emails%20by%20O365%20servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-431492%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F252899%22%20target%3D%22_blank%22%3E%40ALV_Work%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20noticed%20in%20the%20Message%20Header%20-%26nbsp%3B%3C%2FP%3E%3CTABLE%3E%3CTBODY%3E%3CTR%3E%3CTD%3E%26nbsp%3B%3C%2FTD%3E%3CTD%3E%3CA%20href%3D%22http%3A%2F%2Fgo.microsoft.com%2F%3Flinkid%3D9837881%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EReceived-SPF%3C%2FA%3E%3C%2FTD%3E%3CTD%3ENone%20(protection.outlook.com%3A%20gmsuae.com%20does%20not%20designate%20permitted%20sender%20hosts)%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20would%20suggest%20to%20check%20if%20the%20sender%20domain%20is%20added%20in%20the%20allowed%20domain%20settings%20in%20Security%20and%20Compliance%20center.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1.%20Sign%20in%20to%20O365%20Admin%20Portal%3CBR%20%2F%3E2.%20Navigate%20to%20Security%20%26amp%3B%20Compliance%20center%20%26gt%3B%20Threat%20management%20%26gt%3B%20Policy.%3CBR%20%2F%3E3.%20Find%20Anti-spam%2C%20open%20it.%20Expend%20Allow%20lists.%20Add%20the%20sender%E2%80%99s%20domain%20to%20the%20Allow%20domain%20setting.%3C%2FP%3E%3CP%20class%3D%22x-hidden-focus%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22x-hidden-focus%22%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-431867%22%20slang%3D%22en-US%22%3ERe%3A%20Outgoing%20emails%20marked%20as%20SPAM%20and%20Phishing%20emails%20by%20O365%20servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-431867%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F165275%22%20target%3D%22_blank%22%3E%40Robin%20Nishad%3C%2FA%3E%20%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20the%20suggestion.%20We%20already%20have%20the%20domain%20added%20in%20the%20Allow%20list%20of%20Anti-Spam%20policy.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECould%20it%20be%20that%20the%20domain%20is%20showing%20as%20SPF%20not%20designated%20because%20it%20is%20still%20an%20internal%20email%20within%20Office365%20servers%20%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-432014%22%20slang%3D%22en-US%22%3ERe%3A%20Outgoing%20emails%20marked%20as%20SPAM%20and%20Phishing%20emails%20by%20O365%20servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-432014%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F252899%22%20target%3D%22_blank%22%3E%40ALV_Work%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eif%20the%20Domain%20is%20added%20in%20the%20Allow%20list%2C%20then%20I%20would%20suggest%20to%20submit%20the%20message%20to%20MS%20and%20let%20them%20know%20that%20it%20is%20not%20Spam.%20I%20know%20%26amp%3B%20understand%20that%20you%20are%20already%20working%20with%20MS%20on%20this%20however%20I%20would%20like%20you%20to%20refer%20to%20the%20steps%20given%20in%20the%20below%20article....%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fsecuritycompliance%2Fsubmit-spam-non-spam-and-phishing-scam-messages-to-microsoft-for-analysis%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fsecuritycompliance%2Fsubmit-spam-non-spam-and-phishing-scam-messages-to-microsoft-for-analysis%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E(Submit%20messages%20that%20were%20tagged%20as%20junk%20but%20should%20have%20been%20allowed%20through)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESecondly%20the%20proof%20that%20MS%20Servers%20are%20marking%20your%20email%20as%20Spam%20is%20that%20in%20the%20header%20-%20Anti%20Spam%20Report%20-%20It%20has%20SFV-SPM%20that%20means%20the%20email%20is%20marked%20as%20Spam%20because%20of%20the%20EOP%20Spam%20filters.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EReference%20Article%20-%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2FSecurityCompliance%2Fprevent-email-from-being-marked-as-spam%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2FSecurityCompliance%2Fprevent-email-from-being-marked-as-spam%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMoreover%20do%20check%20if%20the%20emails%20that%20you%20are%20sending%20has%20any%20HTML%20Signatures%20or%20they%20are%20simple%20text.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-439995%22%20slang%3D%22en-US%22%3ERe%3A%20Outgoing%20emails%20marked%20as%20SPAM%20and%20Phishing%20emails%20by%20O365%20servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-439995%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F252899%22%20target%3D%22_blank%22%3E%40ALV_Work%3C%2FA%3E%26nbsp%3BWe%20got%20exactly%20the%20same%20problem%20yesterday%2C%20I%20opened%20a%20ticket%20but%20Microsoft%20seems%20to%20have%20no%20clue%20about%20what%20happened.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20worked%20on%20it%20a%20while%20and%20this%20is%20what%20we%20could%20figure%20out%20about%20our%20case%20%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-%20It%20started%20around%207am%20CET%20and%20ended%20around%208pm%20CET%3C%2FP%3E%3CP%3E-%20It%20has%20nothing%20to%20do%20with%20SPF%20or%20whatever%3C%2FP%3E%3CP%3E-%20EOP%20was%20giving%20a%20SFV%3ASPM%20SCL%3A5%20to%20outbound%20emails%20ONLY%20IF%20they%20were%20replies%20or%20forwards%20to%20external%20email%20addresses%2C%20so%20they%20were%20using%20the%20High%20Risk%20Delivery%20Pool%20and%20we%20were%20getting%20a%20BCC%20in%20our%20IT%20mailbox%20as%20our%20Outbound%20spam%20Policy%20specifies%20it.%20I%20can%20see%20in%20your%20header%20that%20it%20was%20the%20same%20for%20you%20%3A%26nbsp%3B%3CSPAN%3EDIR%3AOUT%3BSFP%3A1501%3BSCL%3A5%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E-%20When%20an%20external%20person%20was%20answering%20one%20on%20these%20emails%20they%20were%20coming%20back%20with%26nbsp%3B%3CSPAN%3ESFV%3ASPM%20and%20CAT%3APHSH%2C%20so%20we%20got%20PLENTY%20of%20emails%20yesterday%20ending%20up%20in%20junk%20folder%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E-%20Every%20Outbound%20Spam%20BCC%20in%20our%20IT%20mailbox%20arrived%20twice%2C%20the%20second%20time%20with%20a%20huge%20delay%20(6%2B%20hours)%2C%20and%20message%20stayed%20in%20%22Getting%20Status%22%20for%20very%20long%20time%20in%20traces%2C%20maybe%20because%20they%20were%20going%20through%20the%20High%20Risk%20Pool.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EWe%20didn't%20make%20any%20changes%20in%20our%20SPF%20or%20policies%2C%20it%20just%20randomly%20happened%20and%20ended.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI'm%20still%20waiting%20for%20an%20explanation%20from%20Microsoft.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-442952%22%20slang%3D%22en-US%22%3ERe%3A%20Outgoing%20emails%20marked%20as%20SPAM%20and%20Phishing%20emails%20by%20O365%20servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-442952%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F319592%22%20target%3D%22_blank%22%3E%40Philippe_RAYNAUD%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20might%20want%20to%20read%20the%20following%20article%20on%20the%20%22health%22%20tab%20in%20the%20office%20portal...%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20843px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F108389i6568BA45A3529697%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22health.jpg%22%20title%3D%22health.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-443110%22%20slang%3D%22en-US%22%3ERe%3A%20Outgoing%20emails%20marked%20as%20SPAM%20and%20Phishing%20emails%20by%20O365%20servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-443110%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F319693%22%20target%3D%22_blank%22%3E%40Rafmoerkens%3C%2FA%3E%26nbsp%3BThanks%20for%20this%2C%20It%20doesn't%20appear%20in%20my%20portal%2C%20I%20only%20have%20the%20%22%3CSPAN%20class%3D%22bold%22%3EEX176985%3C%2FSPAN%3E%3CSPAN%3E%26nbsp%3B-%20Can't%20see%20message%20traces%22%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3E...%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-443134%22%20slang%3D%22en-US%22%3ERe%3A%20Outgoing%20emails%20marked%20as%20SPAM%20and%20Phishing%20emails%20by%20O365%20servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-443134%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F319592%22%20target%3D%22_blank%22%3E%40Philippe_RAYNAUD%3C%2FA%3E%3A%20you%20might%20have%20been%20%22out%20of%20scope%22%3F%20%3B)%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F252899%22%20target%3D%22_blank%22%3E%40ALV_Work%3C%2FA%3E%3A%20please%20see%20above%20as%20you%20were%20the%20one%20that%20had%20the%20issue%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-443171%22%20slang%3D%22en-US%22%3ERe%3A%20Outgoing%20emails%20marked%20as%20SPAM%20and%20Phishing%20emails%20by%20O365%20servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-443171%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F319693%22%20target%3D%22_blank%22%3E%40Rafmoerkens%3C%2FA%3E%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F319592%22%20target%3D%22_blank%22%3E%40Philippe_RAYNAUD%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENegative.%20Had%20a%20call%20from%20O365%20support%20guy(not%20direct%20MS%20staff)%20and%20he%20has%20confirmed%20that%20my%20domain%20is%20having%20a%20service%20incident%20but%20I%20still%20donot%20see%20anything%20on%20my%20office%20portal.%20But%20looks%20like%26nbsp%3B%20the%20issue%20is%20not%20happening%20now.%20%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-443213%22%20slang%3D%22en-US%22%3ERe%3A%20Outgoing%20emails%20marked%20as%20SPAM%20and%20Phishing%20emails%20by%20O365%20servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-443213%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%40%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F319592%22%20target%3D%22_blank%22%3E%40Philippe_RAYNAUD%3C%2FA%3E%20%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAll%20the%20scenarios%20mentioned%20by%20you%20is%20the%20same%20for%20me%20too.%20Got%20a%20lot%20of%20emails%20tagged%20as%20PHISH%20by%20AntiSpam%20policy%20and%20all%20went%20into%20quarantine%20due%20to%20our%20Antispam%20settings.%20Had%20to%20release%20them%20manually%20to%20the%20users.%20Also%20we%20got%20a%20lot%20of%20duplicate%20emails%20send%20as%20BCC%20to%20our%20IT%20email%20address%20since%20outgoing%20emails%20where%20getting%20tagged%20as%20SPAM.%20But%20now%20the%20issue%20seems%20to%20be%20have%20stopped.%20Looks%20like%20MS%20Team%20has%20reverted%20the%20changes.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-443360%22%20slang%3D%22en-US%22%3ERe%3A%20Outgoing%20emails%20marked%20as%20SPAM%20and%20Phishing%20emails%20by%20O365%20servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-443360%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F319693%22%20target%3D%22_blank%22%3E%40Rafmoerkens%3C%2FA%3E%26nbsp%3BTheir%20article%20is%20weird%20though%2C%20I%26nbsp%3Bdon't%20understand%20what%20this%20has%20to%20do%20with%20%22URL%20filtering%22!%20Happened%20with%20every%20single%20message.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-447026%22%20slang%3D%22en-US%22%3ERe%3A%20Outgoing%20emails%20marked%20as%20SPAM%20and%20Phishing%20emails%20by%20O365%20servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-447026%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F319592%22%20target%3D%22_blank%22%3E%40Philippe_RAYNAUD%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F319693%22%20target%3D%22_blank%22%3E%40Rafmoerkens%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMay%20be%20something%20to%20do%20with%20links%20in%20signature%20of%20outgoing%20emails.%20%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-448616%22%20slang%3D%22en-US%22%3ERe%3A%20Outgoing%20emails%20marked%20as%20SPAM%20and%20Phishing%20emails%20by%20O365%20servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-448616%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F252899%22%20target%3D%22_blank%22%3E%40ALV_Work%3C%2FA%3E%26nbsp%3BNope%20we%20tried%20with%20blank%20messages%20was%20the%20same%2C%20I%20think%20we%20will%20never%20know%20what%20really%20happened%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-856943%22%20slang%3D%22en-US%22%3ERe%3A%20Outgoing%20emails%20marked%20as%20SPAM%20and%20Phishing%20emails%20by%20O365%20servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-856943%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20facing%20same%20issues%20from%20past%20week.%20Did%20create%20a%20ticket%20with%20MS%20and%20is%20still%20being%20worked%20on.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20didn't%20make%20any%20recent%20changes%20to%20any%20of%20our%20policies%20and%20wondering%20what%20is%20the%20reason%20behind%20it.%20Its%20been%20a%20week%20that%20we%20are%20exchanging%20mail%20headers%20and%20extended%20message%20traces%20and%20didn't%20reach%20to%20isolate%20the%20issue%20yet.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1125605%22%20slang%3D%22en-US%22%3ERe%3A%20Outgoing%20emails%20marked%20as%20SPAM%20and%20Phishing%20emails%20by%20O365%20servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1125605%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F252899%22%20target%3D%22_blank%22%3E%40ALV_Work%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20having%20a%20similar%20issue%20with%20a%20client%20who%20has%20Office%20365%20for%20email.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETheir%20domain%20name%20was%20categorized%20as%20CAT%3AHPHISH%20due%20to%20their%20website%20being%20hacked.%20Once%20cleaned%20up%20they%20started%20having%20emails%20being%20quarantined.%20They%20put%20their%20domain%20name%20in%20their%20signature.%20So%20any%20customers%20they%20emailed%20with%20Office%20365%20wouldn't%20get%20the%20email%2C%20it%20would%20be%20quarantined.%20When%20a%20customer%20who%20wasn't%20on%20Office%20365%20got%20the%20email%20and%20replied%2C%20the%20client%20wouldn't%20get%20the%20email.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe've%20reached%20out%20to%20Microsoft%20Support%2C%20however%2C%20they're%20unable%20to%20understand%20what%20needs%20to%20happen.%20And%20there%20is%20no%20system%20in-place%20to%20change%2Fremove%20domain%20names%20from%20this%20categorization.%20Even%20though%20they%20have%20%3CA%20href%3D%22https%3A%2F%2Fsender.office.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsender.office.com%3C%2FA%3E%20for%20de-listing%20IP%20addresses%2C%20there%20is%20no%20way%20to%20submit%20domain%20names.%3CBR%20%2F%3E%3CBR%20%2F%3EOther%20vendors%20like%20PaloAlto%2C%20FortiNET%20and%20Sohpos%20provide%20the%20means%20to%20submit%20evidence%20for%20delisting%20domain%20names%20categorized%20as%20Phishing%20or%20Spam.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-857003%22%20slang%3D%22en-US%22%3ERe%3A%20Outgoing%20emails%20marked%20as%20SPAM%20and%20Phishing%20emails%20by%20O365%20servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-857003%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F409510%22%20target%3D%22_blank%22%3E%40Sujesh1415%3C%2FA%3E%20%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOnly%20Microsoft%20Team%20can%20resolve%20this%20issue.%20It%20mostly%20due%20to%20an%20issue%20at%20their%20servers%20which%20tags%20outgoing%20emails%20as%20spam.%20This%20affects%20not%20everyone%20i%20guess%20just%20random%20tenants.%20%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1138533%22%20slang%3D%22en-US%22%3ERe%3A%20Outgoing%20emails%20marked%20as%20SPAM%20and%20Phishing%20emails%20by%20O365%20servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1138533%22%20slang%3D%22en-US%22%3EWow.%20this%20seems%20scary.%20you%20should%20not%20have%20had%20to%20go%20through%20all%20this%20before%20finally%20getting%20this%20fixed.%20Glad%20it%20all%20got%20figured%20out%20though.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1152354%22%20slang%3D%22en-US%22%3ERe%3A%20Outgoing%20emails%20marked%20as%20SPAM%20and%20Phishing%20emails%20by%20O365%20servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1152354%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F530644%22%20target%3D%22_blank%22%3E%40EmailIssues%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EI'm%20having%20this%20issue%20with%20three%20of%20my%20personal%20MSFT%20email%20accounts%2C%20not%20through%20O365.%26nbsp%3B%26nbsp%3B%20I%20can%20receive%20emails%20but%20all%20my%20sent%20emails%20are%20being%20returned%20by%20the%20protection.outlook.com%20server.%20%26nbsp%3B%20It%20won't%20even%20let%20me%20send%20an%20email%20to%20myself.%26nbsp%3B%20Weird%20thing%20is%20that%20i%20can%20send%20emails%20from%20same%20accounts%20on%20my%20phone.%3CBR%20%2F%3E%3CBR%20%2F%3EAny%20thoughts%20on%20who%20I%20can%20contact%20or%20do%20I%20just%20assume%20this%20is%20a%20bigger%20problem%20and%20hope%20it%20works%20itself%20out.%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Thank%20you.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2121511%22%20slang%3D%22en-US%22%3ERe%3A%20Outgoing%20emails%20marked%20as%20SPAM%20and%20Phishing%20emails%20by%20O365%20servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2121511%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20been%20through%20this%20now%20%3CSTRONG%3Etwo%3C%2FSTRONG%3E%20times.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEvery%20email%20containing%20my%20domain%20was%20marked%20as%20high%20confidence%20spam%20on%20every%20O365%20tenant%20I%20know.%20On%20my%20own%2C%20as%20well%20as%20on%20customers.%20Even%20at%20the%20bare%20minimum%2C%20a%20plain%20text%20email%20containing%20just%20%22myDomain.org%22%20was%20marked%20as%20spam.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20knew%20about%20some%20spam%20incident%20involving%20our%20domain%20as%20an%20email%20sender%20from%20non%20O365%20servers%20that%20fits%20around%20the%20starting%20time%20of%20the%20issue%20at%20the%20first%20occurence.%20For%20the%20second%20incident%20there%20is%20no%20realted%20event%20known%20to%20me.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3EBoth%20times%20I%20have%20been%20hours%20in%20the%20Hotline%20with%20supportes%20that%20were%20honestly%20friendly%20and%20trying%20their%20best%20but%20tried%20everything%20to%20not%20move%20my%20ticket%20to%20second%20level%20support.%20They%20stick%20to%20their%20checklist%20and%20did%20not%20really%20take%20care%20of%20my%20mentions.%20E.g.%20he%20tried%20thousand%20times%20'https%3A%2F%2Fwww.myDomain.org'%26nbsp%3Bat%20mail%20rules%20and%20stuff%2C%20even%20i%20showed%20him%20dozent%20times%20'myDomain.org'%20was%20sufficinent.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBoth%20times%20it%20seemed%20to%20resolve%20itself%20after%20roughly%207%20days%2C%20which%20lets%20me%20think%20their%20internal%20filters%20drop%20after%20one%20week.%20Support%20guy%20told%20me%20that%20they%20were%20working%20hard%20on%20my%20ticket%20and%20someone%20fixed%20it...%3C%2FP%3E%3CP%3EAfter%20the%20supporter%20saw%20the%20issue%20resolved%20itself%20the%20ticket%20was%20closed.%20Definetly%20not%20satisfiying.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThere%20is%20some%20panel%20the%20support%20guy%20pointed%20me%20towards%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fprotection.office.com%2Freportsubmission%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fprotection.office.com%2Freportsubmission%3C%2FA%3E%26nbsp%3Bwhere%20you%20can%20submit%20URLs%20that%20should%20not%20be%20marked%20as%20spam.%20If%20this%20is%20any%20good%3F%20Idk.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENot%20sure%20if%20this%20has%20already%20been%20posted%20here%2C%20but%20another%20good%20link%20I%20found%20about%20this%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.reddit.com%2Fr%2FOffice365%2Fcomments%2Fev98sd%2Fan_issue_with_a_microsoft_office_365_customers%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.reddit.com%2Fr%2FOffice365%2Fcomments%2Fev98sd%2Fan_issue_with_a_microsoft_office_365_customers%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20i%20am%20sitting%20here%2C%20waiting%20for%20the%20next%20time%20this%20starts%20to%20happen...%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2122296%22%20slang%3D%22en-US%22%3ERe%3A%20Outgoing%20emails%20marked%20as%20SPAM%20and%20Phishing%20emails%20by%20O365%20servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2122296%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F963337%22%20target%3D%22_blank%22%3E%40MaxWinterstein%3C%2FA%3E%26nbsp%3BI%20made%20that%20Reddit%20post.%20It's%20a%20shame%20Microsoft%20doesn't%20have%20a%20means%20to%20resolve%20the%20issue%20you're%20facing.%20When%20a%20organization%20get's%20so%20big%2C%20really%20difficult%20issues%20like%20this%20seem%20to%20slip%20through%20the%20cracks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2389018%22%20slang%3D%22en-US%22%3ERe%3A%20Outgoing%20emails%20marked%20as%20SPAM%20and%20Phishing%20emails%20by%20O365%20servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2389018%22%20slang%3D%22en-US%22%3EOur%20organization%20is%20having%20this%20issue%20with%20incoming%20and%20outgoing%20mail.%20I%20have%20had%20our%20users%20remove%20the%20weblink%20from%20their%20signature%20line%2C%20after%20speaking%20with%20a%20Microsoft%20Tech%2C%20and%20mail%20is%20flowing%20out%20from%20us%20without%20being%20rejected%20now.%3CBR%20%2F%3EToday%2C%20we%20have%20started%20to%20see%20that%20all%20mail%2C%20with%20any%20type%20of%20link%20in%20it%2C%20is%20going%20into%20our%20Junk%20Folders.%20Both%20internal%20and%20external.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1126375%22%20slang%3D%22en-US%22%3ERe%3A%20Outgoing%20emails%20marked%20as%20SPAM%20and%20Phishing%20emails%20by%20O365%20servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1126375%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F530644%22%20target%3D%22_blank%22%3E%40EmailIssues%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYes%2C%20you%20need%20to%20keep%20calling%20them.%20They%20have%20access%20to%20remove%20the%20domain%20name%20from%20their%20internal%20list.%20We%20just%20got%20this%20completed%20by%20their%20support.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1131077%22%20slang%3D%22en-US%22%3ERe%3A%20Outgoing%20emails%20marked%20as%20SPAM%20and%20Phishing%20emails%20by%20O365%20servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1131077%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F530276%22%20target%3D%22_blank%22%3E%40Jordan160%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUnfortunately%20we%20have%20not%20been%20so%20lucky.%20Dozens%20of%20calls%20and%20we%20are%20still%20down.%20No%20one%20at%20Microsoft%20seems%20to%20care.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDo%20you%20happen%20to%20have%20a%20MS%20description%20of%20what%20they%20did%20to%20resolve%20your%20issue%20or%20a%20ticket%20%23%20I%20can%20share%20with%20support%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20could%20maybe%20understand%20this%20run%20around%20if%20this%20was%20a%20small%20company%2C%20but%20they%20have%20nearly%20100%20users.%20I%20can%20not%20believe%20the%20lack%20of%20support%20we%20are%20getting.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1133241%22%20slang%3D%22en-US%22%3ERe%3A%20Outgoing%20emails%20marked%20as%20SPAM%20and%20Phishing%20emails%20by%20O365%20servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1133241%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F530644%22%20target%3D%22_blank%22%3E%40EmailIssues%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20sorry%20to%20hear%20that.%20You%20have%20to%20be%20persistent%20and%20point%20them%20to%20this%20post%20and%20ask%20for%20an%20escalation.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUnfortunately%2C%20I%20am%20unable%20to%20provide%20the%20ticket%20number%20due%20to%20the%20privacy%20of%20the%20client.%20However%2C%20this%20is%20what%20was%20communicated%20by%20the%20person%20who%20got%20ahold%20of%20someone%20at%20Microsoft%20after%208%20hours%20of%20total%20time%20with%20their%20support%20staff.%20They%20also%20had%20to%20make%20sure%20they%20had%20the%20appropriate%20SPF%2FDKIM%2FDMARC%20records%20in-place%20before%20they%20would%20even%20consider%20looking%20further.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CBLOCKQUOTE%3E%3CP%3EBasically%2C%20there%20are%20third-party%20lists%20that%20scan%20sites%20looking%20for%20phishing%20stuff%2C%20they%20had%20found%20domain%20name%20to%20be%20a%20part%20of%20that.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThey%20are%20working%20on%20clearing%20off%20the%20domain%20from%20those%20lists%2C%20and%20while%20that%E2%80%99s%20being%20done%20Microsoft%20is%20clearing%20the%20domain%20from%20the%20watchlist%20at%20the%20moment.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EIt%20should%20take%20a%20couple%20of%20hours%20for%20it%20all%20to%20propagate%20and%20take%20effect%2C%20and%20he%20will%20be%20calling%20me%20when%20it%E2%80%99s%20all%20done.%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1126294%22%20slang%3D%22en-US%22%3ERe%3A%20Outgoing%20emails%20marked%20as%20SPAM%20and%20Phishing%20emails%20by%20O365%20servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1126294%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F530276%22%20target%3D%22_blank%22%3E%40Jordan160%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20having%20the%20exact%20same%20problem.%20Tomorrow%20will%20be%20our%203rd%20day%20of%20being%20mostly%20down%20and%20working%20with%200365%20who%20can't%20figure%20out%20the%20problem%20or%20even%20understand%20that%20it%20is%20bigger%20than%20analyzing%20a%20couple%20email%20headers.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20a%20way%20to%20get%20in%20contact%20with%20higher%20tier%20support%20that%20has%20more%20to%20say%20than%20%22%20tell%20your%20recipients%20to%20whitelist%20you.%22%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1133290%22%20slang%3D%22en-US%22%3ERe%3A%20Outgoing%20emails%20marked%20as%20SPAM%20and%20Phishing%20emails%20by%20O365%20servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1133290%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F530276%22%20target%3D%22_blank%22%3E%40Jordan160%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20Jordan.%20We%20have%20several%20tickets%20open%20two%20of%20which%20have%20been%20escalated.%20We%20provided%20the%20link%20to%20this%20thread%20with%20no%20luck.%20We%20have%20~30%20hours%20into%20this%20client%20and%20MS%20support%20now.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESeems%20like%20your%20luck%20is%20better%20than%20ours%20lol.%20I%20will%20keep%20my%20fingers%20crossed%20that%20the%20description%20provided%20helps%20but%20it's%20pretty%20much%20what%20we%20already%20told%20them.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3034178%22%20slang%3D%22en-US%22%3ERe%3A%20Outgoing%20emails%20marked%20as%20SPAM%20and%20Phishing%20emails%20by%20O365%20servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3034178%22%20slang%3D%22en-US%22%3E%3CP%3EOur%20organization%20is%20also%20experiencing%20the%20same%20exact%20issues%20with%20legitimate%20%2F%20wanted%20emails%20that%20our%20clients%20are%20expecting.%20These%20emails%20are%20being%20quarantined%20%2F%20sent%20to%20spam%2C%20or%20even%20rejected%20in%20some%20cases%2C%20specifically%20by%20Microsoft%20365%20%2F%20Outlook%20receiving%20servers.%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20been%20thoroughly%20testing%20and%20it%20appears%20to%20be%20specific%20to%20our%20domain%20and%20not%20related%20to%20our%20email%20sending%20platforms%20or%20IPs.%20This%20issue%20has%20been%20persisting%20across%20our%20entire%20organization%20for%20the%20last%206%20weeks.%20Our%20DKIM%20%2F%20SPF%20records%20are%20all%20setup%20correctly.%20We're%20using%20Dmarcian%2C%20HetrixTools%20to%20monitor%20%2F%20confirm%20our%20DNS%20settings.%20And%20we've%20also%20had%20two%20email%20deliverability%20consultants%20check%20our%20domain%20settings%20and%20confirm%20that%20they%20believe%20this%20is%20an%20internal%20false%20flag%20on%20Microsoft's%20side.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EAfter%20speaking%20with%20numerous%20Microsoft%20support%20staff%2C%20we've%20finally%20made%20contact%20with%20an%20escalation%20team%20and%20have%20provided%20them%20with%20email%20samples%20of%20quarantined%20%2F%20rejected%20emails%2C%20which%20are%20all%20wanted%20by%20our%20clients.%20This%20issue%20is%20severely%20impacting%20our%20business%2C%20as%20our%20clients%20are%20unable%20to%20receive%20emails%20%2F%20work%20product%20for%20which%20they%20have%20already%20paid.%3CBR%20%2F%3E%3CBR%20%2F%3EI'm%20hoping%20that%20someone%20from%20Microsoft's%20Team%20can%20kindly%20escalate%20this%20issue%20and%20advise%20us%20on%20next%20steps%20to%20delist%20our%20domain%20from%20their%20internal%20blacklists.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi,

Since yesterday, all outgoing emails from our organization using Office365 (fully cloud) are being flagged as either spam or phishing email by Microsoft Outbound email servers. Due to this our Office365 user accounts are getting blocked every hour. We tried contacting Office365 support but they said they cannot help on outbound email spam settings as they do not have any control over the configurations. I spend more than an hour on the phone with the support person and at the end was asked to send 5 sample emails to not_junk@office365microsoft.com and wait for 48 hours. I told O365 support that each user who is blocked sends around 100 emails of which all of them are getting flagged as either spam or phishing email, so sending random samples will not help. No spam or phishing filter settings have been changed since months now so I can only think on some backend updates done by O365 team for tightening the spam filters.

I am not sure whom to contact or escalate this case now so I am posting it in this group to everyone expecting someone who might have experienced the same might help. Any help to resolve this issue will be much appreciated as our users are unable to send emails.

Thanks.

32 Replies

@EmailIssues 

 

Yes, you need to keep calling them. They have access to remove the domain name from their internal list. We just got this completed by their support.

@Jordan160 

 

Unfortunately we have not been so lucky. Dozens of calls and we are still down. No one at Microsoft seems to care. 

 

Do you happen to have a MS description of what they did to resolve your issue or a ticket # I can share with support?

 

I could maybe understand this run around if this was a small company, but they have nearly 100 users. I can not believe the lack of support we are getting. 

@EmailIssues 

 

I'm sorry to hear that. You have to be persistent and point them to this post and ask for an escalation.

 

Unfortunately, I am unable to provide the ticket number due to the privacy of the client. However, this is what was communicated by the person who got ahold of someone at Microsoft after 8 hours of total time with their support staff. They also had to make sure they had the appropriate SPF/DKIM/DMARC records in-place before they would even consider looking further.

 

Basically, there are third-party lists that scan sites looking for phishing stuff, they had found domain name to be a part of that.

 

They are working on clearing off the domain from those lists, and while that’s being done Microsoft is clearing the domain from the watchlist at the moment.


It should take a couple of hours for it all to propagate and take effect, and he will be calling me when it’s all done.


 

@Jordan160 

 

Thank Jordan. We have several tickets open two of which have been escalated. We provided the link to this thread with no luck. We have ~30 hours into this client and MS support now. 

 

Seems like your luck is better than ours lol. I will keep my fingers crossed that the description provided helps but it's pretty much what we already told them.

 

@EmailIssues 

 

That really sucks, trying to get past the first line of support is the hardest.

 

As long as you have the headers stating the category, it should pretty straight forward to resolve. It's just trying to get someone from support who actually understands what needs to happen or have them escalate it to someone that knows.

 

I'm going to post this resolution to Reddit just-in-case MS decides to lock this thread or delete it.

It's a shame that support can't understand their own technology stack to identify and issue and provide some sort of resolution. This type of process resolution has been in place with other vendors like PaloAlto, Fortinet and Sophos for years.

@Jordan160 

 

Update: They finally did it!

 

Here is the text from MS if anyone needs it to point support in the right direction. 

Hi ****,

 

Hope all is well. My name is *** from Office 365 Next Team,

We received an escalation request with regards to your issue on spam emails. After further investigation www[.]**********[.]com was listed as a phish URL, it appears the site may have at one time been compromised but is no longer. We have properly delisted it. Can you please check if your emails are still ending into spam/junk folder?

Thank you,

 

***

Office 365 Next Team

Wow. this seems scary. you should not have had to go through all this before finally getting this fixed. Glad it all got figured out though.

@EmailIssues 

I'm having this issue with three of my personal MSFT email accounts, not through O365.   I can receive emails but all my sent emails are being returned by the protection.outlook.com server.   It won't even let me send an email to myself.  Weird thing is that i can send emails from same accounts on my phone.

Any thoughts on who I can contact or do I just assume this is a bigger problem and hope it works itself out.    Thank you.

I've been through this now two times. 

 

Every email containing my domain was marked as high confidence spam on every O365 tenant I know. On my own, as well as on customers. Even at the bare minimum, a plain text email containing just "myDomain.org" was marked as spam. 

 

I knew about some spam incident involving our domain as an email sender from non O365 servers that fits around the starting time of the issue at the first occurence. For the second incident there is no realted event known to me.

 

Both times I have been hours in the Hotline with supportes that were honestly friendly and trying their best but tried everything to not move my ticket to second level support. They stick to their checklist and did not really take care of my mentions. E.g. he tried thousand times 'https://www.myDomain.org' at mail rules and stuff, even i showed him dozent times 'myDomain.org' was sufficinent. 

 

Both times it seemed to resolve itself after roughly 7 days, which lets me think their internal filters drop after one week. Support guy told me that they were working hard on my ticket and someone fixed it...

After the supporter saw the issue resolved itself the ticket was closed. Definetly not satisfiying. 

 

There is some panel the support guy pointed me towards: https://protection.office.com/reportsubmission where you can submit URLs that should not be marked as spam. If this is any good? Idk. 

 

Not sure if this has already been posted here, but another good link I found about this:

https://www.reddit.com/r/Office365/comments/ev98sd/an_issue_with_a_microsoft_office_365_customers/

 

So i am sitting here, waiting for the next time this starts to happen... 

@MaxWinterstein I made that Reddit post. It's a shame Microsoft doesn't have a means to resolve the issue you're facing. When a organization get's so big, really difficult issues like this seem to slip through the cracks.

Our organization is having this issue with incoming and outgoing mail. I have had our users remove the weblink from their signature line, after speaking with a Microsoft Tech, and mail is flowing out from us without being rejected now.
Today, we have started to see that all mail, with any type of link in it, is going into our Junk Folders. Both internal and external.

Our organization is also experiencing the same exact issues with legitimate / wanted emails that our clients are expecting. These emails are being quarantined / sent to spam, or even rejected in some cases, specifically by Microsoft 365 / Outlook receiving servers.

We've been thoroughly testing and it appears to be specific to our domain and not related to our email sending platforms or IPs. This issue has been persisting across our entire organization for the last 6 weeks. Our DKIM / SPF records are all setup correctly. We're using Dmarcian, HetrixTools to monitor / confirm our DNS settings. And we've also had two email deliverability consultants check our domain settings and confirm that they believe this is an internal false flag on Microsoft's side. 

After speaking with numerous Microsoft support staff, we've finally made contact with an escalation team and have provided them with email samples of quarantined / rejected emails, which are all wanted by our clients. This issue is severely impacting our business, as our clients are unable to receive emails / work product for which they have already paid.

I'm hoping that someone from Microsoft's Team can kindly escalate this issue and advise us on next steps to delist our domain from their internal blacklists.