The sending domain is the e-mail address from which e-mails are sent. There are several recommendations on how your sending domain should be configured to minimize the risk of messages ending up in your spam folder or being blocked by spam filters.
From February 2024, both Gmail and Yahoo are introducing new verification rules that require sending messages from their own sending domain that has been authenticated.
Changes to Gmail and Yahoo mean that messages sent from addresses such as Gmail, Yahoo (or any other publicly available domain) cannot be sent via the site's bulk messaging servers.
Using free email addresses such as @gmail.com, @onet.pl, @wp.pl, @yahoo.com, @wp.pl, @interia.pl, @wp.pl, @o2.pl or @gazeta.pl in the sender field has always been inappropriate. This not only negatively affects your audience's perception of your brand, but may also cause your messages to be rejected by incoming mail servers or classified as spam.
The main reasons why you cannot send emails from a public domain
Inability to configure the domain according to DKIM, SPF and DMARC protocols. These mechanisms help verify that the sender is authentic and increase the chances of the message being delivered to your inbox.
Lack of care for the sending domain reputation. Make sure your sending domain has a good reputation. Regularly monitor your deliverability statistics, avoid spam, and respond to user complaints.
Public domains are not unique. The shipping domain should be unique and dedicated only to sending e-mails. Avoid using a primary domain used for purposes other than sending emails to avoid affecting the domain's overall reputation.
Need more help?
If you have any further questions about the deliverability, please do not hesitate to contact us at hello@edrone.me