search

forwardemail / free-email-forwarding

The best free email forwarding for custom domains. Visit our website to get started (SMTP server)
https://forwardemail.net
Other
2.41k stars 181 forks source link

Zoho needs to whitelist our servers #145

Closed leonheess closed 4 years ago

leonheess commented 5 years ago

I didn't change anything but the forwarding doesn't work anymore. I double-checked the DNS-Records but I everything seems to be in order. I'm not self-hosted.

niftylettuce commented 5 years ago

The service is working fine and up

leonheess commented 5 years ago

Is there anything I can troubleshoot? I tried changing the receiving email but it still doesn't work.

leonheess commented 5 years ago

Those are my DNS records: image

niftylettuce commented 5 years ago

I tested from GMX and I received an email, albeit it went to GMX spam

Screen Shot 2019-06-27 at 9 10 42 AM

niftylettuce commented 5 years ago

From your DNS records for heess-it.de it does not appear you are forwarding to any GMX email address. It looks like you are only forwarding all emails to 62hele1bif@hft-stuttgart.de.

Upon doing a lookup for hft-stuttgart.de, I see that the MX servers are mx1.belwue.de. So you are forwarding emails to this service, and then this service is forwarding emails to GMX? This is not our problem, this is a problem with your intermediary hft-stuttgart.de server.

You must check that the server at mx1.belwue.de is properly set up with all requirements (e.g. FQDN, reverse PTR, ...).

leonheess commented 5 years ago

That mail server is the one of my university. I switched the destination to check if this was the problem. I now switched it back to my main email address leon@heess.me which is at Zoho but it still doesn't work. Would you maybe look into the logs again? :)

Just to clarify the GMX issue is another one with a different domain. No GMX involved here.

niftylettuce commented 5 years ago

You probably need to give it time to propagate OR use the purge cache tool at https://1.1.1.1/purge-cache/

The university mail server is probably not configured properly.

On Thu, Jun 27, 2019 at 9:27 AM Leon Heess notifications@github.com wrote:

That mail server is the one of my university. I switched the destination to check if this was the problem. I now switched it back to my main email address leon@heess.me which is at Zoho but it still doesn't work. Would you maybe look into the logs again? :)

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/niftylettuce/forward-email/issues/145?email_source=notifications&email_token=AAD7XBJGIURWTWLQJYGEMVTP4TE3JA5CNFSM4H33FWH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYXJKOA#issuecomment-506369336, or mute the thread https://github.com/notifications/unsubscribe-auth/AAD7XBOYMXZODTZTT74TXU3P4TE3JANCNFSM4H33FWHQ .

niftylettuce commented 5 years ago

Also, there are ZERO logs, we do not store any logs whatsoever on the service, so I cannot debug anything.

On Thu, Jun 27, 2019 at 9:27 AM Nick Baugh niftylettuce@gmail.com wrote:

You probably need to give it time to propagate OR use the purge cache tool at https://1.1.1.1/purge-cache/

The university mail server is probably not configured properly.

On Thu, Jun 27, 2019 at 9:27 AM Leon Heess notifications@github.com wrote:

That mail server is the one of my university. I switched the destination to check if this was the problem. I now switched it back to my main email address leon@heess.me which is at Zoho but it still doesn't work. Would you maybe look into the logs again? :)

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/niftylettuce/forward-email/issues/145?email_source=notifications&email_token=AAD7XBJGIURWTWLQJYGEMVTP4TE3JA5CNFSM4H33FWH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYXJKOA#issuecomment-506369336, or mute the thread https://github.com/notifications/unsubscribe-auth/AAD7XBOYMXZODTZTT74TXU3P4TE3JANCNFSM4H33FWHQ .

leonheess commented 5 years ago

I see. I temporarily changed it to forward-email=niftylettuce@gmail.com,leon@heess.me and purged the cache now so every email at anything@heess-it.de should end up in your mailbox as well. Could you maybe test that for me? If it works I will give up because then it's obviously neither a problem of the service or my DNS configuration.

I will of course remove your email right after and thank you so much for your time :)

niftylettuce commented 5 years ago

@MiXT4PE this is odd (my tests):

Screen Shot 2019-06-27 at 9 42 19 AM

Screen Shot 2019-06-27 at 9 42 24 AM

niftylettuce commented 5 years ago

Also I got your test:

Screen Shot 2019-06-27 at 9 43 40 AM

niftylettuce commented 5 years ago

I will debug this, sec

leonheess commented 5 years ago

Thank you so much for looking into this. I'm right here if you need me.

Edit: I did receive one of the tests I sent earlier just now 3 minutes ago!!

niftylettuce commented 5 years ago

It appears that that specific Zoho service/server is blocking us, perhaps due to spam or rate limiting.

Can't send mail - all recipients were rejected: 541 5.4.1 Mail rejected by destination domain

It forwards niftylettuce@gmail.com successfully, but it does not forward leon@heess.me successfully. The reason why it doesn't say leon@heess.me in the screenshot above (https://github.com/niftylettuce/forward-email/issues/145#issuecomment-506376074) is because I mask the forwarding addresses EVEN in error messages for people's security and privacy with the original forwarding address (not the end-recipient).

I'll fix that error message so it's clearer and doesn't get chopped off.

I've reached out to Zoho Support (support@zoho.com) and I suggest perhaps you do the same to see if they can whitelist us.

niftylettuce commented 5 years ago

Btw @MiXT4PE I just saw this in my spam folder in my Gmail inbox:

Screen Shot 2019-06-27 at 10 03 18 AM

leonheess commented 5 years ago

Yeah that's the one I also got. I wrote an email to Zoho Support and I really hope they whitelist your servers. Thanks for your help I just don't have enough knowledge about SMTP and stuff to wrap my head about issues like that.

niftylettuce commented 5 years ago

Also just wanted to follow up that the error message is clearer now (you can compare this with the above screenshot; it's joined by a comma):

Screen Shot 2019-06-27 at 10 06 58 AM

niftylettuce commented 5 years ago

I'm going to re-open this and change the title to "Zoho and GMX need to whitelist our server"

leonheess commented 5 years ago

Do you think the same issue exists with GMX? Didn't you try it yourself and it worked?

Here are the "rules" for send emails to GMX servers again: https://postmaster.gmx.com/en/email-policy - are all of them fulfilled?

niftylettuce commented 5 years ago

Good point! It's only Zoho.

leonheess commented 5 years ago

Just for the fun of it I put in a different address by a different provider and tried to sent an email from my zoho-based-address. This is what I got:

From: mailer-daemon@mail.eu.zoho.com
Sent: June 27, 2019 17:17:24
To: leon@heess.me
Subject: Undelivered Mail Returned to Sender

test@heess-it.de, ERROR_CODE :550, ERROR_CODE :The email you sent 
has an invalid DKIM signatureâ if you need help please forward this 
email to support@forwardemail.net or visit https://forwardemail.net

Does this help?

leonheess commented 5 years ago

That's the answer their support send me:

On analysis we observed the emails from no-reply@forwardemail.net were rejected on suspicion for Spam by our Antispam Filter.

However, we have added the sender domain and email address to your Org Whitelist to ensure those emails are not being rejected any further.

However, we see the IP address 178.128.149.101 from which the emails are being sent is currently Blacklisted on multiple DBLs. We request you to contact the sender or technical team for no-reply@forwardemail.net to raise a delist request to have the same removed from the Blacklist.

Once done please do monitor the status at your end or you may also let us know so that we can have the IP address added to your Whitelist as well to ensure a seamless email delivery.

niftylettuce commented 5 years ago

We are only blacklisted on one list, the SORBS DUHL, which listed us because we have a dynamic IP from Digital Ocean. I am planning to transition to a fixed/static IP in the near future when I launch V2 of ForwardEmail.net, which should resolve the issue.

leonheess commented 5 years ago

After whitelisting no-reply@forwardemail.net within my Zoho-Organisation I now get all emails as I should. However when I am sending from any address using the Zoho mailservers to any other (!) address that uses forward-email I get this:

ERROR_CODE :550, ERROR_CODE :The email you sent has an invalid DKIM signatureâ if you need help please forward this email to support@forwardemail.net or visit https://forwardemail.net

I am aware that I can't use forward-email to send from one address to itself but sending from >email< (Zoho) to >email< (using forward-email to forward to an GMX/Web address) shouldn't be an issue, right?

niftylettuce commented 5 years ago

Your Zoho has a bad DKIM setup, fix it and you should be okay

On July 5, 2019 3:29:44 PM UTC, Leon Heess notifications@github.com wrote:

After whitelisting no-reply@forwardemail.net within my Zoho-Organisation I now get all emails as I should. However when I am sending from any address using the Zoho mailservers to any other (!) address that uses forward-email I get this:>

ERROR_CODE :550, ERROR_CODE :The email you sent has an invalid DKIM signatureâ if you need help please forward this email to support@forwardemail.net or visit https://forwardemail.net>

I am aware that I can't use forward-email to send from one address to itself but sending from info@heess.me (Zoho) to info@ellenareali.com (using forward-email) shouldn't be an issue, right?>

-- > You are receiving this because you modified the open/close state.> Reply to this email directly or view it on GitHub:> https://github.com/niftylettuce/forward-email/issues/145#issuecomment-508794921

leonheess commented 5 years ago

Thank you for pointing out that issue on my end. It is now fixed and everything is working perfectly!