Turkeuro
Roadmap · 07

Admin approval before mail is sent

This is a future plan. Admin approval before mail is sent is not available in the mailbox today. A message you send now leaves as the message you sent. Nothing waits for an admin.

What it is

The plan would let a business admin hold outgoing mail until they allow it to leave. A person in the company would finish the message. It would wait. The admin would allow it, or send it back. Until it is allowed, it would not go out. The point is a pause on the company mailbox, for a company that wants a second pair of eyes on what leaves the address.

It is for that admin, and for the person who writes the message and needs to know it has not gone yet. It is a business control. It is not a control on a personal mailbox that has no admin, and it is not a way for Turkeuro staff to read a private letter and decide whether a person may speak.

The message that leaves would be the message the writer finished, if the admin allows that message. The plan is an allow-or-return gate. It is not a hidden editor that substitutes different words and sends them under the writer's name.

How the logic would work

The writer would address the message and write it in the usual way, then hand it to the queue instead of to the outside world. The queue would belong to the company mailbox the admin is responsible for. A message from an address the company does not administer would not enter that queue. The gate has a boundary, and the boundary is the company mailbox.

The admin would see the waiting message, including the recipient and the words. They would allow it, and then it would leave, or they would return it to the writer with the reason they are willing to write down. Returning it would keep it inside the company. Allowing it would send the message the writer prepared. Neither choice would invent a third version of the letter.

The writer would see the waiting state the whole time the message has not left. They would not be told it was sent if it is still in the queue. If the admin returns it, the writer would see that, and they could change it and hand it back. Silence is not an approval. Only an allow sends the message.

A company that does not turn the gate on would send mail the way the mailbox sends mail. The plan would be a choice for the business mailbox, not a new rule for every Turkeuro address on earth.

What you would see

The writer would see their finished message marked as waiting, with the recipient still visible, and with a clear line that it has not left. They would see when it is returned, and they would see when it has been allowed to go.

The admin would see the queue: who wrote the message, who it is addressed to, and the words. They would see an allow control and a way to send it back. They would not see a box that rewrites the letter into a different letter and presents the rewrite as the original.

Today neither person sees a queue. The writer sees the ordinary send control of the mailbox. The admin, if they are only another account holder, sees their own mailbox and not a company approval list.

What it would not do

It would not hold mail the company does not administer. A personal address outside that business is not in the queue. It would not let an admin send different words under the writer's name without the writer seeing that the words changed. The plan is allow or return.

It would not notify the recipient that a message is waiting. The recipient either receives the allowed message or does not receive it. A half-sent letter is not a product feature. It would not apply to mail the company receives. Incoming mail is a different problem. This plan is about what goes out.

It is not built. There is no approval setting in Login settings, and business plans do not include a queue you can turn on.

What is available today instead

Outgoing mail leaves when the person sends it. The mailbox on Postfix, Dovecot, and SnappyMail does not park it for an admin. If you are signed in, you are the person who sends.

A company chooses a business plan for the address it wants. That choice does not add an approval step. The admin described on this page does not exist in the product yet.

What you can use today is a mailbox on Postfix, Dovecot, and SnappyMail. You sign in with a password. The account can hold a 41-character Turkeuro account code that starts with turkeuro, a two-factor choice, an authenticator, and email as a verification choice. Those second-factor choices are saved with the account. They are not asked again at sign-in. The connection uses TLS. Login settings hold the sign-in controls for the mailbox you have open. There is a Windows desktop app. Business plans are listed at https://turkeuro.com/business.

SMS sends nothing. A mobile number saved on the account does not produce a text message from Turkeuro. The unlock choice in Login settings does not lock the screen. Those are limits of the mailbox as it is. They are not a quiet version of the plan on this page.