Skip to content
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

Service is frequently unreliable #1270

Open
Artic6 opened this issue Oct 11, 2024 · 2 comments
Open

Service is frequently unreliable #1270

Artic6 opened this issue Oct 11, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@Artic6
Copy link

Artic6 commented Oct 11, 2024

The service you provide has once again become very unreliable yet your monitoring tells me everything is online when clearly it’s not 😞

I am using SMTP forwarding only.

It’s very obvious to spot because magically I stop receiving emails the day before, I would like to know why your monitoring seems to be very ineffective at detecting this???

The server is online and it’s responding with the correct SMTP headers, but it’s not actually sending the message????

You also have your time to inbox that also seems to not be accurate to the real world. It’s estimating four seconds to my inbox yet on my office 365 tenant I’m getting connection timeouts as you can see below:

Reason: [{LED=450 4.4.315 Connection timed out [Message=Socket error code 10060] [LastAttemptedServerName=a6n.co.uk] [LastAttemptedIP=138.197.213.185:25] [SmtpSecurity=-2;-2] [AM4PEPF0002BAA1.EURPRD83.prod.outlook.com 2024-10-11T09:55:31.684Z 08DCE9029274EC91]};{MSG=Socket error code 10060};{FQDN=a6n.co.uk};{IP=138.197.213.185. OutboundProxyTargetIP: 138.197.213.185. OutboundProxyTargetHostName: a6n.co.uk

Which then seems to fall to MX2:

Reason: [{LED=421 Timeout - closing connection};{MSG=};{FQDN=mx2.forwardemail.net};{IP=2604:a880:400:d1::cd:9001};{LRT=10/11/2024 9:55:31 AM}]. OutboundProxyTargetIP: 2604:a880:400:d1::cd:9001. OutboundProxyTargetHostName: mx2.forwardemail.net

@Artic6 Artic6 added the bug Something isn't working label Oct 11, 2024
@titanism
Copy link
Contributor

Hi @Artic6 thank you for writing in. Do you have an existing support ticket # regarding this? If not no worries.

We just need to know if you've checked your error logs under My Account > Logs, your spam folder (since all your forwarding is done in Gmail), and if you could email us an email (as an attachment with original headers) that was received delayed to your forwarded Gmail account.

@Artic6
Copy link
Author

Artic6 commented Oct 12, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants