-
Notifications
You must be signed in to change notification settings - Fork 27
cannot parse reply from rspamd: bad top object #90
Comments
I just checked on mine (running latest master with the quota policy server rule commented out) and watched a mail get delivered and handled by rmilter and rspamd just fine after a fresh reboot except for these errors in name resolution (which other than being logged didn't do any harm):
A second email did not even show these errors but went through just fine. Here is the complete log for that email. May you find it helpful:
|
I commented out that line as well. Otherwise, no email gets delivered at all. |
For comparison I'm on
Do you happen to run a newer rspamd? |
Newer version on unstable:
|
@dotlambda The new version of rspamd does not work with rmitler anymore (it absorbs all the features into rspamd). We'll have to rewrite the code to use rspamd. I guess that should happen within the next month before it becomes stable. Any help is welcome (see #25) |
I don't pretend to understand rspamd or postfix or SNM so I am the last person you should trust with your mail setup, but here is my workaround which appears to work for me and appears to filter spam into the Junk folder. I added this to the bottom of my module (i.e. if you were using the "quick start" you would paste this gubbins into it before the final closing } ) This is brutal and messy and there are better ways to do it: this is just a hack to reduce the number of emails I'm getting about hair loss and photo editing until we can converge on one.
|
I'm seeing many of these errors in
journalctl
:Is this normal?
(I'm using v2.1.1)
The text was updated successfully, but these errors were encountered: