We have plenty of resources on our servers so this should not be a problem. Also I see no reason why should a message even if it's big be processed for more then a few seconds. If it takes more then 10 seconds there is something wrong with the way the processing works or with some rule or...
Yes that's right I just have updated no issue with that as I have templates setup ever change still applied. I hope this version fixes the issues we had with some messages not processing properly error Out: 451 4.3.0 Error: queue file write error.
Thanks @Stoiko Ivanov it's all fine we are just forwarding email for that domain to our servers that is why the SPF is fail. They have their own filter we just host email from them and we use pmg to forward their email to our server.
I will have to do spamassassin configuration also for AWL...
Here example if I search for SA score=9/5 we have one server whitelisted as you see from the log the message is send from the server that is whitelisted:
Sep 13 08:02:48 server postfix/smtpd: connect from ptr[220.127.116.11]
Sep 13 08:02:49 server postfix/smtpd: Anonymous TLS...
Is it possible to configure the filter to set SA score to 0 if the message is whitelisted? Right now the whitelist messages still score SA higher then 0 even if they are whitelisted and that messes up the statistics.
Same issue here. Should we just update ClamAV manually? we are using no-subscription repository.
Sep 04 22:35:05 freshclam: ClamAV update process started at Sat Sep 4 22:35:05 2021
Sep 04 22:35:05 freshclam: Your ClamAV installation is OUTDATED!
Sep 04 22:35:05 freshclam...
@Stoiko Ivanov Thank you very much. This makes sense.
I did notice this problem a while ago when testing autoreponse when you send an email to address that does not exist and then you get response back about User unknown.
I was thinking that there was something wrong with our configuration but...
We send test email from gmail.com to one of the exchange mailboxes that has autoresponder set. Autoresponder emails should be signed by DKIM but they are not.
We get back autoresponder email that is not signed by DKIM. If we try to send email from our domain to gmail our email is DKIM signed...
We are seeing that a good indication that something is not working when messages are starting to accumulate on our incoming mail filter.
Is it possible to create some rule so we would be notified if messages in Queue reach a specific threshold like more then 50 messages in Queue waiting...
How do you diagnose this? I see daily legitimate emails rejected because they have too high AWL score.
Can we see why there is a high AWL score on particular message?
Found the post here https://forum.proxmox.com/threads/improve-awl.65170/ that helped me.
Will try to retrain the database.
Thank you for this increased from default 4 weeks to 8 weeks.
The main problem that you will have is you will be hitting the web ui limit "aborted by limit (too many hits)"
I seen your post here https://forum.proxmox.com/threads/how-to-increase-tracking-center-log-limit.92914/#post-404651 but...