lingo.lol is one of the many independent Mastodon servers you can use to participate in the fediverse.
A place for linguists, philologists, and other lovers of languages.

Server stats:

69
active users

#smtp

1 post1 participant0 posts today
Replied in thread

System Administration

Week 8, The Simple Mail Transfer Protocol, Part III

In this video, we look at ways to combat Spam. In the process, we learn about email headers, the Sender Policy Framework (#SPF), DomainKeys Identified Mail (#DKIM), and Domain-based Message Authentication, Reporting and Conformance (#DMARC). #SMTP doesn't seem quite so simple any more...

youtu.be/KwCmv3GHGfc

Replied in thread

System Administration

Week 8, The Simple Mail Transfer Protocol, Part II

In this video, we observe the incoming mail on our MTA, look at how STARTTLS can help protect information in transit, how MTA-STS can help defeat a MitM performing a STARTTLS-stripping attack, and how DANE can be used to verify the authenticity of the mail server's certificate.

youtu.be/RgEiAOKv640

Replied in thread

System Administration

Week 8, The Simple Mail Transfer Protocol

In this video, we begin our discussion of E-Mail by looking at the components of the larger mail system (the Mail User Agent, Mail Transfer Agent, Mail Delivery Agent, Access Agent); we observe the packets involved in a simple #SMTP exchange and track an email from one system to the other, both through the logs and on the wire, before we then learn to speak SMTP via telnet(1).

youtu.be/Ai8rjqelwsI

I thought I had seen it all when it comes to mail delivery and security issues.

But this morning I was introduced to the fact that there are Exchange admins who will implement a rule that all incoming mail from outside their own organization should be flagged as potentially dangerous and presented to the user with the option to block sender and no option to mark the message or the sender as valid.

Yes, that for every single message.

What an unfortunate name…

STARTTLS has the innate issue that it is an upgrade of a plaintext session. Anything before TLS initiation can be sniffed off the wire. Unavoidable given the *purpose* of STARTTLS. It allows TLS to be used without dedicating a port to it. It is the ONLY way that mail *transit* is encrypted. *Nothing* there justifies non-support of STARTTLS.

The rest of the issues there are old & implementation-specific.

#email #TLS #InfoSec #SMTP #IMAP
mendeddrum.org/@fanf/114052544

The Mended DrumTony Finch (@fanf@mendeddrum.org)2021 retro-link! https://nostarttls.secvuln.info/ - A security analysis of STARTTLS in email protocols.

Preventing enshittification of platforms rests on credible exit for users and devs. #ActivityPub and #SMTP are not perfect but

a) are implemented und understood by many players,

b) enable freedom of choice of servers and clients,

c) implement #RightToMigrate as well as self/community custody

Many #p2p projects promise to remove servers but often promote and depend on a single implementation stack, have no spec and no interop among #p2p islands, and thus struggle to provide credible exit.

Is SPF Simply Too Hard For Application Developers?
The Sender Policy Framework (SPF) is unloved by some, because it conflicts with some long-established SMTP email use cases. But is it also just too hard to understand and to use correctly for application developers? nxdomain.no/~peter/is_spf_too_
(2016 but still holds) #smtp #spf #mail #spam #antispam #security #openbsd #spamd

nxdomain.noIs SPF Simply Too Hard For Application Developers?

Following a recent discussion of email security over at Linkedin, I think perhaps my old but recently updated spam and malware countermeasures article is still worth reading if the subject is important to you - nxdomain.no/~peter/effective_s.

The reference section has pointers to a seemingly endless sequence of field notes related to these matters. The so far last entry is my New Year 2025 post "A Suitably Bizarre Start of the Year 2025" nxdomain.no/~peter/suitably_bi #email #smtp #spam #malware #security

nxdomain.noEffective Spam and Malware Countermeasures - Network Noise Reduction Using Free Tools

Here's an interesting question for you:
Can RFC 2047 encoded text in the Subject line of an email contain encoded line break characters (i.e.,, ^J, a.k.a. 0x0A)?
I don't think they should, because the point of RFC 2047 encoding is to encode non-ASCII characters which would otherwise be legal in the Subject line, not to encode characters which would otherwise be _illegal_, which includes line breaks.
RFC 2047 itself doesn't give a definitive answer.
What do you think?
#email #MIME #SMTP #SysAdmin