forwardemail / free-email-forwarding Goto Github PK

534 5.7.9 Please log in with your web browser and then try again. Learn more at https://support.google.com/mail/?p=WebLoginRequired q3-v6sm2883638qkf.77 - gsmtp

forward-email gmail sendAs feature stopped working today. I can't send email anymore and did not touch anything.

I tried to generate a new app password and the update it in gmail (the password field) but I get a Authentication failed.

Any idea what is going on?

forwarding multiple emails
forward-email=hello:[email protected],support:[email protected]

If I would add this ->
forward-email=hello:[email protected],support:[email protected], [email protected]
would the last entry be a catch-all?

Hi,

I followed all steps on https://forwardemail.net/#/?id=how-it-works, everything is working fine when sending emails from gmail or other services but I can't send emails from hotmail and outlook...

• SPF record:(TXT): v=spf1 a mx include:spf.forwardemail.net ~all
• hosted on netlify.com with netlify-dns

outlook postmaster reply:
The message was rejected because of Sender Policy Framework violation -> 550 Please ensure the email service you are sending from either has SPF, DKIM, or is a top-ranked <30K Alexa.com domain. You can most likely resolve this problem by searching on Google for "$serviceName SPF DKIM setup" (be sure to replace $serviceName with your email service provider, e.g. "Zoho"). If you continue to have issues, please see https://forwardemail.net or file an issue on GitHub at https://github.com/niftylettuce/forward-email. We'd be glad to help out! -- @niftylettuce If you need help with email-forwarding setup or troubleshooting please visit https://forwardemail.net

As an example, forwarding [email protected] to a service desk. I've tried the following setup:

and

But this isn't working.

Please implement the ability to have a default destination mailbox

domain to be foward: example.com

TXT = forward-email=a:[email protected],b:b@gmailcom,[email protected]

Please, notice the [email protected] is the default mailbox on the domain forward configuration
So, any account that does not match to the ones listed on the TXT entry could be forward to the domain default mail address (almost like ALL EMAILS TO THE DOMAIN).

User Cases:
email to [email protected] will be forward to [email protected]
email to [email protected] will be forward to [email protected]
email to [email protected] or [email protected] they all will be forward to [email protected]

I've followed to tutorial stated on forwardemail.net, but whenever I try to send an email, I get this error: 550 Invalid forward-email TXT record. Did I do something wrong?

Records:

We'd need to enable AUTH command and add onAuth option via https://nodemailer.com/extras/smtp-server/#handling-authentication. Perhaps we only allow sending mail as from Gmail for now?

https://github.com/srijs/node-clam-engine

Via https://www.intra2net.com/en/support/antispam/index.php_sort=accuracy_order=desc.html and https://github.com/silverwind/dnsbl

To keep forwarding addresses anonymous, we need to setup hashing that can only be decrypted by forwardemail.net, to generate a hash, you will enter your email address to forward to at forwardemail.net and a hash will be displayed to copy/paste

Hi,

I'm testing forwardemail for a domain I own (dabo.guru), just using https://forwardemail.net/ for now.

With the latest updates, when I sent an email from a protonmail account (@protonmail.com), it was returned as "Undelivered Mail Returned to Sender" with message:

[email protected]: host mx1.forwardemail.net[178.128.149.101] said: 550 Please ensure the email service you are sending from either has SPF or DKIM. You can most likely resolve this problem by searching on Google for "$serviceName SPF DKIM setup" (be sure to replace $serviceName with your email service provider, e.g. "Zoho"). (in reply to end of DATA command).

However, when I send directly to my gmail account that dabo.guru is set to forward to, gmail states that the message passed both DKIM and SPF.

This is the report from gmail:

Hopefully this can help. If there's any more information that I can grab, I'll upload it.

I thought at first this was an error with protonmail, but it doesn't seem it allows for any user configuration of SPF or DKIM when sending from an @protonmail.com address, only when using a custom domain.

This isn't an urgent issue for me, but it'd be nice to figure out what's causing it. I've been using protonmail to test for a while - it had some issues with DKIM before the last update that I'd hoped had been resolved but now I've run into this.

Having followed the instructions I tried to send an email from Gmail and get it forwarded but Gmail answered with:

 550 Invalid greeting from server: 

Hotmail returned a different error but there is a separate issue for that.

e.g. separate with pipe forward-email=food:[email protected]|[email protected]...

I love this system, it's just awesome and hugely appreciated. However, I think the DNS design is flawed.

Case in point:

$ dig forwardemail.net TXT

; <<>> DiG 9.10.6 <<>> forwardemail.net TXT
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43407
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;forwardemail.net.		IN	TXT

