getSend Blog

Anonymous free and fast E-Mail service

• Why Your Text Arrives as Question Marks and Garbage
  Three symptoms, three causes – and only one of them can be repaired. How one character becomes two, why the subject has rules of its own, and what double encoding does.
• Unicode Addresses and Homograph Attacks: When Two Addresses Look Identical
  Cyrillic a and Latin a are indistinguishable. Why browsers solved this and mail clients did not, and why SPF, DKIM and DMARC raise no flag here.
• MIME: How Text, HTML and Attachments Fit Into One Message
  An email is a text file. The tree that turns it into a message with an attachment and an embedded image – and why a 15 MB file occupies 20 MB inside it.
• Why HTML Email Looks Different in Every Client
  There is no standard for how a mail client renders HTML. A support matrix across four clients, dark mode as the second fracture, and seven rules that follow from it.
• Message-ID, In-Reply-To, References: How a Mail Thread Holds Together
  A thread is not stored anywhere but reassembled from three headers. How that works, where it breaks, and what a sending system has to do about it.
• Why Your Confirmation Email Lands in the Promotions Tab
  The Promotions tab is not a spam folder but a sorting by markers. Eight of them compared, what can be changed in the build, and the one step to take if only one is possible.
• List-Unsubscribe: The Header Google and Yahoo Made Mandatory
  Where the unsubscribe button in the inbox comes from, why POST and not a link, four mistakes invisible in the result – and why it pays for the sender.
• What a Mail Server Checks Before It Accepts the Message
  Most unwanted traffic is refused before a single line of text is transmitted. Five checks, the error messages that go with them, and what follows for your own sending.
• Sending Invoices and Newsletters From Separate Subdomains
  Complaints about the marketing send land in the same ledger as the invoices. What the split looks like, how far it carries, and which DMARC setting turns quietly dangerous.
• Why a New Domain Delivers Worse: Reputation and Warm-Up
  Everything configured correctly and still in the spam folder. What receiving systems actually measure, what a warm-up looks like, and why recipient order matters more than volume.
• BIMI: The Sender Logo in the Inbox and What It Requires
  Five steps, four of which have nothing to do with the logo. What BIMI demands, what a certificate costs, who displays it – and why the logo is not a security signal.
• Reading DMARC Reports: What the XML Files Actually Say
  The daily ZIP attachments answer a question nothing else can: who is sending mail under my name? The structure, one record in the original, and the order of work that succeeds.
• MTA-STS and DANE: Enforcing Encrypted Delivery Instead of Hoping
  SMTP encryption can be switched off from outside without anyone noticing. Two mechanisms end that – compared, with the records and the reporting channel you need alongside.
• Why Forwarding Breaks SPF and DKIM – and What ARC Changes
  Every forward breaks SPF, because a different server does the sending. DKIM survives as long as nobody touches the text. What SRS repairs, what ARC does and where its limit lies.
• SPF Passes, DMARC Fails: The Alignment Problem
  SPF can pass and DMARC still fail. The reason is the two different sender addresses every message carries – and whether their domains match.
• Four addresses, 80 percent of the mail: how unevenly an open mailbox is filled
  1930 archived messages to 89 addresses from the years 2014 to 2016: four addresses got 80 percent of the mail, 54 got exactly one, and for 70 it was over in a day.
• Why clicking unsubscribe on spam can make it worse
  With legitimate senders the unsubscribe link is mandatory and works. With real spam it only confirms your address is being read. How to tell them apart.
• Plus address, alias, forwarding, disposable: four ways compared
  Four methods of not handing over your real email address — with their strengths, limits, and when each one is the right choice.
• Why PDFs and Word files are not harmless
  Every filter blocks executables. Today's dangerous attachments are the ones that look ordinary. What can hide inside PDF and Office files.
• Catch-all: how one domain accepts unlimited addresses
  Addresses nobody had to create in advance. How a catch-all mailbox works, what it is good for, and the drawbacks that come with it.
• How your email address ends up in a data breach
  From sign-up to traded list: the routes by which addresses leak, what attackers do with them, and what you should do afterwards.
• Why some sign-up forms reject temporary addresses
  "Please enter a valid email address" — although the address is valid. How providers detect disposable addresses, why they do it, and what you can do.
• Tracking pixels: how senders know you opened the email
  An invisible image reveals the time, your device and roughly where you are. How it works, what senders read from it, and how to switch it off.
• Why email is not end-to-end encrypted
  TLS protects the route, not the content. What that means in practice, what PGP and S/MIME achieve, and why neither ever caught on.
• reCAPTCHA: what it checks and what it cannot do
  How Google's captcha spots bots, why it does not stop human abuse, what it means for data protection, and which alternatives are worth a look.
• Spotting phishing: eight patterns that keep coming back
  Time pressure, near-miss sender addresses, links that go somewhere else: the patterns that make fraudulent email reliably recognisable.
• When a temporary email address makes sense — and when it does not
  Disposable addresses protect you from spam and tracking. For banking, government and anything you want to keep, they are the wrong tool. An honest boundary.
• Why the first email sometimes takes a minute
  Greylisting, queues and polling intervals: the three reasons a message is not there instantly — and why the delay is usually deliberate.
• What actually arrives in an open mailbox
  We analysed the mail that reaches us: 181 messages, one sender domain, one subject line, five hours. What that says about how spam really works.
• How we prevent abuse on getSend
  Review before delivery, blocked aliases, banned file types and fixed retention periods: what getSend actually does against spam — and where the limits are.