Information Systems:Mail flow - Revision history

Norwinu: Add connector info

2021-07-20T07:56:08Z

Add connector info

Norwinu: Norwinu moved page Information Systems:Mail flow rules to Information Systems:Mail flow: Better title

2021-07-20T07:29:56Z

Norwinu moved page Information Systems:Mail flow rules to Information Systems:Mail flow: Better title

Norwinu at 20:00, 15 March 2021

2021-03-15T20:00:19Z

Norwinu: /* Include staff in shareholder correspondence */

2021-03-12T05:53:19Z

Include staff in shareholder correspondence

Norwinu: /* Include staff in shareholder correspondence */

2021-03-12T05:48:59Z

Include staff in shareholder correspondence

Norwinu: /* Substitute Reply-to header for document distribution emails */

2021-03-12T05:45:17Z

Substitute Reply-to header for document distribution emails

Norwinu: /* Exempt messages to email order addresses from most scanning */

2021-03-12T05:38:30Z

Exempt messages to email order addresses from most scanning

Norwinu at 05:23, 12 March 2021

2021-03-12T05:23:22Z

Norwinu at 05:17, 12 March 2021

2021-03-12T05:17:43Z

Norwinu at 05:17, 12 March 2021

2021-03-12T05:17:22Z

@@ Line 1: / Line 1: @@
 A mechanism to set up "rules" specifying actions when certain criteria are met (i.e. matching certain message properties) is central to most mail server systems. In MDaemon, this is known as the Content Filter. In Exchange, there is a ''Rules'' section within ''Mail flow''.
 ===Substitute Reply-to header for document distribution emails===
 '''Implemented in:''' MDaemon
@@ Line 28: / Line 40: @@
 There are still numerous shareholder stores (big ones at that) that use POS systems or versions of POS systems which transmit orders via email. These orders go to certain email addresses. Rules are set in both Exchange and MDaemon to relax/bypass the regular spam/threat scanning for messages intended for these addresses. The premise is that the priority of having these messages delivered trumps the low risk of impact from any email threats that are accepted. This is because the IBM i, where these messages eventually arrive, can't execute these threats anyway, and the i has demonstrated an admirably unwavering patience in dealing with unsolicited spam/bulk email.
 [[Category: Email]]

← Older revision		Revision as of 20:00, 15 March 2021
Line 12:		Line 12:

	Note that the rules avoid changing the From: header. This should not be modified (i.e. it should remain as unipharm@unipharm.com or uphadmin@unipharm.com), because recipients may have email rules in place to detect this, or more importantly, machine recipients (servers that accept PO emails) may already be set to only accept messages from these addresses. The Reply-To header is more appropriate as it is only implicated when replying to the message.		Note that the rules avoid changing the From: header. This should not be modified (i.e. it should remain as unipharm@unipharm.com or uphadmin@unipharm.com), because recipients may have email rules in place to detect this, or more importantly, machine recipients (servers that accept PO emails) may already be set to only accept messages from these addresses. The Reply-To header is more appropriate as it is only implicated when replying to the message.
		+
		+	Proof of the rule taking effect:
		+	[[File:2021-03-15 12_45_02-Window.png\|400px]]

	===Include staff in shareholder correspondence===		===Include staff in shareholder correspondence===

@@ Line 16: / Line 16: @@
 '''Implemented in:''' Exchange
-When emails are sent to shareholder distribution lists, it is currently a "business rule" to BCC select staff members, with the intent being so that staff remain informed of any mass correspondence in the case they receive calls and questions regarding said correspondence. Rather than implement this business rule by including staff members in the distribution lists themselves (which simply, is bad design), it is more apprporiate to institute a mail flow rule to achieve this same outcome. By doing this, you can also specify the senders to which this rule applies, because some senders that use distribution lists traditionally may intend to send only to recipients suggested by the list name (sending to shareholders should only go to shareholders, because the name of the list is...Shareholders!).
+When emails are sent to shareholder distribution lists, it is currently a "business rule" to BCC select staff members, with the intent being so that staff remain informed of any mass correspondence in the case they receive calls and questions regarding said correspondence. Rather than implement this business rule by including staff members in the distribution lists themselves (which simply, is bad design), it is more apprporiate to institute a mail flow rule to achieve this same outcome. By doing this, you can also specify the senders to which this rule applies, because some senders that use distribution lists in a more conventional fashion may intend to send only to recipients suggested by the list name (i.e. sending to shareholders should only go to shareholders, because the name of the list is...Shareholders!).
 The implementation of this rule is straightforward - if an email is sent to any of the specified lists, then place these users (individual users specified) in the Bcc field.

@@ Line 16: / Line 16: @@
 '''Implemented in:''' Exchange
-When emails are sent to shareholder distribution lists, it is currently a "business rule" to BCC select staff members, with the intent being so that staff remain informed of any mass correspondence in the case they receive calls and questions regarding said correspondence. Rather than implement this business rule by including staff members in the distribution lists (which simply, is bad design), it is more apprporiate to institute a rule to achieve this same outcome. By doing this, you can also specify the senders to which this rule applies, because some senders that use distribution lists traditionally may intend to send only to recipients suggested by the list name (sending to shareholders should only go to shareholders, because the name of the list is...Shareholders!).
+When emails are sent to shareholder distribution lists, it is currently a "business rule" to BCC select staff members, with the intent being so that staff remain informed of any mass correspondence in the case they receive calls and questions regarding said correspondence. Rather than implement this business rule by including staff members in the distribution lists themselves (which simply, is bad design), it is more apprporiate to institute a mail flow rule to achieve this same outcome. By doing this, you can also specify the senders to which this rule applies, because some senders that use distribution lists traditionally may intend to send only to recipients suggested by the list name (sending to shareholders should only go to shareholders, because the name of the list is...Shareholders!).
 ===Exempt messages to email order catch-all addresses from most scanning===

@@ Line 7: / Line 7: @@
 '''Implemented in:''' MDaemon
-Document distribution emails describe emails such as remittance advices, A/R statements, invoices (PDF copy), purchase orders etc. These stem from JetForm (ultimately ASW), or custom mailer scripts on Bart, and therefore use the generic email accounts unipharm@unipharm.com and uphadmin@unipharm.com. Recipients that then naturally hit reply in their client will unknowingly send to these email addresses, which are forwarded to IT.
+Document distribution emails describe emails such as remittance advices, A/R statements, invoices (PDF copy), purchase orders etc. These originate from JetForm (ultimately ASW), or custom mailer scripts on Bart, and are therefore sent using their assigned email accounts - unipharm@unipharm.com and uphadmin@unipharm.com. Recipients that reply by (naturally) hitting the reply button and accepting the suggested To address unknowingly send these emails back to these addresses, which are then forwarded to IT and require manual forwarding to get to their "true" intended recipient.
-The Content Filter rules that pertain to this policy work by looking for properties specific to these emails and then changing the Reply-To header. For example, in A/R statement, the subject always contains "AR STATEMENT" and a From: header of unipharm@unipharm.com. Replies to these emails should go to accountsreceivable@unipharm.com, and so the rule specifies this as the Reply-To.
+The MDaemon Content Filter rule (many rules, but based on the same template) that pertain to this policy works by looking for properties specific to these emails and then changing the Reply-To header. For example, in A/R statement emails, the subject always contains "AR STATEMENT" and contains a From: header with the value unipharm@unipharm.com. Replies to these emails should always go to accountsreceivable@unipharm.com, and so the rule specifies this as the Reply-To. The rule actually deletes this and 2 other headers as well, as these pertain to replies. For example, the Return-Path header is so that mail servers know where to send bounces in scenarios where the message cannot even be delivered to the intended recipient.
 Note that the rules avoid changing the From: header. This should not be modified (i.e. it should remain as unipharm@unipharm.com or uphadmin@unipharm.com), because recipients may have email rules in place to detect this, or more importantly, machine recipients (servers that accept PO emails) may already be set to only accept messages from these addresses. The Reply-To header is more appropriate as it is only implicated when replying to the message.

@@ Line 18: / Line 18: @@
 When emails are sent to shareholder distribution lists, it is currently a "business rule" to BCC select staff members, with the intent being so that staff remain informed of any mass correspondence in the case they receive calls and questions regarding said correspondence. Rather than implement this business rule by including staff members in the distribution lists (which simply, is bad design), it is more apprporiate to institute a rule to achieve this same outcome. By doing this, you can also specify the senders to which this rule applies, because some senders that use distribution lists traditionally may intend to send only to recipients suggested by the list name (sending to shareholders should only go to shareholders, because the name of the list is...Shareholders!).
-===Exempt messages to email order addresses from most scanning===
+===Exempt messages to email order catch-all addresses from most scanning===
 '''Implemented in:''' Exchange, MDaemon

@@ Line 3: / Line 3: @@
 A mechanism to set up actions that are triggered on criteria (e.g. match certain message properties) is central to most mail server systems. In MDaemon, this is known as the Content Filter. In Exchange, there is a "Rules" section. These modules are
-==Rules==
+==Noteworthy Mail Rules==
 ===Substitute Reply-to header for document distribution emails===
 '''Implemented in:''' MDaemon