Cisco Cisco Email Security Appliance C160 Mode D'Emploi

Use as a guide to reading the preceding log file.

 shows the statistics recorded in safelist/blocklist logs.

The log file is initialized.

The listener is configured to use LDAP for masquerading, specifically with the 
LDAP query named “sun.masquerade.”

The address employee@routing.qa is looked up in the LDAP server, a match is 
found, and the resulting masquerade address is employee@mail.qa, which will be 
written to the message headers and/or the envelope from, depending on the 
masquerade configuration.

The user has manually run 

ldapflush

.

A query is about to be sent to sun.qa, port 389. The query template is: 
(&(ObjectClass={g})(mailLocalAddress={a})). 

The {g} will be replaced by the groupname specified in the calling filter, either a 
rcpt-to-group or mail-from-group rule.

The {a} will be replaced by the address in question.

Now the substitution (described previously) takes place, and this is what the query 
looks like before it is sent to the LDAP server.

The connection to the server is not yet established, so make a connection.

The data that is sent to the server.

The result is an empty positive, meaning one record was returned, but since the 
query didn't ask for any fields, there is no data to report. These are used for both 
group and accept queries when the query checks to see  if there is a match in the 
database.

Time that the bytes were transmitted.

The message consists of actions taken, including user authentication, and so forth.