The name on the mail
Before a Geenius Newsletter publication can send, it needs a sender name, a legal name, a postal address and a contact email. The domain check only reads DNS.
Readers should be able to see who wrote to them. Geenius Newsletter will not schedule a first send until the publication says who that is.
What has to be filled in#
Four fields, all of them on the publication:
- The name readers see as the sender.
- The legal name.
- A postal address.
- A contact email.
A reply-to address is optional. If you set one, it has to be an email address.
The domain is checked, not edited#
Issues are meant to leave from your own domain. You add the domain and run the check. It looks up SPF, DKIM and DMARC and shows a record that is missing. It only reads DNS. It does not change your DNS.
During early access that check does not open a real send. No mail provider is connected for production, and sends run in test mode.
Why the app is strict about it#
Readers decide in a second whether a mail is from someone they know. A clear sender name helps them, and the postal address and contact are what European rules ask of a newsletter anyway. So the app treats these fields like the content: the checklist before a send shows a red line while one is missing, and the send button stays off.
You fill them in once per publication, not per issue. If you publish under a company, the legal name is the company; if you write as yourself, it is your name. Your own AI can fill them in through the door, but it cannot send, so a person still sees the result before anything leaves.
A test is not the send#
Before you approve, send a test to yourself. It goes only to the address of the signed-in account, at most five times an hour, and the app records that you sent it. Your own AI cannot approve the issue or schedule the list.
The fields are listed again in Sender identity.