181–190 of 460 posts
CEO of an email marketing platform here (EmailOctopus). If anyone's curious, here's a chart showing our bounce rate to Gmail addresses over the course of the week: https://pbs.twimg.com/media/EpUE20UXYAEa_Uv?format=jpg&name=... That's a peak of 90% of Gmail inboxes bouncing – and this has been going on for almost 24 hours.
Earlier quoted context omitted.
> Not fixed for over a year and they've locked the thread so I'm starting to wonder if they actually deleted the emails by mistake. Did you try pulling them down using the API tester?: https://developers.google.com/gmail/api/reference/rest/v1/us... Some of the internal formatting that Gmail uses has changed over the years, so more likely than not the API that parses the stored message for display in the Gmail UI is j…
I've never had issues over IMAP with old (decade) message in gmail
Is Microsoft's Live Mail (Outlook.com) more reliable than Gmail?
Over the past 24 hours, I've had GitHub request that I re-verify my gmail three times (roughly 22 hours ago, 2 hours ago, and now), each time resetting my primary email's status to "Undeliverable" and "Unverified" The triggering event may be an email bounce. I get a lot of github notifications sent to my email, and the failure of just one/a few may trigger the reverification.
This is another good reason to have email @yourowndomain.tld When this happens, you can spin up a temporary server and have a mechanism in place to redirect email so you don't go down when your provider does.
CEO of an email marketing platform here (EmailOctopus). If anyone's curious, here's a chart showing our bounce rate to Gmail addresses over the course of the week: https://pbs.twimg.com/media/EpUE20UXYAEa_Uv?format=jpg&name=... That's a peak of 90% of Gmail inboxes bouncing – and this has been going on for almost 24 hours.
Earlier quoted context omitted.
I believe you mean: s/s\/his\/her/s\/his\/their/
s#s/his/her#s/his/their# also works and avoids awkward escaping. The first symbol after s is used as the separator. Works in vim, at least. In other words: s%s/s\\/his\\/her/s\\/his\\/their/%s#s/his/her#s/his/their#%
Side note: Love the 2010-era web design. Wtf happened? Everything got bloated, buttons got huge and whitespace took over the screen real-estate.
Earlier quoted context omitted.
Okay, so use "their." It is gender neutral, so should work for everyone.
It's also wrong. because it's not singular. Makes for difficult reading.
CEO of an email marketing platform here (EmailOctopus). If anyone's curious, here's a chart showing our bounce rate to Gmail addresses over the course of the week: https://pbs.twimg.com/media/EpUE20UXYAEa_Uv?format=jpg&name=... That's a peak of 90% of Gmail inboxes bouncing – and this has been going on for almost 24 hours.
As an ESP, how much of a headache will this be for you in weeks/months to come? I'm guessing this throws a huge wrench in deliverability techniques--how're you handling it?
I logged into our sendgrid and mailgun accounts and manually purged all the failed gmail records.
Earlier quoted context omitted.
Googler but nowhere near Gmail, so just educated speculation: * We have a lot of automation/tools to prevent incidents when mitigation is straightforward (e.g. roll back a bad flag, quarantine unusual traffic patterns), which means that when something does go wrong it's often a new failure mode that needs custom, specialized mitigation. (e.g. what if you're in a situation where rolling back could make the problem wor…
Rollback proof bugs are rare, but boy howdy are they exciting. I think I've only seen one so far (unless you count bad data / bad state that persists after a bad change is rolled back... which can also be pretty exciting)