If you have the Front Door Rejector enabled and specified for IP filtering, events caught by the rejector will be logged here.

Appender

<appender class="org.apache.log4j.RollingFileAppender" name="IPATTACKER">
<param name="File" value="logs/IPAttacker.log"/>
<param name="Append" value="true"/>
<param name="MaxFileSize" value="5MB"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p %c{2} - %m%n"/>
</layout>
</appender>

Category

<category name="IPAttacker" additivity="false">
<priority value="DEBUG" />
<appender-ref ref="IPATTACKER"/>
</category>

If you have the Front Door Rejector enabled and specified for IP filtering, events caught by the rejector will be logged here.

Appender

<appender class="org.apache.log4j.RollingFileAppender" name="LDAP">
    <param name="File" value="logs/Ldap.log"/>
    <param name="Append" value="true"/>
    <param name="MaxFileSize" value="5MB"/>
        <layout class="org.apache.log4j.PatternLayout">
    <param name="ConversionPattern" value="%d %-5p %c{2} - %m%n"/>
    </layout>
</appender>

Category

<category name="LdapCommunication" additivity="false">
    <priority value="DEBUG" />
    <appender-ref ref="LDAP"/>
</category>

Xeams has the ability to handle emails with large attachments by using SynaMan to remove the attachment from the message and include it as a download link in the message body. If this occurs, Xeams will log the event here.

Appender

<appender class="org.apache.log4j.RollingFileAppender" name="LARGE_EMAIL_LOG">
<param name="File" value="logs/LargeEmails.log"/>
<param name="Append" value="true"/>
<param name="MaxFileSize" value="5MB"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p %c{2} - %m%n"/>
</layout>
</appender>

Category

<category name="LargeEmail" additivity="false">
<priority value="DEBUG" />
<appender-ref ref="EMAIL"/> 
<appender-ref ref="LARGE_EMAIL_LOG"/> 
</category>

If you have setup a distribution list, whenever an email comes in and gets forwarded to multiple aliases, that email will be logged here, along with the users that recieved it.

Appender

<appender name="ALIAS_HANDLER" class="org.apache.log4j.RollingFileAppender">
<param name="File" value="logs/Aliases.log" />
<param name="Append" value="true" />
<param name="MaxFileSize" value="5MB" /> 
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p %c{2} - %m%n"/>
</layout>
</appender>

Category

<category name="AliasHandler" additivity="false">
<priority value="DEBUG" /> 
<appender-ref ref="ALIAS_HANDLER"/> 
</category>

Xeams has the ability to improve itself via the Spam Learner feature. Whenever you forward a message to the spam learner address it will be logged here.

Appender

<appender name="SPAM_LEARNER" class="org.apache.log4j.RollingFileAppender">
<param name="File" value="logs/SpamLearner.log" />
<param name="Append" value="true" />
<param name="MaxFileSize" value="5MB" /> 
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p %c{2} - %m%n"/>
</layout>
</appender>

Category

 
<category name="SpamLearner" additivity="false">
<priority value="DEBUG" /> 
<appender-ref ref="SPAM_LEARNER"/> 
</category>

If you have the Front Door Rejector enabled and configured to filter content, these events will be logged here.

Appender

<appender name="FRONTDOOR" class="org.apache.log4j.RollingFileAppender">
<param name="File" value="logs/FrontDoor.log" />
<param name="Append" value="true" />
<param name="MaxFileSize" value="5MB" /> 
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p %c{2} - %m%n"/>
</layout>
</appender>

Category

<category name="FrontDoorRejector" additivity="false">
<priority value="DEBUG" />
<appender-ref ref="FRONTDOOR"/> 
</category>

This log will have events related to emails caught by the DomainInspector filter.

Appender

<appender name="DOMAIN_INSPECTOR" class="org.apache.log4j.RollingFileAppender">
<param name="File" value="logs/DomainInspector.log" />
<param name="Append" value="true" />
<param name="MaxFileSize" value="5MB" /> 
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p %c{2} - %m%n"/>
</layout>
</appender>

Category

<category name="DomainInspector" additivity="false">
<priority value="DEBUG" />
<appender-ref ref="DOMAIN_INSPECTOR"/> 
</category>

If you have multiple Xeams server's running with clustering enabled, any communication between the servers is logged here.

Appender

<appender name="CLUSTER" class="org.apache.log4j.RollingFileAppender">
<param name="File" value="logs/Cluster.log" />
<param name="Append" value="true" />
<param name="MaxFileSize" value="5MB" /> 
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p [%t] %c{2} - %m%n"/>
</layout>
</appender>

Category

<category name="ClusterManager" additivity="false">
<priority value="DEBUG" />
<appender-ref ref="CLUSTER"/>
</category>

You can configure Xeams to assign scores to emails that come in with either invalid or no DMARC configured. If an email is assigned a score through this filter it will be logged here.

Appender

<appender name="DMARC" class="org.apache.log4j.RollingFileAppender">
<param name="File" value="logs/Dmarc.log" />
<param name="Append" value="true" />
<param name="MaxFileSize" value="25MB" /> 
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p [%t] %c{2} - %m%n"/>
</layout>
</appender>

Category

<category name="Dmarc" additivity="false">
<priority value="DEBUG" />
<appender-ref ref="DMARC"/> 
</category>

If Xeams is configured to send emails out that it received from a different SMTP server, this log will check that email has a valid DMARC.

Appender

<appender name="DMARC_OB_REPORTS" class="org.apache.log4j.RollingFileAppender">
<param name="File" value="logs/DmarcObReports.log" />
<param name="Append" value="true" />
<param name="MaxFileSize" value="25MB" /> 
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p [%t] %c{2} - %m%n"/>
</layout>
</appender>

Category

<category name="DmarcOutboundReporter" additivity="false">
<priority value="DEBUG" />
<appender-ref ref="DMARC_OB_REPORTS"/> 
</category>

Appender

<appender name="NO_TLS" class="org.apache.log4j.RollingFileAppender">
<param name="File" value="logs/NoTLSRejections.log" />
<param name="Append" value="true" />
<param name="MaxFileSize" value="25MB" /> 
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p %c{2} - %m%n"/>
</layout>
</appender>

Category

<category name="SMTP_TLS_NOT_USED" additivity="false">
<priority value="DEBUG" />
<appender-ref ref="NO_TLS"/> 
</category>

Appender

<appender name="RBL_SERVERS" class="org.apache.log4j.RollingFileAppender">
<param name="File" value="logs/RblServers.log" />
<param name="Append" value="true" />
<param name="MaxFileSize" value="5MB" /> 
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p %c{2} - %m%n"/>
</layout>
</appender>

Category

<category name="RBLServerCheck" additivity="false">
<priority value="DEBUG" />
<appender-ref ref="RBL_SERVERS"/> 
</category>

If you use SynRBL as your RBL server in Xeams, any filtering that is caught by the SynRBL is logged here.

Appender

<appender name="SynRBL" class="org.apache.log4j.RollingFileAppender">
<param name="File" value="logs/SynRBL.log" />
<param name="Append" value="true" />
<param name="MaxFileSize" value="5MB" /> 
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p %c{2} - %m%n"/>
</layout>
</appender>

Category

<category name="SynRblCUM" additivity="false">
<priority value="DEBUG" />
<appender-ref ref="SynRBL"/> 
</category>

Appender

<appender name="WELL_KNOWN_DOMAINS" class="org.apache.log4j.RollingFileAppender">
<param name="File" value="logs/WellKnownDomains.log" />
<param name="Append" value="true" />
<param name="MaxFileSize" value="5MB" /> 
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p %c{2} - %m%n"/>
</layout>
</appender>

Category

<category name="WellKnownDomains" additivity="false">
<priority value="DEBUG"/>
<appender-ref ref="WELL_KNOWN_DOMAINS"/>
</category>

Appender

<appender name="VIRUS_DETECTOR" class="org.apache.log4j.RollingFileAppender">
<param name="File" value="logs/VirusDetector.log" />
<param name="Append" value="true" />
<param name="MaxFileSize" value="5MB" /> 
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p %c{2} - %m%n"/>
</layout>
</appender>

Category

<category name="VirusDetector" additivity="false">
<priority value="DEBUG" />
<appender-ref ref="VIRUS_DETECTOR"/> 
</category>

Appender

<appender name="ClamAV_Client" class="org.apache.log4j.RollingFileAppender">
<param name="File" value="logs/ClamAVClient.log" />
<param name="Append" value="true" />
<param name="MaxFileSize" value="5MB" />   
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p %c{2} - %m%n"/>
</layout>
</appender>

Category

<category name="ClamAvClient" additivity="false">
<priority value="DEBUG" />
<appender-ref ref="ClamAV_Client" />
</category>

Appender

<appender name="CUSTOM_FILTERS_PERF" class="org.apache.log4j.RollingFileAppender">
<param name="File" value="logs/CustomFiltersPerf.log" />
<param name="Append" value="true" />
<param name="MaxFileSize" value="5MB" /> 
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p %c{2} - %m%n"/>
</layout>
</appender>

Category

<category name="CustomFilterPerformance" additivity="false">
<priority value="DEBUG" />
<appender-ref ref="CUSTOM_FILTERS_PERF"/>
</category>

Appender

<appender name="OB_THRU_SLAVE" class="org.apache.log4j.RollingFileAppender">
<param name="File" value="logs/ObThruSlaves.log" />
<param name="Append" value="true" />
<param name="MaxFileSize" value="25MB" />
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p %c{2} - %m%n"/>
</layout>
</appender>

Category

<category name="OutboundEmailToSlaves" additivity="false">
<priority value="DEBUG" />
<appender-ref ref="OB_THRU_SLAVE"/>
</category>

This log is associated with the External Tool feature.
Appender

<appender name="EXTERNAL_TOOL" class="org.apache.log4j.RollingFileAppender">
	<param name="File" value="logs/ExternalTool.log" />
	<param name="Append" value="true" />
	<param name="MaxFileSize" value="5MB" />
	<layout class="org.apache.log4j.PatternLayout">
	<param name="ConversionPattern" value="%d %-5p %c{2} - %m%n"/>
	</layout>
</appender>

Category

<category name="ExternalTool" additivity="false">
	<priority value="DEBUG" />
	<appender-ref ref="EXTERNAL_TOOL"/>
</category>

If you have custom recipient rejectors specified for your front door rejector, any blocked recipients will be logged here.

Appender

<appender name="CUSTOM_RR" class="org.apache.log4j.RollingFileAppender">
<param name="File" value="logs/CustomRecipientRejector.log"/>
<param name="Append" value="true"/>
<param name="MaxFileSize" value="5MB"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p %c{2} - %m%n"/>
</layout>
</appender>

Category

<category name="CustomRecipientRejector" additivity="false">
<priority value="DEBUG"/>
<appender-ref ref="CUSTOM_RR"/>
</category>