-
Notifications
You must be signed in to change notification settings - Fork 508
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
Fetching Problems: Error: Unexpected characters at end of address #1999
Comments
Are you using a modern Microsoft Exchange authentication or regular IMAP? |
Inbound regular IMAP SSL 993 (with Plesk) |
I hawe some error System settings not change. PHP 7.4.29 |
Same thing spotted in one of our instances, occured after an upgrade from 1.7.24 to 1.8.15. Tried restarting and clearing the cache (from GUI) to no avail. Issue seems to clear after troublesome message (long To: list - 5 email addresses) has been marked as read on the mailserver. |
The issue has been fixed in the 1.8.16 release. |
every now and then i get the same error message
i also use IMAP SSL 993 (with Plesk) |
I also get this error randomly, too. On Freescout v1.8.104 via the tiredofit Docker image.
|
Are you using modern Microsoft OAuth IMAP authentication or |
Nope, neither. IMAP to a docker-mailserver container. |
Set |
Ok, I've done that. As the issue is intermittent, I cannot test so I will continue to monitor and advise on this issue if it recurs. |
It has now happened for the second time that an email in the inbox of the web server cannot be picked up by FreeScout. I am then notified myself by mail: "[FreeScout] Fetching Problems" and in the fetching logs there is several times the following entry: Folder: INBOX; Error: Unexpected characters at end of address: <> Maybe this ist not okay: From: <""@syma.com.br>
So far, I have always solved the problem by deleting the stuck email. Here, this is the problematic email (BTW: It is SPAM.):
And here is the header:
The text was updated successfully, but these errors were encountered: