You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mod_clamav with directive "ClamFailsafe false" initiates the transfer of the file via stream for verification and when reaching the transfer size limit via stream (specified in clamad.conf in "StreamMaxLength") the transfer to the Clamav is interrupted, until this point everything is right.
But the file not to been completely scanned by Clamd, then is returns to the FTP client "Operation not permitted" but the directive "ClamFailsafe" does its job of keeping the file sent on the server.
Would be possible to remove such a return to the client? as this may generate doubts to user, such as imagining that the file go corrupted or something like that.
In clamd.conf:
StreamMaxLength 1000M
In proftpd.conf:
<IfModule mod_clamav.c>
ClamAV on
ClamStream on
ClamServer 127.0.0.1
ClamPort 3310
ClamFailsafe false
</IfModule>
Hi jbenden,
mod_clamav with directive "ClamFailsafe false" initiates the transfer of the file via stream for verification and when reaching the transfer size limit via stream (specified in clamad.conf in "StreamMaxLength") the transfer to the Clamav is interrupted, until this point everything is right.
But the file not to been completely scanned by Clamd, then is returns to the FTP client "Operation not permitted" but the directive "ClamFailsafe" does its job of keeping the file sent on the server.
Would be possible to remove such a return to the client? as this may generate doubts to user, such as imagining that the file go corrupted or something like that.
In clamd.conf:
StreamMaxLength 1000M
In proftpd.conf:
./proftpd -n -d10:
Error in client FTP:
FileZilla:
WinSCP:
Upload file minor than 1000M there is not a problem
Resources/version:
The text was updated successfully, but these errors were encountered: