You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm in the process of moving our server to a new machine bit by bit and testing Rspamd over a network. While everything works nicely with Rspamd over network (or locally) there isn't actually any notification if Rspamd request fails and mails are passed.
Should the filter maybe log if Rspamd http requests fail?
I also thought about pinging Rspamd server at startup with rspamd/ping, but that might not be a good idea if Rspamd starts after OpenSMTPD.
The text was updated successfully, but these errors were encountered:
Yes, ping at startup doesn't work as it doesn't prevent rspamd from falling down right after the ping and, at least on openbsd, smtpd is going to be started before rspamd.
Logging is a good idea, the filter has been around for a little while now and we might even reconsider the "bypass filter if rspamd is down" to replace it with a 421 server internal error.
I'm in the process of moving our server to a new machine bit by bit and testing Rspamd over a network. While everything works nicely with Rspamd over network (or locally) there isn't actually any notification if Rspamd request fails and mails are passed.
Should the filter maybe log if Rspamd http requests fail?
I also thought about pinging Rspamd server at startup with rspamd/ping, but that might not be a good idea if Rspamd starts after OpenSMTPD.
The text was updated successfully, but these errors were encountered: