An external list in a filter is not your file.

Answer An external list in a filter is not your file. RFC 6134 describes a Sieve extension for testing externally stored lists. An outside list a filter consults is not the list you paid to mail. The document is RFC 6134, titled Sieve Extension: Externally Stored Lists. That is a fact about mail software or about an old specification. It is not a solo ad price, a rank, or proof that a stranger opted in. A rented send is one letter to someone else's list. A list that a filter happens to consult is not that someone, unless the order says so in words.

Cream stationery and a teal accent on a dark navy desk — The outside list is not the order.

The note that started this: RFC 6134, Sieve Extension: Externally Stored Lists, RFC 6134.

The extension lets a filter test a list stored outside the script. That is a convenience for people who run filters. It is not a solo ad. If you are about to buy solo ads, the file you are buying is the file the letter is sent to. Until an outside list is named on your order, it is not your file. Do not let the consultation stand in for the send.

The document does not make an outside list yours. A seller who says your names were checked against an external list has described a test. A test is not a mailing. Ask what file receives the letter. If they will not name it on the order, with a domain and a refund, the external list stays a filter detail.

What does RFC 6134 let a filter test?

RFC 6134 describes a Sieve extension for testing externally stored lists. An outside list a filter consults is not the list you paid to mail. The document is titled Sieve Extension: Externally Stored Lists.

Testing means the filter can ask something of a list that lives outside the script. The answer to that test matters to the filter. It does not, by itself, matter to your order. You paid, or you are about to pay, for a letter to a list. The list in the extension is whatever the filter was pointed at. Those can be different lists. Assume they are different until the seller identifies them as the same file, in writing, on the order.

Seller consequence: a customer thinks they bought the outside list, then asks for a send to it, and the seller only ever meant a test. Buyer consequence: money bought a consultation the filter performs, and the letter goes somewhere unnamed. Both outcomes come from using one phrase, the list, for two objects. On this desk, the list you paid to mail is the only list that counts. The external one is not that list unless the order says it is.

The order names the file that receives the letter.
An outside list a filter consults is not that file by default.
The sending domain is written next to the file.
The refund line follows the send, not the fact that a test exists.

Is that outside list proof someone opted in?

No. That is a fact about mail software or about an old specification. It is not a solo ad price, a rank, or proof that a stranger opted in. A test against an outside list is not consent.

A filter test answers a filter question. Consent answers whether a person asked for the mail. The extension does not record the second answer. A stranger does not opt in because their address was stored where a script could test it. If the seller offers the external list as proof of permission, they are offering a location, not a relationship. Location is not opt-in.

Do not ask the seller to blend files until a test looks clean, and do not accept a blended story as the product. You are not buying a procedure. You are buying one letter to a list you can name, or you should walk. A seller who can describe only the external store, and not who joined the file, has not shown permission. The specification will not show it for them. It describes a test. A test is not a signup.

What file should the order name?

A buyer still has to name the list, the sending domain, and the refund line on the order. The external list is not a substitute. Name the file the letter is supposed to reach.

Write that file so you could repeat it without the word external. If you cannot, you do not know what you are buying. Write the domain the same way, as a sender a recipient could recognize. Write the refund as the remedy when the letter is not that file on that domain. An extension for testing lists stored outside a script fills none of those lines. It only explains how a filter might look something up.

An external list in a filter is not your file. solo ad pricing belongs on a named send, not on a list a filter consults. If the seller cannot name the file, the domain, and the refund, keep the money.