ripMIME Error code with failed command

When ripmime fails writing to an existing directory with insufficient permissions (e.g. missing x-bits) it prints an error message "mime.c:1484:MIME_decode_text:ERROR: cannot open out/textfile0 for writing" but still returns an exit code 0 to the shell which makes it hard to detect failure in scripts etc.

Dec 11 '17 12:12 ofrzeta

Unfortunatley this issue still exists, I have the situation that my target is a cifs share from windows, sometimes I got an error mime.c:1416:MIME_decode_text:ERROR: cannot open /mnt/billing/textfile0 for writing I tried also to check the exit code, but get 0.

Nov 11 '22 08:11 kava1189

Seems I missed this, sorry - I'll try have a look this weekend.

Nov 11 '22 09:11 inflex

Try the latest git source, just added a few return code ripple-up returns; make sure you use extended-results flag.

ie, ./ripmime --extended-errors

Nov 11 '22 09:11 inflex

Hi, this worked for me, I got Errorcode 255 back that should normally be 0, but I can work with this! Many thanks!

Edit: Need to correct, now I got always Errocode 255, instead of 0. This is the current command: ripmime -i - --extended-errors --no-nameless --paranoid --postfix -d /mnt/billing In the log it looks like this: mime.c:1416:MIME_decode_text:ERROR: cannot open /mnt/billing/textfile0 for writing

Nov 11 '22 13:11 kava1189

okay, thanks - I'll see what I can do. how is it occuring? Just no write permissions of dud mailpack?

Nov 11 '22 15:11 inflex