danisflow.online

You saw a connection from us. Here is what it was.

If your logs show 78.138.0.182 or a HELO of probe.danisflow.online, it was an address verification check against your MX. It issued RCPT TO and then QUIT. It did not issue DATA, so nothing was delivered and there is no message to find.

Common log lines, explained

What you sawWhat it was
A session that ended after RCPT TO Normal and intended. The answer to RCPT TO is the entire purpose of the connection.
Two connections close together from the same address The first offers one deliberately invalid local part to find out whether your server accepts every address; the second checks the real one. See address verification.
MAIL FROM:<> with an empty sender The null reverse-path from RFC 5321 §4.5.5. Used because it cannot be replied to and cannot deliver.
Something else entirely, claiming to be us Not us. Our only host and address are listed on the infrastructure page. Please tell us.

To stop it

Any of these work, and none of them need our cooperation. We do not attempt to work around a block, and we do not change addresses to evade one.

A request to stop is not negotiated. We would rather lose a domain than argue with the person who runs its mail server. If you have asked and it continues, that is a fault on our side and we want to know: postmaster@danisflow.online.

If a person at your domain was written to

Verification and outreach are separate systems on separate domains. Messages come from danisflow.com, and every one carries an unsubscribe path. For removal of a person's details from our records altogether — not just from mailings — see data and removal, which is the request with teeth.

Reaching a human

Abuse reports, block requests abuse@danisflow.online
Technical questions, misconfiguration postmaster@danisflow.online

Both are read by a person, not a ticket queue that closes itself.