;; ANSWER SECTION:
forwardemail.net.	299	IN	TXT	"[email protected]"
forwardemail.net.	299	IN	TXT	"v=spf1 a mx include:spf.forwardemail.net ~all"

;; Query time: 32 msec
;; SERVER: 10.128.128.128#53(10.128.128.128)
;; WHEN: Mon Jul 16 19:37:11 BST 2018
;; MSG SIZE  rcvd: 152

Should there not be a better way to hide the forwarding email address? Spammers can now use the TXT records to find valid email addresses on a domain, which they would have otherwise struggled to find.

Ideas that may work:

• Allow a public key to be specified in the TXT record, and a private key to be uploaded to your service.
• Allow forwarding to be configured from your service (via a simple web UI) once the MX records are set up
• Provide a simple online encryption tool that will take the configuration, encrypt it using your public key, and only you will have the private key to decrypt. This may in fact be the easiest as you can keep your system effectively stateless.

WDYT?

Hi-

Any chance you could take a look at the MX and TXT records for amishscooters.com and tell me what I'm doing wrong? I think I set everything up correctly in route53 but it doesn't seem to be working.

Thanks!

Since TXT Records are public, the forwarding addresses will be always public.
Is there any way to store the mapping in a private mapping?

https://github.com/niftylettuce/forward-email/blob/0769047d51524601949c0622b2a763b83332f0b0/index.js#L285

Thanks for your open source work!

I think an entry in the FAQ about "How to check for messages that aren't forwarded" would be a welcome addition. I expect for the hosted version this "feature" simply isn't practical, but for the self-hosted version, a few commands for how to do this would be most welcome. ❤️

Thank you for this awesome project!

If I have primarydomain a.com that already has email service setup. Can we include the ability so all mails to {username}@b.com can be forwarded to corresponding {username}@a.com?

Looks like we just need to modify this part
https://github.com/niftylettuce/forward-email/blob/cbf58fcbb01ac7539b08b95a5720606a4889a3bd/index.js#L548-L553
to handle TXT records like
forward-email=b.com or [email protected]

What do you think?

I'm using this fantastic service, but I've encounter a problem which I believe I've solved, but I had to try a couple of solutions before getting onto it: I wanted to forward all emails sent to a specific domain (*@mydomain.xyz) to an address ([email protected]) plus redirect a specific address of that same domain ([email protected]) to another address ([email protected]).

I've tried the following TXT record values:

• forward-email=info:[email protected],[email protected] seems not working producing an error 550 Invalid forward-email TXT record
• [email protected],info:[email protected] seems working

You might want to improve the documentation to cover this particular case.

I'm still testing this, so feel free to correct me if my solution is wrong.

I setup my MX and TXT DNS entries but no goodness when attempting to email? Any ideas?

Just emailed you :)

Love only,

I send mail from: hotmail.com and others, and get this message.
From Gmail sends perfect.
Please help, thanks!

Thanks for the fix for #45 . But the original reply-to headers are being overwritten when the origin email.from has DMARC reject/quarantine policy. We need to preserve the original reply-to headers.

Hi,

I have set up the self hosted version and it seems to work well until I found that the forwarding is not working with mail.com. Can you please help me in this?

Below is the debug logs for the issue.

