3 ms·

Really? So if my email sends get stuck in a client's Gmail spam queue, sucks for me or them? Sucks for me a lot more and I'll move to a hosted service instead t

Really? So if my email sends get stuck in a client's Gmail spam queue, sucks for me or them? Sucks for me a lot more and I'll move to a hosted service instead that can guarantee email delivery.

lucb1e 11y ago
> a client's Gmail spam queue I mentioned it's my personal email, not really meant for work (though I did use it for that also). But technically yes, if they choose to trust Google with delivering the email and Google doesn't deliver, it's a problem on their end. Setting up your email in a way that a particular service (in this case Google) accepts it, doesn't scale.
- georgerobinson 11y ago
  Is this not quite risky, even for personal use? How do you contact family and friends who aren't savvy enough to setup their own email server? What about replying to job interviews? It would really suck if you didn't get the job because the hiring manager never received your email.
  - lucb1e 11y ago
    In my few years of using this, and I'm by no means an expert on email servers, I have rarely had issues beyond ending up in Hotmail's and Gmail's spambox. Never outright rejections I think. Google's spamfilter is the most annoying one, followed by Hotmail; everyone else usually works pretty much fine.
zobzu 11y ago
tbh it never gets stuck in gmail spam queue. its crappy providers that give you low reputation by default aaand nearly all of them have an auto reply response with a contact email or page where you can "unblacklist" your ip easily
- vacri 11y ago
  Ah, blacklists. One of the companies I work for is on the RFC-Clueless blacklist. Gmail handles the business mail, but something was screwed with the abuse@ and postmaster@ mailboxes, so RFC-Clueless listed the domain years ago. Eventually we started running into trouble with mail admins who used RFC-Clueless. I got gmail involved, escalated to third-level support, and got those two RFC addresses fixed. I've submitted this fix to RFC-Clueless several times over the past few months, but it's abandoned. Every request times out after a few weeks. Great, we're on a blacklist whose raison d'etre is "blacklist those not following the rules", and the bastards don't even follow their own declared workflow.

Really? So if my email sends get stuck in a client's Gmail spam queue, sucks for me or them? Sucks for me a lot more and I'll move to a hosted service instead that can guarantee email delivery.

lucb1e 11y ago

> a client's Gmail spam queue I mentioned it's my personal email, not really meant for work (though I did use it for that also). But technically yes, if they choose to trust Google with delivering the email and Google doesn't deliver, it's a problem on their end. Setting up your email in a way that a particular service (in this case Google) accepts it, doesn't scale.

georgerobinson 11y ago
Is this not quite risky, even for personal use? How do you contact family and friends who aren't savvy enough to setup their own email server? What about replying to job interviews? It would really suck if you didn't get the job because the hiring manager never received your email.
- lucb1e 11y ago
  In my few years of using this, and I'm by no means an expert on email servers, I have rarely had issues beyond ending up in Hotmail's and Gmail's spambox. Never outright rejections I think. Google's spamfilter is the most annoying one, followed by Hotmail; everyone else usually works pretty much fine.

zobzu 11y ago

tbh it never gets stuck in gmail spam queue. its crappy providers that give you low reputation by default aaand nearly all of them have an auto reply response with a contact email or page where you can "unblacklist" your ip easily

vacri 11y ago
Ah, blacklists. One of the companies I work for is on the RFC-Clueless blacklist. Gmail handles the business mail, but something was screwed with the abuse@ and postmaster@ mailboxes, so RFC-Clueless listed the domain years ago. Eventually we started running into trouble with mail admins who used RFC-Clueless. I got gmail involved, escalated to third-level support, and got those two RFC addresses fixed. I've submitted this fix to RFC-Clueless several times over the past few months, but it's abandoned. Every request times out after a few weeks. Great, we're on a blacklist whose raison d'etre is "blacklist those not following the rules", and the bastards don't even follow their own declared workflow.