-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error code with failed command #4
Comments
Unfortunatley this issue still exists, I have the situation that my target is a cifs share from windows, sometimes I got an error |
Seems I missed this, sorry - I'll try have a look this weekend. |
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 |
Hi, this worked for me, I got Errorcode 255 back that should normally be 0, but I can work with this! Edit: |
okay, thanks - I'll see what I can do. how is it occuring? Just no write permissions of dud mailpack? |
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.
The text was updated successfully, but these errors were encountered: