Domain Alignment - Revision history

Sebastian at 22:35, 11 June 2024

2024-06-11T22:35:42Z

← Older revision		Revision as of 00:35, 12 June 2024
Line 74:		Line 74:

	If the link text contains any domain, it should be the same link as the link location itself.		If the link text contains any domain, it should be the same link as the link location itself.

			=Useful links=

			* [https://inboxsys.com/authentication-and-alignment/ InboxSys blog]: Authentication and alignment

Sebastian at 14:07, 8 September 2023

2023-09-08T14:07:21Z

← Older revision		Revision as of 16:07, 8 September 2023
Line 50:		Line 50:

	* '''aspf''': SPF alignment. Options are "'''s'''" for "'''strict'''" or "'''r'''" for "'''relaxed'''".		* '''aspf''': SPF alignment. Options are "'''s'''" for "'''strict'''" or "'''r'''" for "'''relaxed'''".
	* '''adkim''': ~~SPF~~ alignment. Options are "'''s'''" for "'''strict'''" or "'''r'''" for "'''relaxed'''".		* '''adkim''': DKIM alignment. Options are "'''s'''" for "'''strict'''" or "'''r'''" for "'''relaxed'''".

	The adkim and aspf switches are optional. The default value for adkim and aspf is "r".		The adkim and aspf switches are optional. The default value for adkim and aspf is "r".

Sebastian at 14:00, 8 September 2023

2023-09-08T14:00:55Z

← Older revision		Revision as of 16:00, 8 September 2023
Line 60:		Line 60:
	After multiple A/B tests with [https://inboxsys.com InboxSys], it was discovered, that E-Mail deliverability improves when the image- and linkdomains align to one of the sender domains, RFC5321.MailFrom or RFC5322.From. With SPF identifier alignment, those domains would share the same responsible domain anyway.		After multiple A/B tests with [https://inboxsys.com InboxSys], it was discovered, that E-Mail deliverability improves when the image- and linkdomains align to one of the sender domains, RFC5321.MailFrom or RFC5322.From. With SPF identifier alignment, those domains would share the same responsible domain anyway.

	==~~SPF~~ in InboxSys app==		==Link- and imagedomains in InboxSys app==

	To check your messages for ~~phishing linkdomain~~ alignment, [[Sending a message to the seedlist\|send a message to your seedlist]] and look in the [[Links]] section of the [[:Category:E-Mail analysis\|E-Mail analysis]].		To check your messages for link- or imagedomain alignment, [[Sending a message to the seedlist\|send a message to your seedlist]] and look in the [[Links]] section of the [[:Category:E-Mail analysis\|E-Mail analysis]].

	==Phishing-like links==		==Phishing-like links==

Sebastian at 01:52, 3 September 2023

2023-09-03T01:52:54Z

← Older revision		Revision as of 03:52, 3 September 2023
Line 7:		Line 7:

	=Sending IP / Hostname=		=Sending IP / Hostname=
			''Main article: [[Domain_Name_System_(DNS)#PTR_Record]]

	Each sending IP should resolve recursively to a domain. This domain is the "hostname". Each hostname should resolve to an IP. This IP should be the same sending IP we started from.		Each sending IP should resolve recursively to a domain. This domain is the "hostname". Each hostname should resolve to an IP. This IP should be the same sending IP we started from.

Sebastian at 23:18, 2 September 2023

2023-09-02T23:18:14Z

← Older revision		Revision as of 01:18, 3 September 2023
Line 13:		Line 13:

	<pre>		<pre>
	$ host 2a00:1450:4864:20::632		$ host -t ptr 2a00:1450:4864:20::632
	2.3.6.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.ip6.arpa domain name pointer mail-ej1-x632.google.com.		2.3.6.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.ip6.arpa domain name pointer mail-ej1-x632.google.com.

	$ host mail-ej1-x632.google.com		$ host -t aaaa mail-ej1-x632.google.com
	mail-ej1-x632.google.com has IPv6 address 2a00:1450:4864:20::632		mail-ej1-x632.google.com has IPv6 address 2a00:1450:4864:20::632
	</pre>		</pre>

Sebastian at 23:07, 2 September 2023

2023-09-02T23:07:05Z

← Older revision		Revision as of 01:07, 3 September 2023
Line 32:		Line 32:
	To check your hostname and HELO/EHLO configuration, [[Sending a message to the seedlist\|send a message to your seedlist]] and look in the [[MTA configuration]] section of the [[:Category:E-Mail analysis\|E-Mail analysis]].		To check your hostname and HELO/EHLO configuration, [[Sending a message to the seedlist\|send a message to your seedlist]] and look in the [[MTA configuration]] section of the [[:Category:E-Mail analysis\|E-Mail analysis]].

	=SPF alignment=		=SPF identifier alignment=

	[[SPF]] aligns when the [[RFC5321.MailFrom]] domain matches the RFC5322.From domain. In laymen terms: When the envelope-from domain matches the sender domain.		[[SPF]] aligns when the [[RFC5321.MailFrom]] domain matches the RFC5322.From domain. In laymen terms: When the envelope-from domain matches the sender domain.

Sebastian at 16:53, 31 August 2023

2023-08-31T16:53:18Z

← Older revision		Revision as of 18:53, 31 August 2023
Line 27:		Line 27:
	The argument field contains the fully-qualified domain name of the SMTP client if one is available.		The argument field contains the fully-qualified domain name of the SMTP client if one is available.
	</blockquote>		</blockquote>

			==Hostname and HELO/EHLO in InboxSys==

			To check your hostname and HELO/EHLO configuration, [[Sending a message to the seedlist\|send a message to your seedlist]] and look in the [[MTA configuration]] section of the [[:Category:E-Mail analysis\|E-Mail analysis]].

	=SPF alignment=		=SPF alignment=
Line 54:		Line 58:

	After multiple A/B tests with [https://inboxsys.com InboxSys], it was discovered, that E-Mail deliverability improves when the image- and linkdomains align to one of the sender domains, RFC5321.MailFrom or RFC5322.From. With SPF identifier alignment, those domains would share the same responsible domain anyway.		After multiple A/B tests with [https://inboxsys.com InboxSys], it was discovered, that E-Mail deliverability improves when the image- and linkdomains align to one of the sender domains, RFC5321.MailFrom or RFC5322.From. With SPF identifier alignment, those domains would share the same responsible domain anyway.

			==SPF in InboxSys app==

			To check your messages for phishing linkdomain alignment, [[Sending a message to the seedlist\|send a message to your seedlist]] and look in the [[Links]] section of the [[:Category:E-Mail analysis\|E-Mail analysis]].

	==Phishing-like links==		==Phishing-like links==

Sebastian at 15:58, 31 August 2023

2023-08-31T15:58:11Z

← Older revision		Revision as of 17:58, 31 August 2023
Line 56:		Line 56:

	==Phishing-like links==		==Phishing-like links==
	''Main article: [[Phishing ~~Links~~]]''		''Main article: [[Phishing links]]''

	Another example where A/B tests with [https://inboxsys.com InboxSys] revealed new discoveries, is within an HTML link. Here is an example of a phishing-like HTML link:		Another example where A/B tests with [https://inboxsys.com InboxSys] revealed new discoveries, is within an HTML link. Here is an example of a phishing-like HTML link:

Sebastian at 15:51, 31 August 2023

2023-08-31T15:51:37Z

← Older revision		Revision as of 17:51, 31 August 2023
Line 56:		Line 56:

	==Phishing-like links==		==Phishing-like links==
			''Main article: [[Phishing Links]]''

	Another example where A/B tests with [https://inboxsys.com InboxSys] revealed new discoveries, is within an HTML link. Here is an example of a ~~[[Phishing Links\|~~phishing-like HTML link]]:		Another example where A/B tests with [https://inboxsys.com InboxSys] revealed new discoveries, is within an HTML link. Here is an example of a phishing-like HTML link:

	<pre>		<pre>

Sebastian at 15:50, 31 August 2023

2023-08-31T15:50:50Z

← Older revision		Revision as of 17:50, 31 August 2023
Line 48:		Line 48:

	The adkim and aspf switches are optional. The default value for adkim and aspf is "r".		The adkim and aspf switches are optional. The default value for adkim and aspf is "r".

			=Link- and imagedomains / Sender domains=

			None of the examples above touches the E-Mail content. Nonetheless, InboxSys discovered that domain alignment in the content of the message does make a difference.

			After multiple A/B tests with [https://inboxsys.com InboxSys], it was discovered, that E-Mail deliverability improves when the image- and linkdomains align to one of the sender domains, RFC5321.MailFrom or RFC5322.From. With SPF identifier alignment, those domains would share the same responsible domain anyway.

			==Phishing-like links==

			Another example where A/B tests with [https://inboxsys.com InboxSys] revealed new discoveries, is within an HTML link. Here is an example of a [[Phishing Links\|phishing-like HTML link]]:

			<pre>
			<a href="https://inboxsys.com">www.bankofamerica.com</a>
			</pre>

			If the link text contains any domain, it should be the same link as the link location itself.