Replies: 3 comments 4 replies
-
Hi there @graemev 👋 There was an issue over the past 24 hours with our encryption/decryption helper, where it was using the wrong method. We rolled back to use AES-256-CBC (as we did before) instead of a new approach which used ChaChaPoly-1305. There were a few edge cases where you might have seen a decrypt error as shown above in your post and in your log entries. Rest assured this issue is resolved and emails will flow through without issues. It was just a temporary problem. |
Beta Was this translation helpful? Give feedback.
-
Logs are stored and then parsed on an interval every 5 minutes. Only one unique log is stored per message every hour. forwardemail.net/jobs/index.js Lines 151 to 155 in e36a2c1 https://github.com/forwardemail/forwardemail.net/blob/master/jobs/parse-logs.js |
Beta Was this translation helpful? Give feedback.
-
It's 12:40 BST ...here is the top of my "logs" on a screenshot (these are all admin mails set during the night, mailtest, updates from my Humax PVR etc (AFYI, I see no "errors" here) |
Beta Was this translation helpful? Give feedback.
-
I have a lot of difficulty with the "logs" on the website.
It was not clear what the difference between the 2 logs was. I finally decided "logs" was a log about incoming email (MX) and "mail" was a log about outgoing email (SMTP) .
But the entry "logs" is many many hours out of date. Overnight I noted all my mail was tagged as 550error:1C800064:Provider routines::bad decrypt ...I I look at the logs right now (09:15 BST) this is all they show (550error). However I just sent a test mail via proton email and it arrived just fine. There is no entry in the log (yet) as the latest it has is 02:48 BST . It is very difficult to debug this with logs so old.
So my "guess" is , it was broken, it's not now, but I can't see when it changed.
Beta Was this translation helpful? Give feedback.
All reactions