New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
My bank cannot send email to my mailbox hosted on mxroute
The rep gave me error when tried to send email via outlook.
Delivery has failed to these recipients or groups
Generating server: smtp1.[bankname].com Remote Server Returned '554 5.4.4 < #5.4.4 smtp; 544 5.4.4 [internal] Domain Lookup Failed>'
Is there a problem on DNS settings in my mxroute setup ? Anyone know how to fix this problem?
This discussion has been closed.
Comments
No, this is more like [bankname] issue with DNS (kinda doubt) or @jar issue with DNS (kinda doubt too). Probably somehow both - bankname having shit DNS and mxroute can't validate it because idk, no route to DNS server?
Drop that message (with real domain, of course) to jar he will take a look
or wait, maybe this is from smtp1.[bankname].com not from mxroute SMTP when validating connection? If that is from smtp1.[bankname].com then you fucked up your DNS - do you have MX entries? Do they point to correct servers? Do you even have a domain and not like you forgot to pay for next year?
Throw that domain into https://mxtoolbox.com/ and see what it says.
If you changed nameservers it can take some time (~48h on average let's say) for everyone to update cache. MX entries should be faster, but that depends what TTL they had earlier.
Having anything other than a major company like Gmail or Outlook as your bank email is a bad idea.
Already opened a ticket, waiting for @jar response..
I guess that depends on where you’re from
Here, in Sweden, banks never or very rarely email, they send everything to your physical or digital mailbox (digital mailbox being a special thing where you login with BankID, digital ID issues by a bank)
Guess it’s not the same everywhere
problem with your dns. solved?
I need to host > 1000 domains with 1 catchall and no spam filters
Still haven't found anything suitable. Mxroute looks like good, but not sure if they drop any important spam.
Namecheap cPanel can block if you receive (not send) >1000 similar spam messages.
If you want to sabotage a competitor on NC, you may send >1000 same spam messages
Why you don't want to setup own receive-only email server for such a purpose?
lazy
Yes, want to offload it. + can be detected if 1000 point to 1 IP.
Most ESPs do engage in some form of gateway checks and measures. For example checking the RFC compliance of a message, making sure the domain exists (by querying A/MX records) like in this case, etc. The problem is when it includes DNSBLs or other antispam measures which would increase the likelihood of a message being rejected falsely and the recipient being none the wiser. If the recipient checks their logs diligently maybe they can contact the ESP for some fix.
BTW, we don't perform antispam checks at the gateway, just that the mail is up to spec. This means the end-user has complete control over any antispam measures.
As for @Liso's issue, it could be a DNS issue with
[bankname].com
or @jar's resolver.Check if the bank's domain/hostname has DNA A/MX records by using
dig
, here's a web version:https://toolbox.googleapps.com/apps/dig/
Pavin.
Well I doubt any ESP will be happy "offloading" such client :D
You think spammers are that clever?
Mxroute drop. And doing this without loging. You need provider which could send reports about dropped emails on daily or X basis.
Why not. May lose a high amount of traps buried in their databases.
Would be harder to combat criminals.
But yes, if mxroute resolver is unstable, would be a problem.
Yes, checked. Looks like mxroute lost some important messages. Even not spam. This is not good WIll recheck.
This is serious accusation. Any evidence? And are you sure the messages are lost and not delayed (by greylisting or something similar)?
Yes, will recheck. These non-spam messages are important.
I just checked in
/evo/user/email/tracking
messages with status Unknown and tried to find them in mailbox.Looks like if send spam from the same domain it is not delivered.
from: [email protected] (pretend)
to: [email protected]
like that is not delivered. But it is not related to these important messages with status unknown I cannot find o_O
Yes, confirm, missing an important bounce (non-spam).
How I found it:
go here
*.mxrouting.net:2222/evo/user/email/tracking
in filter, select
State
Unknown
Show
Inbound
Then in the list, view emails where FROM is empty and check if you find it in mailboxes.
I do catchall, domain1.com goes to domain_all.com
Maybe parser cannot match from and so does not forward to this catchall box.
Found many such bounces. Not related to parser.
Looks like a bug in mxroute, found a way to reproduce it
any bonuses for bug hunt?
From tests:
gmail - received
cPanel - received
mxroute - not received
I think will migrate from mxroute and stick with cPanel.
Need it work like a swish clock.
Some data for my case was not accurate. Because mxroute did not process mails properly. Will had to restart huge work
Summary of the issue:
When you send someone from mxroute or only receive there, you may not know that your message was bounced and the recipient did not receive it.
Also, other issues, may not receive general mail in some cases.
Only what I observed. Maybe other stuff.
@jar Its called ViagraBank
That’s not an error message our servers return. Looks like maybe it comes from some specific email gateway appliance that the bank is using? This was the first thing I found for it at least: https://community.broadcom.com/symantecenterprise/communities/community-home/digestviewer/viewthread?MessageKey=22c5ecee-ecbf-464e-9d90-093e3a1476b5&CommunityKey=bba1e9dc-0c56-4fb5-9e3d-ef7f0d79b7ee
Happy to take a look, make sure to open a support ticket.
change the bank
If you're saying that mxroute rejects email without a valid from: header, then that's correct - it's a required field according to the RFC, and should be rejected.
No, it was mitigation I had in place against a large scale backscatter attack.
From one mailbox looks like works now, but from another one do not see even in logs.
Do you disable it per account?
Per server, I made the change on just the one you pointed me to for the moment. Are you trying from a different server now?
Do you implemented solution for "smtp smugling" attack? That's relevant for postfix.
I don’t believe it’s relevant to our current version of exim. But given that the result of failure there is increased spam and likely from sources I’ve already blocked, I haven’t bothered to test it.
Sperm Bank?