Global settings g_log

Table of Contents

g_log_bounce_disable – Stop bounce reject entries filling up log (typically from spam bounces)

Disables useless logging in msg*.rec files, only recommended for busy servers

Syntax: g_log_bounce_disable bool

g_log_date – Log full date in log files

Makes log lines more complete

Syntax: g_log_date bool

g_log_date_msg – Log full date in msg log files (g_log_date required too)

Makes log lines more complete with the full date

Syntax: g_log_date_msg bool

This setting has no further documentation currently available

Syntax: g_log_disable bool

g_log_dns – Log dns responses in gory detail

Useful when debugging unexpected DNS results, search for ‘dns’ in mail.log to find the results.

Syntax: g_log_dns bool

g_log_dropped_disable – Don’t log if no ‘data’ command sent

Disables useless logging in msg*.rec files, only recommended for busy servers

Syntax: g_log_dropped_disable bool

g_log_fakemid – Header to use instead of message-id in log files

This setting has no further documentation currently available

Syntax: g_log_fakemid string

g_log_flush – Flushing log – flush on every write

This makes the server flush log data after every write to the file. This affects performance but can sometimes be the only way to track down an unusual fault eg: if the server dies the log is completely up to date and shows the last thing the server did before dying. 

Syntax: g_log_flush bool

g_log_fwd – Log fwd/redirection rules associated in msg.rec

Log fwd/redirection rules associated with g_log_rcpt in msg.rec files. 

Syntax: g_log_fwd bool

g_log_level – Set logging level

Set the logging level. This is primarily intended for finding faults with the server. Info level logging is the default. Alternatives are ‘error’ and ‘debug’ 

Syntax: g_log_level string

g_log_norcpt – Don’t log individual recipients in msg.rec files

Log individual recipients in msg.rec files

Syntax: g_log_norcpt bool

g_log_password – Log password failures to login_failed.log

It is considered bad form to do this, but it can be very useful, so it’s up to you!

Syntax: g_log_password bool

g_log_path – Path for log files

Sets the path for all SurgeMails generated logfiles. (except the delivery record logs)

Syntax: g_log_path string

g_log_pid – Log pid

Log PID along with thread-id in the UNIXlog files.

Syntax: g_log_pid bool

g_log_quota – Log quota for specified user

Creates a file for each user that matches this list, user_user@domain.log

Syntax: g_log_quota string

g_log_reject_disable – Disable the logging of rejected mail

SurgeMail will normally log failed deliveries due to MFilter / SmiteSpam / etc in the delivery logs. This setting will restrict this logging to accepted mail only.

Syntax: g_log_reject_disable bool

g_log_size – Size of the mail.log files before they are rotated

The mail.log files are a fixed size rotating log of what is happening inside SurgeMail. Dependant on the load of your server this may contain a few days worth of activity or a few minutes worth. This setting allows you to change the default 2MB before rotation size.

Syntax: g_log_size int

g_log_slow – Do slower logging system

Forces logging to disk even if it may slow things down. Not recommended.

Syntax: g_log_slow bool

g_log_start_norotate – Don’t rotate log on startup

By default the mail.log is rotated to mail2.log… on startup.

Syntax: g_log_start_norotate bool

g_log_syslog – Send ‘msg.rec’ entries to syslog

This is useful to ‘merge’ log information on a single host, on unix you specify the destination in your syslog configuration rather than specifying a host. On windows you can specify the remote host as you may not have a local syslog daemon

Syntax: g_log_syslog bool

g_log_syslog_debug – Send ‘mail.log’ entries to syslog as ‘mail.debug’ data

This data is probably not worth sending to syslog, it’s really debugging information of no long term value and too much to store.

Syntax: g_log_syslog_debug bool

g_log_syslog_host – Specify host to send syslog entries to (windows only)

On windows this lets you tell surgemail where the syslog deamon is, on unix you can do this in your syslog config file.

Syntax: g_log_syslog_host string

g_log_syslog_only – Disable writing to msg.rec

This prevents the local logs from being written

Syntax: g_log_syslog_only bool

g_log_tcp_read,g_log_tcp_write – Log actual data for a specific IP

These settings let you ‘trace’ the data going ‘to’ and or ‘from’ a specific IP address (or list, or wild card) Lets say you have a client on a specific address that has a problem where the fault could be server/client or network related. To track it down add this to surgemail.ini

g_log_tcp_read "2.3.4.5"
g_log_tcp_write "2.3.4.5"

Then try whatever is ‘failing’ and examine ‘mail.log’ to see what was read/written to that client.

Syntax: g_log_tcp_read string

g_log_thid – Log thread id in .rec files

Logs the thread id in the msg*.rec files, this is good for some types of debugging.

Syntax: g_log_thid bool

g_log_user – Log pop/imap/smtp protocol for specified user

Creates a file for each user that matches this list, user_user@domain.log

Syntax: g_log_user string

g_login_log_size – Size of login.log file

Max is 2gig, this is the size of login.log

Syntax: g_login_log_size int

Was this article helpful?

Related Articles

Contents

Need Support?

Can't find the answer you're looking for?
Contact Support