For Users of ASSP  <[email protected]> schreibt:
>Is there a web interface?

Yes. The newer versions (since 1.6) use the "Log Trail" to give you
complete control over the message (Resend,Move,Copy,Delete).
There is also a BlockReporting Feature which can deliver to you via
email a list of blocked mail, and some buttons to resend or show the
message.

>From the GUI:

------   Block Reporting  
-----------------------------------------------

ReportLog: Enable Report logging --  default: 2 

EmailBlockReport: Request Block Report -- Any mail sent by
local/authenticated users to this username will be interpreted as a
request to get a report about blocked emails. Do not put the full
address here, just the user part. For example: asspblock Leading
digits/numbers in the mail subject will be interpreted as "report
request for the last number of days". If the number of days is not
specified in the mail subject, a default of 5 days will be used to
build the report. Users defined in EmailBlockTo, EmailAdmins and
EmailAdminReportsTo are 'Admins' and can request a report for multiple
users. They have to use a special syntax with '=>' in the body of the
report request. The syntax is: 
 QueryAddress=>ReportRecipient=>ReportDays  -  there are many possible
combinations of this three parameters. For example:
 u...@domain and u...@domain=>u...@domain - will send a report for
this user to this user
 *...@domain (better use) *...@domain=>* - will send a report for every
blocked user in this domain to this user
 u...@domain=>recipi...@any-domain - will send a report for
u...@domain to recipi...@any-domain
 *...@domain=>recipi...@any-domain - will send a report for every blocked
user in this domain to recipi...@any-domain
 A third parameter is possible to set, which defines the number of
days for which the report should be created. The default (if empty or
not defined) is one day. This value is used to calculate the 'next run
date'. For example:
 *...@domain=>recipi...@any-domain=>2 - creates a report for two days.
 *...@domain=>*=>14 - creates a report for 14 days.
 u...@domain=>=>3 or u...@domain=>*=>3 - creates a report for three
days. The second parameter is here empty or *.
  
  
   default: asspblock 

EmailBlockReportDomain: Request Blocked Email Domain -- Set this to
the domain to which the users can send a request to receive blocked
messages. For example: @assp.local. default: @assp.local 

EmailBlockReply: Reply to Block-Report Request --  default: 1 

QueueUserBlockReports: Queue User Block Report Requests -- How to
process block report requests for users (not EmailBlockTo,
EmailAdmins, EmailAdminReportsTo).
  'run instantly' - the request will be processed instantly (not
stored).
  'store and run once at midnight' - the request will be
stored/queued, runs at QueueSchedule, and will be removed from queue
after that

 'store and run scheduled' - the request will be stored/queued, runs
permanently scheduled at BlockReportSchedule until it will be removed
from queue - a '+' in the subject is not needed
  'run delayed' - the request will be stored and  processed during the
next minutes
  To add a request to queue the user has to send an email to
EmailBlockReport. Leading digits/numbers in the mail subject will be
interpreted as "report request for the last number of days". If the
number of days is not specified in the mail subject, a default of 5
days will be used to build the report.
  If 'run instantly','run delayed' or 'store and run once at midnight'
is selected, but a user wants to schedule a permanent request, a
leading '+' before the digits in subject is required.
  To remove a request from queue the user has to send an email to
EmailBlockReport with a leading '-' in the subject.
   default: 3 

QueueSchedule: Runtime for Queued Requests -- Runtime hour for reports
in QueueUserBlockReports. Set a number between 0 and 23. 0 means
midnight and is default  

BlockRepForwHost: Forward The Blockreportrequest to other ASSP -- If
you are using more than one ASSP (backup MX), define the IP:relayPort
of the other ASSP here (separate multiple entries by "|"). The
Blockreportrequest will be forwarded to this ASSP and the user will
get a blockreport from every ASSP. The perl module  is required to use
this feature.  

EmailBlockTo: Send Copy of Block-Reports TO -- Email sent from ASSP
acknowledging your submissions will be sent to this address. For
example: [email protected]  

