[Solved] DKIM rmilter error

That’s what the cron did. I simply copy/past. Indeed if you don’t do it, every hour it will re-do the cron (even after a successful install).

You should regenerate configuration after performing the upgrade (by doing yunohost service regen-conf rmilter --force)

Sorry, I wasn’t clear. After the update, there was an error message in the log, so I run the command. I’ll edit my post to be clearer.

So I have juste run an upgrade and do

yunohost service regen-conf rmilter --force
and reboot

So now I have

$ sudo systemctl status rmilter.service
● rmilter.service - Another sendmail milter for different mail checks
Loaded: loaded (/lib/systemd/system/rmilter.service; enabled)
Active: active (running) since dim. 2017-02-26 18:10:42 CET; 36min ago
Main PID: 406 (rmilter)
CGroup: /system.slice/rmilter.service
└─406 /usr/sbin/rmilter -c /etc/rmilter.conf -n

$ sudo systemctl status rspamd.service
● rspamd.service - rapid spam filtering system
Loaded: loaded (/lib/systemd/system/rspamd.service; enabled)
Active: active (running) since dim. 2017-02-26 18:10:44 CET; 41min ago
Main PID: 772 (rspamd)
CGroup: /system.slice/rspamd.service
├─772 rspamd: main process
├─800 rspamd: controller process
├─801 rspamd: normal process
├─803 rspamd: normal process
├─804 rspamd: normal process
└─805 rspamd: normal process

thank you @opi

But
yunohost service status tell me:

rmilter:
loaded: enabled
status: inactive
rspamd:
loaded: enabled
status: inactive

strange … is something broken?

The output of yunohost service status is broken for rspamd/rmilter in YunoHost current stable; This is already fixed in testing release; You can manually apply the fix, which is [fix] Rspamd & Rmilter are no more sockets · YunoHost/yunohost@7d4aa63 · GitHub

OK thank you I will wait for release :slight_smile:

Great job.

[quote=“Jean31, post:18, topic:2526, full:true”]
So reinstall package (Paramétrage de rmilter (1.9.2+nmu2)) and regen-confand the problem still here …

segmentation fault

do I have to do the same for rspamd?

May be another information I’m running Raspbian on Raspberry … may be a dependance probleme ?[/quote]

I have exactly the same problem.
I’ve done opi’s recipe to disable sockets, I’ve upgraded as much as I could and I’ve done numerous apt-get install rmilter --reinstall and yunohost service regen-conf rmilter (as well as rspamd) and reboots without any success.
I use a raspberry pi/raspbian too.

Did I miss something or is there something special to do to get rmilter/rspamd work on raspberry pi ? :stuck_out_tongue:

Is your installation new? This is the case why not install directly with the image to raspberry already ready

Actually, my installation isn’t new but it’s not a problem because I own another pizero that allows me to make some testing while keeping my main server online.
So I tried a fresh install based on YunoHost_v251_rpi.img.
Unfortunately, I meet the same segmentation faults with rmilter.
I tried some recipes on this fresh image too, without success.

So For me I have resolved the problem doing the changes given by @opi
But also I have change the raspbery, putting te SD card from the rapsberry B+ to a new Raspberry 3

I installed some package rmilter and ecryption lib in debug, and try to understand the problem…
My conclusion but not confirmed is that some lib used are not compatible with raspberry B+ (libcrypto.so.1.0.0, armv6)

I have fixed everything, but I have no time to go back to raspberry pi B+ to confirm my suspicion.
May be next month …

Thanks a lot for your experience report… I was about to become crazy !
I only own raspberry pi B and zero, so I suppose I’m stucked at the moment…
Is there an easy way to avoid the problem ? (for example, a custom build with an older but working lib)

We’re investigating this the support chat. At this point, we think we understood that the rmiler / rspamd packages both come from yunohost’s repo. It’s probably that they aren’t compiled properly for RPi 1 and 0 (armv6 stuff ?). I’ll try to catch @opi which knows this stuff better than me to see what we can do.

Issue created to track the problem