Skip to content
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

Open
ofrzeta opened this issue Dec 11, 2017 · 5 comments
Open

Error code with failed command #4

ofrzeta opened this issue Dec 11, 2017 · 5 comments

Comments

@ofrzeta
Copy link

ofrzeta commented Dec 11, 2017

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.

@kava1189
Copy link

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.

@inflex
Copy link
Owner

inflex commented Nov 11, 2022

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

@inflex
Copy link
Owner

inflex commented Nov 11, 2022

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

@kava1189
Copy link

kava1189 commented Nov 11, 2022

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

@inflex
Copy link
Owner

inflex commented Nov 11, 2022

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants