How to fix 550 recvq/fax000000005.tif: Operation not permitted
So you setup your elastix or HylaFAX Server and you can’t save or download any of the faxes in your client. Most likely its an issue where your permissions are not set on the downloaded files.
To check, go to the received fax directory on the server and check the permissions on your .tif files.
[root@pbx recvq]# ls -la /var/spool/hylafax/recvq/ total 64 drwxrwxrwx 2 uucp uucp 4096 Oct 14 12:22 . drwxr-xr-x 17 uucp uucp 4096 May 3 14:53 .. -rw------- 1 uucp uucp 12962 Oct 14 11:20 fax000000005.tif -rw------- 1 uucp uucp 14832 Oct 14 11:31 fax000000007.tif -rw------- 1 uucp uucp 1 Oct 14 11:30 seqf
As you can see in my case the files are only readable by uucp. so lets
chmod 666 fax*.tif
Now open your Halyfax client (I use YajHFC), refresh and ensure you can now view your faxes. Most likely now you can, so lets tweak our modem config and make sure future files save properly.
In your modem config file (located in /var/spool/hylafax/etc/config.YourModem [In my case it was config.ttyIAX1]) we want to change the following
Save and you’re done!
If chmod 666 didn’t work try chmod 777
On your client ensure passive mode is disabled.
thanks for the share. Everything works fine till I reload elastix – then the RecvFileMode changes back to 0600 and I can’t open the new faxes. Do you have any suggestion ?
Thank you in advance.
hmmm… I don’t really restart my elastix server.. but you can put a line in your bashrc to copy an already modified file in your home directory to the /var/spool/hylafax/recvq/ on startup.
my problem was that every time that changes was applied on elastix web (eg add new extension, change a user, etc ), the config.ttyIAX1 was overwritten by a template. Just found the template under /usr/share/elastix/privileged/faxconfig, and change the RecvFileMode to 0666 (line 276). Now the RecvFileMode remains 0666 after applying changes. That solve the problem finally!
Thanks for the post and your reply.
and sorry for your name mistype ..
Excellent and easy manual to fix this error and ver very GOOD the solution added by Michalis.
I think this kind of errors are ver very serious problem from the hand of Asterisk, Hylafax and, a “top level”, Elastix. It’s stupid that you can not read your faxes or you have to “take a walk” for all the directory structure opening and reading files to solve it one by one your servers. I think it has to have an option to change it from the Fax configurator.
Thanks a lot to both of you.
Works for me, thanks for the share. Everything works fine.
Kerner Linux(x86_64) v2.6.18 348.1.1.el5
Elastix elastix v2.4.0
FAX hylafax v4.3.10 2rhel5