Custom "From" addresses for Email-In replies enabled     

• We've now enabled the use of custom "From" addresses for Email-In replies. Both confirmed organization email addresses and the email addresses you use to sign in to Bigin will be automatically available as "From" addresses in Email-In. This eliminates the previous limitation that restricted replies to email aliases ending with biginmail.com.
  
• Any emails sent to a custom email address, such as support@zylker.com, can be made available for Email-In by forwarding them to an email alias—for example, support@zylker.biginmail.com.
  
  However, if you attempt to reply to the received email within Email-In, it will be sent using the email alias support@zylker.biginmail.com, potentially causing confusion for the receiving party, as they might expect the reply to come from support@zylker.com. The custom "From" addresses we've introduced solve this problem by allowing you to use the custom email address (added as the organization's email) as the sending email address. 
• The email is still sent through Email-In, but with the custom 'From" address set to the organization's email.
  
• Once the above process is done, you can validate the domain using SPF DKIM keys.
  

Enhancements to Email deliverability

What issue are we addressing? 

Changes made  

• The "Add Domain" button has been removed from the Email Deliverability page. Domains are now automatically included on the Deliverability page, eliminating the need for manual addition.
  
• The "Delete Domain" button is no longer available on the Email Deliverability page, streamlining the domain management process.
  
• The custom domain email addresses that users use to sign in to Bigin will now be displayed on the Deliverability page by default, improving visibility and usability.
  

How do we plan to address this? 

For example, if you want to use a specific domain only for sending emails from Email-In, you can validate that domain for the Email-In server only. Unverified email domains are marked with a red alert icon.

Email authentication involves a two-step process:

1. Automatic domain addition
   
2. Domain validation

• Email Deliverability
  
• Email-In

Notes 

• The maximum domain count has been raised to 20 for both trial and paid plans.
  
• Starting on January 30, any organizational emails that have not been validated will be unable to send emails.