<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>IMAP Archives - SurgeMail</title>
	<atom:link href="https://surgemail.com/article-categories/imap/feed/" rel="self" type="application/rss+xml" />
	<link>https://surgemail.com/article-categories/imap/</link>
	<description>Windows/Linux Mail Server Software</description>
	<lastBuildDate>Thu, 07 Nov 2019 01:34:44 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.7.1</generator>

<image>
	<url>https://surgemail.com/wp-content/uploads/2019/11/cropped-robot_80-32x32.png</url>
	<title>IMAP Archives - SurgeMail</title>
	<link>https://surgemail.com/article-categories/imap/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Global settings g_imap</title>
		<link>https://surgemail.com/knowledge-base/global-settings-g_imap/</link>
		
		<dc:creator><![CDATA[chrisp]]></dc:creator>
		<pubDate>Wed, 06 Nov 2019 00:16:25 +0000</pubDate>
				<guid isPermaLink="false">http://surgemail.com/?post_type=ht_kb&#038;p=722</guid>

					<description><![CDATA[<p>g_imap_acl - Enable ACL (shared folders) in imap This setting allows folders to be shared between users. See the domain setting 'imap_public'. Requires surgemail 3.9d or later! For this to work you will need an imap client that supports ACL's to create and map shared folders (.e.g. thunderbird) Syntax: g_imap_acl bool g_imap_auto_create - Create folders<br /><a class="moretag" href="https://surgemail.com/knowledge-base/global-settings-g_imap/">+ Read More</a></p>
<p>The post <a rel="nofollow" href="https://surgemail.com/knowledge-base/global-settings-g_imap/">Global settings g_imap</a> appeared first on <a rel="nofollow" href="https://surgemail.com">SurgeMail</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<h3 class="wp-block-heading">g_imap_acl - Enable ACL (shared folders) in imap</h3>



<p>This setting allows folders to be shared between users. See the domain setting 'imap_public'. Requires surgemail 3.9d or later! For this to work you will need an imap client that supports ACL's to create and map shared folders (.e.g. thunderbird)</p>



<p>Syntax: g_imap_acl bool</p>



<h3 class="wp-block-heading">g_imap_auto_create - Create folders matching this list in response to 'select' commands</h3>



<p>Some imap clients assume certain folders exist, this setting can be used to let surgemail auto create such folders when the imap client requests some action involving the folder</p>



<p>Syntax: g_imap_auto_create string</p>



<h3 class="wp-block-heading">g_imap_auto_subscribe - Auto subscribe folders for users</h3>



<p>This setting has no further documentation currently available</p>



<p>Syntax: g_imap_auto_subscribe bool</p>



<h3 class="wp-block-heading">g_imap_blacklist - Test if imap users are in rbl's and email admin</h3>



<p>This lets you find any of your users who's ip address has been blacklisted, at most it will email once a day, any additional entries are logged in mail.err log file (search for 'blacklist')</p>



<p>Syntax: g_imap_blacklist bool</p>



<h3 class="wp-block-heading">g_imap_capa - Where to get the CAPABILITY value from</h3>



<p>When you have suffix based domains and you're using SurgeWall the CAPABILITY request comes before the domain of the user is known. As such SurgeMail cannot determine whether to send the real servers CAPABILITY or it's own. This setting will choose the default behaviour, valid values are: Local,&nbsp;. By default SurgeMail defaults to the behaviour of the primary domain, if it's surgewall then it obtains the real server capability. "Local" defaults to SurgeMails own capability, and&nbsp;defaults to the real server capability.</p>



<p>Syntax: g_imap_capa string</p>



<h3 class="wp-block-heading">g_imap_capa_strip - Capability values to hide</h3>



<p>In some situations you might not want to advertise server capabilities, for example SURGEMAIL and XFLDDATA when they cause problems with SurgeWall operations. Or perhaps the IDLE capability. Specifying the capability strings to hide here will cause SurgeMail to stop advertising those capabilies.</p>



<p>Syntax: g_imap_capa_strip string</p>



<h3 class="wp-block-heading">g_imap_cram_enable - Enable CRAM-MD5 authentication (requires nwauth 4.0h or greater)</h3>



<p>Please note that CRAM-MD5 does have security implications, specifically it means that the local users password must be stored in a semi reversable state in the authent database. Also you must be using the new version of the NWAuth module.</p>



<p>Syntax: g_imap_cram_enable bool</p>



<h3 class="wp-block-heading">g_imap_debug - For NetWin use only</h3>



<p>This setting has no further documentation currently available</p>



<p>Syntax: g_imap_debug bool</p>



<h3 class="wp-block-heading">g_imap_delay - Glob data into bigger packets, never use this</h3>



<p>This setting has no further documentation currently available</p>



<p>Syntax: g_imap_delay bool</p>



<h3 class="wp-block-heading">g_imap_expunge_close - Expunge on every close, not recommended</h3>



<p>This setting has no further documentation currently available</p>



<p>Syntax: g_imap_expunge_close bool</p>



<h3 class="wp-block-heading">g_imap_folder - Type can be: Trash,Junk,Sent,Drafts,Archive</h3>



<p>Helps email clients all use the same folder names, Valid types include: Trash,Flagged,AllMail,Junk,Important,Sent,Drafts, note these names have no meaning on the server, in particular AllMail is not actually all mail.</p>



<p>Syntax: g_imap_folder name=string type=string</p>



<h3 class="wp-block-heading">g_imap_friends - Make the friends_pending folder visible in imap</h3>



<p>Setting to map the friends_pending folder into an imap folder. There is no corresponding setting for the 'held' folder as we believe people should always use the friends mechanism as it is a superset of the held folder in functionality</p>



<p>Syntax: g_imap_friends bool</p>



<h3 class="wp-block-heading">g_imap_idle_free - Releases threads in 'idle' state</h3>



<p>This setting has no further documentation currently available</p>



<p>Syntax: g_imap_idle_free bool</p>



<h3 class="wp-block-heading">g_imap_idle_nsf - The number of seconds before a complete directory rescan. To be used on NFS network drives</h3>



<p>Number of seconds for IMAP IDLE to do directory rescan - , note setting is miss spelled, do not correct it!</p>



<p>Syntax: g_imap_idle_nsf int</p>



<h3 class="wp-block-heading">g_imap_inactive_free - Releases threads not active</h3>



<p>This setting has no further documentation currently available</p>



<p>Syntax: g_imap_inactive_free bool</p>



<h3 class="wp-block-heading">g_imap_log_body - Log imap fetch body commands to msg*.rec log files</h3>



<p>This only logs when a body or body part is read via imap</p>



<p>Syntax: g_imap_log_body bool</p>



<h3 class="wp-block-heading">g_imap_log_copy - Log imap copy commands to msg*.rec log files</h3>



<p>This setting has no further documentation currently available</p>



<p>Syntax: g_imap_log_copy bool</p>



<h3 class="wp-block-heading">g_imap_log_flush - IMAP log flush</h3>



<p>Flush IMAP log on every write (for debugging).</p>



<p>Syntax: g_imap_log_flush bool</p>



<h3 class="wp-block-heading">g_imap_log_header - Log imap fetch header commands to msg*.rec log files (not usually needed)</h3>



<p>This logs rather a lot so may create excessive logging. Probably the log body setting is more wise.</p>



<p>Syntax: g_imap_log_header bool</p>



<h3 class="wp-block-heading">g_imap_log_main - Log imap to mail.log too (not recommended)</h3>



<p>This setting has no further documentation currently available</p>



<p>Syntax: g_imap_log_main bool</p>



<h3 class="wp-block-heading">g_imap_log_protocol - Log IMAP protocol</h3>



<p>Log IMAP protocol and other IMAP information to the mail.log file.</p>



<p>Syntax: g_imap_log_protocol bool</p>



<h3 class="wp-block-heading">g_imap_log_size - Size of imap.log file</h3>



<p>This sets the imap.log file size, default is 2mb</p>



<p>Syntax: g_imap_log_size int</p>



<h3 class="wp-block-heading">g_imap_max_messages - The number of messages in a single imap folder, default 200000</h3>



<p>This setting helps limit impact when a user has a large folder, it will fail to load a folder larger than this and report errors in the log, it does not prevent the folder from having messages added to it, and it does not inform the user that the problem has occurred, this setting is primarily to limit impact of a crazy user :-), see also G_MAILDIR_MAX</p>



<p>Syntax: g_imap_max_messages int</p>



<h3 class="wp-block-heading">g_imap_maxdup - Max duplicate imap fetch commands before we throttle connection, default 500</h3>



<p>This setting has no further documentation currently available</p>



<p>Syntax: g_imap_maxdup int</p>



<h3 class="wp-block-heading">g_imap_move - IMAP move extension</h3>



<p>This setting has no further documentation currently available</p>



<p>Syntax: g_imap_move bool</p>



<h3 class="wp-block-heading">g_imap_no_internal_date - Disable the internal date output on IMAP commands</h3>



<p>The RFC implementation of internal dateis broken wiht MS outlook. SurgeMail has been modified to conform to the outlook inplementation of internal date making this setting redundant..</p>



<p>Syntax: g_imap_no_internal_date bool</p>



<h3 class="wp-block-heading">g_imap_old - Revert to old imap module</h3>



<p>Replace normal imap with old imap module, not recommended/supported</p>



<p>Syntax: g_imap_old bool</p>



<h3 class="wp-block-heading">g_imap_old_ip - Revert to old imap module for some ip's</h3>



<p>Replace normal imap with old imap module, not recommended/supported</p>



<p>Syntax: g_imap_old_ip string</p>



<h3 class="wp-block-heading">g_imap_pop_burst - Always burst using imap code</h3>



<p>Prevents redownloading messages if file indicating user is using imap is lost. Generally this setting is not needed and should not be used. Turning it on/off will result in users getting duplicate messagese if they are using POP and have leave on server ticked</p>



<p>Syntax: g_imap_pop_burst bool</p>



<h3 class="wp-block-heading">g_imap_port - IMAP Port (default 143)</h3>



<p>Specifies the PORT to listen for IMAP connections on. IMAP is an alternative to POP protocol where the messages and folders all exist on the server. This is ideal when sharing a mail account between several users or when using Email from more than one computer.&nbsp; Use the keyword 'disabled' to disable this part of the surgemail service.</p>



<p>Syntax: g_imap_port int</p>



<h3 class="wp-block-heading">g_imap_search_body - Build and use indexes for imap body searching</h3>



<p>This setting has no further documentation currently available</p>



<p>Syntax: g_imap_search_body bool</p>



<h3 class="wp-block-heading">g_imap_search_index - Build and use indexes for imap header searching</h3>



<p>This setting has no further documentation currently available</p>



<p>Syntax: g_imap_search_index bool</p>



<h3 class="wp-block-heading">g_imap_search_noattach - Skip non text attachments when searching</h3>



<p>This setting has no further documentation currently available</p>



<p>Syntax: g_imap_search_noattach bool</p>



<h3 class="wp-block-heading">g_imap_search_text - Use only body and header indexes, fast but won't get all matches</h3>



<p>This setting has no further documentation currently available</p>



<p>Syntax: g_imap_search_text bool</p>



<h3 class="wp-block-heading">g_imap_search_timeout - Limit on imap search, default is 180 seconds</h3>



<p>This setting has no further documentation currently available</p>



<p>Syntax: g_imap_search_timeout int</p>



<h3 class="wp-block-heading">g_imap_secure_port - IMAP Port (default 993)</h3>



<p>Specifies the PORT to listen for dedicated SSL IMAP connections.</p>



<p>Syntax: g_imap_secure_port int</p>



<h3 class="wp-block-heading">g_imap_size_fetch - If true, will display message sizes on fetch command. (ie * 123 EXISTS)</h3>



<p>Displays message size in IMAP responses</p>



<p>Syntax: g_imap_size_fetch bool</p>



<h3 class="wp-block-heading">g_imap_spam_train - Train if moving message to 'spam' folder, or from 'spam' folder to inbox</h3>



<p>This setting has no further documentation currently available</p>



<p>Syntax: g_imap_spam_train bool</p>



<h3 class="wp-block-heading">g_imap_status_cache - Cache imap status responses (Obsolete, use _stored setting)</h3>



<p>Improves performance/reduces disk IO for imap</p>



<p>Syntax: g_imap_status_cache bool</p>



<h3 class="wp-block-heading">g_imap_status_stored - Keep imap folder counts stored on disk</h3>



<p>Improves performance/reduces disk IO for imap</p>



<p>Syntax: g_imap_status_stored bool</p>



<h3 class="wp-block-heading">g_imap_sync_all - Apply imap_max_sync to all folders</h3>



<p>This setting has no further documentation currently available</p>



<p>Syntax: g_imap_sync_all bool</p>



<h3 class="wp-block-heading">g_imap_sync_nomax - Exception to imap_max_sync setting</h3>



<p>This setting has no further documentation currently available</p>



<p>Syntax: g_imap_sync_nomax string</p>



<h3 class="wp-block-heading">g_imap_testing - Test imap module instead of normal one (not functional)</h3>



<p>Replace normal imap with a test one, this is not functional, do not use this setting.</p>



<p>Syntax: g_imap_testing bool</p>



<h3 class="wp-block-heading">g_imap_throttle - Limit for sustained imap commands per second before warning admin, default is 5</h3>



<p>Useful for detecting an email client in a loop wasting your resources</p>



<p>Syntax: g_imap_throttle int</p>



<h3 class="wp-block-heading">g_imap_throttle_exclude - Users who are not limited</h3>



<p>This setting has no further documentation currently available</p>



<p>Syntax: g_imap_throttle_exclude string</p>



<h3 class="wp-block-heading">g_imap_throttle_limit - Daily mb download limit before applying throttle speed, e.g. 500</h3>



<p>This setting has no further documentation currently available</p>



<p>Syntax: g_imap_throttle_limit int</p>



<h3 class="wp-block-heading">g_imap_throttle_speed - Limit to this speed in bytes per second when throttling, e.g. 50k</h3>



<p>This setting has no further documentation currently available</p>



<p>Syntax: g_imap_throttle_speed int</p>



<h3 class="wp-block-heading">g_imap_timeout - Time, in minutes for imap timeout, RFC required default is 30</h3>



<p>You may in some cases wish to reduce this below the RFC required default if your server is under very heavy load. Results may be unexpected when breaking RFC behavior!</p>



<p>Syntax: g_imap_timeout int</p>



<h3 class="wp-block-heading">g_imap_timeout_login - Timeout prior to login in seconds</h3>



<p>You may in some cases wish to reduce this below the RFC required default if your server is under very heavy load. Results may be unexpected when breaking RFC behavior!</p>



<p>Syntax: g_imap_timeout_login int</p>



<h3 class="wp-block-heading">g_imap_timezone - Timezone to display - for testing purposes only</h3>



<p>as per title <img src="https://s.w.org/images/core/emoji/15.0.3/72x72/1f642.png" alt="🙂" class="wp-smiley" style="height: 1em; max-height: 1em;" /></p>



<p>Syntax: g_imap_timezone string</p>



<h3 class="wp-block-heading">g_imap_trash_nocopy - Prevent copying from Trash to Trash folder</h3>



<p>This setting has no further documentation currently available</p>



<p>Syntax: g_imap_trash_nocopy bool</p>



<h3 class="wp-block-heading">g_imap_uidl_nofix - Disable UIDL auto repair of duplicate entries</h3>



<p>If true disable auto repair of identical UIDL entries.</p>



<p>Syntax: g_imap_uidl_nofix bool</p>



<h3 class="wp-block-heading">g_imap_unsub_auto - Unsubscribe if a folder doesn't exist</h3>



<p>Helps dumb email clients that get confused</p>



<p>Syntax: g_imap_unsub_auto bool</p>



<h3 class="wp-block-heading">g_imap_user_flags - This setting may confuse some email clients (mac) use with cautioun</h3>



<p>This may confused some email clients if multiple clients are used on a single account as the user flags can conflict</p>



<p>Syntax: g_imap_user_flags bool</p>



<h3 class="wp-block-heading">g_imap_warn_big - Warn user if inbox or sent has more than this many messages</h3>



<p>We recommend setting this at about 10000, users should use the auto cleanup features (via user.cgi) to archive older messages to another folder</p>



<p>Syntax: g_imap_warn_big int</p>
<p>The post <a rel="nofollow" href="https://surgemail.com/knowledge-base/global-settings-g_imap/">Global settings g_imap</a> appeared first on <a rel="nofollow" href="https://surgemail.com">SurgeMail</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
