Syntax: g_acctlog_noauth bool g_acctlog_sum_inactive - Summarise local accounts that have not logged in yet as setting has no further documentation currently available Syntax: g_acctlog_aliases bool g_acctlog_noauth - Log sending usage based on from which may be fake Syntax: g_access_webonly string g_acctlog_aliases - Log redirection & aliases in account usage too Syntax: g_access_surgeweb bool g_access_webonly - Users in this group can only use web not imap or pop Syntax: g_access_group_default string g_access_surgeweb - Apply g_access_group rules to surgeweb sessions based on client's address

(mustīe used in conjunction with g_access_group) Syntax: g_access_group group=string access_pop=string access_imap=string access_smtp=string access_incoming=string g_access_group_default -Īccess group defaults for users with no access groups set. G_access_group group='nowebmail' access_pop='*,!webmail.ip'Īccess_imap='*,!webmail.ip' access_smtp='*'Īnd put the users you want to limit in a group called G_access_group group='normal' access_pop='*' access_imap=*' To prevent webmail access for some users you would do this: With 'Access type' set to 'free_user' on accounts page orĮquivalently in nwauth authentication. G_access_group group=free_user access_pop=Īccess_imap= access_smtp= G_access_group group=paid_user access_pop=* access_imap=* this could allow you to charge webmail users for pop access

When a user is authenticated access isĬhecked against group membership defined in the 'mailaccess' field Syntax: g_about_disable bool g_access_group - Access groupsĪccess rules defining groups of IP addresses with certain POP, This setting has no further documentation currently available Will take ranges also like 10.0.1-120.5 and also support CIDRĪnd there is an online CIDR calculator here. Try and match on any 127.* or 10.* domains. Many settings will also accept a ! as a 'not', and are processedįrom left to right.

Note: Most 'matching' settings take wild card lists as

Surgemail smtp authentication