Hi all,
fixed in assp 2.2.2 build 12228:
changed:
- If the receive of mail data takes longer than 'smtpIdleTimeOut' (or 180
seconds if not set) and all the data
are queued for the final Plugin-, charset conversion- or DKIM-
processing - assp sends a simple header line
X-ASSP-KEEP:[CR][LF]
A month ago I upgraded ASSP 2.2.1(12137) (and also moved to a new partition).
Since then, my volume of spam getting through ASSP has increased considerably.
Attached below is an example - clearly forged sender. Why isn't ASSP trapping
this?
I attached the analysis of the header below.
On 8/14/2012 1:25 AM, Thomas Eckardt wrote:
Or what about changing the color of the GUI to a 'nice' yellow after
some time of no update and later to a dazzlingly 'deafening :)' red.
Or another way would be to popup in the GUI - 'man - do an upgrade' -
more often than later the time (mean
In fact, having a manual update button could be a good thing.
Here it is (I can't remember how long):
(AutoUpdateASSP)
If this value is changed to 'download and install', the autoupdate
procedure will be scheduled immediatly.
...
changelog available prior to the update
It is available
On 8/15/2012 11:00 AM, Thomas Eckardt wrote:
In fact, having a manual update button could be a good thing.
Here it is (I can't remember how long):
(AutoUpdateASSP)
If this value is changed to 'download and install', the autoupdate
procedure will be scheduled immediatly.
...
I see
so admins can't read the changelog BEFORE installing
Oh ... admins who expects to find information at the 'Info and Stats'
screen would be able to read the current installed and the last available
change log :):):)
(Server Information)
but where is this shown outside of logs
GUI - TopMenu -
On 8/15/2012 12:22 PM, Thomas Eckardt wrote:
so admins can't read the changelog BEFORE installing
Oh ... admins who expects to find information at the 'Info and Stats'
screen would be able to read the current installed and the last available
change log :):):)
(Server Information)
Every day