BlockReportFile: File for Blockreportrequest -- A file with
BlockReport requests. ASSP will generate a block report for every line
in this file (file:files/blockreportlist.txt - file: is required if
defined!) every day at midnight for the last day. The perl modules 
and  are required to use this feature. A report will be only created,
if there is at least one blocked email found! The syntax is: 
 QueryAddress=>ReportRecipient=>ReportDays  -  there are many possible
combinations of this three parameters. For example:
 u...@domain and u...@domain=>u...@domain - will send a report for
this user to this user
 *...@domain (better use) *...@domain=>* - will send a report for every
blocked user in this domain to this user
 *...@* - creates a report for all local users in all local domains
 u...@domain=>recipi...@any-domain - will send a report for
u...@domain to recipi...@any-domain
 *...@domain=>recipi...@any-domain - will send a report for every blocked
user in this domain to recipi...@any-domain
 A third parameter is possible to set, which defines the number of
days for which the report should be created. The default (if empty or
not defined) is one day. This value is used to calculate the 'next run
date'. For example:
 *...@domain=>recipi...@any-domain=>2 - creates a report for two days.
 *...@domain=>*=>14 - creates a report for 14 days.
 u...@domain=>=>3 or u...@domain=>*=>3 - creates a report for three
days. The second parameter is here empty or *!
 Only Admins are able to request blockreports for non local email
addresses. For example:
 u...@non_local_domain=>recipi...@any-domain=>4
 *...@non_local_domain=>recipi...@any-domain=>4
 This will result in an extended blockreport for the non local
address(es).  

BlockReportSchedule: Runtime BlockReportFile -- Runtime hour for
reports in BlockReportFile. Set a number between 0 and 23. 0 means
midnight and is default.   

BlockReportNow: Generate a BlockReport from BlockReportFile Now -- If
selected, ASSP will generate a block report from BlockReportFile now.
&nbsp;  

BlockMaxSearchTime: Max Search time per log File -- The maximum time
in seconds, the Blockreport feature spends on searching in one log
file. If this value is reached, the next log file will be processed.
Default is 0. A value of 0 disables this feature and all needed log
files will be fully processed.  

BlockReportFormat: The format of the Report Email -- Block reports
will be sent as multipart/alternative MIME messages. They normaly
contains two parts, a plain text part and a html part. Select "text
only" or "html only" if you want to skip any of this parts.
  To make it possible to detect a resent email, ASSP will add a header
line "X-Assp-Resend-Blocked: myName" to each email! default: 1 

BlockReportHTTPName: My HTTP Name -- The hostname for HTTP(S) links in
AdminUsers Blockreports. If not defined the local hostname will be
used.  

BlockReportFilter: Regular Expression to Skip Log Records* -- Put
anything here to identify messages which should not be reported. For
example:  \[Virus\]|\[BlackDomain\]   

inclResendLink: Include a Resend-Link for every resendable email --
Block reports will be sent as multipart/alternative MIME messages.
They contains two parts, a plain text part and a html part. If a
blocked email is stored in any folder, it is possible to include a
link for each email in to the report. Define here what you want ASSP
to do. Default is "in both". Note: File name logging (fileLogging)
must be on! The perl module  is required to use this feature. default:
3 

BlockResendLink: Which Link Should be included -- If HTML is enabled
in inclResendLink, two links (one on the left and one on the right
site) will be included in the report email by default. Depending on
the used email clients it could be possible, that one of the two links
will not work for you. Try out what link is working and disable the
other one, if you want.  

BlockResendLinkLeft: User which get the Left link only*  -- List of
users and domains that will get the left link only. The setting for
BlockResendLink will be ignored for this entries!  

BlockResendLinkRight: User which get the right link only*  -- List of
users and domains that will get the right link only. The setting for
BlockResendLink will be ignored for this entries!  

DelResendSpam: Delete Mails in Spam Folder -- If selected, an user
request to resend a blocked email will delete the file in the spamlog
folder - an admin request will move the file to the correctednotspam
folder. default: 1 

autoAddResendToWhite: Automatic add Resend Senders to Whitelist -- If
a resend request is made by any of the selected users, the original
sender of the resent mail will be added to whitelist.
  Notes On Block Reporting
    


------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Assp-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-user

Reply via email to