[ZendTo] Error on File Upload

[Jules Field]

Kevin,

If it's not clamdscan, then it's probably the SELinux access rules on 
/var/zendto and its children. These will get destroyed if you moved 
/var/zendto (or any part of it) to another location, even if you put in 
symlinks pointing to the new location.

(Or possibly the "classic" file permissions and ownerships, but that's 
far easier to check so you have probably already done so).

If you did a default install, you will be running SELinux on your new 
ZendTo box in "enforcing" mode.
Run this command as root:
     restorecon -v -F -R /var/zendto

Then give it 1 last go.

If it still doesn't work at that point, then a rebuild is probably fastest.

Note that if you move /var/zendto (or anything below it) into another 
filesystem, you will need to do that restorecon command *if it all still 
appears under /var/zendto*.
If you move it anywhere else (for example /srv/zendto) or anything like 
that, then all the SELinux rules for everything under your new location 
will be blank. At that point, you need to add the new rules yourself:
   semanage fcontext --add -s system_u -t httpd_sys_rw_content_t 
'*/var/zendto*(/.*)?'
   semanage fcontext --add -s system_u -t httpd_sys_ra_content_t 
'*/var/zendto*/zendto.log(.*)?'
   semanage fcontext --add -s system_u -t httpd_sys_content_t 
'*/var/zendto*/rrd(/.*)?'
   restorecon -F -R */var/zendto*
where you should change all the *bold* "/var/zendto" strings to the 
*real* path you have moved it to.

This is one of the hazards of SELinux. The rules can be added in 2 
different ways, and they tend to break if you shift stuff around after 
setting the rules.

Cheers,
Jules.

On 01/06/2018 11:48, O'Connor, Kevin wrote:
> Jules,
>
> Disabling the clamdscan made no difference.
>
> I've done the upgrade to 5.03 and updated the config files. There was no zendto.conf.rpmnew I assume because there were no changes.
>
> The issue still exists. I can view and download the uploaded file from the outbox, using the resend mail option produces a blank page.
>
> This is not a production system, we still have an old 4.28-2 system running, so I'm thinking a complete rebuild from the ground up might be the best bet.
>
> Regards
>
> Kevin
>
>> -----Original Message-----
>> From: Jules Field [mailto:Jules at Zend.To]
>> Sent: 01 June 2018 10:31
>> To: O'Connor, Kevin <KevinO'Connor at merseyfire.gov.uk>; ZendTo Users
>> <zendto at zend.to>
>> Subject: Re: [ZendTo] Error on File Upload
>>
>> Kevin,
>>
>> To rule out ClamAV permissions issues, edit preferences.php and set
>>       'clamdscan' => 'DISABLED',
>> Make sure you keep the old value, just comment it out.
>>
>> Does that make any difference?
>>
>> I would also advise a quick "yum update" to the latest release of 5.03.
>> According to my ChangeLog, the changes from 5.01-5 and 5.03-1 are all
>> security improvements or bug fixes.
>>
>> Cheers,
>> Jules.
>>
>> On 01/06/2018 09:35, O'Connor, Kevin wrote:
>>> Jules,
>>>
>>> Thanks for the quick response. Please see my responses below.
>>>
>>>> -----Original Message-----
>>>> From: Jules Field [mailto:Jules at Zend.To]
>>>> Sent: 01 June 2018 09:23
>>>> To: ZendTo Users <zendto at zend.to>
>>>> Cc: O'Connor, Kevin <KevinO'Connor at merseyfire.gov.uk>
>>>> Subject: Re: [ZendTo] Error on File Upload
>>>>
>>>> Kevin,
>>>>
>>>> Does anything show up in /var/zendto/zendto.log when this happens?
>>> No there is nothing logged. All that the file contains as the logins
>>> to the system
>>>
>>>
>>>> How long are the uploads taking before this error appears?
>>> It occurs even with small files that take seconds to upload.
>>>
>>>> It is caused by the PHP session failing/disappearing/timing-out
>>>> during the upload process. It means the server received nothing of your
>> files.
>>> The files are present and as far as I can determine have completed upload.
>>>
>>>> The comment about files/directories is because that is one thing that
>>>> will cause it, as in some browsers it is still impossible for me to
>>>> check if what you've added to the list of files is a dir or a real file.
>>>>
>>>> Cheers,
>>>> Jules.
>>>>
>>>> On 01/06/2018 08:52, O'Connor, Kevin via ZendTo wrote:
>>>>> Morning,
>>>>>
>>>>> I've got a 5.01 clean install running on CentOS 7 with AD authentication.
>>>>>
>>>>> On completion of the file upload an error message pops up "Sorry I
>>>>> failed to
>>>> dropoff your files! Note that you cannot dropoff directories, only
>>>> files" The file is successfully uploaded but this error seems to
>>>> prevent the email being sent.
>>>>> I noticed someone posted the same fault back in March but I can find
>>>>> no
>>>> response or resolution posted so was hoping someone could point me in
>>>> the direction of a fix or a setting I might have got wrong.
>>>>> TIA
>>>>>
>>>>> Kevin
> This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
> If you have received this e-mail in error please notify the originator of the message.
>
> Any views expressed in this message are those of the individual sender, except where the sender specifies and with authority, states them to be the views of Merseyside Fire & Rescue Service, (MFRS).
>
> Incoming and outgoing emails may be monitored in line with current legislation.
>
> Steps have been taken to ensure that this email and attachments are free from any virus.  In keeping with good computing practice the recipient should ensure they are actually virus free.
>
> http://www.merseyfire.gov.uk/
>

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

Wight, Portland, Plymouth: South or southwest 3 or 4, increasing 5 at times.
Slight or moderate. Showers, fog patches at first. Moderate or good,
occasionally very poor at first.

www.Zend.To
Twitter: @JulesFM
PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20180601/47b7c5da/attachment.html>