4 ms·
You're both right, but you're solving different problems. Just because your message got past your spam filter doesn't mean it would get past all spam filters.
by space_ghost 7y ago
You're both right, but you're solving different problems. Just because your message got past your spam filter doesn't mean it would get past all spam filters.
- kick 7y agoIt is absolutely not. Even if you are not considering the whole spam thing. They specified that it wasn't even if you could ignore the spam issue. I said that it was if you ignored the spam issue. The first post in this thread was "We've made sending electronic mail way too complicated under the guise of fighting spam." I'm aware that it won't get past every spam filter, but it gets past both Gmail's and my own provider (a smaller, non-American one), which is good enough for my own use. My claim was that sending electronic mail is a solved problem, because it is.
- bigiain 7y ago> My claim was that sending electronic mail is a solved problem, because it is. Agreed. I mean, I can _probably_ remember enough to be able to send mail using just telnet without even needing to look anything up. (And that mail, without any mime parts or urls - it very very likely to not fall into any of the spam filtering on my inbound email accounts...)
- greglindahl 7y agoIn the modern era, lots of mailservers run software that looks for weirdnesses in incoming email. I don't know, but I'd suspect that the typing delays of using telnet to send mail are likely to trigger their defenses.
- bigiain 7y agoSO I just tested. After working out that on macOS I now need to use nc -c instead of telnet... I _can_ send mail manually, but it _does_ end up in gmails's spam folder saying "Why is this message in spam? It is similar to messages that were identified as spam in the past." Iain-2:~ iain$ nc -c gmail-smtp-in.l.google.com 25 220 mx.google.com ESMTP k5si5682618pls.209 - gsmtp EHLO elided.org 250-mx.google.com at your service, [202.171.181.100] 250-SIZE 157286400 250-8BITMIME 250-STARTTLS 250-ENHANCEDSTATUSCODES 250-PIPELINING 250-CHUNKING 250 SMTPUTF8 MAIL FROM: <bigiain@elided.org> 250 2.1.0 OK k5si5682618pls.209 - gsmtp RCPT TO: <bigiain@gmail.com> 250 2.1.5 OK k5si5682618pls.209 - gsmtp DATA 354 Go ahead k5si5682618pls.209 - gsmtp Subject: Test From: bigiain@elided.org To: bigiain@gmail.com Date: Fri, 31 Jan 2020 13:07:00 +1100 Foo baz nah . 250 2.0.0 OK 1580436443 k5si5682618pls.209 - gsmtp QUIT 221 2.0.0 closing connection k5si5682618pls.209 - gsmtp Iain-2:~ iain$
- wolco 7y agoI wonder why google treats this simple email as spam. It contains nothing that should trigger the spam filter aside from where it came from.
- greglindahl 7y agoMost mailservers don't send emails one character at a time. You appear to have a mental model of how a spam filter works that doesn't include fingerprinting the behavior of the sending server? Even open source mail servers do that, for example postscreen is a part of postfix.
- bigiain 7y agoI wonder if it'd fare better if I scripted nc with expect? (Not sure I care enough to try...)
- duskwuff 7y agoSome of the things it doesn't contain, though -- like Message-ID and Content-Type headers -- are likely to contribute to its spam score. If your domain has SPF headers which don't permit mail from the (residential?) IP you're connecting from, that'll be a major factor as well.
- nrb 7y agoWhere it came from is one of the most important details! Is this mail relay actually elided.org or is it impersonating elided.org? There does not appear to be an SPF record for that domain so Gmail cannot determine if this is a fraudulent message, especially if the machine this request came from does not match the IP of the A record for that domain.
- arein2 7y agoSome years ago I wrote my email in a forum, available to crawlers. I’ve been getting spam ever since.
- edmundsauto 7y agoSimilarly, talking is a solved problem. Talking, so that people will listen, is not. Communication is much more than just broadcasting, just as email is about more than sending emails.