We're using ripmime with Procmail to extract email contents into files. When extracting the email body (the text) ripmime correctly uses the configured procmail UMASK (022) for the files, but when there is an attachment it creates the file for the attachement with a 077 umask. Here's an example of files that ripmime created for one email that had a "testTrades2.csv" attachment:
-rw-r--r-- 1 fsdevprod fsdevprod 2341 2012-06-07 06:36 textfile4
-rw-r--r-- 1 fsdevprod fsdevprod 19 2012-06-07 06:36 textfile3
-rw-r--r-- 1 fsdevprod fsdevprod 294 2012-06-07 06:36 textfile2
-rw-r--r-- 1 fsdevprod fsdevprod 573 2012-06-07 06:36 textfile1
-rw-r--r-- 1 fsdevprod fsdevprod 0 2012-06-07 06:36 textfile0
-rw------- 1 fsdevprod fsdevprod 66 2012-06-07 06:36 testTrades2.csv
Here's how ripmime is being called in the procmail rc file:
| ripmime -i - -d /tmp
Why does the "testTrades2.csv" have different permissions from the textfile* files, and is there any way to have it use the same UMASK?
We're on ripmime v1.4.0.9.
thanks, David
The
ripmime
source (mime.c) had a bunch of these:So it was hardcoded. I changed them to be this:
and recompiled. Now the files are created group and publicly readable. Not an ideal solution as it is also hard-coded, but it works for me.
Ideally it should be command line configurable which shouldn't be hard to do, and then sent to the ripmime maintainer.