![]() Syntax: g_redirect_from from=string to=string g_redirect_from_cc – Carbon Copy redirect message if from matches Redirect a message to another address if the from matches. Syntax: g_redirect_cc_attach was=string to=string header=string contains=string g_redirect_from – Redirect message if from matches This rule is applied at the point of delivery, so only if the original user actually gets the email, and the message is sent as an attachment, the original message is ALSO delivered Syntax: g_redirect_cc was=string to=string g_redirect_cc_attach – Redirect message as attachment if rule applies For g_redirect_cc there are two special names defined “$localdomain$” and “$remotedomain$”, which can be used in the ‘was’ paramater (requires SurgeMail 2.3). Same as ‘redirect’ but the message is still delivered to the original address as well. Syntax: g_redirect was=string to=string g_redirect_cc – Carbon Copy redirect message Your script will run as the user ‘mail’ so if that user does not have access to the script file or work files then it will fail Your script can then process the message and if it want’s to respond must use smtp to send a response back etc… Your script can read the environment variables:Īnd must read the message on ‘stdin’, the message will be terminated with “crlf.crlf” You can also redirect a message to a robot or script like this: Use a domain redirect rule if this is required. G_redirect –> –> rules are processed ‘before’ the domain is identified, therefore you cannot use host_alias domain values in them. An example rule would be: –> or –> cards can be used and replaced, e.g. ![]() These rules are applied to local and remote addresses so should be used with ‘care’, for domain based redirection use the redirect rules within a domain. Syntax: g_received_skip_spf bool g_redirect – Redirect messages to ‘was’ to the ‘new’ address Syntax: g_received_skip_all bool g_received_skip_spf – Skip spf received header for messages that have non local recipients This not quite right, ideally one should skip this for outgoing only but since the header is added at delivery time we thought this was close enough. Note that in the case of a message that is to a local and remote recipeient, it will skip the headers for both, even though the desire is to skip them for the remote recipient only. Syntax: g_received_skip bool g_received_skip_all – Skip local received header for messages that have non local recipients This will make tracking abuse more difficult, we do not recommend using this setting generally. This setting can be used to hide sensitive local ip addresses from outgoing mail headers. Syntax: g_received_names string g_received_skip – Don’t write a received header for local trusted users It defines the valid received names to expect quoted in a properly formed bounce message for a message from this server/system. This list is used when processing vanish_bad_bounces, vanish_virus_bounces and vanish_any_bounce. Syntax: g_received_name string g_received_names – List of valid received names for incoming email Name shown as received “by” in the received headers this defaults to server name but can be specified if required:Įg “myservername” Received: from .nz (unverified )īy myservername (SurgeMail 1.5f) with ESMTP id 1140619 Syntax: g_rdns_timeout int g_received_name – Name shown in received headers Syntax: g_rcpt_trace bool g_rdns_timeout – Timeout for reverse DNS lookups default is 30 seconds This will list all recipients in the message to facilitate tracing Syntax: g_rcpt_quote bool g_rcpt_trace – Add X-Rcpt-Trace headers There is no known reason for ever turning this setting on. Syntax: g_rcpt_ok string g_rcpt_quote – Allow quote character(s) in addressesīy default quotes are blocked at the SMTP level, this is because some of the authent modules don’t handle quotes in addresses so it’s best not to let them through. This setting has no further documentation currently available Syntax: g_rcpt_nodup bool g_rcpt_ok – Whitelist for invalid rcpt addresses we will permit When enabled this prevents a message being delivered more than once to a single person, it’s a fairly good setting to use and will get rid of some spam for people using fallback addresses. Syntax: g_rcpt_msg string g_rcpt_nodup – Ignore duplicate recipients to the same user Response given for invalid recipient errors message is prefixed by email address. Syntax: g_rcpt_max_in int g_rcpt_msg – Invalid recipient response This limit is only applied to untrusted sessions (incoming mail) Syntax: g_rcpt_max int g_rcpt_max_in – Limit for recipients of untrusted channels, default g_rcpt_max Max recipients per message, default is 1000, can only be lower than 1000. Syntax: g_rcpt_colon bool g_rcpt_max – Max recipients per message, default is 1000 Syntax: g_rcpt_bang bool g_rcpt_colon – Allow colon characters in addressesĪllow colon characters in addresses. G_rcpt_bang – Allow bang characters in addressesĪllow exclamation marks in addresses.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |