<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://help.ncf.ca/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Ga627</id>
	<title>Support - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://help.ncf.ca/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Ga627"/>
	<link rel="alternate" type="text/html" href="https://help.ncf.ca/Special:Contributions/Ga627"/>
	<updated>2026-04-27T23:23:20Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.36.4</generator>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8420</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8420"/>
		<updated>2025-04-08T22:46:45Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, an error message may be sent back from the mail server explaining why the message was rejected.  In this case, the bounce-back should explain [[Emails not delivered#Undeliverable bounce-back messages|why the message was rejected]].&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the outbox, the problem is likely that the mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to the mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in the email should explain why it was detected as spam.  The recipient could also have a [[Spam#Zimbra Filters|mail filter]] which is removing the messages.   Otherwise, the mail provider can check their email logs to track what happened to an email by looking up the recipient/sender address and the time when the message was sent.&lt;br /&gt;
&lt;br /&gt;
Messages are often blocked because an attachment is too big or is detected as malware, or if something in the subject/content appears to be malicious.  Sending a simple test email can identify if the problem has to do with a specific message.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounce-back messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details explaining why the message was rejected, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@ncf.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@ncf.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=sender@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.56.78) which is not allowed to send mail according the SPF record on the sender's domain name (i.e. the part of their address following @, &amp;quot;somewhere.ca&amp;quot; in the example).&lt;br /&gt;
&lt;br /&gt;
'''SPF fail errors'''&lt;br /&gt;
&lt;br /&gt;
Domain names (e.g. &amp;quot;ncf.ca&amp;quot;) can set an SPF record to restrict which servers are allowed to send from their addresses (e.g. &amp;quot;name@ncf.ca&amp;quot;), which helps block messages sent from other servers [[Spam#Spoofing|spoofing]] their addresses.&lt;br /&gt;
&lt;br /&gt;
[https://duckduckgo.com/?q=SPF+check SPF tools] can be used to check if a server's IP is allowed by a domain name's SPF, or if there are problems with the SPF. &lt;br /&gt;
&lt;br /&gt;
Links to &amp;quot;openspf.net&amp;quot; no longer work because the site is offline, but the details in the link can be checked using another SPF tool.  For example this checks the details from the error above:&lt;br /&gt;
&lt;br /&gt;
https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;br /&gt;
&lt;br /&gt;
SPF records can also be checked manually, for example on the command line using &amp;quot;dig&amp;quot;:&lt;br /&gt;
 $ dig TXT +short ncf.ca&lt;br /&gt;
 &amp;quot;v=spf1 ip4:104.160.252.0/24 ip6:2607:c280:1::/64 mx a:mx4.ncf.ca a:mx5.ncf.ca a:mail.ncf.ca -all&amp;quot;&lt;br /&gt;
SPF records are normally set as TXT records and begin with &amp;quot;v=spf1&amp;quot;, followed by a list of allowed servers.  The ending &amp;quot;-all&amp;quot; indicates that all other servers are not allowed.&lt;br /&gt;
&lt;br /&gt;
Looking up the server's IP address via [https://search.arin.net/rdap/?query=104.160.252.11 Whois/RDAP] to see who it's registered to may help explain what changed to cause the error. For example, the sender may have changed which service provider they use for sending emails, and need to update their SPF to include the new provider's servers.&lt;br /&gt;
&lt;br /&gt;
'''Blacklist errors'''&lt;br /&gt;
&lt;br /&gt;
Another common reason for mail to be rejected is if the sender's mail server is [[Email blacklisting|blacklisted]] which is the case for errors like &amp;quot;Connection originating from an IP address with a poor reputation.&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
'''Other bounce-back reasons'''&lt;br /&gt;
&lt;br /&gt;
The recipient could be out of space in their mailbox, their address may not exist (e.g. typo in address, account disabled), or their mail server or domain name could be having problems.  The reason is usually explained in the bounce-back, otherwise the mail provider's IT can investigate using the details in the bounce-back.&lt;br /&gt;
&lt;br /&gt;
'''Testing bounce-back issues affecting all addresses on the same domain'''&lt;br /&gt;
&lt;br /&gt;
If messages to an address such as &amp;quot;recipient@somewhere.ca&amp;quot; are bouncing, a test can be sent to a fake address on the same domain such as &amp;quot;test@somewhere.ca&amp;quot; to check if it's a general problem with the server/domain (same bounce-back error), or specific to the account (the fake address may have a different error saying the address does not exist).  &lt;br /&gt;
[[Category:Email]]&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8419</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8419"/>
		<updated>2025-04-08T21:05:13Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, an error message may be sent back from the mail server explaining why the message was rejected.  In this case, the bounce-back should explain [[Emails not delivered#Undeliverable bounce-back messages|why the message was rejected]].&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the outbox, the problem is likely that the mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to the mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in the email should explain why it was detected as spam.  The recipient could also have a [[Spam#Zimbra Filters|mail filter]] which is removing the messages.   Otherwise, the mail provider can check their email logs to track what happened to an email by looking up the recipient/sender address and the time when the message was sent.&lt;br /&gt;
&lt;br /&gt;
Messages are often blocked because an attachment is too big or is detected as malware, or if something in the subject/content appears to be malicious.  Sending a simple test email can identify if the problem has to do with a specific message.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounce-back messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details explaining why the message was rejected, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@ncf.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@ncf.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=sender@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.56.78) which is not allowed to send mail according the SPF record on the sender's domain name (i.e. the part of their address following @, &amp;quot;somewhere.ca&amp;quot; in the example).&lt;br /&gt;
&lt;br /&gt;
'''SPF fail errors'''&lt;br /&gt;
&lt;br /&gt;
Domain names (e.g. &amp;quot;ncf.ca&amp;quot;) can set an SPF record to restrict which servers are allowed to send from their addresses (e.g. &amp;quot;name@ncf.ca&amp;quot;), which helps block messages sent from other servers [[Spam#Spoofing|spoofing]] their addresses.&lt;br /&gt;
&lt;br /&gt;
[https://duckduckgo.com/?q=SPF+check SPF tools] can be used to check if a server's IP is allowed by a domain name's SPF, or if there are problems with the SPF. &lt;br /&gt;
&lt;br /&gt;
Links to &amp;quot;openspf.net&amp;quot; no longer work because the site is offline, but the details in the link can be checked using another SPF tool.  For example using the details from the error above:&lt;br /&gt;
&lt;br /&gt;
https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;br /&gt;
&lt;br /&gt;
SPF records can also be checked manually, for example on the command line using &amp;quot;dig&amp;quot;:&lt;br /&gt;
 $ dig TXT +short ncf.ca&lt;br /&gt;
 &amp;quot;v=spf1 ip4:104.160.252.0/24 ip6:2607:c280:1::/64 mx a:mx4.ncf.ca a:mx5.ncf.ca a:mail.ncf.ca -all&amp;quot;&lt;br /&gt;
SPF records are normally set as TXT records and begin with &amp;quot;v=spf1&amp;quot;, followed by a list of allowed servers.  The ending &amp;quot;-all&amp;quot; indicates that all other servers are not allowed.&lt;br /&gt;
&lt;br /&gt;
Looking up the server's IP address via [https://search.arin.net/rdap/?query=104.160.252.11 Whois/RDAP] to see who it's registered to may help explain what changed to cause the error. For example, the sender may have changed which service provider they use for sending emails, and need to update their SPF to include the new provider's servers.&lt;br /&gt;
&lt;br /&gt;
'''Blacklist errors'''&lt;br /&gt;
&lt;br /&gt;
Another common reason for mail to be rejected is if the sender's mail server is [[Email blacklisting|blacklisted]] which is the case for errors like &amp;quot;Connection originating from an IP address with a poor reputation.&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
'''Other bounce-back reasons'''&lt;br /&gt;
&lt;br /&gt;
The recipient could be out of space in their mailbox, their address may not exist (e.g. typo in address, account disabled), or their mail server or domain name could be having problems.  The reason is usually explained in the bounce-back, otherwise the mail provider's IT can investigate using the details in the bounce-back.&lt;br /&gt;
&lt;br /&gt;
'''Testing bounce-back issues affecting all addresses on the same domain'''&lt;br /&gt;
&lt;br /&gt;
If messages to an address such as &amp;quot;recipient@somewhere.ca&amp;quot; are bouncing, a test can be sent to a fake address on the same domain such as &amp;quot;test@somewhere.ca&amp;quot; to check if it's a general problem with the server/domain (same bounce-back error), or specific to the account (the fake address may have a different error saying the address does not exist).  &lt;br /&gt;
[[Category:Email]]&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8418</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8418"/>
		<updated>2025-04-08T21:04:27Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, an error message may be sent back from the mail server explaining why the message was rejected.  In this case, the bounce-back should explain [[Emails not delivered#Undeliverable bounce-back messages|why the message was rejected]].&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the outbox, the problem is likely that the mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to the mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in the email should explain why it was detected as spam.  The recipient could also have a [[Spam#Zimbra Filters|mail filter]] which is removing the messages.   Otherwise, the mail provider can check their email logs to track what happened to an email by looking up the recipient/sender address and the time when the message was sent.&lt;br /&gt;
&lt;br /&gt;
Messages are often blocked because an attachment is too big or is detected as malware, or if something in the subject/content appears to be malicious.  Sending a simple test email can identify if the problem has to do with a specific message.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounce-back messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details explaining why the message was rejected, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@ncf.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@ncf.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=sender@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.56.78) which is not allowed to send mail according the SPF record on the sender's domain name (i.e. the part of their address following @, &amp;quot;somewhere.ca&amp;quot; in the example).&lt;br /&gt;
&lt;br /&gt;
'''SPF fail errors'''&lt;br /&gt;
&lt;br /&gt;
Domain names (e.g. &amp;quot;ncf.ca&amp;quot;) can set an SPF record to restrict which servers are allowed to send from their addresses (e.g. &amp;quot;name@ncf.ca&amp;quot;), which helps block messages sent from other servers [[Spam#Spoofing|spoofing]] their addresses.&lt;br /&gt;
&lt;br /&gt;
[https://duckduckgo.com/?q=SPF+check SPF tools] can be used to check if a server's IP is allowed by a domain name's SPF, or if there are problems with the SPF. &lt;br /&gt;
&lt;br /&gt;
Links to &amp;quot;openspf.net&amp;quot; no longer work because the site is offline, but the details in the link can be checked using another SPF tool.  For example using the details from the error above:&lt;br /&gt;
&lt;br /&gt;
https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;br /&gt;
&lt;br /&gt;
Looking up the server's IP address via [https://search.arin.net/rdap/?query=104.160.252.11 Whois/RDAP] to see who it's registered to may help explain what changed to cause the error. For example, the sender may have changed which service provider they use for sending emails, and need to update their SPF to include the new provider's servers.&lt;br /&gt;
&lt;br /&gt;
SPF records can also be checked manually, for example on the command line using &amp;quot;dig&amp;quot;:&lt;br /&gt;
 $ dig TXT +short ncf.ca&lt;br /&gt;
 &amp;quot;v=spf1 ip4:104.160.252.0/24 ip6:2607:c280:1::/64 mx a:mx4.ncf.ca a:mx5.ncf.ca a:mail.ncf.ca -all&amp;quot;&lt;br /&gt;
SPF records are normally set as TXT records and begin with &amp;quot;v=spf1&amp;quot;, followed by a list of allowed servers.  The ending &amp;quot;-all&amp;quot; indicates that all other servers are not allowed.&lt;br /&gt;
&lt;br /&gt;
'''Blacklist errors'''&lt;br /&gt;
&lt;br /&gt;
Another common reason for mail to be rejected is if the sender's mail server is [[Email blacklisting|blacklisted]] which is the case for errors like &amp;quot;Connection originating from an IP address with a poor reputation.&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
'''Other bounce-back reasons'''&lt;br /&gt;
&lt;br /&gt;
The recipient could be out of space in their mailbox, their address may not exist (e.g. typo in address, account disabled), or their mail server or domain name could be having problems.  The reason is usually explained in the bounce-back, otherwise the mail provider's IT can investigate using the details in the bounce-back.&lt;br /&gt;
&lt;br /&gt;
'''Testing bounce-back issues affecting all addresses on the same domain'''&lt;br /&gt;
&lt;br /&gt;
If messages to an address such as &amp;quot;recipient@somewhere.ca&amp;quot; are bouncing, a test can be sent to a fake address on the same domain such as &amp;quot;test@somewhere.ca&amp;quot; to check if it's a general problem with the server/domain (same bounce-back error), or specific to the account (the fake address may have a different error saying the address does not exist).  &lt;br /&gt;
[[Category:Email]]&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8417</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8417"/>
		<updated>2025-04-08T21:03:09Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, an error message may be sent back from the mail server explaining why the message was rejected.  In this case, the bounce-back should explain [[Emails not delivered#Undeliverable bounce-back messages|why the message was rejected]].&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the outbox, the problem is likely that the mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to the mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in the email should explain why it was detected as spam.  The recipient could also have a [[Spam#Zimbra Filters|mail filter]] which is removing the messages.   Otherwise, the mail provider can check their email logs to track what happened to an email by looking up the recipient/sender address and the time when the message was sent.&lt;br /&gt;
&lt;br /&gt;
Messages are often blocked because an attachment is too big or is detected as malware, or if something in the subject/content appears to be malicious.  Sending a simple test email can identify if the problem has to do with a specific message.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounce-back messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details explaining why the message was rejected, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@ncf.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@ncf.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=sender@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.56.78) which is not allowed to send mail according the SPF record on the sender's domain name (i.e. the part of their address following @, &amp;quot;somewhere.ca&amp;quot; in the example).&lt;br /&gt;
&lt;br /&gt;
'''SPF fail errors'''&lt;br /&gt;
&lt;br /&gt;
Domain names (e.g. &amp;quot;ncf.ca&amp;quot;) can set an SPF record to restrict which servers are allowed to send from their addresses (e.g. &amp;quot;name@ncf.ca&amp;quot;), which helps block messages sent from other servers [[Spam#Spoofing|spoofing]] their addresses.&lt;br /&gt;
&lt;br /&gt;
[https://duckduckgo.com/?q=SPF+check SPF tools] can be used to check if a server's IP is allowed by a domain name's SPF, or if there are problems with the SPF. &lt;br /&gt;
&lt;br /&gt;
Links to &amp;quot;openspf.net&amp;quot; no longer work because the site is offline, but the details in the link can be checked using another SPF tool.  For example using the details from the error above:&lt;br /&gt;
&lt;br /&gt;
https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;br /&gt;
&lt;br /&gt;
Looking up the server's IP address via [https://search.arin.net/rdap/?query=104.160.252.11 Whois/RDAP] to see who it's registered to may help explain what changed to cause the error. For example, the sender may have changed the service provider they use for sending emails, and need to update their SPF to include the new provider's servers.&lt;br /&gt;
&lt;br /&gt;
SPF records can also be checked manually, for example on the command line using &amp;quot;dig&amp;quot;:&lt;br /&gt;
 $ dig TXT +short ncf.ca&lt;br /&gt;
 &amp;quot;v=spf1 ip4:104.160.252.0/24 ip6:2607:c280:1::/64 mx a:mx4.ncf.ca a:mx5.ncf.ca a:mail.ncf.ca -all&amp;quot;&lt;br /&gt;
SPF records are normally set as TXT records and begin with &amp;quot;v=spf1&amp;quot;, followed by a list of allowed servers.  The ending &amp;quot;-all&amp;quot; indicates that all other servers are not allowed.&lt;br /&gt;
&lt;br /&gt;
'''Blacklist errors'''&lt;br /&gt;
&lt;br /&gt;
Another common reason for mail to be rejected is if the sender's mail server is [[Email blacklisting|blacklisted]] which is the case for errors like &amp;quot;Connection originating from an IP address with a poor reputation.&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
'''Other bounce-back reasons'''&lt;br /&gt;
&lt;br /&gt;
The recipient could be out of space in their mailbox, their address may not exist (e.g. typo in address, account disabled), or their mail server or domain name could be having problems.  The reason is usually explained in the bounce-back, otherwise the mail provider's IT can investigate using the details in the bounce-back.&lt;br /&gt;
&lt;br /&gt;
'''Testing bounce-back issues affecting all addresses on the same domain'''&lt;br /&gt;
&lt;br /&gt;
If messages to an address such as &amp;quot;recipient@somewhere.ca&amp;quot; are bouncing, a test can be sent to a fake address on the same domain such as &amp;quot;test@somewhere.ca&amp;quot; to check if it's a general problem with the server/domain (same bounce-back error), or specific to the account (the fake address may have a different error saying the address does not exist).  &lt;br /&gt;
[[Category:Email]]&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8416</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8416"/>
		<updated>2025-04-08T20:53:49Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, an error message may be sent back from the mail server explaining why the message was rejected.  In this case, the bounce-back should explain [[Emails not delivered#Undeliverable bounce-back messages|why the message was rejected]].&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the outbox, the problem is likely that the mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to the mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in the email should explain why it was detected as spam.  The recipient could also have a [[Spam#Zimbra Filters|mail filter]] which is removing the messages.   Otherwise, the mail provider can check their email logs to track what happened to an email by looking up the recipient/sender address and the time when the message was sent.&lt;br /&gt;
&lt;br /&gt;
Messages are often blocked because an attachment is too big or is detected as malware, or if something in the subject/content appears to be malicious.  Sending a simple test email can identify if the problem has to do with a specific message.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounce-back messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details explaining why the message was rejected, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@ncf.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@ncf.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=sender@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.56.78) which is not allowed to send mail according the SPF record on the sender's domain name (i.e. the part of their address following @, &amp;quot;somewhere.ca&amp;quot; in the example).&lt;br /&gt;
&lt;br /&gt;
'''SPF fail errors'''&lt;br /&gt;
&lt;br /&gt;
Domain names (e.g. &amp;quot;ncf.ca&amp;quot;) can set an SPF record to restrict which servers are allowed to send from their addresses (e.g. &amp;quot;name@ncf.ca&amp;quot;), which helps block messages sent from other servers [[Spam#Spoofing|spoofing]] their addresses.&lt;br /&gt;
&lt;br /&gt;
[https://duckduckgo.com/?q=SPF+check SPF tools] can be used to check if a server's IP is allowed by a domain name's SPF, or if there are problems with the SPF. &lt;br /&gt;
&lt;br /&gt;
Links to &amp;quot;openspf.net&amp;quot; no longer work because the site is offline, but the details in the link can be checked using another SPF tool.  For example using the details from the error above:&lt;br /&gt;
&lt;br /&gt;
https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;br /&gt;
&lt;br /&gt;
Looking up the owner of the server's IP address via [https://search.arin.net/rdap/?query=104.160.252.11 Whois/RDAP] might help explain what changed to cause the error. For example, the sender may have changed to a new email provider and need to update their SPF to include the new provider's servers.&lt;br /&gt;
&lt;br /&gt;
SPF records can also be checked manually, for example on the command line using &amp;quot;dig&amp;quot;:&lt;br /&gt;
 $ dig TXT +short ncf.ca&lt;br /&gt;
 &amp;quot;v=spf1 ip4:104.160.252.0/24 ip6:2607:c280:1::/64 mx a:mx4.ncf.ca a:mx5.ncf.ca a:mail.ncf.ca -all&amp;quot;&lt;br /&gt;
SPF records are normally set as TXT records and begin with &amp;quot;v=spf1&amp;quot;, followed by a list of allowed servers.  The ending &amp;quot;-all&amp;quot; indicates that all other servers are not allowed.&lt;br /&gt;
&lt;br /&gt;
'''Blacklist errors'''&lt;br /&gt;
&lt;br /&gt;
Another common reason for mail to be rejected is if the sender's mail server is [[Email blacklisting|blacklisted]] which is the case for errors like &amp;quot;Connection originating from an IP address with a poor reputation.&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
'''Other bounce-back reasons'''&lt;br /&gt;
&lt;br /&gt;
The recipient could be out of space in their mailbox, their address may not exist (e.g. typo in address, account disabled), or their mail server or domain name could be having problems.  The reason is usually explained in the bounce-back, otherwise the mail provider's IT can investigate using the details in the bounce-back.&lt;br /&gt;
&lt;br /&gt;
'''Testing bounce-back issues affecting all addresses on the same domain'''&lt;br /&gt;
&lt;br /&gt;
If messages to an address such as &amp;quot;recipient@somewhere.ca&amp;quot; are bouncing, a test can be sent to a fake address on the same domain such as &amp;quot;test@somewhere.ca&amp;quot; to check if it's a general problem with the server/domain (same bounce-back error), or specific to the account (the fake address may have a different error saying the address does not exist).  &lt;br /&gt;
[[Category:Email]]&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8415</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8415"/>
		<updated>2025-04-08T20:47:58Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, an error message may be sent back from the mail server explaining why the message was rejected.  In this case, the bounce-back should explain [[Emails not delivered#Undeliverable bounce-back messages|why the message was rejected]].&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the outbox, the problem is likely that the mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to the mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in the email should explain why it was detected as spam.  The recipient could also have a [[Spam#Zimbra Filters|mail filter]] which is removing the messages.   Otherwise, the mail provider can check their email logs to track what happened to an email by looking up the recipient/sender address and the time when the message was sent.&lt;br /&gt;
&lt;br /&gt;
Messages are often blocked because an attachment is too big or is detected as malware, or if something in the subject/content appears to be malicious.  Sending a simple test email can identify if the problem has to do with a specific message.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounce-back messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details explaining why the message was rejected, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@ncf.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@ncf.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=sender@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.56.78) which is not allowed to send mail according the SPF record on the sender's domain name (i.e. the part of their address following @, &amp;quot;somewhere.ca&amp;quot; in the example).&lt;br /&gt;
&lt;br /&gt;
'''SPF fail errors'''&lt;br /&gt;
&lt;br /&gt;
Domain names (e.g. &amp;quot;ncf.ca&amp;quot;) can set an SPF record to restrict which servers are allowed to send from their addresses (e.g. &amp;quot;name@ncf.ca&amp;quot;), which helps block messages sent from other servers [[Spam#Spoofing|spoofing]] their addresses.&lt;br /&gt;
&lt;br /&gt;
[https://duckduckgo.com/?q=SPF+check SPF checking tools] can be used to check if a server's IP is allowed by a domain name's SPF, or if there are problems with the SPF. &lt;br /&gt;
&lt;br /&gt;
Links to &amp;quot;openspf.net&amp;quot; no longer work because the site is offline, but the details in the link can be checked using another SPF tool.  For example using the details from the error above:&lt;br /&gt;
&lt;br /&gt;
https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;br /&gt;
&lt;br /&gt;
Looking up the owner of the server's IP address on [https://search.arin.net/rdap/?query=104.160.252.11 ARIN Whois/RDAP] might help explain what changed to cause the error. For example, the sender might have changed to a new email provider and they need to update their SPF to include the new provider's servers.&lt;br /&gt;
&lt;br /&gt;
SPF records can also be checked manually, for example on the command line using &amp;quot;dig&amp;quot;:&lt;br /&gt;
 $ dig TXT +short ncf.ca&lt;br /&gt;
 &amp;quot;v=spf1 ip4:104.160.252.0/24 ip6:2607:c280:1::/64 mx a:mx4.ncf.ca a:mx5.ncf.ca a:mail.ncf.ca -all&amp;quot;&lt;br /&gt;
SPF records are normally set as TXT records and begin with &amp;quot;v=spf1&amp;quot;, followed by a list of allowed servers.  The ending &amp;quot;-all&amp;quot; indicates that all other servers are not allowed.&lt;br /&gt;
&lt;br /&gt;
'''Blacklist errors'''&lt;br /&gt;
&lt;br /&gt;
Another common reason for mail to be rejected is if the sender's mail server is [[Email blacklisting|blacklisted]] which is the case for errors like &amp;quot;Connection originating from an IP address with a poor reputation.&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
'''Other bounce-back reasons'''&lt;br /&gt;
&lt;br /&gt;
The recipient could be out of space in their mailbox, their address may not exist (e.g. typo in address, account disabled), or their mail server or domain name could be having problems.  The reason is usually explained in the bounce-back, otherwise the mail provider's IT can investigate using the details in the bounce-back.&lt;br /&gt;
&lt;br /&gt;
'''Testing bounce-back issues affecting all addresses on the same domain'''&lt;br /&gt;
&lt;br /&gt;
If messages to an address such as &amp;quot;recipient@somewhere.ca&amp;quot; are bouncing, a test can be sent to a fake address on the same domain such as &amp;quot;test@somewhere.ca&amp;quot; to check if it's a general problem with the server/domain (same bounce-back error), or specific to the account (the fake address may have a different error saying the address does not exist).  &lt;br /&gt;
[[Category:Email]]&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8414</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8414"/>
		<updated>2025-04-08T20:47:24Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, an error message may be sent back from the mail server explaining why the message was rejected.  In this case, the bounce-back should explain [[Emails not delivered#Undeliverable bounce-back messages|why the message was rejected]].&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the outbox, the problem is likely that the mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to the mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in the email should explain why it was detected as spam.  The recipient could also have a [[Spam#Zimbra Filters|mail filter]] which is removing the messages.   Otherwise, the mail provider can check their email logs to track what happened to an email by looking up the recipient/sender address and the time when the message was sent.&lt;br /&gt;
&lt;br /&gt;
Messages are often blocked because an attachment is too big or is detected as malware, or if something in the subject/content appears to be malicious.  Sending a simple test email can identify if the problem has to do with a specific message.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounce-back messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details explaining why the message was rejected, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@ncf.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@ncf.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=sender@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.56.78) which is not allowed to send mail according the SPF record on the sender's domain name (i.e. the part of their address following @, &amp;quot;somewhere.ca&amp;quot; in the example).&lt;br /&gt;
&lt;br /&gt;
'''SPF fail errors'''&lt;br /&gt;
&lt;br /&gt;
Domain names (e.g. &amp;quot;ncf.ca&amp;quot;) can set an SPF record to restrict which servers are allowed to send from their addresses (e.g. &amp;quot;name@ncf.ca&amp;quot;), which helps block messages sent from other servers [[Spam#Spoofing|spoofing]] their addresses.&lt;br /&gt;
&lt;br /&gt;
[https://duckduckgo.com/?q=SPF+check SPF checking tools] can be used to check if a server's IP is allowed by a domain name's SPF, or if there are problems with the SPF. &lt;br /&gt;
&lt;br /&gt;
Links to &amp;quot;openspf.net&amp;quot; no longer work because the site is offline, but the details in the link can be checked using another SPF tool.  For example using the details from the error above:&lt;br /&gt;
&lt;br /&gt;
https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;br /&gt;
&lt;br /&gt;
Looking up the owner of the server's IP address on [https://search.arin.net/rdap/?query=104.160.252.11 ARIN Whois/RDAP] might help explain what changed to cause the error. For example, the sender might have changed to a new email provider and they need to update their SPF to include the new provider's servers.&lt;br /&gt;
&lt;br /&gt;
The SPF record can also be checked manually, for example on the command line using &amp;quot;dig&amp;quot;:&lt;br /&gt;
 $ dig TXT +short ncf.ca&lt;br /&gt;
 &amp;quot;v=spf1 ip4:104.160.252.0/24 ip6:2607:c280:1::/64 mx a:mx4.ncf.ca a:mx5.ncf.ca a:mail.ncf.ca -all&amp;quot;&lt;br /&gt;
SPF records are normally set as TXT records and begin with &amp;quot;v=spf1&amp;quot;, followed by a list of allowed servers.  The ending &amp;quot;-all&amp;quot; indicates that all other servers are not allowed.&lt;br /&gt;
&lt;br /&gt;
'''Blacklist errors'''&lt;br /&gt;
&lt;br /&gt;
Another common reason for mail to be rejected is if the sender's mail server is [[Email blacklisting|blacklisted]] which is the case for errors like &amp;quot;Connection originating from an IP address with a poor reputation.&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
'''Other bounce-back reasons'''&lt;br /&gt;
&lt;br /&gt;
The recipient could be out of space in their mailbox, their address may not exist (e.g. typo in address, account disabled), or their mail server or domain name could be having problems.  The reason is usually explained in the bounce-back, otherwise the mail provider's IT can investigate using the details in the bounce-back.&lt;br /&gt;
&lt;br /&gt;
'''Testing bounce-back issues affecting all addresses on the same domain'''&lt;br /&gt;
&lt;br /&gt;
If messages to an address such as &amp;quot;recipient@somewhere.ca&amp;quot; are bouncing, a test can be sent to a fake address on the same domain such as &amp;quot;test@somewhere.ca&amp;quot; to check if it's a general problem with the server/domain (same bounce-back error), or specific to the account (the fake address may have a different error saying the address does not exist).  &lt;br /&gt;
[[Category:Email]]&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8413</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8413"/>
		<updated>2025-04-08T20:44:20Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, an error message may be sent back from the mail server explaining why the message was rejected.  In this case, the bounce-back should explain [[Emails not delivered#Undeliverable bounce-back messages|why the message was rejected]].&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the outbox, the problem is likely that the mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to the mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in the email should explain why it was detected as spam.  The recipient could also have a [[Spam#Zimbra Filters|mail filter]] which is removing the messages.   Otherwise, the mail provider can check their email logs to track what happened to an email by looking up the recipient/sender address and the time when the message was sent.&lt;br /&gt;
&lt;br /&gt;
Messages are often blocked because an attachment is too big or is detected as malware, or if something in the subject/content appears to be malicious.  Sending a simple test email can identify if the problem has to do with a specific message.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounce-back messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details explaining why the message was rejected, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@ncf.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@ncf.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=sender@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.56.78) which is not allowed to send mail according the SPF record on the sender's domain name (i.e. the part of their address following @, &amp;quot;somewhere.ca&amp;quot; in the example).&lt;br /&gt;
&lt;br /&gt;
'''SPF fail errors'''&lt;br /&gt;
&lt;br /&gt;
Domain names (e.g. &amp;quot;ncf.ca&amp;quot;) can set an SPF record to restrict which servers are allowed to send from their addresses (e.g. &amp;quot;name@ncf.ca&amp;quot;), which helps block messages sent from other servers [[Spam#Spoofing|spoofing]] their addresses.&lt;br /&gt;
&lt;br /&gt;
[https://duckduckgo.com/?q=SPF+check SPF checking tools] can be used to check if a server's IP is allowed by a domain name's SPF, or if there are problems with the SPF. &lt;br /&gt;
&lt;br /&gt;
Links to &amp;quot;openspf.net&amp;quot; no longer work because the site is offline, but the details in the link can be checked using another SPF tool.  For example using the details from the error above:&lt;br /&gt;
&lt;br /&gt;
https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;br /&gt;
&lt;br /&gt;
Looking up the owner of the server's IP address might help explain what changed, that can be checked with [https://search.arin.net/rdap/?query=104.160.252.11 ARIN Whois/RDAP]. For example, the sender might have changed to a new email provider and need to update their SPF to include the new provider's servers.&lt;br /&gt;
&lt;br /&gt;
The SPF record can also be checked manually, for example on the command line using &amp;quot;dig&amp;quot;:&lt;br /&gt;
 $ dig TXT +short ncf.ca&lt;br /&gt;
 &amp;quot;v=spf1 ip4:104.160.252.0/24 ip6:2607:c280:1::/64 mx a:mx4.ncf.ca a:mx5.ncf.ca a:mail.ncf.ca -all&amp;quot;&lt;br /&gt;
SPF records are normally set as TXT records and begin with &amp;quot;v=spf1&amp;quot;, followed by a list of allowed servers.  The ending &amp;quot;-all&amp;quot; indicates that all other servers are not allowed.&lt;br /&gt;
&lt;br /&gt;
'''Blacklist errors'''&lt;br /&gt;
&lt;br /&gt;
Another common reason for mail to be rejected is if the sender's mail server is [[Email blacklisting|blacklisted]] which is the case for errors like &amp;quot;Connection originating from an IP address with a poor reputation.&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
'''Other bounce-back reasons'''&lt;br /&gt;
&lt;br /&gt;
The recipient could be out of space in their mailbox, their address may not exist (e.g. typo in address, account disabled), or their mail server or domain name could be having problems.  The reason is usually explained in the bounce-back, otherwise the mail provider's IT can investigate using the details in the bounce-back.&lt;br /&gt;
&lt;br /&gt;
'''Testing bounce-back issues affecting all addresses on the same domain'''&lt;br /&gt;
&lt;br /&gt;
If messages to an address such as &amp;quot;recipient@somewhere.ca&amp;quot; are bouncing, a test can be sent to a fake address on the same domain such as &amp;quot;test@somewhere.ca&amp;quot; to check if it's a general problem with the server/domain (same bounce-back error), or specific to the account (the fake address may have a different error saying the address does not exist).  &lt;br /&gt;
[[Category:Email]]&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8412</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8412"/>
		<updated>2025-04-08T20:14:19Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, an error message may be sent back from the mail server explaining why the message was rejected.  In this case, the bounce-back should explain [[Emails not delivered#Undeliverable bounce-back messages|why the message was rejected]].&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the outbox, the problem is likely that the mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to the mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in the email should explain why it was detected as spam.  The recipient could also have a [[Spam#Zimbra Filters|mail filter]] which is removing the messages.   Otherwise, the mail provider can check their email logs to track what happened to an email by looking up the recipient/sender address and the time when the message was sent.&lt;br /&gt;
&lt;br /&gt;
Messages are often blocked because an attachment is too big or is detected as malware, or if something in the subject/content appears to be malicious.  Sending a simple test email can identify if the problem has to do with a specific message.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounce-back messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details explaining why the message was rejected, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@ncf.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@ncf.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=sender@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.56.78) which is not allowed to send mail according the SPF record on the sender's domain name (i.e. the part of their address following @, &amp;quot;somewhere.ca&amp;quot; in the example).&lt;br /&gt;
&lt;br /&gt;
'''SPF fail errors'''&lt;br /&gt;
&lt;br /&gt;
Domain names (e.g. &amp;quot;ncf.ca&amp;quot;) can set an SPF record to restrict which servers are allowed to send from their addresses (e.g. &amp;quot;name@ncf.ca&amp;quot;), which helps block messages sent from other servers [[Spam#Spoofing|spoofing]] their addresses.&lt;br /&gt;
&lt;br /&gt;
[https://duckduckgo.com/?q=SPF+check SPF checking tools] can be used to check if a server's IP is allowed by a domain name's SPF, or if there are problems with the SPF. &lt;br /&gt;
&lt;br /&gt;
Links to &amp;quot;openspf.net&amp;quot; no longer work because the site is offline, but the details in the link can be checked using another SPF tool.  For example using the details from the error above:&lt;br /&gt;
&lt;br /&gt;
https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;br /&gt;
&lt;br /&gt;
The SPF record can also be checked manually, for example on the command line using &amp;quot;dig&amp;quot;:&lt;br /&gt;
 $ dig TXT +short ncf.ca&lt;br /&gt;
 &amp;quot;v=spf1 ip4:104.160.252.0/24 ip6:2607:c280:1::/64 mx a:mx4.ncf.ca a:mx5.ncf.ca a:mail.ncf.ca -all&amp;quot;&lt;br /&gt;
SPF records are normally set as TXT records and begin with &amp;quot;v=spf1&amp;quot;, followed by a list of allowed servers.  The ending &amp;quot;-all&amp;quot; indicates that all other servers are not allowed.&lt;br /&gt;
&lt;br /&gt;
'''Blacklist errors'''&lt;br /&gt;
&lt;br /&gt;
Another common reason for mail to be rejected is if the sender's mail server is [[Email blacklisting|blacklisted]] which is the case for errors like &amp;quot;Connection originating from an IP address with a poor reputation.&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
'''Other bounce-back reasons'''&lt;br /&gt;
&lt;br /&gt;
The recipient could be out of space in their mailbox, their address may not exist (e.g. typo in address, account disabled), or their mail server or domain name could be having problems.  The reason is usually explained in the bounce-back, otherwise the mail provider's IT can investigate using the details in the bounce-back.&lt;br /&gt;
&lt;br /&gt;
'''Testing bounce-back issues affecting all addresses on the same domain'''&lt;br /&gt;
&lt;br /&gt;
If messages to an address such as &amp;quot;recipient@somewhere.ca&amp;quot; are bouncing, a test can be sent to a fake address on the same domain such as &amp;quot;test@somewhere.ca&amp;quot; to check if it's a general problem with the server/domain (same bounce-back error), or specific to the account (the fake address may have a different error saying the address does not exist).  &lt;br /&gt;
[[Category:Email]]&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8411</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8411"/>
		<updated>2025-04-08T20:11:13Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, an error message may be sent back from the mail server explaining why the message was rejected.  In this case, the bounce-back should explain [[Emails not delivered#Undeliverable bounce-back messages|why the message was rejected]].&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the outbox, the problem is likely that the mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to the mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in the email should explain why it was detected as spam.  The recipient could also have a [[Spam#Zimbra Filters|mail filter]] which is removing the messages.   Otherwise, the mail provider can check their email logs to track what happened to an email by looking up the recipient/sender address and the time when the message was sent.&lt;br /&gt;
&lt;br /&gt;
Messages are often blocked because an attachment is too big or is detected as malware, or if something in the subject/content appears to be malicious.  Sending a simple test email can identify if the problem has to do with a specific message.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounce-back messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details explaining why the message was rejected, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@ncf.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@ncf.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=sender@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.56.78) which is not allowed to send mail according the SPF record on the sender's domain name (i.e. the part of their address following @, &amp;quot;somewhere.ca&amp;quot; in the example).&lt;br /&gt;
&lt;br /&gt;
'''SPF fail errors'''&lt;br /&gt;
&lt;br /&gt;
Domain names (e.g. &amp;quot;ncf.ca&amp;quot;) can set an SPF record to restrict which servers are allowed to send from their addresses (e.g. &amp;quot;name@ncf.ca&amp;quot;), which helps block messages sent from other servers [[Spam#Spoofing|spoofing]] their addresses.&lt;br /&gt;
&lt;br /&gt;
[https://duckduckgo.com/?q=SPF+check SPF checking tools] can be used to check if a server's IP is allowed by a domain name's SPF, or if there are problems with the SPF. &lt;br /&gt;
&lt;br /&gt;
Links to &amp;quot;openspf.net&amp;quot; no longer work because the site is offline, but the details in the link can be checked using another SPF tool.  For example using the details from the error above:&lt;br /&gt;
&lt;br /&gt;
https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;br /&gt;
&lt;br /&gt;
The SPF record can also be checked manually, for example on the command line using &amp;quot;dig&amp;quot;:&lt;br /&gt;
 $ dig TXT +short ncf.ca&lt;br /&gt;
 &amp;quot;v=spf1 ip4:104.160.252.0/24 ip6:2607:c280:1::/64 mx a:mx4.ncf.ca a:mx5.ncf.ca a:mail.ncf.ca -all&amp;quot;&lt;br /&gt;
SPF records are normally set as TXT records and begin with &amp;quot;v=spf1&amp;quot;, followed by a list of allowed servers.  The ending &amp;quot;-all&amp;quot; indicates that all other servers are not allowed.&lt;br /&gt;
&lt;br /&gt;
'''Blacklist errors'''&lt;br /&gt;
&lt;br /&gt;
Another common reason for mail to be rejected is if the sender's mail server is [[Email blacklisting|blacklisted]] which is the case for errors like &amp;quot;Connection originating from an IP address with a poor reputation.&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
'''Other bounce-back reasons'''&lt;br /&gt;
&lt;br /&gt;
The recipient could be out of space in their mailbox, their address may not exist (e.g. typo in address, account disabled), or their mail server or domain name could be having problems.  The reason is usually explained in the bounce-back, otherwise the mail provider's IT can investigate using the details in the bounce-back.&lt;br /&gt;
&lt;br /&gt;
'''Testing bounce-back to a server'''&lt;br /&gt;
&lt;br /&gt;
If messages to an address such as &amp;quot;recipient@somewhere.ca&amp;quot; are bouncing, a test can be sent to a fake address on the same domain such as &amp;quot;test@somewhere.ca&amp;quot; to check if it's a general problem with the server (same bounce-back error), or specific to the account (the fake address may have a different error saying the address does not exist).  &lt;br /&gt;
[[Category:Email]]&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8410</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8410"/>
		<updated>2025-04-08T20:10:58Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, an error message may be sent back from the mail server explaining why the message was rejected.  In this case, the bounce-back should explain [[Emails not delivered#Undeliverable bounce-back messages|why the message was rejected]].&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the outbox, the problem is likely that the mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to the mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in the email should explain why it was detected as spam.  The recipient could also have a [[Spam#Zimbra Filters|mail filter]] which is removing the messages.   Otherwise, the mail provider can check their email logs to track what happened to an email by looking up the recipient/sender address and the time when the message was sent.&lt;br /&gt;
&lt;br /&gt;
Messages are often blocked because an attachment is too big or is detected as malware, or if something in the subject/content appears to be malicious.  Sending a simple test email can identify if the problem has to do with a specific message.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounce-back messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details explaining why the message was rejected, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@ncf.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@ncf.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=sender@somewhere.ca;ip=12.34.156.178;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.156.178) which is not allowed to send mail according the SPF record on the sender's domain name (i.e. the part of their address following @, &amp;quot;somewhere.ca&amp;quot; in the example).&lt;br /&gt;
&lt;br /&gt;
'''SPF fail errors'''&lt;br /&gt;
&lt;br /&gt;
Domain names (e.g. &amp;quot;ncf.ca&amp;quot;) can set an SPF record to restrict which servers are allowed to send from their addresses (e.g. &amp;quot;name@ncf.ca&amp;quot;), which helps block messages sent from other servers [[Spam#Spoofing|spoofing]] their addresses.&lt;br /&gt;
&lt;br /&gt;
[https://duckduckgo.com/?q=SPF+check SPF checking tools] can be used to check if a server's IP is allowed by a domain name's SPF, or if there are problems with the SPF. &lt;br /&gt;
&lt;br /&gt;
Links to &amp;quot;openspf.net&amp;quot; no longer work because the site is offline, but the details in the link can be checked using another SPF tool.  For example using the details from the error above:&lt;br /&gt;
&lt;br /&gt;
https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;br /&gt;
&lt;br /&gt;
The SPF record can also be checked manually, for example on the command line using &amp;quot;dig&amp;quot;:&lt;br /&gt;
 $ dig TXT +short ncf.ca&lt;br /&gt;
 &amp;quot;v=spf1 ip4:104.160.252.0/24 ip6:2607:c280:1::/64 mx a:mx4.ncf.ca a:mx5.ncf.ca a:mail.ncf.ca -all&amp;quot;&lt;br /&gt;
SPF records are normally set as TXT records and begin with &amp;quot;v=spf1&amp;quot;, followed by a list of allowed servers.  The ending &amp;quot;-all&amp;quot; indicates that all other servers are not allowed.&lt;br /&gt;
&lt;br /&gt;
'''Blacklist errors'''&lt;br /&gt;
&lt;br /&gt;
Another common reason for mail to be rejected is if the sender's mail server is [[Email blacklisting|blacklisted]] which is the case for errors like &amp;quot;Connection originating from an IP address with a poor reputation.&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
'''Other bounce-back reasons'''&lt;br /&gt;
&lt;br /&gt;
The recipient could be out of space in their mailbox, their address may not exist (e.g. typo in address, account disabled), or their mail server or domain name could be having problems.  The reason is usually explained in the bounce-back, otherwise the mail provider's IT can investigate using the details in the bounce-back.&lt;br /&gt;
&lt;br /&gt;
'''Testing bounce-back to a server'''&lt;br /&gt;
&lt;br /&gt;
If messages to an address such as &amp;quot;recipient@somewhere.ca&amp;quot; are bouncing, a test can be sent to a fake address on the same domain such as &amp;quot;test@somewhere.ca&amp;quot; to check if it's a general problem with the server (same bounce-back error), or specific to the account (the fake address may have a different error saying the address does not exist).  &lt;br /&gt;
[[Category:Email]]&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8409</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8409"/>
		<updated>2025-04-08T20:09:43Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, an error message may be sent back from the mail server explaining why the message was rejected.  In this case, the bounce-back should explain [[Emails not delivered#Undeliverable bounce-back messages|why the message was rejected]].&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the outbox, the problem is likely that the mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to the mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in the email should explain why it was detected as spam.  The recipient could also have a [[Spam#Zimbra Filters|mail filter]] which is removing the messages.   Otherwise, the mail provider can check their email logs to track what happened to an email by looking up the recipient/sender address and the time when the message was sent.&lt;br /&gt;
&lt;br /&gt;
Messages are often blocked because an attachment is too big or is detected as malware, or if something in the subject/content appears to be malicious.  Sending a simple test email can identify if the problem has to do with a specific message.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounce-back messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details explaining why the message was rejected, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@ncf.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@ncf.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=sender@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.56.78) which is not allowed to send mail according the SPF record on the sender's domain name (i.e. the part of their address following @, &amp;quot;somewhere.ca&amp;quot; in the example).&lt;br /&gt;
&lt;br /&gt;
'''SPF fail errors'''&lt;br /&gt;
&lt;br /&gt;
Domain names (e.g. &amp;quot;ncf.ca&amp;quot;) can set an SPF record to restrict which servers are allowed to send from their addresses (e.g. &amp;quot;name@ncf.ca&amp;quot;), which helps block messages sent from other servers [[Spam#Spoofing|spoofing]] their addresses.&lt;br /&gt;
&lt;br /&gt;
[https://duckduckgo.com/?q=SPF+check SPF checking tools] can be used to check if a server's IP is allowed by a domain name's SPF, or if there are problems with the SPF. &lt;br /&gt;
&lt;br /&gt;
Links to &amp;quot;openspf.net&amp;quot; no longer work because the site is offline, but the details in the link can be checked using another SPF tool.  For example using the details from the error above:&lt;br /&gt;
&lt;br /&gt;
https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;br /&gt;
&lt;br /&gt;
The SPF record can also be checked manually, for example on the command line using &amp;quot;dig&amp;quot;:&lt;br /&gt;
 $ dig TXT +short ncf.ca&lt;br /&gt;
 &amp;quot;v=spf1 ip4:104.160.252.0/24 ip6:2607:c280:1::/64 mx a:mx4.ncf.ca a:mx5.ncf.ca a:mail.ncf.ca -all&amp;quot;&lt;br /&gt;
SPF records are normally set as TXT records and begin with &amp;quot;v=spf1&amp;quot;, followed by a list of allowed servers.  The ending &amp;quot;-all&amp;quot; indicates that all other servers are not allowed.&lt;br /&gt;
&lt;br /&gt;
'''Blacklist errors'''&lt;br /&gt;
&lt;br /&gt;
Another common reason for mail to be rejected is if the sender's mail server is [[Email blacklisting|blacklisted]] which is the case for errors like &amp;quot;Connection originating from an IP address with a poor reputation.&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
'''Other bounce-back reasons'''&lt;br /&gt;
&lt;br /&gt;
The recipient could be out of space in their mailbox, their address may not exist (e.g. typo in address, account disabled), or their mail server or domain name could be having problems.  The reason is usually explained in the bounce-back, otherwise the mail provider's IT can investigate using the details in the bounce-back.&lt;br /&gt;
&lt;br /&gt;
'''Testing bounce-back to a server'''&lt;br /&gt;
&lt;br /&gt;
If messages to an address such as &amp;quot;recipient@somewhere.ca&amp;quot; are bouncing, a test can be sent to a fake address on the same domain such as &amp;quot;test@somewhere.ca&amp;quot; to check if it's a general problem with the server (same bounce-back error), or specific to the account (the fake address may have a different error saying the address does not exist).  &lt;br /&gt;
[[Category:Email]]&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8408</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8408"/>
		<updated>2025-04-08T20:08:31Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, an error message may be sent back from the mail server explaining why the message was rejected.  In this case, the bounce-back should explain [[Emails not delivered#Undeliverable bounce-back messages|why the message was rejected]].&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the outbox, the problem is likely that the mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to the mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in the email should explain why it was detected as spam.  The recipient could also have a [[Spam#Zimbra Filters|mail filter]] which is removing the messages.   Otherwise, the mail provider can check their email logs to track what happened to an email by looking up the recipient/sender address and the time when the message was sent.&lt;br /&gt;
&lt;br /&gt;
Messages are often blocked because an attachment is too big or is detected as malware, or if something in the subject/content appears to be malicious.  Sending a simple test email can identify if the problem has to do with a specific message.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounceback messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details of the reason for the bounce back, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@ncf.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@ncf.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=sender@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.56.78) which is not allowed to send mail according the SPF record on the sender's domain name (i.e. the part of their address following @, &amp;quot;somewhere.ca&amp;quot; in the example).&lt;br /&gt;
&lt;br /&gt;
'''SPF fail errors'''&lt;br /&gt;
&lt;br /&gt;
Domain names (e.g. &amp;quot;ncf.ca&amp;quot;) can set an SPF record to restrict which servers are allowed to send from their addresses (e.g. &amp;quot;name@ncf.ca&amp;quot;), which helps block messages sent from other servers [[Spam#Spoofing|spoofing]] their addresses.&lt;br /&gt;
&lt;br /&gt;
[https://duckduckgo.com/?q=SPF+check SPF checking tools] can be used to check if a server's IP is allowed by a domain name's SPF, or if there are problems with the SPF. &lt;br /&gt;
&lt;br /&gt;
Links to &amp;quot;openspf.net&amp;quot; no longer work because the site is offline, but the details in the link can be checked using another SPF tool.  For example using the details from the error above:&lt;br /&gt;
&lt;br /&gt;
https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;br /&gt;
&lt;br /&gt;
The SPF record can also be checked manually, for example on the command line using &amp;quot;dig&amp;quot;:&lt;br /&gt;
 $ dig TXT +short ncf.ca&lt;br /&gt;
 &amp;quot;v=spf1 ip4:104.160.252.0/24 ip6:2607:c280:1::/64 mx a:mx4.ncf.ca a:mx5.ncf.ca a:mail.ncf.ca -all&amp;quot;&lt;br /&gt;
SPF records are normally set as TXT records and begin with &amp;quot;v=spf1&amp;quot;, followed by a list of allowed servers.  The ending &amp;quot;-all&amp;quot; indicates that all other servers are not allowed.&lt;br /&gt;
&lt;br /&gt;
'''Blacklist errors'''&lt;br /&gt;
&lt;br /&gt;
Another common reason for mail to be rejected is if the sender's mail server is [[Email blacklisting|blacklisted]] which is the case for errors like &amp;quot;Connection originating from an IP address with a poor reputation.&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
'''Other bounce-back reasons'''&lt;br /&gt;
&lt;br /&gt;
The recipient could be out of space in their mailbox, their address may not exist (e.g. typo in address, account disabled), or their mail server or domain name could be having problems.  The reason is usually explained in the bounce-back, otherwise the mail provider's IT can investigate using the details in the bounce-back.&lt;br /&gt;
&lt;br /&gt;
'''Testing bounce-back to a server'''&lt;br /&gt;
&lt;br /&gt;
If messages to an address such as &amp;quot;recipient@somewhere.ca&amp;quot; are bouncing, a test can be sent to a fake address on the same domain such as &amp;quot;test@somewhere.ca&amp;quot; to check if it's a general problem with the server (same bounce-back error), or specific to the account (the fake address may have a different error saying the address does not exist).  &lt;br /&gt;
[[Category:Email]]&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8407</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8407"/>
		<updated>2025-04-08T20:04:26Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, an error message may be sent back from the mail server explaining why the message was rejected.  In this case, the bounce-back should explain [[Emails not delivered#Undeliverable bounce-back messages|why the message was rejected]].&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the outbox, the problem is likely that the mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to the mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in the email should explain why it was detected as spam.  The recipient could also have a [[Spam#Zimbra Filters|mail filter]] which is removing the messages.   Otherwise, the mail provider can check their email logs to track what happened to an email using on the recipient/sender address and the time when the message was sent.&lt;br /&gt;
&lt;br /&gt;
Messages are often blocked because an attachment is too big or is detected as malware, or if something in the subject/content appears to be malicious.  Sending a simple test email can identify if the problem has to do with a specific message.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounceback messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details of the reason for the bounce back, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@ncf.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@ncf.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=sender@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.56.78) which is not allowed to send mail according the SPF record on the sender's domain name (i.e. the part of their address following @, &amp;quot;somewhere.ca&amp;quot; in the example).&lt;br /&gt;
&lt;br /&gt;
'''SPF fail errors'''&lt;br /&gt;
&lt;br /&gt;
Domain names (e.g. &amp;quot;ncf.ca&amp;quot;) can set an SPF record to restrict which servers are allowed to send from their addresses (e.g. &amp;quot;name@ncf.ca&amp;quot;), which helps block messages sent from other servers [[Spam#Spoofing|spoofing]] their addresses.&lt;br /&gt;
&lt;br /&gt;
[https://duckduckgo.com/?q=SPF+check SPF checking tools] can be used to check if a server's IP is allowed by a domain name's SPF, or if there are problems with the SPF. &lt;br /&gt;
&lt;br /&gt;
Links to &amp;quot;openspf.net&amp;quot; no longer work because the site is offline, but the details in the link can be checked using another SPF tool.  For example using the details from the error above:&lt;br /&gt;
&lt;br /&gt;
https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;br /&gt;
&lt;br /&gt;
The SPF record can also be checked manually, for example on the command line using &amp;quot;dig&amp;quot;:&lt;br /&gt;
 $ dig TXT +short ncf.ca&lt;br /&gt;
 &amp;quot;v=spf1 ip4:104.160.252.0/24 ip6:2607:c280:1::/64 mx a:mx4.ncf.ca a:mx5.ncf.ca a:mail.ncf.ca -all&amp;quot;&lt;br /&gt;
SPF records are normally set as TXT records and begin with &amp;quot;v=spf1&amp;quot;, followed by a list of allowed servers.  The ending &amp;quot;-all&amp;quot; indicates that all other servers are not allowed.&lt;br /&gt;
&lt;br /&gt;
'''Blacklist errors'''&lt;br /&gt;
&lt;br /&gt;
Another common reason for mail to be rejected is if the sender's mail server is [[Email blacklisting|blacklisted]] which is the case for errors like &amp;quot;Connection originating from an IP address with a poor reputation.&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
'''Other bounce-back reasons'''&lt;br /&gt;
&lt;br /&gt;
The recipient could be out of space in their mailbox, their address may not exist (e.g. typo in address, account disabled), or their mail server or domain name could be having problems.  The reason is usually explained in the bounce-back, otherwise the mail provider's IT can investigate using the details in the bounce-back.&lt;br /&gt;
&lt;br /&gt;
'''Testing bounce-back to a server'''&lt;br /&gt;
&lt;br /&gt;
If messages to an address such as &amp;quot;recipient@somewhere.ca&amp;quot; are bouncing, a test can be sent to a fake address on the same domain such as &amp;quot;test@somewhere.ca&amp;quot; to check if it's a general problem with the server (same bounce-back error), or specific to the account (the fake address may have a different error saying the address does not exist).  &lt;br /&gt;
[[Category:Email]]&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8406</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8406"/>
		<updated>2025-04-08T20:03:15Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, an error message may be sent back from the mail server explaining why the message was rejected.  In this case, the bounce-back should explain [[Emails not delivered#Undeliverable bounce-back messages|why the message was rejected]].&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the outbox, the problem is likely that the mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to the mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in the email should explain why it was detected as spam.  The recipient could also have a [[Spam#Zimbra Filters|mail filter]] which is removing the messages.   Otherwise, the mail provider can check their email logs to track what happened to an email using on the recipient/sender address and the time when the message was sent.&lt;br /&gt;
&lt;br /&gt;
Messages are often blocked because an attachment is too big or is detected as malware, or if something in the subject/content appears to be malicious.  Sending a simple test email can identify if the problem has to do with a specific message.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounceback messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details of the reason for the bounce back, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@ncf.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@ncf.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=sender@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.56.78) which is not allowed to send mail according the SPF record on the sender's domain name (i.e. the part of their address following @, &amp;quot;somewhere.ca&amp;quot; in the example).&lt;br /&gt;
&lt;br /&gt;
'''SPF fail errors'''&lt;br /&gt;
&lt;br /&gt;
Domain names (e.g. &amp;quot;ncf.ca&amp;quot;) can set an SPF record to restrict which servers are allowed to send from their addresses (e.g. &amp;quot;name@ncf.ca&amp;quot;), which helps block messages sent from other servers [[Spam#Spoofing|spoofing]] their addresses.&lt;br /&gt;
&lt;br /&gt;
[https://duckduckgo.com/?q=SPF+check SPF checking tools] can be used to check if a server's IP is allowed by a domain name's SPF, or if there are problems with the SPF. &lt;br /&gt;
&lt;br /&gt;
Links to &amp;quot;openspf.net&amp;quot; no longer work because the site is offline, but the details in the link can be checked using another SPF tool.  For example using the details from the error above:&lt;br /&gt;
&lt;br /&gt;
https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;br /&gt;
&lt;br /&gt;
The SPF record can also looked up directly, for example on the command line with &amp;quot;dig&amp;quot;:&lt;br /&gt;
 $ dig TXT +short ncf.ca&lt;br /&gt;
 &amp;quot;v=spf1 ip4:104.160.252.0/24 ip6:2607:c280:1::/64 mx a:mx4.ncf.ca a:mx5.ncf.ca a:mail.ncf.ca -all&amp;quot;&lt;br /&gt;
SPF records are normally set as TXT records and begin with &amp;quot;v=spf1&amp;quot;, followed by a list of allowed servers.  The ending &amp;quot;-all&amp;quot; indicates that all other servers are not allowed.&lt;br /&gt;
&lt;br /&gt;
'''Blacklist errors'''&lt;br /&gt;
&lt;br /&gt;
Another common reason for mail to be rejected is if the sender's mail server is [[Email blacklisting|blacklisted]] which is the case for errors like &amp;quot;Connection originating from an IP address with a poor reputation.&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
'''Other bounce-back reasons'''&lt;br /&gt;
&lt;br /&gt;
The recipient could be out of space in their mailbox, their address may not exist (e.g. typo in address, account disabled), or their mail server or domain name could be having problems.  The reason is usually explained in the bounce-back, otherwise the mail provider's IT can investigate using the details in the bounce-back.&lt;br /&gt;
&lt;br /&gt;
'''Testing bounce-back to a server'''&lt;br /&gt;
&lt;br /&gt;
If messages to an address such as &amp;quot;recipient@somewhere.ca&amp;quot; are bouncing, a test can be sent to a fake address on the same domain such as &amp;quot;test@somewhere.ca&amp;quot; to check if it's a general problem with the server (same bounce-back error), or specific to the account (the fake address may have a different error saying the address does not exist).  &lt;br /&gt;
[[Category:Email]]&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8405</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8405"/>
		<updated>2025-04-08T19:27:51Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, an error message may be sent back from the mail server explaining why the message was rejected.  In this case, the bounce-back should explain [[Emails not delivered#Undeliverable bounce-back messages|why the message was rejected]].&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the outbox, the problem is likely that the mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to the mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in the email should explain why it was detected as spam.  The recipient could also have a [[Spam#Zimbra Filters|mail filter]] which is removing the messages.   Otherwise, the mail provider can check their email logs to track what happened to an email using on the recipient/sender address and the time when the message was sent.&lt;br /&gt;
&lt;br /&gt;
Messages are often blocked because an attachment is too big or is detected as malware, or if something in the subject/content appears to be malicious.  Sending a simple test email can identify if the problem has to do with a specific message.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounceback messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details of the reason for the bounce back, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@ncf.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@ncf.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=sender@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.56.78) which is not allowed to send mail according the SPF record on the sender's domain name (i.e. the part of their address following @, &amp;quot;somewhere.ca&amp;quot; in the example).&lt;br /&gt;
&lt;br /&gt;
'''SPF fail errors'''&lt;br /&gt;
&lt;br /&gt;
Domain names (e.g. &amp;quot;ncf.ca&amp;quot;) can set an SPF record to restrict which servers are allowed to send from their addresses (e.g. &amp;quot;name@ncf.ca&amp;quot;), which helps block messages send from other servers [[Spam#Spoofing|spoofing]] their addresses.&lt;br /&gt;
&lt;br /&gt;
[https://duckduckgo.com/?q=SPF+check SPF checking tools] can be used to check if a server's IP is allowed by a domain name's SPF, or if there are problems with the SPF. &lt;br /&gt;
&lt;br /&gt;
Links to &amp;quot;openspf.net&amp;quot; no longer work because the site is offline, but the details in the link can be checked using another SPF tool.  For example using the details from the error above:&lt;br /&gt;
&lt;br /&gt;
https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;br /&gt;
&lt;br /&gt;
The SPF record can also looked up directly, for example on the command line with &amp;quot;dig&amp;quot;:&lt;br /&gt;
 $ dig TXT +short ncf.ca&lt;br /&gt;
 &amp;quot;v=spf1 ip4:104.160.252.0/24 ip6:2607:c280:1::/64 mx a:mx4.ncf.ca a:mx5.ncf.ca a:mail.ncf.ca -all&amp;quot;&lt;br /&gt;
SPF records are normally set as TXT records and begin with &amp;quot;v=spf1&amp;quot;, followed by a list of allowed servers.  The ending &amp;quot;-all&amp;quot; indicates that all other servers are not allowed.&lt;br /&gt;
&lt;br /&gt;
'''Blacklist errors'''&lt;br /&gt;
&lt;br /&gt;
Another common reason for mail to be rejected is if the sender's mail server is [[Email blacklisting|blacklisted]] which is the case for errors like &amp;quot;Connection originating from an IP address with a poor reputation.&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
'''Other bounce-back reasons'''&lt;br /&gt;
&lt;br /&gt;
The recipient could be out of space in their mailbox, their address may not exist (e.g. typo in address, account disabled), or their mail server or domain name could be having problems.  The reason is usually explained in the bounce-back, otherwise the mail provider's IT can investigate using the details in the bounce-back.&lt;br /&gt;
&lt;br /&gt;
'''Testing bounce-back to a server'''&lt;br /&gt;
&lt;br /&gt;
If messages to an address such as &amp;quot;recipient@somewhere.ca&amp;quot; are bouncing, a test can be sent to a fake address on the same domain such as &amp;quot;test@somewhere.ca&amp;quot; to check if it's a general problem with the server (same bounce-back error), or specific to the account (the fake address may have a different error saying the address does not exist).  &lt;br /&gt;
[[Category:Email]]&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8404</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8404"/>
		<updated>2025-04-08T19:15:33Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, an error message may be sent back from the mail server explaining why the message was rejected.  In this case, the bounce-back should explain [[Emails not delivered#Undeliverable bounce-back messages|why the message was rejected]].&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the sender's outbox, the problem is likely that their mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to their mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in that email should explain why it was detected as spam.  The recipient could also have a [[Spam#Zimbra Filters|mail filter]] which is removing the messages.   Otherwise, the mail provider can check their email logs to track what happened to an email using on the recipient/sender address and the time when the message was sent.  Messages are often blocked because an attachment is too big or is detected as malware, or if something in the subject/content appears to be malicious.  Sending a simple test email can identify if the problem is to do with a specific message.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounceback messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details of the reason for the bounce back, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@ncf.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@ncf.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=sender@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.56.78) which is not allowed to send mail according the SPF record on the sender's domain name (i.e. the part of their address following @, &amp;quot;somewhere.ca&amp;quot; in the example).&lt;br /&gt;
&lt;br /&gt;
'''SPF fail errors'''&lt;br /&gt;
&lt;br /&gt;
Domain names (e.g. &amp;quot;ncf.ca&amp;quot;) can set an SPF record to restrict which servers are allowed to send from their addresses (e.g. &amp;quot;name@ncf.ca&amp;quot;), which helps block messages send from other servers [[Spam#Spoofing|spoofing]] their addresses.&lt;br /&gt;
&lt;br /&gt;
[https://duckduckgo.com/?q=SPF+check SPF checking tools] can be used to check if a server's IP is allowed by a domain name's SPF, or if there are problems with the SPF. &lt;br /&gt;
&lt;br /&gt;
Links to &amp;quot;openspf.net&amp;quot; no longer work because the site is offline, but the details in the link can be checked using another SPF tool.  For example using the details from the error above:&lt;br /&gt;
&lt;br /&gt;
https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;br /&gt;
&lt;br /&gt;
The SPF record can also looked up directly, for example on the command line with &amp;quot;dig&amp;quot;:&lt;br /&gt;
 $ dig TXT +short ncf.ca&lt;br /&gt;
 &amp;quot;v=spf1 ip4:104.160.252.0/24 ip6:2607:c280:1::/64 mx a:mx4.ncf.ca a:mx5.ncf.ca a:mail.ncf.ca -all&amp;quot;&lt;br /&gt;
SPF records are normally set as TXT records and begin with &amp;quot;v=spf1&amp;quot;, followed by a list of allowed servers.  The ending &amp;quot;-all&amp;quot; indicates that all other servers are not allowed.&lt;br /&gt;
&lt;br /&gt;
'''Blacklist errors'''&lt;br /&gt;
&lt;br /&gt;
Another common reason for mail to be rejected is if the sender's mail server is [[Email blacklisting|blacklisted]] which is the case for errors like &amp;quot;Connection originating from an IP address with a poor reputation.&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
'''Other bounce-back reasons'''&lt;br /&gt;
&lt;br /&gt;
The recipient could be out of space in their mailbox, their address may not exist (e.g. typo in address, account disabled), or their mail server or domain name could be having problems.  The reason is usually explained in the bounce-back, otherwise the mail provider's IT can investigate using the details in the bounce-back.&lt;br /&gt;
[[Category:Email]]&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8403</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8403"/>
		<updated>2025-04-08T19:13:19Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, an error message may be sent back from the mail server explaining why the message was rejected.  In this case, the bounce-back should explain [[Emails not delivered#Undeliverable bounce-back messages|why the message was rejected]].&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the sender's outbox, the problem is likely that their mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to their mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in that email should explain why it was detected as spam.  The recipient could also have a [[Spam#Zimbra Filters|mail filter]] which is removing the messages.   Otherwise, the mail provider can check their email logs to track what happened to an email using on the recipient/sender address and the time when the message was sent.  Messages are often blocked because an attachment is too big or is detected as malware, or if something in the subject/content appears to be malicious.  Sending a simple test email can identify if the problem is to do with a specific message.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounceback messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details of the reason for the bounce back, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@ncf.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@ncf.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=sender@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.56.78) which is not allowed to send mail according the SPF record on the sender's domain name (i.e. the part of their address following @, &amp;quot;somewhere.ca&amp;quot; in the example).&lt;br /&gt;
&lt;br /&gt;
'''SPF fail errors'''&lt;br /&gt;
&lt;br /&gt;
Domain names (like &amp;quot;ncf.ca&amp;quot;) can set an SPF record to restrict which servers are allowed to send from their addresses (like &amp;quot;name@ncf.ca&amp;quot;), which helps block messages from other servers [[Spam#Spoofing|spoofing]] their addresses.&lt;br /&gt;
&lt;br /&gt;
[https://duckduckgo.com/?q=SPF+check SPF checking tools] can be used to check if a server's IP is allowed by a domain name's SPF, or if there are problems with the SPF. &lt;br /&gt;
&lt;br /&gt;
Links to &amp;quot;openspf.net&amp;quot; no longer work because the site is offline, but the details in the link can be checked using another SPF tool.  For example using the details from the error above:&lt;br /&gt;
&lt;br /&gt;
https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;br /&gt;
&lt;br /&gt;
The SPF record can also looked up directly, for example on the command line with &amp;quot;dig&amp;quot;:&lt;br /&gt;
 $ dig TXT +short ncf.ca&lt;br /&gt;
 &amp;quot;v=spf1 ip4:104.160.252.0/24 ip6:2607:c280:1::/64 mx a:mx4.ncf.ca a:mx5.ncf.ca a:mail.ncf.ca -all&amp;quot;&lt;br /&gt;
SPF records are normally set as TXT records and begin with &amp;quot;v=spf1&amp;quot;, followed by a list of allowed servers.  The ending &amp;quot;-all&amp;quot; indicates that all other servers are not allowed.&lt;br /&gt;
&lt;br /&gt;
'''Blacklist errors'''&lt;br /&gt;
&lt;br /&gt;
Another common reason for mail to be rejected is if the sender's mail server is [[Email blacklisting|blacklisted]] which is the case for errors like &amp;quot;Connection originating from an IP address with a poor reputation.&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
'''Other bounce-back reasons'''&lt;br /&gt;
&lt;br /&gt;
The recipient could be out of space in their mailbox, their address may not exist (e.g. typo in address, account disabled), or their mail server or domain name could be having problems.  The reason is usually explained in the bounce-back, otherwise the mail provider's IT can investigate using the details in the bounce-back.&lt;br /&gt;
[[Category:Email]]&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8402</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8402"/>
		<updated>2025-04-08T19:13:08Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, an error message may be sent back from the mail server explaining why the message was rejected.  In this case, the bounce-back should explain [[Emails not delivered#Undeliverable bounce-back messages|why the message was rejected]].&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the sender's outbox, the problem is likely that their mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to their mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in that email should explain why it was detected as spam.  The recipient could also have a [[Spam#Zimbra Filters|mail filter]] which is removing the messages.   Otherwise, the mail provider can check their email logs to track what happened to an email using on the recipient/sender address and the time when the message was sent.  Messages are often blocked because an attachment is too big or is detected as malware, or if something in the subject/content appears to be malicious.  Sending a simple test email can identify if the problem is to do with a specific message.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounceback messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details of the reason for the bounce back, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@ncf.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@ncf.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=sender@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.56.78) which is not allowed to send mail according the SPF record on the sender's domain name (i.e. the part of their address following @, &amp;quot;somewhere.ca&amp;quot; in the example).&lt;br /&gt;
&lt;br /&gt;
'''SPF fail errors'''&lt;br /&gt;
&lt;br /&gt;
Domain names (like &amp;quot;ncf.ca&amp;quot;) can set an SPF record to restrict which servers are allowed to send from their addresses (like &amp;quot;name@ncf.ca&amp;quot;), which helps block messages from other servers [[Spam#Spoofing|spoofing]] their addresses.&lt;br /&gt;
&lt;br /&gt;
[https://duckduckgo.com/?q=SPF+check SPF checking tools] can be used to check if a server's IP is allowed by a domain name's SPF, or if there are problems with the SPF. &lt;br /&gt;
&lt;br /&gt;
Links to &amp;quot;openspf.net&amp;quot; no longer work because the site is offline, but the details in the link can be checked using another SPF tool.  For example using the details from the error above:&lt;br /&gt;
&lt;br /&gt;
https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;br /&gt;
&lt;br /&gt;
The SPF record can also looked up directly, for example on the command line with &amp;quot;dig&amp;quot;:&lt;br /&gt;
 $ dig TXT +short ncf.ca&lt;br /&gt;
 &amp;quot;v=spf1 ip4:104.160.252.0/24 ip6:2607:c280:1::/64 mx a:mx4.ncf.ca a:mx5.ncf.ca a:mail.ncf.ca -all&amp;quot;&lt;br /&gt;
SPF records are normally set as TXT records and begin with &amp;quot;v=spf1&amp;quot;, followed by a list of allowed servers.  The ending &amp;quot;-all&amp;quot; indicates that all other servers are not allowed.&lt;br /&gt;
&lt;br /&gt;
'''Blacklist errors'''&lt;br /&gt;
&lt;br /&gt;
Another common reason for mail to be rejected is if the sender's mail server is [[Email blacklisting|blacklisted]] which is the case for errors like &amp;quot;Connection originating from an IP address with a poor reputation.&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
'''Other bounce-back reasons'''&lt;br /&gt;
&lt;br /&gt;
The recipient could be out of space in their mailbox, their address may not exist (e.g. typo in address, account disabled), or their mail server or domain name could be having problems.  The reason is usually explained in the bounce-back, otherwise the mail provider's IT can investigate using the details in the bounce-back.&lt;br /&gt;
[[Category:Email]]&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8401</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8401"/>
		<updated>2025-04-08T19:04:22Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, an error message may be sent back from the mail server explaining why the message was rejected.  In this case, the bounce-back should explain [[Emails not delivered#Undeliverable bounce-back messages|why the message was rejected]].&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the sender's outbox, the problem is likely that their mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to their mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in that email should explain why it was detected as spam.  The recipient could also have a [[Spam#Zimbra Filters|mail filter]] which is removing the messages.   Otherwise, the mail provider can check their email logs to track what happened to an email using on the recipient/sender address and the time when the message was sent.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounceback messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details of the reason for the bounce back, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@ncf.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@ncf.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=sender@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.56.78) which is not allowed to send mail according the SPF record on the sender's domain name (i.e. the part of their address following @, &amp;quot;somewhere.ca&amp;quot; in the example).&lt;br /&gt;
&lt;br /&gt;
'''SPF fail errors'''&lt;br /&gt;
&lt;br /&gt;
Domain names (like &amp;quot;ncf.ca&amp;quot;) can set an SPF record to restrict which servers are allowed to send from their addresses (like &amp;quot;name@ncf.ca&amp;quot;), which helps block messages from other servers [[Spam#Spoofing|spoofing]] their addresses.&lt;br /&gt;
&lt;br /&gt;
[https://duckduckgo.com/?q=SPF+check SPF checking tools] can be used to check if a server's IP is allowed by a domain name's SPF, or if there are problems with the SPF. &lt;br /&gt;
&lt;br /&gt;
Links to &amp;quot;openspf.net&amp;quot; no longer work because the site is offline, but the details in the link can be checked using another SPF tool.  For example using the details from the error above:&lt;br /&gt;
&lt;br /&gt;
https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;br /&gt;
&lt;br /&gt;
The SPF record can also looked up directly, for example on the command line with &amp;quot;dig&amp;quot;:&lt;br /&gt;
 $ dig TXT +short ncf.ca&lt;br /&gt;
 &amp;quot;v=spf1 ip4:104.160.252.0/24 ip6:2607:c280:1::/64 mx a:mx4.ncf.ca a:mx5.ncf.ca a:mail.ncf.ca -all&amp;quot;&lt;br /&gt;
SPF records are normally set as TXT records and begin with &amp;quot;v=spf1&amp;quot;, followed by a list of allowed servers.  The ending &amp;quot;-all&amp;quot; indicates that all other servers are not allowed.&lt;br /&gt;
&lt;br /&gt;
'''Blacklist errors'''&lt;br /&gt;
&lt;br /&gt;
Another common reason for mail to be rejected is if the sender's mail server is [[Email blacklisting|blacklisted]] which is the case for errors like &amp;quot;Connection originating from an IP address with a poor reputation.&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
'''Other bounce-back reasons'''&lt;br /&gt;
&lt;br /&gt;
The recipient could be out of space in their mailbox, their address may not exist (e.g. typo in address, account disabled), or their mail server or domain name could be having problems.  The reason is usually explained in the bounce-back, otherwise the mail provider's IT can investigate using the details in the bounce-back.&lt;br /&gt;
[[Category:Email]]&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8400</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8400"/>
		<updated>2025-04-08T19:02:56Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, an error message might be sent back from the mail server explaining why the message was rejected.  In this case, the bounce-back message should explains [[Emails not delivered#Undeliverable bounce-back messages|why the message was rejected]].&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the sender's outbox, the problem is likely that their mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to their mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in that email should explain why it was detected as spam.  The recipient could also have a [[Spam#Zimbra Filters|mail filter]] which is removing the messages.   Otherwise, the mail provider can check their email logs to track what happened to an email using on the recipient/sender address and the time when the message was sent.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounceback messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details of the reason for the bounce back, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@ncf.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@ncf.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=sender@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.56.78) which is not allowed to send mail according the SPF record on the sender's domain name (i.e. the part of their address following @, &amp;quot;somewhere.ca&amp;quot; in the example).&lt;br /&gt;
&lt;br /&gt;
'''SPF fail errors'''&lt;br /&gt;
&lt;br /&gt;
Domain names (like &amp;quot;ncf.ca&amp;quot;) can set an SPF record to restrict which servers are allowed to send from their addresses (like &amp;quot;name@ncf.ca&amp;quot;), which helps block messages from other servers [[Spam#Spoofing|spoofing]] their addresses.&lt;br /&gt;
&lt;br /&gt;
[https://duckduckgo.com/?q=SPF+check SPF checking tools] can be used to check if a server's IP is allowed by a domain name's SPF, or if there are problems with the SPF. &lt;br /&gt;
&lt;br /&gt;
Links to &amp;quot;openspf.net&amp;quot; no longer work because the site is offline, but the details in the link can be checked using another SPF tool.  For example using the details from the error above:&lt;br /&gt;
&lt;br /&gt;
https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;br /&gt;
&lt;br /&gt;
The SPF record can also looked up directly, for example on the command line with &amp;quot;dig&amp;quot;:&lt;br /&gt;
 $ dig TXT +short ncf.ca&lt;br /&gt;
 &amp;quot;v=spf1 ip4:104.160.252.0/24 ip6:2607:c280:1::/64 mx a:mx4.ncf.ca a:mx5.ncf.ca a:mail.ncf.ca -all&amp;quot;&lt;br /&gt;
SPF records are normally set as TXT records and begin with &amp;quot;v=spf1&amp;quot;, followed by a list of allowed servers.  The ending &amp;quot;-all&amp;quot; indicates that all other servers are not allowed.&lt;br /&gt;
&lt;br /&gt;
'''Blacklist errors'''&lt;br /&gt;
&lt;br /&gt;
Another common reason for mail to be rejected is if the sender's mail server is [[Email blacklisting|blacklisted]] which is the case for errors like &amp;quot;Connection originating from an IP address with a poor reputation.&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
'''Other bounce-back reasons'''&lt;br /&gt;
&lt;br /&gt;
The recipient could be out of space in their mailbox, their address may not exist (e.g. typo in address, account disabled), or their mail server or domain name could be having problems.  The reason is usually explained in the bounce-back, otherwise the mail provider's IT can investigate using the details in the bounce-back.&lt;br /&gt;
[[Category:Email]]&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Email_blacklisting&amp;diff=8399</id>
		<title>Email blacklisting</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Email_blacklisting&amp;diff=8399"/>
		<updated>2025-04-08T19:02:33Z</updated>

		<summary type="html">&lt;p&gt;Ga627: /* See also */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Email blacklisting''' occurs when an [[email]] service provider puts another e-mail service provider on a &amp;quot;blacklist&amp;quot; and stops accepting email from that provider. This is usually done because it is perceived that a high volume of spam is coming from the blocked provider and its &amp;quot;reputation&amp;quot; is downgraded.&lt;br /&gt;
&lt;br /&gt;
If you send an email to someone whose provider has blacklisted NCF mail you will generally get a message back that indicates that delivery was refused, such as:&lt;br /&gt;
&lt;br /&gt;
:''This is the mail system at host mail.ncf.ca.''&lt;br /&gt;
:''I'm sorry to have to inform you that your message could not be delivered to one or more recipients...''&lt;br /&gt;
:''The mail system...host mx1c9.megamailservers.com[69.156.240.34] said ...Connection originating from an IP address with a poor reputation.''&lt;br /&gt;
&lt;br /&gt;
==What causes blacklisting of NCF mail==&lt;br /&gt;
Generally other e-mail providers blacklist NCF mail when they think that a high volume of spam is coming from NCF. This may actually be the case or it may be that a spammer is [https://en.wikipedia.org/wiki/Spoofing_attack spoofing] NCF IP addresses, in other words pretending that their spam mail is coming from NCF, when it isn't.&lt;br /&gt;
&lt;br /&gt;
In most cases blacklisting of NCF occurs because one or more NCF members running Microsoft Windows have had their computers infected with a virus that grabs their address book and sends out spam to all their contacts. Their computer may also be part of a [https://en.wikipedia.org/wiki/Botnet botnet] and under remote control to send out large quantities of spam.&lt;br /&gt;
&lt;br /&gt;
==What can you do if your email gets bounced==&lt;br /&gt;
The easiest solution is simply to wait.&lt;br /&gt;
&lt;br /&gt;
Most large email service providers use commercial blacklisting services, such as Barracuda or Cloudmark. Typically these will blacklist a service provider for a short period of time, such as 12, 24 or 48 hours and then the blacklist is recycled and cleared. If they didn't do this then soon they would have every email provider on their blacklist and no email would get through.&lt;br /&gt;
&lt;br /&gt;
If you need to get an email message to someone whose provider is blacklisting NCF mail in a hurry then you can:&lt;br /&gt;
&lt;br /&gt;
*See if you have an alternate address for the person to whom wish to send an email to and try that address instead&lt;br /&gt;
*Use your own alternate email address to send your email to them, such as Gmail, Hotmail, or Yahoo&lt;br /&gt;
&lt;br /&gt;
While most NCF members rely on NCF email, it is still handy to have an alternate email address to use. In normal circumstances you can just forward your Gmail, Hotmail or Yahoo mail to your NCF account and that keeps the alternate account available in case you ever need it.&lt;br /&gt;
&lt;br /&gt;
==Reporting==&lt;br /&gt;
If the blacklist doesn't clear in 24 hours or so and you still can't send a message to a certain e-mail provider the bounce back message may provide instructions for the NCF staff to help speed up clearing the blacklisting of NCF mail. Normally you can't do that yourself directly, though. You can see if there is already a posting about the specific issue on the [http://www.ncf.ca/ncf/dg/index.jsp?dg=1 NCF Help Desk Discussion Group] and, if not, post one or send the information to NCF via an [http://www.ncf.ca/ncf/support/officeMsg.jsp? office message].&lt;br /&gt;
&lt;br /&gt;
Some blacklists respond well to NCF system administrator requests for removal of NCF from a blacklist and others do not. Some blacklists do not take inputs at all and NCF has no means to make them take our mail, other than just waiting for the list to clear on its own.&lt;br /&gt;
&lt;br /&gt;
==Prevention==&lt;br /&gt;
The best way to prevent blacklist problems is to keep NCF mail off other provider's blacklists in the first place. &lt;br /&gt;
&lt;br /&gt;
The easiest way to do this is for NCF members who run Microsoft Windows to [[Using Windows safely|ensure they use it safely as possible]], including making sure that they are running an anti-virus application. Some recent surveys have shown that almost half of all Windows PCs are infected and are part of botnets. Windows users must keep their virus definitions up-to-date and run scans daily to prevent themselves from becoming part of spamming botnets.&lt;br /&gt;
&lt;br /&gt;
If you are running Windows and do not have anti-virus installed some good free anti-virus applications are:&lt;br /&gt;
&lt;br /&gt;
* [http://www.clamwin.com/ ClamWin] - free software&lt;br /&gt;
* [http://www.avast.com/en-us/index Avast Free] - commercial freeware&lt;br /&gt;
* [https://www.avira.com/en/avira-free-antivirus Avira Free Antivirus] - commercial freeware&lt;br /&gt;
* [http://free.avg.com/ca-en/free-antivirus-download AVG Free] - commercial freeware&lt;br /&gt;
&lt;br /&gt;
If you suspect your computer is being used for spamming (check your sent mail) then disconnect it from the internet until it is cleaned.&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
*[[Email]]&lt;br /&gt;
*[[Email spoofing]]&lt;br /&gt;
*[[Emails not delivered]]&lt;br /&gt;
*[[Using Windows safely]]&lt;br /&gt;
*[[Zimbra]] - NCF's webmail client&lt;br /&gt;
&lt;br /&gt;
==Additional reading==&lt;br /&gt;
*[http://techrights.org/2009/12/23/loss-of-control-of-windows-pcs/ One in Two Windows PCs is a Zombie PC (Part of Botnet/s)]&lt;br /&gt;
*[http://techrights.org/2008/05/14/windows-zombie-pc-40-pct/ A World Where Almost One in Two PCs is a Windows Zombie PC]&lt;br /&gt;
*[http://linux.oneandoneis2.org/wrongms.htm What's wrong with Microsoft?] by Dominic Humphries&lt;br /&gt;
&lt;br /&gt;
[[Category:Email]]&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8398</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8398"/>
		<updated>2025-04-08T18:56:33Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, an error message might be sent back from the mail server explaining why the message was rejected.  In this case, the bounce-back message should explains [[Emails not delivered#Undeliverable bounce-back messages|why the message was rejected]].&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the sender's outbox, the problem is likely that their mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to their mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in that email should explain why it was detected as spam.  The recipient could also have a [[Spam#Zimbra Filters|mail filter]] which is removing the messages.   Otherwise, the mail provider can check their email logs to track what happened to an email using on the recipient/sender address and the time when the message was sent.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounceback messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details of the reason for the bounce back, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@ncf.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@ncf.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=sender@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.56.78) which is not allowed to send mail according the SPF record on the sender's domain name (i.e. the part of their address following @, &amp;quot;somewhere.ca&amp;quot; in the example).&lt;br /&gt;
&lt;br /&gt;
'''SPF fail errors'''&lt;br /&gt;
&lt;br /&gt;
Domain names (like &amp;quot;ncf.ca&amp;quot;) can set an SPF record to restrict which servers are allowed to send from their addresses (like &amp;quot;name@ncf.ca&amp;quot;), which helps block messages from other servers [[Spam#Spoofing|spoofing]] their addresses.&lt;br /&gt;
&lt;br /&gt;
[https://duckduckgo.com/?q=SPF+check SPF checking tools] can be used to check if a server's IP is allowed by a domain name's SPF, or if there are problems with the SPF. &lt;br /&gt;
&lt;br /&gt;
Links to &amp;quot;openspf.net&amp;quot; no longer work because the site is offline, but the details in the link can be checked using another SPF tool.  For example using the details from the error above:&lt;br /&gt;
&lt;br /&gt;
https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;br /&gt;
&lt;br /&gt;
The SPF record can also looked up directly, for example on the command line with &amp;quot;dig&amp;quot;:&lt;br /&gt;
 $ dig TXT +short ncf.ca&lt;br /&gt;
 &amp;quot;v=spf1 ip4:104.160.252.0/24 ip6:2607:c280:1::/64 mx a:mx4.ncf.ca a:mx5.ncf.ca a:mail.ncf.ca -all&amp;quot;&lt;br /&gt;
SPF records are normally set as TXT records and begin with &amp;quot;v=spf1&amp;quot;, followed by a list of allowed servers.  The ending &amp;quot;-all&amp;quot; indicates that all other servers are not allowed.&lt;br /&gt;
&lt;br /&gt;
'''Blacklist errors'''&lt;br /&gt;
&lt;br /&gt;
Another common reason for mail to be rejected is if the sender's mail server is [[Email blacklisting|blacklisted]] which is the case for errors like &amp;quot;Connection originating from an IP address with a poor reputation.&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
'''Other bounce-back reasons'''&lt;br /&gt;
&lt;br /&gt;
The recipient could be out of space in their mailbox, their address may not exist (e.g. typo in address, account disabled), or their mail server or domain name could be having problems.  The reason is usually explained in the bounce-back, otherwise the mail provider's IT can investigate using the details in the bounce-back.&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8397</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8397"/>
		<updated>2025-04-08T18:56:09Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, an error message might be sent back from the mail server explaining why the message was rejected.  In this case, the bounce-back message should explains [[Emails not delivered#Undeliverable bounce-back messages|why the message was rejected]].&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the sender's outbox, the problem is likely that their mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to their mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in that email should explain why it was detected as spam.  The recipient could also have a [[Spam#Zimbra Filters|mail filter]] which is removing the messages.   Otherwise, the mail provider can check their email logs to track what happened to an email using on the recipient/sender address and the time when the message was sent.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounceback messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details of the reason for the bounce back, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@ncf.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@ncf.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=sender@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.56.78) which is not allowed to send mail according the SPF record on the sender's domain name (i.e. the part of their address following @, &amp;quot;somewhere.ca&amp;quot; in the example).&lt;br /&gt;
&lt;br /&gt;
'''SPF fail errors'''&lt;br /&gt;
&lt;br /&gt;
Domain names (like &amp;quot;ncf.ca&amp;quot;) can set an SPF record to restrict which servers are allowed to send from their addresses (like &amp;quot;name@ncf.ca&amp;quot;), which helps block messages from other servers [[Spam#Spoofing|spoofing]] their addresses.&lt;br /&gt;
&lt;br /&gt;
[https://duckduckgo.com/?q=SPF+check SPF checking tools] can be used to check if a server's IP is allowed by a domain name's SPF, or if there are problems with the SPF. &lt;br /&gt;
&lt;br /&gt;
Links to &amp;quot;openspf.net&amp;quot; no longer work because the site is offline, but the details in the link can be checked using another SPF tool.  For example using the details from the error above: https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;br /&gt;
&lt;br /&gt;
The SPF record can also looked up directly, for example on the command line with &amp;quot;dig&amp;quot;:&lt;br /&gt;
 $ dig TXT +short ncf.ca&lt;br /&gt;
 &amp;quot;v=spf1 ip4:104.160.252.0/24 ip6:2607:c280:1::/64 mx a:mx4.ncf.ca a:mx5.ncf.ca a:mail.ncf.ca -all&amp;quot;&lt;br /&gt;
SPF records are normally set as TXT records and begin with &amp;quot;v=spf1&amp;quot;, followed by a list of allowed servers.  The ending &amp;quot;-all&amp;quot; indicates that all other servers are not allowed.&lt;br /&gt;
&lt;br /&gt;
'''Blacklist errors'''&lt;br /&gt;
&lt;br /&gt;
Another common reason for mail to be rejected is if the sender's mail server is [[Email blacklisting|blacklisted]] which is the case for errors like &amp;quot;Connection originating from an IP address with a poor reputation.&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
'''Other bounce-back reasons'''&lt;br /&gt;
&lt;br /&gt;
The recipient could be out of space in their mailbox, their address may not exist (e.g. typo in address, account disabled), or their mail server or domain name could be having problems.  The reason is usually explained in the bounce-back, otherwise the mail provider's IT can investigate using the details in the bounce-back.&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8396</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8396"/>
		<updated>2025-04-08T18:55:09Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, an error message might be sent back from the mail server explaining why the message was rejected.  In this case, the bounce-back message should explains [[Emails not delivered#Undeliverable bounce-back messages|why the message was rejected]].&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the sender's outbox, the problem is likely that their mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to their mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in that email should explain why it was detected as spam.  The recipient could also have a [[Spam#Zimbra Filters|mail filter]] which is removing the messages.   Otherwise, the mail provider can check their email logs to track what happened to an email using on the recipient/sender address and the time when the message was sent.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounceback messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details of the reason for the bounce back, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@ncf.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@ncf.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=sender@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.56.78) which is not allowed to send mail according the SPF record on the sender's domain name (i.e. the part of their address following @, &amp;quot;somewhere.ca&amp;quot; in the example).&lt;br /&gt;
&lt;br /&gt;
'''SPF fail errors'''&lt;br /&gt;
&lt;br /&gt;
Domain names (like &amp;quot;ncf.ca&amp;quot;) can set an SPF record to restrict which servers are allowed to send from their addresses (like &amp;quot;name@ncf.ca&amp;quot;), which helps block messages from other servers [[Spam#Spoofing|spoofing]] their addresses.&lt;br /&gt;
&lt;br /&gt;
[https://duckduckgo.com/?q=SPF+check SPF checking tools] can be used to check if a server's IP is allowed by a domain name's SPF, or if there are problems with the SPF. &lt;br /&gt;
&lt;br /&gt;
Links to &amp;quot;openspf.net&amp;quot; no longer work because the site is offline, but the details in the link can be checked using another SPF tool.  For example using the details from the error above: https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;br /&gt;
&lt;br /&gt;
The SPF record can also looked up directly, for example on the command line with &amp;quot;dig&amp;quot;:&lt;br /&gt;
 $ dig TXT +short ncf.ca&lt;br /&gt;
 &amp;quot;v=spf1 ip4:104.160.252.0/24 ip6:2607:c280:1::/64 mx a:mx4.ncf.ca a:mx5.ncf.ca a:mail.ncf.ca -all&amp;quot;&lt;br /&gt;
SPF records are normally set as TXT records and begin with &amp;quot;v=spf1&amp;quot;, followed by a list of allowed servers.  The ending &amp;quot;-all&amp;quot; indicates that all other servers are not allowed.&lt;br /&gt;
&lt;br /&gt;
'''Blacklist errors'''&lt;br /&gt;
&lt;br /&gt;
Another common reason for mail to be rejected is if the sender's mail server is [[Email blacklisting|blacklisted]] which is the case for errors like &amp;quot;Connection originating from an IP address with a poor reputation.&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
'''Other bounce-back reasons'''&lt;br /&gt;
&lt;br /&gt;
The recipient could be out of space in their mailbox, their address may not exist (e.g. typo in address or mail account is disabled), or their mail server could be having problems.  The reason is usually explained in the bounce-back, otherwise the mail provider's IT can investigate using the details in the bounce-back.&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8395</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8395"/>
		<updated>2025-04-08T18:53:39Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, an error message might be sent back from the mail server explaining why the message was rejected.  In this case, the bounce-back message should explains [[Emails not delivered#Undeliverable bounce-back messages|why the message was rejected]].&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the sender's outbox, the problem is likely that their mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to their mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in that email should explain why it was detected as spam.  The recipient could also have a [[Spam#Zimbra Filters|mail filter]] which is removing the messages.   Otherwise, the mail provider's IT support could check their email logs to track what happened to an email from the recipient's address and the time the message was sent.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounceback messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details of the reason for the bounce back, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@ncf.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@ncf.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=sender@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.56.78) which is not allowed to send mail according the SPF record on the sender's domain name (i.e. the part of their address following @, &amp;quot;somewhere.ca&amp;quot; in the example).&lt;br /&gt;
&lt;br /&gt;
'''SPF fail errors'''&lt;br /&gt;
&lt;br /&gt;
Domain names (like &amp;quot;ncf.ca&amp;quot;) can set an SPF record to restrict which servers are allowed to send from their addresses (like &amp;quot;name@ncf.ca&amp;quot;), which helps block messages from other servers [[Spam#Spoofing|spoofing]] their addresses.&lt;br /&gt;
&lt;br /&gt;
[https://duckduckgo.com/?q=SPF+check SPF checking tools] can be used to check if a server's IP is allowed by a domain name's SPF, or if there are problems with the SPF. &lt;br /&gt;
&lt;br /&gt;
Links to &amp;quot;openspf.net&amp;quot; no longer work because the site is offline, but the details in the link can be checked using another SPF tool.  For example using the details from the error above: https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;br /&gt;
&lt;br /&gt;
The SPF record can also looked up directly, for example on the command line with &amp;quot;dig&amp;quot;:&lt;br /&gt;
 $ dig TXT +short ncf.ca&lt;br /&gt;
 &amp;quot;v=spf1 ip4:104.160.252.0/24 ip6:2607:c280:1::/64 mx a:mx4.ncf.ca a:mx5.ncf.ca a:mail.ncf.ca -all&amp;quot;&lt;br /&gt;
SPF records are normally set as TXT records and begin with &amp;quot;v=spf1&amp;quot;, followed by a list of allowed servers.  The ending &amp;quot;-all&amp;quot; indicates that all other servers are not allowed.&lt;br /&gt;
&lt;br /&gt;
'''Blacklist errors'''&lt;br /&gt;
&lt;br /&gt;
Another common reason for mail to be rejected is if the sender's mail server is [[Email blacklisting|blacklisted]] which is the case for errors like &amp;quot;Connection originating from an IP address with a poor reputation.&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
'''Other bounce-back reasons'''&lt;br /&gt;
&lt;br /&gt;
The recipient could be out of space in their mailbox, their address may not exist (e.g. typo in address or mail account is disabled), or their mail server could be having problems.  The reason is usually explained in the bounce-back, otherwise the mail provider's IT can investigate using the details in the bounce-back.&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8394</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8394"/>
		<updated>2025-04-08T18:51:53Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, the sender may receive a bounce-back email from their mail server explaining why the message was rejected.  In this case, the bounce-back message usually includes details explaining [[Emails not delivered#Undeliverable bounce-back messages|why the message was rejected]].&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the sender's outbox, the problem is likely that their mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to their mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in that email should explain why it was detected as spam.  The recipient could also have a [[Spam#Zimbra Filters|mail filter]] which is removing the messages.   Otherwise, the mail provider's IT support could check their email logs to track what happened to an email from the recipient's address and the time the message was sent.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounceback messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details of the reason for the bounce back, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@ncf.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@ncf.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=sender@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.56.78) which is not allowed to send mail according the SPF record on the sender's domain name (i.e. the part of their address following @, &amp;quot;somewhere.ca&amp;quot; in the example).&lt;br /&gt;
&lt;br /&gt;
'''SPF fail errors'''&lt;br /&gt;
&lt;br /&gt;
Domain names (like &amp;quot;ncf.ca&amp;quot;) can set an SPF record to restrict which servers are allowed to send from their addresses (like &amp;quot;name@ncf.ca&amp;quot;), which helps block messages from other servers [[Spam#Spoofing|spoofing]] their addresses.&lt;br /&gt;
&lt;br /&gt;
[https://duckduckgo.com/?q=SPF+check SPF checking tools] can be used to check if a server's IP is allowed by a domain name's SPF, or if there are problems with the SPF. &lt;br /&gt;
&lt;br /&gt;
Links to &amp;quot;openspf.net&amp;quot; no longer work because the site is offline, but the details in the link can be checked using another SPF tool.  For example using the details from the error above: https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;br /&gt;
&lt;br /&gt;
The SPF record can also looked up directly, for example on the command line with &amp;quot;dig&amp;quot;:&lt;br /&gt;
 $ dig TXT +short ncf.ca&lt;br /&gt;
 &amp;quot;v=spf1 ip4:104.160.252.0/24 ip6:2607:c280:1::/64 mx a:mx4.ncf.ca a:mx5.ncf.ca a:mail.ncf.ca -all&amp;quot;&lt;br /&gt;
SPF records are normally set as TXT records and begin with &amp;quot;v=spf1&amp;quot;, followed by a list of allowed servers.  The ending &amp;quot;-all&amp;quot; indicates that all other servers are not allowed.&lt;br /&gt;
&lt;br /&gt;
'''Blacklist errors'''&lt;br /&gt;
&lt;br /&gt;
Another common reason for mail to be rejected is if the sender's mail server is [[Email blacklisting|blacklisted]] which is the case for errors like &amp;quot;Connection originating from an IP address with a poor reputation.&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
'''Other bounce-back reasons'''&lt;br /&gt;
&lt;br /&gt;
The recipient could be out of space in their mailbox, their address may not exist (e.g. typo in address or mail account is disabled), or their mail server could be having problems.  The reason is usually explained in the bounce-back, otherwise the mail provider's IT can investigate using the details in the bounce-back.&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8393</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8393"/>
		<updated>2025-04-08T18:48:11Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, the sender may receive a bounce-back email from their mail server explaining why the message was rejected.  In this case, the bounce-back message usually includes details explaining [[Emails not delivered#Undeliverable bounce-back messages|why the message was rejected]].&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the sender's outbox, the problem is likely that their mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to their mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in that email should explain why it was detected as spam.  The recipient could also have a mail filter which is removing the messages.   Otherwise, the mail provider's IT support could check their email logs to track what happened to an email from the recipient's address and the time the message was sent.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounceback messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details of the reason for the bounce back, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@ncf.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@ncf.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=sender@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.56.78) which is not allowed to send mail according the SPF record on the sender's domain name (i.e. the part of their address following @, &amp;quot;somewhere.ca&amp;quot; in the example).&lt;br /&gt;
&lt;br /&gt;
'''SPF fail errors'''&lt;br /&gt;
&lt;br /&gt;
Domain names (like &amp;quot;ncf.ca&amp;quot;) can set an SPF record to restrict which servers are allowed to send from their addresses (like &amp;quot;name@ncf.ca&amp;quot;), which helps block messages from other servers [[Spam#Spoofing|spoofing]] their addresses.&lt;br /&gt;
&lt;br /&gt;
[https://duckduckgo.com/?q=SPF+check SPF checking tools] can be used to check if a server's IP is allowed by a domain name's SPF, or if there are problems with the SPF. &lt;br /&gt;
&lt;br /&gt;
Links to &amp;quot;openspf.net&amp;quot; no longer work because the site is offline, but the details in the link can be checked using another SPF tool.  For example using the details from the error above: https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;br /&gt;
&lt;br /&gt;
The SPF record can also looked up directly, for example on the command line with &amp;quot;dig&amp;quot;:&lt;br /&gt;
 $ dig TXT +short ncf.ca&lt;br /&gt;
 &amp;quot;v=spf1 ip4:104.160.252.0/24 ip6:2607:c280:1::/64 mx a:mx4.ncf.ca a:mx5.ncf.ca a:mail.ncf.ca -all&amp;quot;&lt;br /&gt;
SPF records are normally set as TXT records and begin with &amp;quot;v=spf1&amp;quot;, followed by a list of allowed servers.  The ending &amp;quot;-all&amp;quot; indicates that all other servers are not allowed.&lt;br /&gt;
&lt;br /&gt;
'''Blacklist errors'''&lt;br /&gt;
&lt;br /&gt;
Another common reason for mail to be rejected is if the sender's mail server is [[Email blacklisting|blacklisted]] which is the case for errors like &amp;quot;Connection originating from an IP address with a poor reputation.&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
'''Other bounce-back reasons'''&lt;br /&gt;
&lt;br /&gt;
The recipient could be out of space in their mailbox, their address may not exist (e.g. typo in address or mail account is disabled), or their mail server could be having problems.  The reason is usually explained in the bounce-back, otherwise the mail provider's IT can investigate using the details in the bounce-back.&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8392</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8392"/>
		<updated>2025-04-08T18:47:45Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, the sender may receive a bounce-back email from their mail server explaining why the message was rejected.  In this case, the bounce-back message usually includes details explaining [[Emails not delivered#Undeliverable bounce-back messages|why the message was rejected]].&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the sender's outbox, the problem is likely that their mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to their mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in that email should explain why it was detected as spam.  The recipient could also have a mail filter which is removing the messages.   Otherwise, the mail provider's IT support could check their email logs to track what happened to an email from the recipient's address and the time the message was sent.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounceback messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details of the reason for the bounce back, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@ncf.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@ncf.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=sender@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.56.78) which is not allowed to send mail according the SPF record on the sender's domain name (i.e. the part of their address following @, &amp;quot;somewhere.ca&amp;quot; in the example).&lt;br /&gt;
&lt;br /&gt;
'''SPF Fail errors'''&lt;br /&gt;
&lt;br /&gt;
Domain names (like &amp;quot;ncf.ca&amp;quot;) can set an SPF record to restrict which servers are allowed to send from their addresses (like &amp;quot;name@ncf.ca&amp;quot;), which helps block messages from other servers [[Spam#Spoofing|spoofing]] their addresses.&lt;br /&gt;
&lt;br /&gt;
[https://duckduckgo.com/?q=SPF+check SPF checking tools] can be used to check if a server's IP is allowed by a domain name's SPF, or if there are problems with the SPF. &lt;br /&gt;
&lt;br /&gt;
Links to &amp;quot;openspf.net&amp;quot; no longer work because the site is offline, but the details in the link can be checked using another SPF tool.  For example using the details from the error above: https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;br /&gt;
&lt;br /&gt;
The SPF record can also looked up directly, for example on the command line with &amp;quot;dig&amp;quot;:&lt;br /&gt;
 $ dig TXT +short ncf.ca&lt;br /&gt;
 &amp;quot;v=spf1 ip4:104.160.252.0/24 ip6:2607:c280:1::/64 mx a:mx4.ncf.ca a:mx5.ncf.ca a:mail.ncf.ca -all&amp;quot;&lt;br /&gt;
SPF records are normally set as TXT records and begin with &amp;quot;v=spf1&amp;quot;, followed by a list of allowed servers.  The ending &amp;quot;-all&amp;quot; indicates that all other servers are not allowed.&lt;br /&gt;
&lt;br /&gt;
'''Blacklist errors'''&lt;br /&gt;
&lt;br /&gt;
Another common reason for mail to be rejected is if the sender's mail server is [[Email blacklisting|blacklisted]] which is the case for errors like &amp;quot;Connection originating from an IP address with a poor reputation.&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
'''Other bounce-back reasons'''&lt;br /&gt;
&lt;br /&gt;
The recipient could be out of space in their mailbox, their address may not exist (e.g. typo in address or mail account is disabled), or their mail server could be having problems.  The reason is usually explained in the bounce-back, otherwise the mail provider's IT can investigate using the details in the bounce-back.&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8391</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8391"/>
		<updated>2025-04-08T18:45:17Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, the sender may receive a bounce-back email from their mail server explaining why the message was rejected.  In this case, the bounce-back message should include details explaining why the message was rejected.&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the sender's outbox, the problem is likely that their mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to their mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in that email should explain why it was detected as spam.  The recipient could also have a mail filter which is removing the messages.   Otherwise, the mail provider's IT support could check their email logs to track what happened to an email from the recipient's address and the time the message was sent.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounceback messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details of the reason for the bounce back, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@ncf.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@ncf.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=sender@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.56.78) which is not allowed to send mail according the SPF record on the sender's domain name (i.e. the part of their address following @, &amp;quot;somewhere.ca&amp;quot; in the example).&lt;br /&gt;
&lt;br /&gt;
'''SPF Fail errors'''&lt;br /&gt;
&lt;br /&gt;
Domain names (like &amp;quot;ncf.ca&amp;quot;) can set an SPF record to restrict which servers are allowed to send from their addresses (like &amp;quot;name@ncf.ca&amp;quot;), which helps block messages from other servers [[Spam#Spoofing|spoofing]] their addresses.&lt;br /&gt;
&lt;br /&gt;
[https://duckduckgo.com/?q=SPF+check SPF checking tools] can be used to check if a server's IP is allowed by a domain name's SPF, or if there are problems with the SPF. &lt;br /&gt;
&lt;br /&gt;
Links to &amp;quot;openspf.net&amp;quot; no longer work because the site is offline, but the details in the link can be checked using another SPF tool.  For example using the details from the error above: https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;br /&gt;
&lt;br /&gt;
The SPF record can also looked up directly, for example on the command line with &amp;quot;dig&amp;quot;:&lt;br /&gt;
 $ dig TXT +short ncf.ca&lt;br /&gt;
 &amp;quot;v=spf1 ip4:104.160.252.0/24 ip6:2607:c280:1::/64 mx a:mx4.ncf.ca a:mx5.ncf.ca a:mail.ncf.ca -all&amp;quot;&lt;br /&gt;
SPF records are normally set as TXT records and begin with &amp;quot;v=spf1&amp;quot;, followed by a list of allowed servers.  The ending &amp;quot;-all&amp;quot; indicates that all other servers are not allowed.&lt;br /&gt;
&lt;br /&gt;
'''Blacklist errors'''&lt;br /&gt;
&lt;br /&gt;
Another common reason for mail to be rejected is if the sender's mail server is [[Email blacklisting|blacklisted]] which is the case for errors like &amp;quot;Connection originating from an IP address with a poor reputation.&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
'''Other bounce-back reasons'''&lt;br /&gt;
&lt;br /&gt;
The recipient could be out of space in their mailbox, their address may not exist (e.g. typo in address or mail account is disabled), or their mail server could be having problems.  The reason is usually explained in the bounce-back, otherwise the mail provider's IT can investigate using the details in the bounce-back.&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Email&amp;diff=8390</id>
		<title>Email</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Email&amp;diff=8390"/>
		<updated>2025-04-08T18:26:53Z</updated>

		<summary type="html">&lt;p&gt;Ga627: /* See also */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page provides some basic information about NCF email, how it works and how to configure it.&lt;br /&gt;
&lt;br /&gt;
For information on using the Zimbra webmail system, please see [[Zimbra]].&lt;br /&gt;
&lt;br /&gt;
== Sending and receiving email ==&lt;br /&gt;
{{:Template:Quick Facts (Email)}}&lt;br /&gt;
===General information===&lt;br /&gt;
NCF provides every member with a personal email address. NCF email addresses are simply a member's account ID (eg., 'ab123') followed by '@ncf.ca', for example, 'ab123@ncf.ca'.&lt;br /&gt;
    &lt;br /&gt;
Optionally, you can arrange for an [[Email Alias|email alias]], for example, 'jsmith@ncf.ca'.&lt;br /&gt;
&lt;br /&gt;
'''Important:''' If you already have an email address and do not plan to use your NCF email address, be sure to tell us, using [https://secure.ncf.ca/ncf/home/tools/preferences.jsp Change Preferences] at the bottom-right of the StartPage. NCF needs to be able to reach you about your account.&lt;br /&gt;
&lt;br /&gt;
=== Receiving mail===&lt;br /&gt;
Incoming email for you is stored on NCF's computer until you ask for it.&lt;br /&gt;
There are two ways to receive email:&lt;br /&gt;
&lt;br /&gt;
;Using NCF WebMail (browser-based)&lt;br /&gt;
:All you need to use WebMail is a web browser connected to the internet (eg., home, office, library, internet cafe, anywhere in the world via internet). No set-up is required. You read and send mail from the browser using the [[Zimbra]] interface and your mail is stored on an NCF computer. With WebMail, your email stays on the computers at NCF and is backed up there, too, to protect against loss.&lt;br /&gt;
&lt;br /&gt;
:A disadvantage of using WebMail is that you have to stay connected to the internet while you are reading and composing your email.&lt;br /&gt;
&lt;br /&gt;
;Using an email client (on your personal computer)&lt;br /&gt;
:Email client software allows your email to be transferred to your computer and then read there. The size of your mail archive can be as large as your hard drive.&lt;br /&gt;
&lt;br /&gt;
:A disadvantage is that your mail is only accessible while you are at your own computer.&lt;br /&gt;
&lt;br /&gt;
In the past personal computer-based mail clients were dominant, but in recent years the trend has been away from mail clients and towards server-based webmail, because of the convenience of being able to access the mail from any browser anywhere, even from phones and hand-held devices, as well as automatic back-ups.&lt;br /&gt;
&lt;br /&gt;
== Zimbra Limits at NCF ==&lt;br /&gt;
There are several limits you may encounter in your use of Zimbra.&lt;br /&gt;
# '''Mail storage size''' - members are allocated 5GB of storage. This contains all the mail and briefcase data. Members must manage their space within that limit. See [[Zimbra webmail#How much storage space are you using.3F|how to check your storage space.]]&lt;br /&gt;
# '''Mail message size''' - the maximum message size allowed is 50MB. The actual file size of the attachments is 20-30% less due to the encoding is required to send it via email. If you have large files that you wish to share, there are a number of other file sharing approaches that may be better than attachments. One of those is using the Zimbra Briefcase -  see [[Zimbra: Briefcase]].&lt;br /&gt;
# '''Sending rate''' - NCF limits the rate at which members can send out email to protect against spamming. A limit of 200 messages over a 4 hour span is in place. If you have large distribution lists that will exceed this, please contact the office - we have a solution.&lt;br /&gt;
&lt;br /&gt;
== NCF Webmail ==&lt;br /&gt;
NCF Webmail allows you to compose, send, receive and manage your email using any browser. It is the easiest way to send and receive email while you are away from home. Your mail stays on the NCF's mail server. To use it, all you need is a web browser and connection to the Internet.&lt;br /&gt;
&lt;br /&gt;
You can try WebMail by going to the [http://start.ncf.ca StartPage] and clicking on 'Get your NCF WebMail'. There is nothing to install on your computer.&lt;br /&gt;
&lt;br /&gt;
Up to 5GB of email can be accumulated and stored in your WebMail Inbox and folders. NCF's storage capacity increases regularly as facilities are upgraded.&lt;br /&gt;
&lt;br /&gt;
The NCF Webmail system runs the [[Zimbra]] mail system.  For an overview of the benefits of Zimbra, please visit the [http://www.ncf.ca/ncf/home/zimbraIntro.jsp Introducing Zimbra] page.&lt;br /&gt;
&lt;br /&gt;
For specific and detailed help on all things Zimbra, visit the [[Zimbra]] Help Page.&lt;br /&gt;
&lt;br /&gt;
== Mail Clients (Mail readers) ==&lt;br /&gt;
&lt;br /&gt;
Some common current mail clients, all available for download free of charge, are:&lt;br /&gt;
&lt;br /&gt;
* [http://mail.live.com Microsoft Outlook]&lt;br /&gt;
* [https://www.mozilla.org/en-US/thunderbird/ Mozilla Thunderbird]&lt;br /&gt;
* [http://www.pmail.com/ Pegasus]&lt;br /&gt;
&lt;br /&gt;
If you do not have a mail reader, you can download one for free. Once it is installed on your computer, you need to configure it so it knows from where to retrieve/send your email.&lt;br /&gt;
&lt;br /&gt;
'''Notes:'''&lt;br /&gt;
*Microsoft Outlook Express is very outdated, has serious security problems, is no longer supported by Microsoft and is not recommended by NCF. See [http://en.wikipedia.org/wiki/Outlook_Express this article] for more detail on why you should replace it.&lt;br /&gt;
*Microsoft Outlook is commercial software and comes with ''Microsoft Office''.&lt;br /&gt;
&lt;br /&gt;
=== Setting up a Mail Client or Mail Reader ===&lt;br /&gt;
Modern mail readers are pretty easy to set up.  Typically you just need some of the information in the 'Quick Facts' box above.&lt;br /&gt;
&lt;br /&gt;
For step-by-step instructions, click on your mail reader below:&lt;br /&gt;
&lt;br /&gt;
Step-by-step instruction for popular mail readers:&lt;br /&gt;
* [[IPhone|iPhone, iPad, or iPod Touch]]&lt;br /&gt;
*[[Gmail]]&lt;br /&gt;
* [http://www.ncf.ca/ncf/support/android/ Android Devices (eg. Google Nexus One, Motorola Milestone, or HTC Hero)]&lt;br /&gt;
* [[Apple Mail|Apple Mail (2011)]]&lt;br /&gt;
*[[Windows Mail]]&lt;br /&gt;
* [http://www.ncf.ca/ncf/support/evolution.html Evolution Mail and Calendar]&lt;br /&gt;
* [[Microsoft Outlook 2016]]&lt;br /&gt;
* [http://www.ncf.ca/ncf/support/mail_thunderbird3.html Mozilla Thunderbird]&lt;br /&gt;
* [http://web.ncf.ca/aw958/mail_help_files/zimbra/index.html Zimbra Desktop email client] by Graeme Beckett, NCF&lt;br /&gt;
&lt;br /&gt;
Step-by-step instructions for older mail readers, still in use on some systems:&lt;br /&gt;
&lt;br /&gt;
(Note: as of November 2024 these clients may not support the TLS 1.2 encryption standard our mail servers require. You may need to use ports 25 (SMTP) and 143 (IMAP) or 110 (POP3) and disable SSL for them to work. This is not recommended though as these ports are unsecured, NCF recommends using a modern email client like the ones listed above.) &lt;br /&gt;
* [http://web.ncf.ca/glennj/ncf/bookshelf/appleMail/index.shtml Apple Mail (2006)]&lt;br /&gt;
* [http://www.ncf.ca/ncf/support/eudora.html Eudora Mail]&lt;br /&gt;
* [http://www.ncf.ca/ncf/support/outlook.html Microsoft Outlook Express]&lt;br /&gt;
* [http://www.ncf.ca/ncf/support/mail_thunderbird.html Mozilla Thunderbird 1.x or 2.x]&lt;br /&gt;
* [http://www.ncf.ca/ncf/support/ns71.html Netscape Mail]&lt;br /&gt;
* [http://www.ncf.ca/ncf/support/pegasusMail.html Pegasus Mail]&lt;br /&gt;
*[http://web.ncf.ca/aw958/mail_help_files/outlook_2003_setup/outlook_2003.html Microsoft Outlook 2003]&lt;br /&gt;
* [[Microsoft Outlook 2010]]&lt;br /&gt;
*[[BlackBerry 10]]&lt;br /&gt;
* [[PlayBook|Blackberry PlayBook]]&lt;br /&gt;
&lt;br /&gt;
For information on whether you should set up your reader for POP or IMAP see [http://www.ncf.ca/ncf/support/pop_imap.html What's the difference between POP and IMAP?].&lt;br /&gt;
&lt;br /&gt;
Keep in mind if you use an email client that it will not retrieve your yellow mail that the spam filter saves there for you.&lt;br /&gt;
&lt;br /&gt;
=== I can receive email, but I can't send! (Relay Access Denied) ===&lt;br /&gt;
If your mail account appears to be setup correctly, but you are having trouble sending, it could be that you don't have SSL and authentication enabled.&lt;br /&gt;
&lt;br /&gt;
Step-by-step instructions to update or confirm that your account is correctly configured for SSL and authentication:&lt;br /&gt;
* [http://www.ncf.ca/ncf/support/outlook_ssl.html Microsoft Outlook Express SSL Setup]&lt;br /&gt;
* [http://www.ncf.ca/ncf/support/mail_thunderbird_smtp.html Mozilla Thunderbird SSL Setup]&lt;br /&gt;
* [http://www.ncf.ca/ncf/support/windowsLiveMail_ssl.html Windows Live Mail SSL Setup]&lt;br /&gt;
&lt;br /&gt;
== Spam Reduction ==&lt;br /&gt;
&lt;br /&gt;
=== Customizing SpamFilter ===&lt;br /&gt;
Regardless of how you read your mail, you can use NCF's SpamFilter if you have problems with spam.&lt;br /&gt;
&lt;br /&gt;
You can view or change your SpamFilter settings by going to the [http://start.ncf.ca StartPage], and clicking on [https://www.ncf.ca/en/members/email/yellowmail/settings SpamFilter set-up] under 'Email' in the left column. There is information on that page about how SpamFilter works and [http://www.ncf.ca/ncf/support/faqMaker.jsp?faq=2 Frequently Asked Questions] on customizing SpamFilter.&lt;br /&gt;
&lt;br /&gt;
There is also [https://youtu.be/PWEibPkXCS0 a short video on setting SpamFilter options].&lt;br /&gt;
&lt;br /&gt;
=== Blocking Specific Email Addresses ===&lt;br /&gt;
Spam can be difficult to stop as spammers are relentless, and can often send messages from many different emails, making it much more difficult to stop.&lt;br /&gt;
&lt;br /&gt;
If the undesirable messages you are receiving are coming from the same address, it would be best to add a mail exception on your spam filtering page [https://www.ncf.ca/ncf/home/spamfilter/greenListMgr.jsp here] to ensure the offending address is blocked from sending you mail in the future.&lt;br /&gt;
&lt;br /&gt;
Simply enter the offending email into the “Email address” bar and enter “Classification” as “Red” to ensure this address will be marked as spam and not be delivered to your mailbox in the future.&lt;br /&gt;
&lt;br /&gt;
===Using Yellow Mail===&lt;br /&gt;
NCF provides a facility to screen mail items that your SPAM filter settings have found questionable before the mail enters your Zimbra inbox. This is called yellow mail. You can see a short video [[https://youtu.be/3rqLbGhvA8w here]] on how to use it.&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
*[[Alternate email address]]&lt;br /&gt;
*[[Email Alias|Email alias]]&lt;br /&gt;
*[[Emails not delivered]]&lt;br /&gt;
*[[Email blacklisting]]&lt;br /&gt;
*[[Email spoofing]]&lt;br /&gt;
*[[Tips (Email)|Email tips]]&lt;br /&gt;
*[[Zimbra]] - for help on the Zimbra webmail system&lt;br /&gt;
&lt;br /&gt;
[[Category: Email]]&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8389</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8389"/>
		<updated>2025-04-08T18:25:41Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, the sender may receive a bounce-back email from their mail server explaining why the message was rejected.  In this case, the bounce-back message should include details explaining why the message was rejected.&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the sender's outbox, the problem is likely that their mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to their mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in that email should explain why it was detected as spam.  Otherwise, the mail provider's IT support could check their email logs to track what happened to the email.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounceback messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details of the reason for the bounce back, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@ncf.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@ncf.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=sender@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.56.78) which is not allowed to send mail according the SPF record on the sender's domain name (i.e. the part of their address following @, &amp;quot;somewhere.ca&amp;quot; in the example).&lt;br /&gt;
&lt;br /&gt;
'''SPF Fail errors'''&lt;br /&gt;
&lt;br /&gt;
Domain names (like &amp;quot;ncf.ca&amp;quot;) can set an SPF record to restrict which servers are allowed to send from their addresses (like &amp;quot;name@ncf.ca&amp;quot;), which helps block messages from other servers spoofing their addresses.&lt;br /&gt;
&lt;br /&gt;
[https://duckduckgo.com/?q=SPF+check SPF checking tools] can be used to check if a server's IP is allowed by a domain name's SPF, or if there are problems with the SPF. &lt;br /&gt;
&lt;br /&gt;
Links to &amp;quot;openspf.net&amp;quot; no longer work because the site is offline, but the details in the link can be checked using another SPF tool.  For example using the details from the error above: https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;br /&gt;
&lt;br /&gt;
The SPF record can also looked up directly, for example on the command line with &amp;quot;dig&amp;quot;:&lt;br /&gt;
 $ dig TXT +short ncf.ca&lt;br /&gt;
 &amp;quot;v=spf1 ip4:104.160.252.0/24 ip6:2607:c280:1::/64 mx a:mx4.ncf.ca a:mx5.ncf.ca a:mail.ncf.ca -all&amp;quot;&lt;br /&gt;
SPF records are normally set as TXT records and begin with &amp;quot;v=spf1&amp;quot;, followed by a list of allowed servers.  The ending &amp;quot;-all&amp;quot; indicates that all other servers are not allowed.&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8388</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8388"/>
		<updated>2025-04-08T18:24:51Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, the sender may receive a bounce-back email from their mail server explaining why the message was rejected.  In this case, the bounce-back message should include details explaining why the message was rejected.&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the sender's outbox, the problem is likely that their mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to their mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in that email should explain why it was detected as spam.  Otherwise, the mail provider's IT support could check their email logs to track what happened to the email.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounceback messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details of the reason for the bounce back, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@ncf.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@ncf.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=sender@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.56.78) which is not allowed to send mail according the SPF record on the sender's domain name (i.e. the part of their address following @, &amp;quot;somewhere.ca&amp;quot; in the example).&lt;br /&gt;
&lt;br /&gt;
'''SPF Fail errors'''&lt;br /&gt;
&lt;br /&gt;
Domain names (like &amp;quot;ncf.ca&amp;quot;) can set an SPF record to restrict which servers are allowed to send from their addresses (like &amp;quot;name@ncf.ca&amp;quot;), which helps block messages from other servers spoofing their addresses.&lt;br /&gt;
&lt;br /&gt;
[https://duckduckgo.com/?q=SPF+check SPF checking tools] be used to check if a server's IP is allowed by a domain name's SPF.&lt;br /&gt;
&lt;br /&gt;
Links to &amp;quot;openspf.net&amp;quot; no longer work because the site is offline, but the details in the link can be checked using another SPF tool.  For example using the details from the error above: https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;br /&gt;
&lt;br /&gt;
The SPF record can also looked up directly, for example on the command line with &amp;quot;dig&amp;quot;:&lt;br /&gt;
 $ dig TXT +short ncf.ca&lt;br /&gt;
 &amp;quot;v=spf1 ip4:104.160.252.0/24 ip6:2607:c280:1::/64 mx a:mx4.ncf.ca a:mx5.ncf.ca a:mail.ncf.ca -all&amp;quot;&lt;br /&gt;
SPF records are normally set as TXT records and begin with &amp;quot;v=spf1&amp;quot;, followed by a list of allowed servers.  The ending &amp;quot;-all&amp;quot; indicates that all other servers are not allowed.&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8387</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8387"/>
		<updated>2025-04-08T18:24:13Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, the sender may receive a bounce-back email from their mail server explaining why the message was rejected.  In this case, the bounce-back message should include details explaining why the message was rejected.&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the sender's outbox, the problem is likely that their mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to their mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in that email should explain why it was detected as spam.  Otherwise, the mail provider's IT support could check their email logs to track what happened to the email.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounceback messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details of the reason for the bounce back, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@ncf.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@ncf.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=sender@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.56.78) which is not allowed to send mail according the SPF record on the sender's domain name (i.e. the part of their address following @, &amp;quot;somewhere.ca&amp;quot; in the example).&lt;br /&gt;
&lt;br /&gt;
'''SPF Fail errors'''&lt;br /&gt;
&lt;br /&gt;
Domain names (like &amp;quot;ncf.ca&amp;quot;) can set an SPF record to restrict which servers are allowed to send from their addresses (like &amp;quot;name@ncf.ca&amp;quot;), which helps block messages from other servers which are spoofing their addresses.&lt;br /&gt;
&lt;br /&gt;
[https://duckduckgo.com/?q=SPF+check SPF checking tools] be used to check if a server's IP is allowed by a domain name's SPF.&lt;br /&gt;
&lt;br /&gt;
Links to &amp;quot;openspf.net&amp;quot; no longer work because the site is offline, but the details in the link can be checked using another SPF tool.  For example using the details from the error above: https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;br /&gt;
&lt;br /&gt;
The SPF record can also looked up directly, for example on the command line with &amp;quot;dig&amp;quot;:&lt;br /&gt;
 $ dig TXT +short ncf.ca&lt;br /&gt;
 &amp;quot;v=spf1 ip4:104.160.252.0/24 ip6:2607:c280:1::/64 mx a:mx4.ncf.ca a:mx5.ncf.ca a:mail.ncf.ca -all&amp;quot;&lt;br /&gt;
SPF records are normally set as TXT records and begin with &amp;quot;v=spf1&amp;quot;, followed by a list of allowed servers.  The ending &amp;quot;-all&amp;quot; indicates that all other servers are not allowed.&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8386</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8386"/>
		<updated>2025-04-08T18:09:02Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, the sender may receive a bounce-back email from their mail server explaining why the message was rejected.  In this case, the bounce-back message should include details explaining why the message was rejected.&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the sender's outbox, the problem is likely that their mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to their mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in that email should explain why it was detected as spam.  Otherwise, the mail provider's IT support could check their email logs to track what happened to the email.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounceback messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details of the reason for the bounce back, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@ncf.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@ncf.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=sender@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.56.78) which is not allowed to send mail according the SPF record on the sender's domain name (i.e. the part of their address following @, &amp;quot;somewhere.ca&amp;quot; in the example).&lt;br /&gt;
&lt;br /&gt;
'''SPF Fail errors'''&lt;br /&gt;
&lt;br /&gt;
Domain names (like &amp;quot;ncf.ca&amp;quot;) can set an SPF record to restrict which servers are allowed to send from their addresses (like &amp;quot;name@ncf.ca&amp;quot;), which helps block messages from other servers which are spoofing their addresses.&lt;br /&gt;
&lt;br /&gt;
Links to &amp;quot;openspf.net&amp;quot; do not work because that tool is no longer available, but the details in that link can be checked in another SPF tool to see the issue, for example: https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8385</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8385"/>
		<updated>2025-04-08T18:01:31Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, the sender may receive a bounce-back email from their mail server explaining why the message was rejected.  In this case, the bounce-back message should include details explaining why the message was rejected.&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the sender's outbox, the problem is likely that their mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to their mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in that email should explain why it was detected as spam.  Otherwise, the mail provider's IT support could check their email logs to track what happened to the email.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounceback messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details of the reason for the bounce back, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@ncf.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@ncf.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=sender@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.56.78) which is not allowed to send mail according the SPF record on the sender's domain name (i.e. the part of their address following @, &amp;quot;somewhere.ca&amp;quot; in the example).  Links to &amp;quot;openspf.net&amp;quot; do not work because that tool is no longer available, but the details in that link can be checked in another SPF tool to see the issue, for example: https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8384</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8384"/>
		<updated>2025-04-08T17:57:30Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, the sender may receive a bounce-back email from their mail server explaining why the message was rejected.  In this case, the bounce-back message should include details explaining why the message was rejected.&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the sender's outbox, the problem is likely that their mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to their mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in that email should explain why it was detected as spam.  Otherwise, the mail provider's IT support could check their email logs to track what happened to the email.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounceback messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details of the reason for the bounce back, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@somewhere.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@somewhere.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=recipient@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;In this example, the problem is that the message was sent from a mail server (with IP 12.34.56.78) which is not allowed to send mail according the SPF record on the sender's domain name (somewhere.ca).  Links to &amp;quot;openspf.net&amp;quot; do not work because that tool is no longer available, but the details from that link can be checked in another SPF tool to see the issue, for example: https://mxtoolbox.com/SuperTool.aspx?action=spf%3asomewhere.ca%3a12.34.56.78&amp;amp;run=toolpage&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8383</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8383"/>
		<updated>2025-04-08T17:48:07Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, the sender may receive a bounce-back email from their mail server explaining why the message was rejected.  In this case, the bounce-back message should include details explaining why the message was rejected.&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the sender's outbox, the problem is likely that their mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to their mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in that email should explain why it was detected as spam.  Otherwise, the mail provider's IT support could check their email logs to track what happened to the email.&lt;br /&gt;
&lt;br /&gt;
==== Undeliverable bounce-back messages ====&lt;br /&gt;
Bounceback messages typically have a subject starting like &amp;quot;Undeliverable: &amp;quot;, followed by the original message's subject.  The message should begin with details of the reason for the bounce back, for example:&amp;lt;blockquote&amp;gt;This message was created automatically by the mail system.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;gt;&amp;gt;&amp;gt; recipient@somewhere.ca (Undelivered): 550 5.7.23 &amp;lt;recipient@somewhere.ca&amp;gt;: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see &amp;lt;nowiki&amp;gt;http://www.openspf.net/Why?s=mfrom;id=recipient@somewhere.ca;ip=12.34.56.78;r=&amp;lt;/nowiki&amp;gt;;&amp;lt;/blockquote&amp;gt;&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8382</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8382"/>
		<updated>2025-04-08T17:37:08Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails from a specific sender, the sender may receive a bounce-back email from their mail server explaining why the message was rejected.  In this case, the bounce-back message should include details explaining why the message was rejected.&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email may not have actually been sent.  If the email still appears in the sender's outbox, the problem is likely that their mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to their mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the sender's side but is not received and no error is reported, the message was likely detected as spam and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in that email should explain why it was detected as spam.  Otherwise, the mail provider's IT support could check their email logs to track what happened to the email.&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Email_messages_rejected&amp;diff=8381</id>
		<title>Email messages rejected</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Email_messages_rejected&amp;diff=8381"/>
		<updated>2025-04-08T17:34:56Z</updated>

		<summary type="html">&lt;p&gt;Ga627: Ga627 moved page Email messages rejected to Emails not delivered&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Emails not delivered]]&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8380</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8380"/>
		<updated>2025-04-08T17:34:55Z</updated>

		<summary type="html">&lt;p&gt;Ga627: Ga627 moved page Email messages rejected to Emails not delivered&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails sent to you from a specific sender, the sender may receive a bounce-back email from their mail server explaining why the message was rejected.  In this case, the bounce-back message should include details explaining why the recipient's mail server rejected the message.&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email might not have actually been sent.  If the email is still in the sender's outbox, the problem is likely that their mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to their mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the senders side but is not received and no error is reported, the message was likely detected as spam, or as having malicious content, and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in that email source should explain why it was detected as spam.  Otherwise, the mail provider's IT support could check their email logs to track what happened to the email.&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8379</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8379"/>
		<updated>2025-04-08T17:32:39Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If emails you are sending are not being delivered, or you are not receiving emails sent to you from a specific sender, the sender may receive a bounce-back email from their mail server explaining why the message was rejected.  In this case, the bounce-back message should include details explaining why the recipient's mail server rejected the message.&lt;br /&gt;
&lt;br /&gt;
When no bounce-back message is received, the email might not have actually been sent.  If the email is still in the sender's outbox, the problem is likely that their mail client is set to &amp;quot;work offline&amp;quot; or is having an error connecting to their mail server.&lt;br /&gt;
&lt;br /&gt;
When an email appears to have been sent on the senders side but is not received and no error is reported, the message was likely detected as spam, or as having malicious content, and filtered out.  In this case, the recipient may find the email in their Spam/Junk folder, and the headers in that email source should explain why it was detected as spam.  Otherwise, the mail provider's IT support could check their email logs to track what happened to the email.&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8378</id>
		<title>Emails not delivered</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Emails_not_delivered&amp;diff=8378"/>
		<updated>2025-04-08T17:03:39Z</updated>

		<summary type="html">&lt;p&gt;Ga627: Created page with &amp;quot;...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;...&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Template:Home_Networking_Accessories_for_Sale&amp;diff=8377</id>
		<title>Template:Home Networking Accessories for Sale</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Template:Home_Networking_Accessories_for_Sale&amp;diff=8377"/>
		<updated>2025-03-27T19:34:35Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+Networking Accessories for Sale&lt;br /&gt;
!Networking Accessory&lt;br /&gt;
!Description&lt;br /&gt;
!Purpose&lt;br /&gt;
!Warranty&lt;br /&gt;
!Costs&lt;br /&gt;
|-&lt;br /&gt;
|Cable Modem with Wireless AC Router  &lt;br /&gt;
|Refurbished cable modem with dual-band router&lt;br /&gt;
|Provides Wi-Fi N and Wi-Fi AC.&lt;br /&gt;
|90 day warranty&lt;br /&gt;
|$ 60.00 + HST&lt;br /&gt;
|-&lt;br /&gt;
|VDSL Modem with Wireless AC Router  &lt;br /&gt;
|Refurbished VDSL modem with dual-band router&lt;br /&gt;
|Provides Wi-Fi N and Wi-Fi AC.&lt;br /&gt;
|90 day warranty&lt;br /&gt;
|$ 40.00 + HST&lt;br /&gt;
|-&lt;br /&gt;
|VDSL Modem with Wireless N Router  &lt;br /&gt;
|Refurbished VDSL modem with WiFi N router&lt;br /&gt;
|Provides Wi-Fi N.&lt;br /&gt;
|90 day warranty&lt;br /&gt;
|$ 30.00 + HST&lt;br /&gt;
|-&lt;br /&gt;
|VDSL Modem Only (No Wi-Fi)&lt;br /&gt;
|Refurbished cable modem with dual-band router&lt;br /&gt;
|Provides ethernet only&lt;br /&gt;
|90 day warranty&lt;br /&gt;
|$ 25.00 + HST&lt;br /&gt;
|-&lt;br /&gt;
|Wireless AC Router   &lt;br /&gt;
|Refurbished dual-band routers supporting Wi-Fi N and Wi-Fi AC&lt;br /&gt;
|Provides Wi-Fi N and Wi-Fi AC.&lt;br /&gt;
|90 day warranty&lt;br /&gt;
|$ 20.00 + HST&lt;br /&gt;
|-&lt;br /&gt;
|TP-Link TL-WN752N&lt;br /&gt;
|Wi-Fi N Adapter (150 Mbps)&lt;br /&gt;
|For computers with failing or missing Wi-Fi modules, to allow them to use Wi-Fi.&lt;br /&gt;
|2 year warranty&lt;br /&gt;
|$ 19.99 + HST&lt;br /&gt;
|-&lt;br /&gt;
|TP-Link T1U                       &lt;br /&gt;
|Wi-Fi AC Adapter (450 Mbps)&lt;br /&gt;
|For computers with failing or missing Wi-Fi modules, to allow them to use Wi-Fi.&lt;br /&gt;
|2 year warranty&lt;br /&gt;
|$ 29.99 + HST&lt;br /&gt;
|-&lt;br /&gt;
|TP-Link Archer T2U       &lt;br /&gt;
|Wi-Fi N + AC Adapter (150 Mbps + 450 Mbps)&lt;br /&gt;
|For computers with failing or missing Wi-Fi modules, to allow them to use Wi-Fi.&lt;br /&gt;
|2 year warranty&lt;br /&gt;
|$ 33.99 + HST&lt;br /&gt;
|-&lt;br /&gt;
|TP-Link Archer T4U      &lt;br /&gt;
|Wi-Fi N + AC Adapter (300 Mbps + 867 Mbps)&lt;br /&gt;
|For computers with failing or missing Wi-Fi modules, to allow them to use Wi-Fi.&lt;br /&gt;
|2 year warranty&lt;br /&gt;
|$ 42.99 + HST&lt;br /&gt;
|-&lt;br /&gt;
|Ethernet Cable                                      &lt;br /&gt;
|Cat5e (10 feet)&lt;br /&gt;
|Connects 2 devices with Ethernet (RJ45) ports like a modem and computer&lt;br /&gt;
|1 year warranty&lt;br /&gt;
|$ 10.00 + HST&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Template:DSL_Modems_for_Sale&amp;diff=8376</id>
		<title>Template:DSL Modems for Sale</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Template:DSL_Modems_for_Sale&amp;diff=8376"/>
		<updated>2025-03-17T16:13:59Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+DSL Modems for Sale&lt;br /&gt;
!Modem&lt;br /&gt;
!Condition&lt;br /&gt;
!DSL Type&lt;br /&gt;
!WiFi&lt;br /&gt;
!Warranty&lt;br /&gt;
!Costs&lt;br /&gt;
|-&lt;br /&gt;
|Ovislink OV804WVA&lt;br /&gt;
|New&lt;br /&gt;
|VDSL / ADSL&lt;br /&gt;
|Yes, WiFi AC&lt;br /&gt;
|1 year&lt;br /&gt;
|$ 110.00 + HST&lt;br /&gt;
|-&lt;br /&gt;
|Ovislink OV501GF&lt;br /&gt;
|New&lt;br /&gt;
|VDSL / ADSL&lt;br /&gt;
|No WiFi&lt;br /&gt;
|1 year&lt;br /&gt;
|$ 80.00 + HST&lt;br /&gt;
|-&lt;br /&gt;
|VDSL with WiFi AC*&lt;br /&gt;
|Refurbished&lt;br /&gt;
|VDSL / ADSL&lt;br /&gt;
|Yes / WiFi AC&lt;br /&gt;
|90 days&lt;br /&gt;
|$ 30.00 + HST&lt;br /&gt;
|-&lt;br /&gt;
|VDSL with WiFi N or older*&lt;br /&gt;
|Refurbished&lt;br /&gt;
|VDSL / ADSL&lt;br /&gt;
|Yes / WiFi N or older&lt;br /&gt;
|90 days&lt;br /&gt;
|$ 20.00 + HST&lt;br /&gt;
|-&lt;br /&gt;
|VDSL*&lt;br /&gt;
|Refurbished&lt;br /&gt;
|VDSL / ADSL&lt;br /&gt;
|No&lt;br /&gt;
|90 days&lt;br /&gt;
|$ 10.00 + HST&lt;br /&gt;
|-&lt;br /&gt;
|ADSL with WiFi*&lt;br /&gt;
|Refurbished&lt;br /&gt;
|ADSL&lt;br /&gt;
|Yes&lt;br /&gt;
|90 days&lt;br /&gt;
|$ 10.00 + HST&lt;br /&gt;
|-&lt;br /&gt;
|ADSL*&lt;br /&gt;
|Refurbished&lt;br /&gt;
|ADSL&lt;br /&gt;
|No&lt;br /&gt;
|90 days&lt;br /&gt;
|$ 10.00 + HST&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;6&amp;quot; align=&amp;quot;left&amp;quot; | * Refurbished modems are subject to availability.&lt;br /&gt;
&lt;br /&gt;
'''Notes:''' &lt;br /&gt;
&lt;br /&gt;
- Modems may be returned for a full refund within 30 days of purchase. To be eligible for refund:&amp;lt;br&amp;gt;&lt;br /&gt;
New modems must be returned in good and working condition, in original packaging, and including all cables.&amp;lt;br&amp;gt;&lt;br /&gt;
Refurbished modems must be returned with all accompanying cables.&lt;br /&gt;
&lt;br /&gt;
- Refurbished modems are fully tested by NCF.&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Template:BYOD_Cable_Modems_on_Rogers&amp;diff=8375</id>
		<title>Template:BYOD Cable Modems on Rogers</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Template:BYOD_Cable_Modems_on_Rogers&amp;diff=8375"/>
		<updated>2025-03-10T16:47:30Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+Cable Modems Eligible for Use on the Rogers Network&lt;br /&gt;
!Manufacturer&lt;br /&gt;
!Model&lt;br /&gt;
!Firmware Version&lt;br /&gt;
|-&lt;br /&gt;
|CBN&lt;br /&gt;
|CD8000&lt;br /&gt;
|7.13.198.12&lt;br /&gt;
|-&lt;br /&gt;
|CBN&lt;br /&gt;
|CH8568&lt;br /&gt;
|CH8568-7.13.198.53-NOSH&lt;br /&gt;
|-&lt;br /&gt;
|Hitron&lt;br /&gt;
|CODA-45&lt;br /&gt;
|7.2.4.3.1b3&lt;br /&gt;
|-&lt;br /&gt;
|Hitron&lt;br /&gt;
|CODA-4582U&lt;br /&gt;
|7.2.4.5.1b8&lt;br /&gt;
|-&lt;br /&gt;
|Hitron&lt;br /&gt;
|CODA-4680&lt;br /&gt;
|7.2.4.5.2b8&lt;br /&gt;
|-&lt;br /&gt;
|Hitron&lt;br /&gt;
|CODA-56&lt;br /&gt;
|7.2.4.7.1b7&lt;br /&gt;
|-&lt;br /&gt;
|Hitron&lt;br /&gt;
|CODA-5610Q&lt;br /&gt;
|7.2.4.5.3b7&lt;br /&gt;
|-&lt;br /&gt;
|Sercomm&lt;br /&gt;
|DG4244&lt;br /&gt;
|V01.14.04.012&lt;br /&gt;
|-&lt;br /&gt;
|Sercomm&lt;br /&gt;
|DM1000&lt;br /&gt;
|V1.21.04.025&lt;br /&gt;
|-&lt;br /&gt;
|Technicolor&lt;br /&gt;
|CGA4234DGW&lt;br /&gt;
|CGA4234-P15-13-CA902-c0200r181-191007&lt;br /&gt;
|-&lt;br /&gt;
|Technicolor&lt;br /&gt;
|TC4400&lt;br /&gt;
|SR701343-190628-D&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; align=&amp;quot;left&amp;quot; |&lt;br /&gt;
'''Last updated 2025-03-10'''&lt;br /&gt;
&lt;br /&gt;
- As of December 31, 2024, only DOCSIS 3.1 cable modems can be used on the Rogers network.&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Template:BYOD_Cable_Modems_on_Rogers&amp;diff=8374</id>
		<title>Template:BYOD Cable Modems on Rogers</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Template:BYOD_Cable_Modems_on_Rogers&amp;diff=8374"/>
		<updated>2025-03-10T16:38:27Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+Cable Modems Eligible for Use on the Rogers Network&lt;br /&gt;
!Manufacturer&lt;br /&gt;
!Model&lt;br /&gt;
!DOCSIS Support&lt;br /&gt;
!Firmware Version&lt;br /&gt;
|-&lt;br /&gt;
|CBN&lt;br /&gt;
|CD8000&lt;br /&gt;
|3.1&lt;br /&gt;
|7.13.198.12&lt;br /&gt;
|-&lt;br /&gt;
|CBN&lt;br /&gt;
|CH8568&lt;br /&gt;
|3.1&lt;br /&gt;
|CH8568-7.13.198.53-NOSH&lt;br /&gt;
|-&lt;br /&gt;
|Hitron&lt;br /&gt;
|CODA-45&lt;br /&gt;
|3.1&lt;br /&gt;
|7.2.4.3.1b3&lt;br /&gt;
|-&lt;br /&gt;
|Hitron&lt;br /&gt;
|CODA-4582U&lt;br /&gt;
|3.1&lt;br /&gt;
|7.2.4.5.1b8&lt;br /&gt;
|-&lt;br /&gt;
|Hitron&lt;br /&gt;
|CODA-4680&lt;br /&gt;
|3.1&lt;br /&gt;
|7.2.4.5.2b8&lt;br /&gt;
|-&lt;br /&gt;
|Hitron&lt;br /&gt;
|CODA-56&lt;br /&gt;
|3.1&lt;br /&gt;
|7.2.4.7.1b7&lt;br /&gt;
|-&lt;br /&gt;
|Hitron&lt;br /&gt;
|CODA-5610Q&lt;br /&gt;
|3.1&lt;br /&gt;
|7.2.4.5.3b7&lt;br /&gt;
|-&lt;br /&gt;
|Sercomm&lt;br /&gt;
|DG4244&lt;br /&gt;
|3.1&lt;br /&gt;
|V01.14.04.012&lt;br /&gt;
|-&lt;br /&gt;
|Sercomm&lt;br /&gt;
|DM1000&lt;br /&gt;
|3.1&lt;br /&gt;
|V1.21.04.025&lt;br /&gt;
|-&lt;br /&gt;
|Technicolor&lt;br /&gt;
|CGA4234DGW&lt;br /&gt;
|3.1&lt;br /&gt;
|CGA4234-P15-13-CA902-c0200r181-191007&lt;br /&gt;
|-&lt;br /&gt;
|Technicolor&lt;br /&gt;
|TC4400&lt;br /&gt;
|3.1&lt;br /&gt;
|SR701343-190628-D&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; align=&amp;quot;left&amp;quot; |&lt;br /&gt;
'''Last updated 2025-03-10'''&lt;br /&gt;
&lt;br /&gt;
- As of December 31, 2024, only DOCSIS 3.1 cable modems can be used on the Rogers network.&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Template:BYOD_Cable_Modems_on_Rogers&amp;diff=8373</id>
		<title>Template:BYOD Cable Modems on Rogers</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Template:BYOD_Cable_Modems_on_Rogers&amp;diff=8373"/>
		<updated>2025-03-10T16:37:47Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+Cable Modems Eligible for Use on the Rogers Network&lt;br /&gt;
!Manufacturer&lt;br /&gt;
!Model&lt;br /&gt;
!DOCSIS Support&lt;br /&gt;
!Firmware Version&lt;br /&gt;
|-&lt;br /&gt;
|CBN&lt;br /&gt;
|CD8000&lt;br /&gt;
|3.1&lt;br /&gt;
|7.13.198.12&lt;br /&gt;
|CBN&lt;br /&gt;
|-&lt;br /&gt;
|CH8568&lt;br /&gt;
|3.1&lt;br /&gt;
|CH8568-7.13.198.53-NOSH&lt;br /&gt;
|Hitron&lt;br /&gt;
|-&lt;br /&gt;
|CODA-45&lt;br /&gt;
|3.1&lt;br /&gt;
|7.2.4.3.1b3&lt;br /&gt;
|Hitron&lt;br /&gt;
|-&lt;br /&gt;
|CODA-4582U&lt;br /&gt;
|3.1&lt;br /&gt;
|7.2.4.5.1b8&lt;br /&gt;
|Hitron&lt;br /&gt;
|-&lt;br /&gt;
|CODA-4680&lt;br /&gt;
|3.1&lt;br /&gt;
|7.2.4.5.2b8&lt;br /&gt;
|Hitron&lt;br /&gt;
|-&lt;br /&gt;
|CODA-56&lt;br /&gt;
|3.1&lt;br /&gt;
|7.2.4.7.1b7&lt;br /&gt;
|-&lt;br /&gt;
|Hitron&lt;br /&gt;
|CODA-5610Q&lt;br /&gt;
|3.1&lt;br /&gt;
|7.2.4.5.3b7&lt;br /&gt;
|-&lt;br /&gt;
|Sercomm&lt;br /&gt;
|DG4244&lt;br /&gt;
|3.1&lt;br /&gt;
|V01.14.04.012&lt;br /&gt;
|-&lt;br /&gt;
|Sercomm&lt;br /&gt;
|DM1000&lt;br /&gt;
|3.1&lt;br /&gt;
|V1.21.04.025&lt;br /&gt;
|-&lt;br /&gt;
|Technicolor&lt;br /&gt;
|CGA4234DGW&lt;br /&gt;
|3.1&lt;br /&gt;
|CGA4234-P15-13-CA902-c0200r181-191007&lt;br /&gt;
|-&lt;br /&gt;
|Technicolor&lt;br /&gt;
|TC4400&lt;br /&gt;
|3.1&lt;br /&gt;
|SR701343-190628-D&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; align=&amp;quot;left&amp;quot; |&lt;br /&gt;
'''Last updated 2025-03-10'''&lt;br /&gt;
&lt;br /&gt;
- As of December 31, 2024, only DOCSIS 3.1 cable modems can be used on the Rogers network.&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Template:BYOD_Cable_Modems_on_Rogers&amp;diff=8372</id>
		<title>Template:BYOD Cable Modems on Rogers</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Template:BYOD_Cable_Modems_on_Rogers&amp;diff=8372"/>
		<updated>2025-03-10T16:25:15Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+Cable Modems Eligible For Sign-ups (on the Rogers network)&lt;br /&gt;
!Manufacturer&lt;br /&gt;
!Model&lt;br /&gt;
!DOCSIS Support&lt;br /&gt;
!Firmware Version&lt;br /&gt;
|-&lt;br /&gt;
|CBN&lt;br /&gt;
|CD8000&lt;br /&gt;
|3.1&lt;br /&gt;
|7.13.198.12&lt;br /&gt;
|-&lt;br /&gt;
|Hitron &lt;br /&gt;
|CODA-45&lt;br /&gt;
|3.1&lt;br /&gt;
|7.1.1.1.2b1 or 7.2.4.3.1b3&lt;br /&gt;
|-&lt;br /&gt;
|Hitron&lt;br /&gt;
|CODA-4680&lt;br /&gt;
|3.1&lt;br /&gt;
|7.1.1.2.2b9&lt;br /&gt;
|-&lt;br /&gt;
|Technicolor&lt;br /&gt;
|TC4400&lt;br /&gt;
|3.1&lt;br /&gt;
|SR7011343-190628-D&lt;br /&gt;
|-&lt;br /&gt;
|Technicolor&lt;br /&gt;
|CGA4234DGW&lt;br /&gt;
|3.1&lt;br /&gt;
|CGA4234-P15-13-CA902-c0200r181-191007&lt;br /&gt;
|-&lt;br /&gt;
|CBN&lt;br /&gt;
|CH8568&lt;br /&gt;
|3.1&lt;br /&gt;
|CH8568-7.13.198.53-NOSH&lt;br /&gt;
|-&lt;br /&gt;
|Sercomm&lt;br /&gt;
|DM1000&lt;br /&gt;
|3.1&lt;br /&gt;
|V1.12.03.011&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; align=&amp;quot;left&amp;quot; |&lt;br /&gt;
'''Last updated 2025-03-10'''&lt;br /&gt;
&lt;br /&gt;
- As of December 31, 2024, only DOCSIS 3.1 cable modems can be used on the Rogers network.&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
	<entry>
		<id>https://help.ncf.ca/index.php?title=Use_Your_Own_Modem&amp;diff=8371</id>
		<title>Use Your Own Modem</title>
		<link rel="alternate" type="text/html" href="https://help.ncf.ca/index.php?title=Use_Your_Own_Modem&amp;diff=8371"/>
		<updated>2025-03-10T16:24:26Z</updated>

		<summary type="html">&lt;p&gt;Ga627: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Introduction==&lt;br /&gt;
If you currently own a cable modem, you might be able to use that modem with NCF's cable service.&lt;br /&gt;
&lt;br /&gt;
Each network vendor certifies and approves cable modem hardware and firmware versions for use on their network infrastructure. This certification process tests the modem and firmware version on the network to ensure its performance and stability.&lt;br /&gt;
&lt;br /&gt;
==On the Rogers network==&lt;br /&gt;
&lt;br /&gt;
If you own one of the following cable modems, and the firmware version of your modem matches the firmware version for your make and model below, you can use the cable modem with NCF's cable internet service on the Rogers network.&lt;br /&gt;
&lt;br /&gt;
{{Template:BYOD Cable Modems on Rogers}}&lt;br /&gt;
&lt;br /&gt;
==Checking Your Modem Firmware Version==&lt;br /&gt;
To check what firmware version your modem is using,  login to your modem's configuration to find that information. Consult the User Guide for your modem to find out how to access the modem configuration.&lt;br /&gt;
&lt;br /&gt;
[[Category:Cable]]&lt;/div&gt;</summary>
		<author><name>Ga627</name></author>
	</entry>
</feed>