I’m experimenting with a new email setup (for the imminently-launching Neatnik ID setup) and could really use some help testing email deliverability. If you have a spare moment and would like to test, just send an email to testing@email.engineering with any subject line and any message body.
I’m mostly concerned with ensuring that you receive a reply within 15 seconds, and that the reply winds up in your inbox (not spam/junk).
Thanks in advance if you’re able to help test! :prami_happy:
@rckt thanks! This seems consistent with what I’m seeing so far from mailbox.org, which is an intentional deferment due to my IP address not having an established reputation yet. Hopefully this will improve soon!
@adam since you already had Fastmail custom domain verified, I tried two different things:
Attached an image. I got a reply, but it contained the base 64 representation of the image in the reply. Before I realized that, I tried replying in the Fastmail iOS app and it hung trying to load the reply.
@bnb Oh, that attachment behavior is interesting. The BCC behavior is good (since I have the reply set to only trigger if the message is addressed to testing@email.engineering explicitly). 👍
@andycarolan So, interestingly, the logs show that the receiving email server (which is operated by MailChannels, the company Dreamhost uses) responded with “Delivered: Code: 250, Enhanced code: 2.1.5, Message: Ok" which should mean that the message was delivered to you. (It could have landed in spam/junk, but it should at least be accessible to you somewhere.)
Can you take another peek, and maybe search for "mail@email.engineering" (which is the address it would have come from)?
@andycarolan Got it! I suspect the other one was gobbled up when I was doing some weird server config stuff during all of the testing (not a great time to be doing that, heh). Thank you!
@jason If it’s not too much trouble, could you reply to the email and paste in the raw headers? Hopefully there will be some spam headers there that Proton applies and I can use those to understand what happened.
@adam the big issue with iCloud mails is, that it’s totally unreliable. They’re shadow blocking mails and you never know why. You can find a lot of reports online.
So don’t waste too much time into iCloud reliability.
@case2tv it looks like they’re using Proofpoint, and if an IP address is flagged on Proofpoint it’s an automatic rejection from the iCloud mail server. I’m going through the process of clearing that now, which should hopefully help. 👍
@adam can you have an email address without the word “testing”? I think that’s one reason it got delivered mostly in Spam folder or not delivered at all.
@andyn Good to know! Had two reports of them placing the reply in junk, but maybe a few "not junk" reports from some people was enough for them to update some stuff? I have zero clue how they do spam filtering but I assume there’s some kind of algorithm and shared dataset being used somehow. 🤷🏻♂️
@von Awesome! I’m over here bracing for a torrent of “your reply went to spam, and my mail server has blocked you, and you’re a jerk” but so far so good... I’m cautiously optimistic that this new setup could actually be decent after all!
Add comment