robmoss2k
commented
7 years ago I've managed to work out that every email address I send them to is flagging them as bad enough spam that it won't even chuck them in the Junk E-mail folder. This is getting added by Exchange Server, for example:
X-Original-X-Forefront-Antispam-Report: CIP:209.61.151.226;IPV:NLI;CTRY:US;EFV:NLI;SFV:SPM;SFS:(8156002)(31610200002)(1060300004)(2980300002)(438002)(47530400004)(596005)(286005)(189002)(199003)(4290100001)(575854001)(110476001)(50466002)(6916009)(42882006)(104016004)(980100002)(33656002)(42186006)(22452003)(2351001)(104766002)(15650500001)(106002)(345774005)(106466001)(3450100001)(10290500003)(356003)(42520400002)(236005)(16003)(246002)(966005)(413944005)(23846002)(45080400002)(10126004)(7596002)(36756003)(7636002)(54356999)(50986999)(1096003)(1076002)(230700001)(606006)(8676002)(9686003)(6306002)(92140200001)(527704001003);DIR:INB;SFP:;SCL:5;SRVR:HE1PR0701MB1916;H:rs226.mailgun.us;FPR:;SPF:Pass;PTR:rs226.mailgun.us;MX:1;A:0;
So the content filter is marking the email as spam. I'm not sure why - but it seems all email providers I've tried are doing the same.
https://ecsapi.portal.azure-api.net/ will not issue a verification email. I've tried:
rob.moss@weaveability.com robmoss2k@hotmail.co.uk robmoss2k@outlook.com
None of them receives the verification email, whether it's the inbox, junk mail folder or whatever. As such, the API isn't usable (even though it would be beneficial).