DKIM, DMARC, SPF, rDNS/PTR, EHLO... all correct and verified in the email "original source," BY GOOGLE. Still goes to SPAM folder because **** you, apparently. I hate Google.

top 90 comments

sorted by: hot top controversial new old
[–] 63 points 2 months ago (2 children)

I stopped thinking of any email as “private” regardless of where it’s hosted, when I realized that everyone I email uses Gmail anyways; so all my emails end up going to Google anyways.

It made me an email nihilist

  • source
  • hideshow 2 child comments
  • [–] 8 points 2 months ago

    Microsoft Exchange and the web-based Outlook probably still has a plurality of email volume, because of their dominance in enterprise. Even on the web based consumer space, Apple and Yahoo still have significant market share.

  • source
  • parent
  • [–] 44 points 2 months ago (1 child)

    I work for state government and even we have trouble with email reputation issues from the big orgs. It's a pain for everyone.

  • source
  • hideshow 1 child comment
  • [–] 18 points 2 months ago

    This is done on purpose, to make people to switch to their e-mail or use them for hosting.

    Google did the same thing with XMPP (they were welcomed when they joined, then they made it so XMPP users couldn't message GTalk/Hangouts users, but the other way worked), they tried similar thing with Usenet, but they never get dominance there so they let their services to be major source of spam on Usenet until they were blocked, ultimately removing Usenet indexing from Google).

    I would really encourage to contact our local reps (both federal as well as state) and encourage them to introduce legislation that would punish this practice.

  • source
  • parent
  • [–] 25 points 2 months ago (4 children)

    I run my own mailserver in docker and it's not so hard! There was some difficulty at the start with mail going to spam, but after a little while "warming up" the IP with usage, it works fine. It's hardest to build an IP's reputation in the beginning because if your mail goes to spam, it doesn't typically lead to healthy conversations that can support it's history.

    My trick was to forward all my incoming gmail messages from the account I was replacing into the new server - that way I could receive and reply from the new mailserver if people sent mail to the old one. Once it built up a bit of a history it started working fine, and that took maybe a few conversations over a couple of days.

    The thing I have noticed is that you very quickly get destroyed by incoming spam - a more advanced filter is definitely on the list.

  • source
  • hideshow 4 child comments
  • [–] 15 points 2 months ago (3 children)

    One of the problems with self hosting is that a lot of IP addresses have historically been used for spam and still have a bad reputation. If you get assigned one of those IP addresses there's very little you can do about your mails going to spam.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 5 points 2 months ago

    Another is most ISPs will put your IP in the PBL so unless you use a relay your outbound email is going nowhere. Google fiber was slow on updating their PBL when they rolled out service in my area so I got to send direct for several months before having to use an external relay.

  • source
  • parent
  • [–] 177 points 2 months ago* (last edited 2 months ago) (30 children)

    Tbh, out of all services I've seen people self-host, email is the most common one I've seen people describe as a bad idea™️.

    I just chose a paid mail service (mailbox) and called it a day.

  • source
  • hideshow 30 child comments
  • [–] 19 points 2 months ago* (last edited 2 months ago) (5 children)

    Even using a reputable hosting provider and personal domain will get you spam black holed these days

  • source
  • parent
  • hideshow 5 child comments
  • [–] 14 points 2 months ago (2 children)

    I wonder if there should be some kind of law or regulation around this. It’s an antitrust issue. Though no one in Congress would understand what this is.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 48 points 2 months ago (13 children)

    Yeah we should just let them win. Why fight? It’s not like most of the spam and phishing come from Gmail and hotmail accounts. It’s those fucking self hosters

  • source
  • parent
  • hideshow 13 child comments
  • [–] 38 points 2 months ago* (8 children)

    How's your self hosted email going? Any advice you can share to avoid some of the major issues?

  • source
  • parent
  • hideshow 8 child comments
  • [–] 33 points 2 months ago (7 children)

    I've run a mail server since the late 90s. I gave up running my own outbound years ago. Whether it gets received is too inconsistent. Primarily, make sure the IP you use isn't on any spam lists. If it is, get a new IP or try to submit appeals. Make sure you have the standard anti spam/authenticity measures implemented (they're listed in the OP).

    These are the minimum. Years ago it was enough to have reasonable delivery. Unfortunately these aren't that helpful anymore because spammers also set them up (often with seemingly randomly generated domain names). I assume because not having them was a fairly strong signal for being a spammer, so now they also set them up, which also means there's not really any configuration / setup you can do to seem legitimate (aside from mail volume and the content itself which will be analyzed).

    Anyway running your own SMTP itself is easy. The problem is getting your mail to the inbox or at least spam/junk folder (your mail may get blackholed and not even show up in spam). At least when you get a rejection, you know something is wrong, but many times the receiving server will indicate a success code and simply not deliver it to the user (not even to their spam).

  • source
  • parent
  • hideshow 7 child comments
  • [–] 10 points 2 months ago (6 children)

    Interesting! You said you gave up on the outbound, does that mean you can't reply to mails you receive? But if you can reply, does that mean the sender (let's assume someone with gmail) will get it or would even that likely end up blackholed or in spam?

  • source
  • parent
  • hideshow 6 child comments
  • [–] 14 points 2 months ago (4 children)

    I can reply yo emails. It's what jaybone said -- I use a 3rd party outbound (SMTP).

    I use Thunderbird as my mail client. In there you can define multiple IMAP/pop accounts (inbound) and multiple SMTP (outbound). So when I click reply, the SMTP I have set for that email address is a 3rd party service that sends emails using my domain.

    This does have a privacy implication, so whether that's appropriate for you is for you to decide. The 3rd party can read and save a copy of your outbound email inclusive of any content included with it (like the email you're replying to if you include it).

  • source
  • parent
  • hideshow 4 child comments
  • [–] 1 point 2 months ago (2 children)

    What 3rd party service do you use?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 6 points 2 months ago* (last edited 2 months ago) (1 child)

    Don't take this as an endorsement as it's not really intended to be used for this purpose and I'm probably going to switch, but I've been using sendgrid for a few years as I was familiar with it from business use. I was using mandrill before that until they changed their pricing and some other things.

    EDIT: also worth mentioning I have a grandfathered free plan.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 4 points 2 months ago

    Good for you if you have a grandfathered account, but Sendgrid has a terrible interface. Setting up things is so messed up!

    Again, not an endorsement, but Qboxmail is nice and EU-based.

  • source
  • parent
  • [–] 21 points 2 months ago (2 children)

    Maybe the way to fight GMail's outsized power is to stop using GMail. You can do that without going all the way to self-hosting.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 2 months ago

    Maybe the way to fight GMail’s outsized power is to stop using GMail.

    Stopping your own gmail use is trivially easy. It just scratches the surface. In order to not lick Google’s boots, you also need to stop sending email to gmail users. That means doing an MX lookup before emailing to see if their vanity email address is on a Gmail host. And of course this also means not sharing an email address with gmail users.

    I do that, in fact. I also boycott Microsoft. In the end, this means I am not using email much at all.

  • source
  • parent
  • [–] 13 points 2 months ago (4 children)

    Soon not using a chromium browser will probably be considered a bad idea

  • source
  • parent
  • hideshow 4 child comments
  • [–] 12 points 2 months ago (3 children)

    I get what you mean, but this website specifically works completely fine on my Firefox (with uBlock). Please check your browser settings for things like disabled JavaScript.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 4 points 2 months ago (2 children)

    Yeah everything is disabled its Firefox focus, everything always worked fine then like this past week all sorts of sites started showing that

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 2 months ago (1 child)

    That screen is from cloudflare. It means you're blocking their JavaScript or iframe elements used to create the bot challenge. I get it quite often as I still use the old uMatrix extension. Temporarily unblocking and refreshing the page will let you through.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 4 points 2 months ago

    I use a free outbound smtp relay that lets me do like 5k emails on the free tier. I use it primarily for alerts and Immich updates / new user links. But I don't do inbound so don't have to expose any ports. Only time I did was to do validation with the relay so just a few minutes during setup.

  • source
  • parent
  • [–] 2 points 2 months ago

    I do not understand all the people who are too afraid to try email hosting on their own that are out here discouraging people cause they want to sound right.

    Email is hard cause people don't host it enough and the few corps ignore the minority problems.

    If more people shift back to hosting email the balance will tip again.

    It is fine if you don't want to host email but telling people not too without even trying yourself is anti-selfhost IMHO.

  • source
  • parent
  • [–] 44 points 2 months ago* (last edited 2 months ago)

    Self-hosting email is quite the undertaking... I don't have the energy to deal with it and just pay 10€/year for a hosting service.

    Here's an informative (and funny) talk on why self-hosting email in its current state is probably a bad idea.

  • source
  • [–] 21 points 2 months ago (11 children)

    Me and a couple other people have ran into on the internet have thought that we need to invent "email 2", a clean slate implementation of email that serves it's asynchronous long form and attachment friendly function while leaving behind Decades of Cruft . We can make it into an encrypted by default and have conveniences that we never had before. It might even be an actual useful thing instead of just being the thing you sign up for accounts with to get to 2fa codes and spam from websites you buy stuff from

  • source
  • hideshow 11 child comments
  • [–] 10 points 2 months ago* (2 children)

    Love this idea!

    I feel like Arcane/Delta Chat is a step toward this. It somehow uses an email protocol and it works just like Signal or any other message app! I dunno how the heck it works but it's super cool.

    That's something I want too: An open standard my friends and family can be on, where "the market" isn't.

    Edit: I see, it seems the issue in the main thread is:

    • Gmail blocks custom servers as spam 99% of the time.
    • 99% of normieverse uses Gmail. :(

    But getting people on other email providers to talk to each other... shouldn't be an issue then?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 4 points 2 months ago (7 children)

    Frankly, I'm rather shocked it hasn't happened by now.

    We've tried to bandaid over it with various weird things, but fundamentally SMTP is just weird.

    I could easily imagine a domain having some SRV record to advertise "hey, I support NeoSMTP", and peers switching to that instead, possibly pinning on successful NeoSMTP negotiation.

    Get rid of a lot of the relaying which has not been useful in modern times and only a liability, and perhaps offer an https option to be less likely to be blocked (a TXT record to indicate url, and a node could declare their NeoSMTP entry point as https://mail.server/NeoSMTP/ or whatever works for them).

  • source
  • parent
  • hideshow 7 child comments
  • [–] 3 points 2 months ago (4 children)

    Oh, there have been plenty. The issue though is the classic "make a better standard, and now you have N+1 standards".
    Everything is wrong with SMTP. It's still in use because it's supported everywhere. Anything that wants to replace it either needs to entirely replace it in one fell swoop, or it needs to be backwards compatible.

    The result is that occasionally a new thing comes up, a handful of people try it but there isn't critical mass to make other features really useful so it fades.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 1 point 2 months ago (1 child)

    Hence my references to DNS records in addition to MX to determine if an endpoint is SMTP only or better. For compatible interop.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 0 points 2 months ago

    But that's the thing: now you haven't made an email replacement, you've made email more complicated.

    If you're backwards compatible you need a very compelling feature to get people to switch, and using the feature is limited until people switch.
    That's how we added spf, dkim, dmarc and starttls.
    The biggest difficulty is managing the layers of compatibility.

  • source
  • parent
  • [–] 18 points 2 months ago
    [–] 15 points 2 months ago

    I have this problem for a while as well. Similar to you all mechanisms are implemented multiple sites say the configuration is correct, even headers in Gmail say DKIM and SPF passed. E-mail arrives everywhere except for gmail.

    Thanks for posting, at least I know I'm not the only one.

  • source
  • [–] 15 points 2 months ago (1 child)

    I self-hosted my own email for a few years, everything was set up and reporting correctly, but Google just would never have it. I think the worst is it would be a bit inconsistent.

    Anyway, I switched to an email provider with my own domain and it's much more reliable. That is until this week, I have noticed that some services are rejecting my domain. I think there is some whitelisting nonsense going on, but in those instances I just use an alias and that seems to work.

    I just want to have control of my data!

  • source
  • hideshow 1 child comment
  • [–] 30 points 2 months ago (3 children)

    If you want you can PM me your dkim and dmarc and SPF policy. Or just send me your url and I'll look it up. I used to fix these for a living. It's likely an issue with your SPF not being properly annotated.

  • source
  • hideshow 3 child comments
  • [–] 13 points 2 months ago (1 child)

    @laurenceOfSuburbia This ain't anything new. They have been doing this for decades and will still do it forever. Just move on with it, since it like trying to figure out something which has no meaning at all.Just know for sure that every company has systems designed by some developer based on a whimsical mindset of someone at the very top. So, I can care less for these stupid companies and their useless management.

  • source
  • hideshow 1 child comment
  • [–] 12 points 2 months ago* (last edited 2 months ago)

    I also self host email and so far haven’t had any problems. Initial setup was annoying but it’s required zero effort this past few years, and I don’t think my emails land in spam folders. Maybe I can help?

    Shoot me a message at test-message-lawrenceOfSuburbia@mspencer.net (which I’ll delete after it gets a message, for obvious reasons) and I’ll take a look. (I misspelled the name, I apologize, no insult intended)

    Honestly I think I’ve received 10 spam messages in the last four years, and five have been from gmail addresses (Best Buy invoice spam) in the past two months. I submit each one to support.google.com/mail/contact/abuse and hopefully it helps.

  • source
  • [–] 9 points 2 months ago

    i never had problems with Google, but Outlook always blocks my emails, just because it's not a standard .com .net etc domain...

  • source
  • [–] 9 points 2 months ago

    Self hosting an email server to send mails that don’t get flagged as spam is a nightmare, I’d rather not attempt doing it again. My Lemmy instance is using SMTP2Go and the free tier is more than enough for my current sending capacity needs

  • source
  • [–] 7 points 2 months ago* (3 children)

    They claim its for spam prevention which is why most ISPs actually also block outgoing SMTP port 25.

    The dumb thing is, all it really does is push spammers onto using botted/stolen accounts which work way more effectively, and everyone else is forced to set up their email with Google or Microsoft.

    If your domain isn't big enough to be recognized, all that SPF and DMARC won't mean crap to them.

  • source
  • hideshow 3 child comments
  • [–] 1 point 2 months ago (2 children)

    They claim its for spam prevention which is why most ISPs actually also block outgoing SMTP port 25.

    European ISPs block egress port 25, not American ones, generally. Not sure about the rest of the world.

    In Europe, one refuge is to send using the GSM networks, which tend not to block egress 25 for some reason.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 2 months ago (1 child)

    not American ones, generally.

    Well then screw you AT&T lmao

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 2 months ago

    AT&T is the worst of the worst. And I boycott them for countless reasons like snooping on their own customers voluntarily without a warrant. It’s really a hard-right corp. In any case, never tried them so I didn’t know they blocked egress 25.

    One trick that works if truth-in-advertising laws are in force: ask the sales people before subscribing if the block port 25. They always say “no, we block nothing” (in my experience). So you subscribe and sign the contract. Then when you see they actually block 25, you have a false advertising situation and also a contract violation (if either verbal contracts are enforcable or if you can get it in writing that nothing is blocked). So you complain. In my experience, they give a gratis upgrade to an enterprise level of service that generally has a static IP and no blocks -- for the price of the residential plan you signed up for.

  • source
  • parent
  • [–] 16 points 2 months ago

    Most email providers block new domains... You need to have the DNS records up for like 2 years before they start getting accepted... Or contact all the big doers to get yourself whitelisted

  • source
  • [–] 5 points 2 months ago (5 children)

    I might be out of the loop on how email works, but doesn’t it hop between several other email servers on its way from Alice to Bob (and at least some of it must still be unencrypted)? If so and given google’s scale you could probably just assume that even if they’re not your inbox they’re going to be at least handling many if not most emails along the way.

  • source
  • hideshow 5 child comments
  • [–] 6 points 2 months ago

    Depends. Usually not. It hops from your computer to your email provider which then looks up the server of the recipient and sends it there. The recipient's server might send it on internally and in big installations probably does so.

    It is theoretically possible that one of the involved parties has a third party authorised to accept mails on their behalf in case of outages. I don't believe that is very common nowadays. It's much more likely that your provider will keep the mail for a few hours to days when it can't reach the recipient.

    But ideally only your provider and the recipient's provider can read the mail with all connections in between being encrypted. There's just no guarantee that all paths are encrypted. But I think nowadays that is much more likely than it used to be, thanks to Let's Encrypt.

    Now, if you don't want any of the servers to be able to read the mail you have to encrypt it with something like GPG. But for that to work you need the recipient's key. But hardly anyone uses that. And it only encrypts the content of the mail. Not the metadata.

  • source
  • parent
  • [–] 4 points 2 months ago (2 children)

    That was the theory, nowadays moest email goes from google or microsoft to google or microsoft. At least 99% of the rest goes directly from the senders provider to the recipients provider. Afaik none of the larger providers still accept non-TLS connections.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 2 months ago (1 child)

    Yeah that’s what I’m saying. Even if you’re not using one of the big providers there’s a good chance they’re going to be at least handing it on its way to your self-hosted inbox, and its contents are unencrypted while they’re handling it (unless you encrypt the contents yourself). So there’s not much benefit to self hosting email if your goal is to keep your data out of big tech’s hands (and if that is your goal, don’t send anything important with email)

  • source
  • parent
  • hideshow 1 child comment
  • [–] 5 points 2 months ago* (last edited 2 months ago)

    If neither the sender nor the recipient is hosted by google the email is never going to reach googles servers. It will go directly from the sender provider to the recipients provider.

  • source
  • parent
  • [–] 4 points 2 months ago

    If you control the DNS and the mail server, you get to decide where it goes. However, if any senders or recipients are on gmail, Google basically has all of those emails' content.

  • source
  • parent
  • [–] 4 points 2 months ago (2 children)

    Probably bad place to ask but.

    Self hosting email is complicated only for sending mails or for receiving mail it's also hard?

    Depending on what you want to do you might not need to actually send any mail.

    Also, the anti-spam rules do also apply if you are answering a mail, I suppose it does as a response envelopement doesn't have any evidence that it's an actual response. But I have no experience self hosting email.

  • source
  • hideshow 2 child comments
  • [–] 6 points 2 months ago

    @daniskarma @laurenceOfSuburbia yeah the complication is not technical so much as bureaucratic. Email itself is simple, but then you have to jump through hoops of tuning various other technical settings for Big Email to allow you inI think it's usually to do with sending, so if you're only interested in receiving I think you'll be fine (unless your server uptime's really bad or something)

  • source
  • parent
  • [–] 5 points 2 months ago

    Self hosting receiving mail is honestly, pretty straightforward, all things considered. Setup your MX record to point at a server you control, configure software to save messages however you want. Perhaps the most complicated step is wiring up certbot or similar software to get your SSL certificate for your mailserver. A Debian Linux system, apt-get install postfix; apt-get install dovecot will get you nearly 90% of the way there.

    Depending on your preference. there are docker containers that can do 100% of the process too, with all sorts of nice bells and whistles. If you don't care about sending email, you can skip DKIM/SPF/DMARC. (though, if you are never sending from your domain, check here: https://www.cloudflare.com/learning/dns/dns-records/protect-domains-without-email/ -- there are some entries you can add to DNS to make sure everyone else knows)

  • source
  • parent
  • [–] 3 points 2 months ago
    [–] 3 points 2 months ago

    I've started mine and it works fine. All the Google shit goes straight to the bin though.

  • source
  • [–] 3 points 2 months ago*

    Ngl, I can't blame most for flocking to Gmail. It's a lot more of a pain in the rear to self-host something like that, and it's just plain convenient.

    It's the same reason a lot of the people leaving Gmail go to essentially the Privacy Google (Proton) as the replacement.

  • source
  • [–] 5 points 2 months ago (1 child)

    Running your own email server is also a good way to get a ton of headaches from your isp

  • source
  • hideshow 1 child comment
  • [–] 4 points 2 months ago

    I put dog shit in my ass and Google knew five minutes before it happened, filmed it, and sold it back to me as a custom highlight of my home alone shenanigans. I find this a bit egregious, personally.

  • source
  • [–] 2 points 2 months ago

    My email service provider just marks everything as spam. So they’re not alone, you say?

    Irritating how much spam comes from Gmail/microsoft.

  • source
  • [–] 1 point 2 months ago

    Do you send enough email to classify for Google to allow you to contest your status as spam? Because there is a minimum.

  • source
  • [–] 1 point 2 months ago

    Google can still automatically mark your message as spam if enough people mark it as such or you trigger spam identification too often (this can happen if you send frequent test emails with not much in them) - it's not neccesarily an attack on you. But plenty of spammers will send perfectly well verified emails today, so you are just caught in the crossfire.

    Try sending a gmail account you still have access to a couple of genuine looking mails (eg. At least a paragraph of legible text and with a signature), then marking the messages as not spam. That worked for me. Even after that though, one line messages can still trigger the spam detection.

  • source
  • load more comments
    view more: next ›