![]() |
5 år sedan | |
---|---|---|
app | 5 år sedan | |
bootstrap | 6 år sedan | |
config | 5 år sedan | |
database | 5 år sedan | |
public | 5 år sedan | |
resources | 5 år sedan | |
routes | 5 år sedan | |
storage | 6 år sedan | |
tests | 5 år sedan | |
.editorconfig | 6 år sedan | |
.env.example | 6 år sedan | |
.gitattributes | 6 år sedan | |
.gitignore | 6 år sedan | |
.php_cs | 6 år sedan | |
.prettierignore | 6 år sedan | |
.prettierrc | 6 år sedan | |
LICENSE.md | 6 år sedan | |
README.md | 5 år sedan | |
artisan | 6 år sedan | |
composer.json | 5 år sedan | |
composer.lock | 5 år sedan | |
package-lock.json | 5 år sedan | |
package.json | 5 år sedan | |
phpunit.xml | 6 år sedan | |
server.php | 6 år sedan | |
tailwind.config.js | 6 år sedan | |
webpack.mix.js | 6 år sedan | |
yarn.lock | 6 år sedan |
This is the source code for self-hosting AnonAddy.
AnonAddy is short for "Anonymous Email Address". The word "Addy" is internet slang for email address, e.g.
"My email addy is being spammed. I should've kept it private."
I made this service after trying a few other options that do a similar thing. I was really interested in how they worked and loved the thought of protecting my real email addresses from spam.
I also wanted to address some issues with other services such as:
I made the code open-source to show everyone what was going on behind the scenes and to allow others to help improve the application.
I use this service myself for the vast majority of sites I'm signed up to.
There are a number of reasons you should consider using this service:
No I definitely do not store/save any emails that pass through the server.
Yes you can use your own domain name so you can also have *@example.com as your aliases. To do so you simply need to add an MX record to your domain so that our server can handle incoming emails.
Here are a few reasons I can think of:
Yes there is an open-source browser extension available to download for Firefox and Chrome (also available on other chromium based browsers such as Brave and Vivaldi). You can use the extension to generate UUID aliases remotely.
On the recipients page you simply need to click "Add public key" and paste in your public key data. Now all emails forwarded to you will be encrypted with your key. You should also replace the subject line of forwarded messages in your account settings as this cannot be encrypted.
Yes attachments are part of the email body and are also encrypted if you have it enabled.
Yes when you have encryption enabled all forwarded emails are signed using our mailer@anonaddy.me private key.
You can add this key to your own keyring so that you can verify emails have come from us.
The fingerprint of the mailer@anonaddy.me key is "26A987650243B28802524E2F809FD0D502E2F695" you can find the key on https://keys.openpgp.org.
If you're concerned that your aliases are all linked by your username e.g. @johndoe.anonaddy.com, then you have a couple of options:
The server is located in Amsterdam, Netherlands with Greenhost.net. Greenhost focuses greatly on privacy and security and their servers run entirely on Dutch wind energy.
It's good to keep your guard up when online so you should never trust anyone 100%. I'll try my best to be as honest and transparent as I can but if you still aren't convinced you can always just fire up your own server and self-host this application. You'll need to know about server administration and PHP. I'll be adding more details on how to do this soon.
The limit is currently set to 10 which should suffice in the vast majority of situations.
When you delete your account the following happens:
Yes this will work with any provider, althought I can't guarantee it won't land in spam initially.
No, your real email will not be shown, the email will look as if it has come from us instead. Just make sure not to include anything that might identify you when composing the reply, i.e. your full name.
Yes you can add attachments to emails forwarded and replies. Attachments count towards your bandwidth.
The max email size is currently set to 10MB (including attachments).
If you cancel your subscription it will remain active until the end of your current billing cycle, you will still be able to use Pro features until the billing cycle ends.
A few days before your billing cycle ends you will receive an email letting you know the steps you need to take to prevent the loss of any emails. Shortly after ending the following will happen:
You will not be able to activate any of the above again until you resubscribe.
The following is in place to help prevent spam:
The server is running a local DNS caching server to improve the speed of queries. DNS.WATCH resolvers are used as a fallback.
Not unless you are really going to town. Each user is throttled to 200 emails per hour through the server.
Currently you are limited to creating 10 new aliases per hour on the free plan and 50 per hour on the pro plan. If you try to create more than this the emails will be deferred until you are back below the limit.
Each time a new email is received Postfix calculates its size in bytes. A column in the database is then simply incremented by that size when the email is forwarded or a reply is sent. At the start of each month your bandwidth is reset to 0.
I don't use rolling 30 day total as the only way to do this would be to log the date and size of every single email received.
Blocked emails do not count towards your bandwidth (e.g. an alias is inactive or deleted).
The average email is about 76800 bytes (75KB), this is roughly equivalent to 7,000 words in plain text. So the 10MB monthly allowance would be around 140 emails and the Pro plan's 500MB would be almost 7,000 emails.
If you get close to your limit you'll be sent an email letting you know. If you continue and go over your limit the server will start discarding emails until your bandwidth resets the next month.
You can add up to 3 additional usernames as a Pro user for a total of 4 (including the one you signed up with). You can currently only login with the one that you originally signed up with.
Please make sure to add mailer@anonaddy.me to your address book and check your spam folder. Make sure to mark emails from us as safe if they turn up in spam.
If an alias has been previously deleted and you try to send email to it, the emails will bounce with an error message - "554 5.7.1 Recipient address rejected: Access denied".
Check that you have not deactivated the alias, custom domain or additional username. When any of these are deactivated, emails will be silently discarded, they will not bounce or return any error message.
The sender of the email may be failing SPF, DMARC or DNS blacklist checks resulting in the email being rejected. The sender should also have correct reverse DNS setup and use a FQDN as their hostname.
If you still aren't receiving emails please contact me.
I am very passionite about this project. I use it myself everyday and will be keeping it running indefinitely.
Yes it has over 130 automated PHPUnit tests written.
You will need to set up your own server with Postfix so that you can pipe the received mail to the application. You can find more information here https://github.com/anonaddy/anonaddy#self-hosting.
My name is Will Browning, I'm a web developer from the UK and an advocate for online privacy and open-source software. You can find me on Twitter although I don't tweet that much!
For any other questions just send an email to - contact@anonaddy.com (5FCAFD8A67D2A783CFF4D0E31AC6D923E6FB4EF7)
In /etc/postfix/master.cf you need to make sure it has this at the top:
smtp inet n - - - - smtpd
-o content_filter=anonaddy:dummy
This should be the only line for smtp.
Then add this these lines to the bottom:
anonaddy unix - n n - - pipe
flags=F user=youruser argv=php /path/to/your/webapp/artisan anonaddy:receive-email --sender=${sender} --recipient=${recipient} --local_part=${user} --extension=${extension} --domain=${domain} --size=${size}
Making sure to replace youruser
with the username of the user who will run the artisan command and also to update the /path to your installation.
This is what will pipe the email through to our applicaton so we can determine who the alias belongs to and who to forward the email to.
More instructions to follow soon...
Thanks to https://gitlab.com/mailcare/mailcare and https://github.com/niftylettuce/forward-email for their awesome open-source projects that helped me along the way.
The MIT License (MIT). Please see License File for more information.