What is email masking?
When an email is sent out on almabase, it is sent from special email id that looks like email@example.com, instead of firstname.lastname@example.org (which is the email that is listed on your profile page)
Why do emails need to be masked?
- Emails need to pass the DMARC test. Learn More
How do the emails look like to the receiver for one-to-one emails?
If an email is sent between 2 alumni, the receiver will see it in their inbox like this:
From: John Doe (email@example.com)
Reply to : firstname.lastname@example.org
The replies to this, are then automatically forwarded to the actual email address on their respective profiles (say, email@example.com)
This way, alumni can start conversations with others on the platform, without having to reveal their private email addresses.
What about bulk emails to an email group?
For bulk emails, any reply to the email will first come to firstname.lastname@example.org, and then be forwarded to Marcus' real inbox (let's say it is email@example.com)
In a similar manner, when Marcus replies to that email, it will first be sent to a masked email that was generated by Almabase for the author of the first reply.
Wait, so can anyone that has access to this masked email send an email to my alumni?
Not quite. when a reply or an email hits the Almabase system, the sender's email is looked up on your database. If no record has been found for that email, the email will not go through to the final recipient.
Eg: If someone named Greg tries to send an email to firstname.lastname@example.org ; almabase first checks for Greg's email on your almabase database.
If it exists - John will recieve the email.
If it does not exist - John will not receive the email. Greg will subsequently get an automated reply from Almabase stating that he does not have sufficient permissions to email John.