Happy new year everyone. We fixed a bug in our SPF instruction where the copy data is different from the displayed one Thanks to Sergi
One of use case of email forwarding is to have unlimited alias and hide your real email so no one can spam you. When a service started to send you to many emails, you can blackhole an alias to stop receiving email on that. Recently, we rolled out sieve filter so advanced user can write sieve filter to drop spam. Currently, the sieve filter is limited and only support spam definition
We have been accidently forward email twice
Tweak alias API
Up until now, the destination email in an alias rule is static. But what happen if you want to do dynamic forwarding? Such as simply change the domain by keep the same email address. We support that now with a simple `*@domain.com` in the destination.
We have onboard a few users that were superfulp and give userful feedback and point out the bug and error in the system. Much thanks to Filippo for many bugs reporting. Much thanks to Daren for all the works to help correct the typo and grammar. Customers like you made the service survive.
We rework our webhook log viewer so you can load more responses now. It has only last 20 requests limit before.
Up until now, to debug email delivery an user has to navigate through the maillog or inbox page by page. Today we release a search functionality to make filtering out email easiser. Head to maillog or Inbox simply enter a term in the search box to find all email has from/to/subject contains that query.
Big release that let Mailwip talk to Cloudflare API use your API key and can help you manage/update DNS record easiser. Read <%= link_to t("our document to activate this feature"), "/" %>
Mailwip power is its frienly UI/UX to manage multiple domains at a time. We release a few updates to make this easiser for users with lots of domains.
Improve our UI to make it more consistent among pages/screens. Also, to guarantee a best experience we added a safe-guard to only allow generate SMTP credential once DKIM is configured.
Make it easy to delete all domains that are missing DNS(in not ready status) with one click. It's very useful for users with many domains and don't want to delete expired domains one by one.
Beta support for IMAP is rolled out. We're actively improve it but it's one more steps to make email forward easiser for our user.
At Mailwip, we move fast and focus more on the email forwarding side to make our core feature which is email forwarding super fast and amazing. Due to the size of our team, we didn't have time to focus on the accounting aspect of the site. For awhile, we didn't have the ability to view invoices directly in the dashboard. We usually email the receipt to our user but they cannot view it in dashboard. We now support exactly that so our customers can view/download/print their invoices . Head over to Mailwip dashboard to see your invoice
We already supported bulk import but if user has many domains, we don't have a way to do batch delete yet. Our users have to rely on the API to delete domains. We hear you, and add ability to do batch delete domains right from our UI
We made maillog way faster like 10x faster. No longer have to wait a few seconds. it should load immediately
Big day for our API users. We address a pain point of customers with lots of email and have to manually delete them one by one. We made this easiser for you now with a single API call to remove domains from your account.
Big Release for users that leverage our maillog/inbox. We make it faster, easiser, and better.
Big release. We supports API to manage alias now so you can dynamically provision an Inbox. Head to our api docs for detail. Web Reply are available to pro/business user now.
We rolled out MFA to protect your account with another layer of security. Head to your profile > Security > Enable MFA to activate this feature.
We release our first API endpoint. You can now literally fetch your email with a REST API using `curl` :-)
We release Inbox, a place to view maillog for all of your domains.
Fine grain control of log level on maillog. You now can chooese what to log: meta data, subject and body of email. Refer to our email forwarding log
We release a small tools to help our customers check their DNS record(MX/SPF easier). We plan to release more of those small utils for free. This helps to check DNS to make sure email forwarding is properly setup.
We roll out Emoji domains a few days ago and at first we have to use punycode to enter. That's fixed now. Long live emoji. Now you can forward email from emoji domain.
Consistenly order alias chronologically to help customer with a lot of alias sort through them easier
Improve webhook integration.
Add DKIM Signing for SMTP
SMTP server is release. Our user can send out email using Mailwip smtp server for faster delivery and get rid of the ugly "Via mailwip.com" text in gmail.
Emails are hard. An email can be plain text, html, utf8, base64, multile parts, each part with different encoding...That's why we're to serve you :-).
We release a free service to show of our webhook feature at pix.fastloop.xyz. Give it a try and let us know what you think.
Added email notification to let us know once a domain is ready. MX records usually have high TTL and take a bit long for DNS propagation to be done. We added an email notification to let our customers know once a domain is ready in order to save them a round trip to our dashboard to check on the domain status.
A few beta testers love webhook. Before this, every email triggers webhooks but a few users said they only wanted to fire webhooks for a specific email address. So we added that. We can filter out what email will hit webhook. Try it out and let us know how you think.
At Mailwip, we think email should be fun. Thus we introduced webhook feature. Every time we receive an email, we parse the email into a nice JSON document, and post to your webhook HTTP endpoins. What can you do with it? Well, how about "Sending an email to turn on your light?". Not a practical usage, but hey, it's fun. Let us know what you come up with for webhook usage. For us, we are using this webhook to power a comment system which we will soon release to the world.
This is where we start adding changelog. However, our system has been used since November 2020. This is because we gotta start from somewhere, and when we started building this, we focused on other aspects and didn’t have time for changelog.