Comcast outgoing mail with Dropbox links in them going directly to Xfinity Connect Spam folder....

[Ftlog]

Hello. As of today, any emails I send that have a shared Dropbox link pasted into them get trapped in the Comcast webmail/Xfinity Connect Spam folder, even though I've sent them from my own Comcast email address (using Outlook for Mac). I've done a few tests and it's specifically Dropbox links that cause the outgoing email to get caught (intended receipients do not receive the email, so it's caught in the sending/outgoing process). The original emails show up in my Outlook Sent folder, but again, they get caught in the Comcast Spam folder I see when logged into webmail/Xfinity Connect. Can someone please help! I need to be able to share links via email to send files and haven't had any trouble with this until today! Thank you!

[BruceW]

If @ComcastAntiSpam or another employee doesn't help you here, Comcast Security Assurance may be able to tell you what the problem is. You can reach them at 1-888-565-4329 (from https://internetsecurity.xfinity.com/help/report-abuse/). Note that this is NOT one of the general customer service numbers. The first-line reps there are sometimes not very helpful, so be persistent, and keep at them until you get a satisfactory resolution.

[CCAntiSpam]

@Ftlog Could you go into your webmail and mark one of the messages in your spam folder as "Not Spam"?

[Ftlog]

I did that previously and it then sent the emails that were in the Spam folder, but the next test I sent was caught in there again.  

[CCAntiSpam]

@Ftlog Yes, we needed a sample of the message for analysis.  The more you mark as "Not Spam" the more it trains the filters, but sometimes we prefer to have one for analysis.

[Ftlog]

For what it's worth, it seems the emails with the Dropbox links are going through fine again now. I'm not sure if something was changed on Comcast's end, but I didn't change anything. Fingers crossed this issue doesn't come up again.

[CCAntiSpam]

@Ftlog Sorry I hadn't responded.  The example from your "Not Spam" report was enough to help them figure out why it was being incorrectly flagged.  Thanks for the assist.