<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Kevin,<br>
<br>
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.<br>
<br>
(Or possibly the "classic" file permissions and ownerships, but
that's far easier to check so you have probably already done so).<br>
<br>
If you did a default install, you will be running SELinux on your
new ZendTo box in "enforcing" mode.<br>
Run this command as root:<br>
<tt> restorecon -v -F -R /var/zendto</tt><br>
<br>
Then give it 1 last go.<br>
<br>
If it still doesn't work at that point, then a rebuild is probably
fastest.<br>
<br>
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*.<br>
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:<br>
<tt> semanage fcontext --add -s system_u -t httpd_sys_rw_content_t
'<b>/var/zendto</b>(/.*)?'</tt><tt><br>
</tt><tt> semanage fcontext --add -s system_u -t
httpd_sys_ra_content_t '<b>/var/zendto</b>/zendto.log(.*)?'</tt><tt><br>
</tt><tt> semanage fcontext --add -s system_u -t
httpd_sys_content_t '<b>/var/zendto</b>/rrd(/.*)?'</tt><tt><br>
</tt><tt> restorecon -F -R <b>/var/zendto</b></tt><br>
where you should change all the <b>bold</b> "/var/zendto" strings
to the *real* path you have moved it to.<br>
<br>
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.<br>
<br>
Cheers,<br>
Jules.<br>
<br>
<div class="moz-cite-prefix">On 01/06/2018 11:48, O'Connor, Kevin
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:WM!a65c09229589118a95783f6282f0ec87b5844b7475d18a56a979ffdccea17246b383ea2b0b61296003dedd6da08f7a33!@mx.jul.es">
<pre wrap="">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
</pre>
<blockquote type="cite">
<pre wrap="">-----Original Message-----
From: Jules Field [<a class="moz-txt-link-freetext" href="mailto:Jules@Zend.To">mailto:Jules@Zend.To</a>]
Sent: 01 June 2018 10:31
To: O'Connor, Kevin <a class="moz-txt-link-rfc2396E" href="mailto:KevinO'Connor@merseyfire.gov.uk"><KevinO'Connor@merseyfire.gov.uk></a>; ZendTo Users
<a class="moz-txt-link-rfc2396E" href="mailto:zendto@zend.to"><zendto@zend.to></a>
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:
</pre>
<blockquote type="cite">
<pre wrap="">Jules,
Thanks for the quick response. Please see my responses below.
</pre>
<blockquote type="cite">
<pre wrap="">-----Original Message-----
From: Jules Field [<a class="moz-txt-link-freetext" href="mailto:Jules@Zend.To">mailto:Jules@Zend.To</a>]
Sent: 01 June 2018 09:23
To: ZendTo Users <a class="moz-txt-link-rfc2396E" href="mailto:zendto@zend.to"><zendto@zend.to></a>
Cc: O'Connor, Kevin <a class="moz-txt-link-rfc2396E" href="mailto:KevinO'Connor@merseyfire.gov.uk"><KevinO'Connor@merseyfire.gov.uk></a>
Subject: Re: [ZendTo] Error on File Upload
Kevin,
Does anything show up in /var/zendto/zendto.log when this happens?
</pre>
</blockquote>
<pre wrap="">No there is nothing logged. All that the file contains as the logins
to the system
</pre>
<blockquote type="cite">
<pre wrap="">How long are the uploads taking before this error appears?
</pre>
</blockquote>
<pre wrap="">It occurs even with small files that take seconds to upload.
</pre>
<blockquote type="cite">
<pre wrap="">It is caused by the PHP session failing/disappearing/timing-out
during the upload process. It means the server received nothing of your
</pre>
</blockquote>
</blockquote>
<pre wrap="">files.
</pre>
<blockquote type="cite">
<pre wrap="">The files are present and as far as I can determine have completed upload.
</pre>
<blockquote type="cite">
<pre wrap="">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:
</pre>
<blockquote type="cite">
<pre wrap="">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
</pre>
</blockquote>
<pre wrap="">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.
</pre>
<blockquote type="cite">
<pre wrap="">I noticed someone posted the same fault back in March but I can find
no
</pre>
</blockquote>
<pre wrap="">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.
</pre>
<blockquote type="cite">
<pre wrap="">TIA
Kevin
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">
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.
<a class="moz-txt-link-freetext" href="http://www.merseyfire.gov.uk/">http://www.merseyfire.gov.uk/</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">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.
<a class="moz-txt-link-abbreviated" href="http://www.Zend.To">www.Zend.To</a>
Twitter: @JulesFM
PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
</pre>
</body>
</html>