-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Would you be interested in tailoring this guide for use with Forward Email's free plan? #3
Comments
Definitely interesting. How do you imaging this would work? Like adding a section in the docs with recommendations and a tutorial on how to set it up? |
Note you can't forward without bringing in your own domain, or you can get vanity domain at 3$/month from these guys iirc. |
@securitybrahh Correct, you should bring your own domain name, but we do offer one of our own if you pay $3/mo. It's cheaper to use us on the free plan with your own domain name (e.g. $3*12=$36, and most domains cost ~$5-10/yr – and it's encouraged vs. using ours actually). You should own your presence on the Internet and not be tied to a single provider for life. |
Any provider you like that is reliable + nokyc? (Always looking for new such domain registrars 😋) |
@securitybrahh use https://namecheap.com and |
@securitybrahh also we offer coupon code |
Haha I'm glad this repository is an official support channel now haha ;) |
Hello @AnandChowdhary and hope you are doing well.
I'm sure you may have seen our service @forwardemail at https://forwardemail.net (since we were contributors to Upptime Monitor 😄, e.g. dark/light mode, and more; https://status.forwardemail.net).
Curious if you would be open to tailoring this guide to work with the free plan at https://forwardemail.net?
Recently we added the support of encrypted TXT records on the free plan, so that you can keep your forwarding configuration private from public DNS records.
See https://forwardemail.net/en/faq and the page to encrypt TXT records at https://forwardemail.net/encrypt.
The text was updated successfully, but these errors were encountered: