4 ms·
Have you, perhaps, not run a mail server? The limitation of SMTP/IMAP is that they're built with the assumption the connecting party can be trusted and acting
by gnabgib 3y ago
Have you, perhaps, not run a mail server? The limitation of SMTP/IMAP is that they're built with the assumption the connecting party can be trusted and acting in good faith (like many of the original protocols).
You can implement TCP rate limits on top, but that doesn't work when botnets and spammers (likely using "crowdsourced VPNs") rarely use the same IP twice. Further if you're running robust mail infrastructure (backup/fallback mail exchanges) communicating these limits/ reputations is left up to the operator (not supported by protocols, rarely supported by servers). I don't think MAPI/OWA/EWS is better, at all, especially not against open mail standards, but SMTP & IMAP don't cut it either. On a new server, it only takes a few hours before someone connects over IMAP and starts testing passwords against accounts (faster if the server is assigned to the MX or A of an existing domain, and valid emails might be known from hacks/cracks/dumps/leaks/people posting their email in their profile).
- brnt 3y agoWhat is a floss supercedant to IMAP that solves those things?