Upgraded last night and all mail is being delivered to Trash floder… Moved sliders in Anti-Spam Configuration with no result.
Has been working fine for a year before the upgrade.
Community
Upgraded last night and all mail is being delivered to Trash floder… Moved sliders in Anti-Spam Configuration with no result.
Has been working fine for a year before the upgrade.
Hello,
Without having some logs to check I think nobody could provide you an explanation for this abnormal situation.
Thus please set the log level to Protocol Communication for PROCESSING
and SMTP Receiving
and share here the corresponding log lines related to 2-3 the messages that are delivered to Trash.
You should see some lines like:
PROCESSING:xxxxxxxx: Mail delivered to mailbox 'Trash' of <user@domain> with id y
and we need all lines for PROCESSING:xxxxxxxx
so we could understand why the delivery was made into Trash instead of Inbox.
By the way - you have upgraded to 10.4.1 - right?
HTH,
Ioan
Correct I am at 10.4.1 and upgraded last night.
It is giving me a new user error when posting the full log but it looks like the issue is here
2022-12-19 23:18:02 -0500 08 mail PROCESSING:003ABDD0: Start filter WASieveServer of type script filter from server
2022-12-19 23:18:02 -0500 08 mail PROCESSING:003ABDD0: WASieveServer of type script filter from server (@5) [WA_Blacklist_Check]: Pattern match of email address EOpaleychuk@computer-talk.com found in server black list
2022-12-19 23:18:02 -0500 08 mail PROCESSING:003ABDD0: WASieveServer of type script filter from server (@14) [WA_Blacklist_Check]: Move email into ‘Trash’ folder
2022-12-19 23:18:02 -0500 08 mail PROCESSING:003ABDD0: Fileinto [Trash] requested for erin@ryft.net
2022-12-19 23:
Hello,
Please login into CLI and provide the output from the following commands:
> config server
> config filters
> list Blacklist
HTH,
Ioan
Hi, I am sorry but I could not tolerate the extended issue and reverted a snapshot back to 10.3.3.52 … Once the revert was done all mail was flowing properly again. I think there is an underlying issue of change in behavior in 10.4
Hello,
There are no problems - its good to hear that you successfully rolled-back your upgrade.
In case you will face the same problem later on you will know what info is needed.
BR,
Ioan
Hello, we also have the same problem, after updating to version 10.4.1, all new emails go to the deleted folder, even having the header AXIGEN SPAM LEVEL: 1, rollback was made to version 10.3.3.53
Hello Salvador,
Could you please share the server sieve filter file located into <working-dir>/filters/wasieve-server.sieve
where the working-dir
is usually set to /var/opt/axigen
.
Looking forward for your reply.
BR,
Ioan
Hello,
Could you please share the server sieve filter file located into <working-dir>/filters/wasieve-server.sieve
where the working-dir
is usually set to /var/opt/axigen
.
Looking forward for your reply.
BR,
Ioan
Hello Salvador,
Thank you for provided file - could you please confirm if you made any changes inside that file before sharing here as there are definitely signs of entire lines removed from it.
If affirmative - than no need to share it again as we were able to match your report from this thread with the support ticket you have opened from WebAdmin.
Best regards,
Ioan
Hello,
The problem was identified and corrected in 10.4.2 so in case there are still similar issues please let us know.
BR,
Ioan
Hello, I’m unfortunately I was unable to endure the drawn out issue and returned a preview to 10.3.3.52 … Once the return was done all mail was streaming appropriately once more. I think there is a hidden issue of progress in conduct in 10.4