A huge solo ad can be refused for size

Answer A mail server can refuse a message because it is too big. RFC 1870 defines the extension a server uses to declare a maximum size. A solo ad that carries huge images can die at that door. The refusal is about the file. It is not a report card on the list, and it is not a reason to buy a new list.

The note that started this: RFC 1870, SMTP Service Extension for Message Size Declaration, RFC 1870.

Designers build email like a webpage and then act surprised when a mailbox declines the package. The webpage sits on a host and sends a thumbnail. The email often embeds the art. Embedded art has weight. Weight has a limit, and the limit is allowed to be different at each server. Solo ad pricing that assumes every byte will be welcome is a price for a wish.

The specification is old and still ordinary. During the SMTP conversation, a server can advertise the largest message it is willing to take. The client can say how large the message is. If the message is over the limit, the server can refuse it before the rest of the content is transferred. That is a courtesy and a control. It keeps a giant file from clogging a queue. It also means your beautiful solo can be rejected by a machine that never evaluated the offer, the links, or the reputation. Size went first.

Can a mail server refuse a solo ad because of size?

Yes. RFC 1870 defines the SIZE extension. A server can declare the largest message it will accept, and it can refuse a message that exceeds that size.

You will not get a poetic bounce. You will get a refusal that means too big, if you get a bounce at all and if anyone reads it. The seller's platform may count the attempt in a way that flatters the send. Ask, before the date, what a size refusal looks like in their report. If they have never seen one, either their mail is light or they do not read the failures. Both facts are useful. Only one of them is comforting.

There is no universal maximum in this note, because the specification does not set one number for the whole internet. Each server declares its own. A blog that tells you the one true kilobyte limit is inventing a census. Ask the platform what it recommends, and then stay under the recommendation with room to spare. Room to spare is cheaper than a resend.

• The creative has a size in the draft, not only a look.
• Images are as small as the design can stand.
• A hosted image is still a risk, and an embedded image is still weight.
• A size refusal is recorded separately from a complaint.

Does a size refusal mean the list is bad?

No. A size refusal is about the message. List quality is about the addresses and whether those people asked for the mail. Do not let a seller combine the two into one excuse.

The excuse sounds like this. The mail did not land, so the list must be tired, so you should buy a second drop to a different segment. Sometimes the list is tired. Sometimes the message was a poster. You can tell those apart if the failure mentions size, or if a lighter copy of the same offer to the same kind of address goes through. A seller who will not try the lighter copy wants the second invoice more than the diagnosis.

Buyers do the mirror version. They blame the copy, then they add more images to make the copy look serious, and the message gets heavier. Serious is a sentence. A sentence is small. Add the picture only if the picture earns its bytes.

What should you ask about creative weight?

Ask for the approximate size of the submitted message, ask what the platform does when a receiver refuses it, and ask for a lighter version before the send date.

Approximate is fair. You are not asking for a byte-perfect forensic export. You are asking whether the draft is a page of text or a magazine. If it is a magazine, cut it before the scheduler starts. A lighter version in the folder is the contingency. When a provider refuses the heavy one, you already know what to send next, and you do not need a new theory about the readers.

RFC 1870 lets the server name a limit. Let the creative respect a limit you have not even seen yet. Size is a property of the file. Keep it there. The list has enough real problems without being blamed for a poster.