1|smtps    | [2018-09-28 10:14:51] DEBUG [#VpnXhUAAXeey] S: 554 Invalid greeting from server:
1|smtps    | [2018-09-28 10:14:51] DEBUG [#VpnXhUAAXeey] 554-mail.com (mxgmxus007) Nemesis ESMTP Service not available
1|smtps    | [2018-09-28 10:14:51] DEBUG [#VpnXhUAAXeey] 554-No SMTP service
1|smtps    | [2018-09-28 10:14:51] DEBUG [#VpnXhUAAXeey] 554 invalid DNS PTR resource record, IP=XXX.XX.XXX.XX: 554-mail.com (mxgmxus007) Nemesis ESMTP Service not available
1|smtps    | [2018-09-28 10:14:51] DEBUG [#VpnXhUAAXeey] 554-No SMTP service
1|smtps    | [2018-09-28 10:14:51] DEBUG [#VpnXhUAAXeey] 554 invalid DNS PTR resource record, IP=XXX.XX.XXX.XX
1|smtps    | [2018-09-28 10:14:51] DEBUG [#VpnXhUAAXeey] 

Thanks in advance.

Whenever I try to use Send Mail As I get this reply:

I've reached out to https://www.abuseipdb.com and waiting to hear back. This would vastly reduce spammers if we could check for 5-10%+ rate of spam it would probably eliminate a vast amount.

I've attempted to email @Flolagale so we can get this patched.

https://gist.github.com/niftylettuce/f6703a110ebab8edba47f29ae727f796
https://github.com/Flolagale/mailin/blob/d806e622af785605608c42673d63c3033e396d56/lib/mailUtilities.js#L79

Hi, today I started using the forwardemail.net service, when I was trying to send an email from a yahoo account, It return "550: Message failed: 550-5.7.1 Unauthenticated email from yahoo.com is not accepted due to domain's" .

Can you help me with this problem, has it happened to you?

Thank you very much.

Best regards.

I would like to know if there is a feature to forward all emails to multiple address.

Here is a example:

TXT "forward-email=[email protected],[email protected]"

TXT records are limited to 255 characters.

Please note that if you have multiple TXT record lines for forward-email: the service will only read the FIRST listed - please ensure you only have one line.

From RFC4408 3.1.3:

If a published record contains multiple strings, then the record MUST be treated as if those strings are concatenated together without adding spaces.

I don't see how the spf record and multiple forward-email TXT records would be able to be concatenated successfully.

Would love to see the README updated to show an example of many forwarding addresses to exceed 255 characters.

What would you think about supporting something like "forward-email-file:http://url.to/text/file.map"

Does the self-hosted option support getting the forward-email lookup map from somewhere other than TXT records? It seems like it would be nice to keep that list private, yes?

Hi and thankyou for a great product. I setup my account yesterday to forward to my gmail account. today, these emails are being returned as spam. I use iwantmyname for dns... any suggestions?

Hello, my domain name is bytedevs.com.
I have added the TXT & MX records as mentioned in the documentation and it's been more than 24 hrs but I am still not receiving emails. When I send an email to [email protected], I get a 550 error.

Hi
Trying to install forward-email on ubuntu.
Node, NPM
Other modules are ok.
When i am trying to add this line in my script -

const ForwardEmail = require('forward-email');

I get -
Cannot find module 'forward-email'

Looks like node installation problem. So I have tried the installation with other NPM packages, and they work fine.
Any idea?

I'm pointing my MX records with instructions provided at https://forwardemail.net/ (you can query ahmet.im to see my MX/TXT records). However all emails are bouncing.

I'm getting connection timeouts to mx1.forwardemail.net`'s IP address from https://mxtoolbox.com/SuperTool.aspx?action=smtp%3a192.81.219.215&run=toolpage.

Is this hosted service actively being supported? I want to trust it with all my email completely but I'd like to understand if there's anyone using the hosted service seriously (it's been down for a week for me) so that perhaps I should do self-hosting myself.

I'm not sure why, but when I send an email from my Dutch home email address ([email protected] which now belongs to [email protected]) to an email address forwarded with this, it gets blocked for spam (6.3). Is there a way to make this spamfilter more lenient (or remove it altogether) and could this be possible with forwardemail.net?

Any Email service provider having a p=REJECT DMARC policy tells other DMARC compliant systems to reject mail that doesn't originate from its server thereby throwing an error like 550-5.7.1 Unauthenticated email from google.com is not accepted due to domain's DMARC policy.

gmail.com has a DMARC policy of (p=NONE sp=QUARANTINE) header.from=gmail.com So a mail with a from address of *@gmail.com but not originating from a gmail server will end up in Inbox or may end up in spam in worst case.
but google.com has a DMARC policy of (p=REJECT) header.from=google.com So any unauthenticated mail from *@google.com (mail not originating from Google server) will straight away get rejected. Yahoo's DMARC policy is same as Google's.
The "Gmail Send email-as" #2 feature was a workaround to only allow emails from [email protected], but it's not going to allow any other mails from *@google.com or *@yahoo.com #39 or any other domain which publishes a p=REJECT DMARC policy

A way to mitigate this would be to use the sender's name in the friendly from. A “friendly from” is when you use a name to appear as the from address, instead of the email address itself:
[email protected] can be sent as “Example User” <[email protected]> and also add a reply-to header of [email protected]. This way the recipients still recognize the individual that sent the message, and you’re no longer at risk of violating the DMARC policy.
Users of this service can whitelist the email address [email protected] so that they receive every mail that is forwarded and you can also publish a stringent DMARC policy for forwardemail.net to prevent spoofing.

Need to ignore case on the names, should be a oneliner don't have time to do it right now

Hi,
I've set up forwarding for my domain "mikkle.io". Works great when sending from other gmail-addresses, etc, but when sending from my company domain "conscia.com" which is office365-hosted, I get a bounce with Status code: 550 5.7.23 "mikkle.io couldn't confirm that your message was sent from a trusted location."

I've attached a bounce-mail, output from "host -t mx mikkle.io", "host -t txt mikkle.io", and "host -t txt conscia.com" in the files "mail-error.txt", "my-domain.txt", "company.txt"
company.txt
my-domain.txt
mail-error.txt

As far as I can tell, the spf record for my company is set up correctly. The entry is a bit long, though, but according to mxtoolbox.com, the string length is ok (see attached screenshot "mxtoolbox_spf_conscia.com.png") - and we have no issues sending mails to the world in general.

Please let know, if more information is needed in order to investigate this.
Edit: I don't believe it's a dns propagation/timing issue - it's about a day ago since I set up the forwarding, and as mentioned, it works when sending from other sources.

prob use https://github.com/FGRibreau/mailchecker in addition to or instead of https://github.com/ivolo/disposable-email-domains#readme

I am currently using another (paid) forwarding service, but not all emails are received properly. Looking at this solution, but our txt record would have more than 255 characters, to setup 11 email forwarders.

Is there any way to split them up into multiple txt records which in turn are concatenated?

Hello! I've set up my DNS records to include the proper MX records, the SPF TXT record, and a DMARC TXT record. I cannot figure out how to set up a DKIM record for my domain on GoDaddy. Because of this (I think), I'm getting the following response when sending emails to email addresses at the domain:

 This is an automatically generated Delivery Status Notification.      

Delivery to the following recipients failed permanently:

• [email protected]

Reason: There was an error while attempting to deliver your message with [Subject: "Test Email 5"] to [email protected]. MTA p3plmtsmtp03.prod.phx3.secureserver.net received this response from the destination host IP - 178.128.149.101 - 550 , 550 Please ensure the email service you are sending from either has SPF, DKIM, or is a top-ranked <30K Alexa.com domain. You can most likely resolve this problem by searching on Google for "$serviceName SPF DKIM setup" (be sure to replace $serviceName with your email service provider, e.g. "Zoho"). If you continue to have issues, please see https://forwardemail.net or file an issue on GitHub at https://github.com/niftylettuce/forward-email. We'd be glad to help out! -- @niftylettuce

If you need help with email-forwarding setup or troubleshooting please visit https://forwardemail.net
.

Reporting-MTA: dns; p3plmtsmtp03.prod.phx3.secureserver.net [184.168.131.199]
Received-From-MTA: dns; n83.mail01.mtsvc.net [216.70.64.234]
Arrival-Date: Tue, 04 Sep 2018 10:52:41 -0700

Final-recipient: rfc822; [email protected]
Diagnostic-Code: smtp; 550 Please ensure the email service you are sending from either has SPF, DKIM, or is a top-ranked <30K Alexa.com domain. You can most likely resolve this problem by searching on Google for "$serviceName SPF DKIM setup" (be sure to replace $serviceName with your email service provider, e.g. "Zoho"). If you continue to have issues, please see https://forwardemail.net or file an issue on GitHub at https://github.com/niftylettuce/forward-email. We'd be glad to help out! -- @niftylettuce
Last-attempt-Date: Tue, 04 Sep 2018 10:53:12 -0700

========================================

What am I missing? I've tried searching 'GoDaddy SPF DKIM Setup' but to no avail. Any suggestions?

Thanks!

Like
if address@ not in TXT listing than
mx*.forwardemail.net reject and email pass to the next MX server?

(i need to split couple of email addresses to different mail services)

Hi,
First of all, thanks so much for such a solution!

I was asked to make a catch-all forwarding for a domain which is in Hebrew. After doing all what is in the guide, the forwarding still doesn't work.
Unfortunately, I can't post the domain name publicly, but would do so in a private message to whoever can investigate the issue. I can say it starts with xn----0hc

Thank you in advance.

ForwardEmail already supports IDN domain names and they work quite nicely and I use them a lot.

However, it currently does not support IDN usernames which are also allowed. I think a simple conversion from unicode to punycode should solve this problem. (and then putting the punycode in the DNS TXT record).

Mail forwarding was working yesterday, now it seems to be down for the last 4 hours or extremely delayed.

Hi nifty,

I've followed the steps for "Send mail as" but unfortunately I'm not able to send mails due to the error "You're sending this from another Google account using the 'Send mail as' feature."

Any ideas how I can fix this problem?

Email dump:
534 5.7.14 <https://accounts.google.com/signin/continue?sarp=1&scc=1&plt=...> Please log in via your web browser and then try again. Learn more at https://support.google.com/mail/answer/78754 z12-v6sm3000767edk.43 - gsmtp

Email was my first name [at] olderhall.com