Our website works on any device, mobile/tablet/desktop – and we have an alias manager even for folks that don’t have a custom domain of their own. You can use any of our vanity domains (e.g. you@hideaddress.net).
The interface is extremely simple to use:
Screenshot:
“Storage is shared across all of your domains and aliases, but you can impose limits if desired on a per domain and alias basis.”
Is there a guide on how to set a limit on a alias? I been looking but can’t figure out how to do it.
Yes, you can edit domain-wide limits on our website under Settings for a domain – and if you’re a domain admin then you can also set per-alias limit under Edit Alias or Create Alias.
Our API also supports setting max_quota_per_alias on a domain and max_quota on an alias, see our API documentation at https://forwardemail.net/api for more insight.
We use bytes to parse the values – which means you don’t need to manually convert 1 GB to bytes, you can simply enter 1 GB (it’s human-friendly and dummy-proof). There is also validation in place to ensure that alias-specific values do not exceed domain values.
We use pooled storage (unlike many other providers) – which is great for users that use our service for families and groups. This means you can have a limit domain-wide of 10 GB, and then, for example, enforce a 2 GB limit across all members of your household. This is also useful for organizations in case of a malicious or rogue employee that attempts to flood storage across the entire domain.
Email notifications automatically go out when various storage thresholds are reached of 50%, 60%, 70%, 80%, 90%, and 100% (to alert you in advance) – and at anytime you can view storage thresholds in real-time from My Account → Domains → Aliases.
Screenshots:
My Account → Domains (shows you real-time pooled storage usage across all domains on your account)
My Account → Domains → Aliases (shows you real-time pooled storage usage across all aliases for a given domain on your account)
My Account → Domains → Settings → Storage Max Quota Per Alias
My Account → Domains → Aliases → Edit Alias (or Create Alias)
Yes, we plan to eventually make all of our vanity domains such as @hideaddress.net, @mailsire.com, @hash.fyi, and some awesome other TLD’s (including a 2 letter domain name we own) available to the public. This means we’ll not only have forwarding/disposable addresses available on those domains, but we’ll also support IMAP/POP3/CalDAV (which means you won’t need to bring your own domain to use our service as a complete replacement). Hopefully sometime later this year or next we will be able to roll this out. This means we’ll be a replacement for normal everyday Gmail and Proton Mail users that don’t want to buy and maintain a domain name registration.
Hi folks and happy new year! 
To keep you folks apprised, here’s a brief update!
We’ve recently optimized and refactored the entirety of our MX server in our codebase and merged it into our GitHub monorepo. This means our code is way more maintainable and easier for community contributions. We’re also actively working on self-hosting (@shaunw is leading that effort) and have made a lot of progress (e.g. think 1-click deploy). As of today, we’re still the only 100% open-source email provider.
We’ve released two highly-requested features in the past few weeks:
All messages now (including forwarding) support OpenPGP/WKD. This means IMAP and forwarded emails support PGP encryption. Note that since Proton Mail rewrites your emails, we do not support PGP encryption for Proton Mail and it is explicitly disabled in our codebase, see https://github.com/forwardemail/forwardemail.net/blob/ce46d825d9963c90a026f93fddaec2630109a7dd/helpers/send-email.js#L225-L244 for insight. If we did not go with this approach, then a banner would appear in your Proton Mail inbox warning you about the message (since they rewrite headers, see 1, 2, 3, and 4 for more insight).
We also released our vacation responder 
(e.g. out of office auto-reply) feature, see https://x.com/fwdemail/status/1876802495659249698 for more insight. We use this feature ourselves in order to send an automated reply whenever someone emails support@forwardemail.net.
We’re still working on our whitepaper and hope to release it this year – and then conduct 3rd party security audits afterwards.
Currently we are transitioning our infrastructure to a new data center with bare metal hardware (think 10 new servers running blazing fast AMD powered hardware ). Over the next few weeks we’re warming up those IP addresses and will be introducing them.
Our plan is to move away from Vultr and Digital Ocean completely (or as much as possible). This new data center is powered by DataPacket, which are the same folks that power Mullvad – and a company we take inspiration from.
We put an extensive amount of R&D time and effort into our new infrastructure. We focused down to the hardware and on performance, e.g. AMD processors which are incredibly performant for single-core apps running Node.js (single-threaded). We also have lightning fast NVMe SSD drives with LUKS encryption 
and multiple upstream connections running to the servers. A lot of time went into benchmarking, cost comparison, and reliability comparison. For some insight, we also explored:
We’d love to go into more detail, but we’re a small team & limited on time! 
Happy new year,
Forward Email
https://forwardemail.net
Hi folks Sharing a massive performance update we’re releasing this evening…
We’re boosting server performance with file system I/O reads between 179–573%+ faster and seeing writes at least 215%+ faster!
Learn more (and see the benchmarks before vs. after) at https://x.com/fwdemail/status/1889440529647280580
You can now opt-in to our newsletter at https://forwardemail.net/my-account/profile?newsletter=true and follow us on 𝕏 at https://x.com/fwdemail.
Links added in our navbar and footer:
Our newsletter will announce new features and product updates. We’ll still try to post new features here, but that will be a much better place to opt-in for folks.
We also have a new rudimentary RSS feed you can subscribe to with your reader:
Announcing Email Analytics! 
At a glance you can gain insight into:
Account/domain deliverability
Inbound/outbound traffic (250)
Soft bounces (4xx)
Hard bounces (5xx)
Viruses/spam blocked
The best part?..
Past 30 days of activity = no extra cost! 
Screenshots:
𝕏 post at https://x.com/fwdemail/status/1892482854044447210
Thanks!
Logs now appear in real-time now (as opposed to a 5-30m+ delay). You’ll also get more logs too 
+ analytics/logs are snappy + instant (thanks to indices) 
tldr; rewrote a lot of our log stuff (which is built on our work from Cabin & Axe)
https://github.com/cabinjs/cabin
𝕏 post (+ video) at https://x.com/fwdemail/status/1895291166515675544
I created an account and configured two of my domains to test it out, and today I got two emails (I imagine one for each domain) in the email of the forwardemail account I registered with. These emails were in German (I’m not from Germany) about some kind of delivery being dispatched.
Was the email I used to register sold or was there a breach of some kind? It’s from ForwardEmail for sure because I got these emails on an alias I only used for ForwardEmail
EDIT: weird because they didn’t send it to my email directly, but they used the Addy syntax. The email was sent by notification@dpd.ch to forwardemail+thomas=<domain-registered-in-fe>@<my-addy-account>.addy.io instead of forwardemail@<my-addy-account>.addy.io as it would be normal.
@forwardemail that is nice
Is this yours website as well? It’s strikingly similar to ForwardEmail.net: https://improvmx.com
I don’t think so.
No. ImprovMX has also just changed hands in a small acquisition (and by a relatively unknown party) for the 3rd time. Additionally, they are completely closed-source on the back-end (and front-end) – just like everyone else including Privacy Guides’ current recommended email services… To this day we’re still the only 100% open-source provider.
Hi folks, another product update!
Ever use 
CalDAV/iCal/Calendar clients and experience duplicate calendar names?
Problem solved
We’re the first service to normalize + localize (i18n) + dummy-proof CalDAV (w/support for iOS/macOS edge case detection) across all platforms. 
𝕏 post at https://x.com/fwdemail/status/1902565786717241403
Ref: https://github.com/forwardemail/forwardemail.net/commit/7461352155984df5641428700e61fd3a0f36e5ea and https://github.com/forwardemail/caldav-adapter/releases
While we’re working on webmail/audit/carddav/etc – in the interim, we thought we’d share a new repository we made on GitHub which answers this popular question…
“Who do you recommend for a mail server provider?”
https://github.com/forwardemail/awesome-mail-server-providers
Feel free to give it a 
on GitHub!
𝕏 post https://x.com/fwdemail/status/1906996674129449293 and https://x.com/fwdemail/status/1907234197003173904
Announcing 4 new blog posts with insight into different parts of Forward Email
Feedback welcome, these are all on GitHub and open source Markdown files.
We now support crypto payments!
Privacy upgrade! Forward Email now accepts crypto payments via @stripe powered by @ethereum, @solana, and @0xPolygon networks.
Connect with @MetaMask, @phantom, @coinbase, and @WalletConnect and keep your financial identity separate from your email.
I can’t believe that you guys supported all shitcoins and didn’t support the only useful and anonymous cryptocurrency Monero.
Why Crypto Payments Matter
- Maintain greater anonymity when purchasing our email services
But then you admit that the only supported shitcoins have transparent blockchain which means that they are “pseudonymous” and not anonymous. And you are using Stripe as crypto payment processor which is not a private method. I already suggested a reliable, open source and private/anonymous way to accept crypto for businesses.
