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

<channel>
	<title>Exchange Archives - SCD Information Technology</title>
	<atom:link href="http://blog.scdit.com/exchange/feed/" rel="self" type="application/rss+xml" />
	<link></link>
	<description>We fix IT and you benefit...</description>
	<lastBuildDate>Fri, 09 Oct 2020 13:54:30 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9</generator>
	<item>
		<title>O365 Password Expire Phishing Attempt</title>
		<link>http://blog.scdit.com/o365-password-expire-phishing-attempt/</link>
					<comments>http://blog.scdit.com/o365-password-expire-phishing-attempt/#respond</comments>
		
		<dc:creator><![CDATA[Dwayne Grimes]]></dc:creator>
		<pubDate>Fri, 09 Oct 2020 13:47:59 +0000</pubDate>
				<category><![CDATA[Exchange]]></category>
		<category><![CDATA[Office 365]]></category>
		<category><![CDATA[Scam]]></category>
		<category><![CDATA[Spam]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Firewall]]></category>
		<category><![CDATA[Phishing Attempt]]></category>
		<guid isPermaLink="false">http://blog.scdit.com/?p=11766</guid>

					<description><![CDATA[<p>During a cloud migration from a on-premise Exchange server behind a commercial firewall to a full Office365 Exchange we noticed the amount of spam that was getting through. Here is an example of the email. The phishing email looks very genuine, but isn&#8217;t. We hope you find this information prior to an incident at your [&#8230;]</p>
<p>The post <a href="http://blog.scdit.com/o365-password-expire-phishing-attempt/">O365 Password Expire Phishing Attempt</a> appeared first on <a href="http://blog.scdit.com">SCD Information Technology</a>.</p>
]]></description>
		
					<wfw:commentRss>http://blog.scdit.com/o365-password-expire-phishing-attempt/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Exchange 2016 &#8211; Grant Full Permissions Over A Mailbox</title>
		<link>http://blog.scdit.com/exchange-2016-grant-full-permissions-over-a-mailbox/</link>
					<comments>http://blog.scdit.com/exchange-2016-grant-full-permissions-over-a-mailbox/#respond</comments>
		
		<dc:creator><![CDATA[Dwayne Grimes]]></dc:creator>
		<pubDate>Mon, 21 Jan 2019 17:20:35 +0000</pubDate>
				<category><![CDATA[Email]]></category>
		<category><![CDATA[Exchange]]></category>
		<guid isPermaLink="false">http://blog.scdeval.com/?p=601</guid>

					<description><![CDATA[<p>I recently had to remove permissions from a mailbox where another user had &#8220;Full Access&#8221; or &#8220;Full Permissions&#8221; over. The original setup was done on the old Exchange 2010 server that was upgraded to 2016. Log into the web interface of the Exchange. Locate the mailbox and double-click on the mailbox display name. Click on [&#8230;]</p>
<p>The post <a href="http://blog.scdit.com/exchange-2016-grant-full-permissions-over-a-mailbox/">Exchange 2016 &#8211; Grant Full Permissions Over A Mailbox</a> appeared first on <a href="http://blog.scdit.com">SCD Information Technology</a>.</p>
]]></description>
		
					<wfw:commentRss>http://blog.scdit.com/exchange-2016-grant-full-permissions-over-a-mailbox/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Export Mailbox List From Office 365</title>
		<link>http://blog.scdit.com/export-mailbox-list-from-office-365/</link>
					<comments>http://blog.scdit.com/export-mailbox-list-from-office-365/#respond</comments>
		
		<dc:creator><![CDATA[Dwayne Grimes]]></dc:creator>
		<pubDate>Tue, 04 Sep 2018 20:18:22 +0000</pubDate>
				<category><![CDATA[Email]]></category>
		<category><![CDATA[Exchange]]></category>
		<category><![CDATA[Office 365]]></category>
		<guid isPermaLink="false">http://blog.scdeval.com/?p=372</guid>

					<description><![CDATA[<p>We needed to put together of list of email accounts a customer has in their Office 365 account. The following article was a huge help. https://community.spiceworks.com/how_to/84674-export-office-365-users-to-csv-online-without-using-powershell Let us know if this helped you&#8230;. &#160;</p>
<p>The post <a href="http://blog.scdit.com/export-mailbox-list-from-office-365/">Export Mailbox List From Office 365</a> appeared first on <a href="http://blog.scdit.com">SCD Information Technology</a>.</p>
]]></description>
		
					<wfw:commentRss>http://blog.scdit.com/export-mailbox-list-from-office-365/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>#550 4.4.7 QUEUE Exchange Unable To Send To Comcast</title>
		<link>http://blog.scdit.com/550-4-4-7-queue-exchange-unable-to-send-to-comcast/</link>
					<comments>http://blog.scdit.com/550-4-4-7-queue-exchange-unable-to-send-to-comcast/#respond</comments>
		
		<dc:creator><![CDATA[Dwayne Grimes]]></dc:creator>
		<pubDate>Wed, 25 Jul 2018 19:45:06 +0000</pubDate>
				<category><![CDATA[Comcast]]></category>
		<category><![CDATA[Email]]></category>
		<category><![CDATA[Exchange]]></category>
		<category><![CDATA[ISP]]></category>
		<guid isPermaLink="false">http://blog.scdeval.com/?p=346</guid>

					<description><![CDATA[<p>We recently had a customer get a ISP change and on the same day were moving their DNS to Godaddy.  A few weeks later they noticed a bunch of emails bouncing back with a lot of the email addresses being for Comcast. We weren&#8217;t sure if this was a Godaddy,DNS, Exchange, or ISP issue. It [&#8230;]</p>
<p>The post <a href="http://blog.scdit.com/550-4-4-7-queue-exchange-unable-to-send-to-comcast/">#550 4.4.7 QUEUE Exchange Unable To Send To Comcast</a> appeared first on <a href="http://blog.scdit.com">SCD Information Technology</a>.</p>
]]></description>
		
					<wfw:commentRss>http://blog.scdit.com/550-4-4-7-queue-exchange-unable-to-send-to-comcast/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Not Receiving Emails In Office 365 &#8211; After My Mailbox Was Compromised.</title>
		<link>http://blog.scdit.com/not-receiving-emails-in-office-365-after-my-mailbox-was-compromised/</link>
					<comments>http://blog.scdit.com/not-receiving-emails-in-office-365-after-my-mailbox-was-compromised/#respond</comments>
		
		<dc:creator><![CDATA[Dwayne Grimes]]></dc:creator>
		<pubDate>Wed, 07 Feb 2018 19:15:20 +0000</pubDate>
				<category><![CDATA[Email]]></category>
		<category><![CDATA[Exchange]]></category>
		<category><![CDATA[Office]]></category>
		<category><![CDATA[Office 365]]></category>
		<guid isPermaLink="false">http://blog.scdeval.com/?p=199</guid>

					<description><![CDATA[<p>We had a customer get their Office 365 email account compromised / attacked. The password was reset and the user could send email she just didn&#8217;t receive them. I went into her online Office 365 account and verified the issue. This page lead me to the fix. https://support.office.com/en-us/article/Find-and-fix-email-delivery-issues-as-an-Office-365-for-business-admin-e7758b99-1896-41db-bf39-51e2dba21de6 Their advice to check the mail flow [&#8230;]</p>
<p>The post <a href="http://blog.scdit.com/not-receiving-emails-in-office-365-after-my-mailbox-was-compromised/">Not Receiving Emails In Office 365 &#8211; After My Mailbox Was Compromised.</a> appeared first on <a href="http://blog.scdit.com">SCD Information Technology</a>.</p>
]]></description>
		
					<wfw:commentRss>http://blog.scdit.com/not-receiving-emails-in-office-365-after-my-mailbox-was-compromised/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Install Godaddy SSL Certificate Into A 2010 Exchange</title>
		<link>http://blog.scdit.com/install-godaddy-ssl-certificate-into-a-2010-exchange/</link>
					<comments>http://blog.scdit.com/install-godaddy-ssl-certificate-into-a-2010-exchange/#respond</comments>
		
		<dc:creator><![CDATA[Dwayne Grimes]]></dc:creator>
		<pubDate>Mon, 05 Feb 2018 14:49:45 +0000</pubDate>
				<category><![CDATA[Exchange]]></category>
		<category><![CDATA[Godaddy Web Hosting]]></category>
		<category><![CDATA[SSL]]></category>
		<guid isPermaLink="false">http://blog.scdeval.com/?p=186</guid>

					<description><![CDATA[<p>We got a notification from Godaddy that our SSL has been renewed and is ready to be downloaded and installed. This download will not work you will need to Re-key, wait for verification ( 30 minutes ), and install this new certificate. Log into the Exchange Console and click on &#8220;New Exchange Certificate&#8220;. Give the [&#8230;]</p>
<p>The post <a href="http://blog.scdit.com/install-godaddy-ssl-certificate-into-a-2010-exchange/">Install Godaddy SSL Certificate Into A 2010 Exchange</a> appeared first on <a href="http://blog.scdit.com">SCD Information Technology</a>.</p>
]]></description>
		
					<wfw:commentRss>http://blog.scdit.com/install-godaddy-ssl-certificate-into-a-2010-exchange/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Solved &#8211; &#8220;Cannot start Microsoft Outlook.&#8221;</title>
		<link>http://blog.scdit.com/solved-cannot-start-microsoft-outlook/</link>
					<comments>http://blog.scdit.com/solved-cannot-start-microsoft-outlook/#respond</comments>
		
		<dc:creator><![CDATA[Corie Branch]]></dc:creator>
		<pubDate>Mon, 30 Oct 2017 15:34:14 +0000</pubDate>
				<category><![CDATA[Exchange]]></category>
		<category><![CDATA[Office 365]]></category>
		<category><![CDATA[Outlook]]></category>
		<guid isPermaLink="false">http://blog.scdeval.com/?p=146</guid>

					<description><![CDATA[<p>We had a rough time with a customers Outlook 2016. It wouldn&#8217;t start and would give us the &#8220;Cannot start Microsoft Outlook&#8221; error. We repaired the OST and reinstalled Office 2016, but this didn&#8217;t fix the issue. It would seem like the error was fixed, but after a restart the issue would come back. We [&#8230;]</p>
<p>The post <a href="http://blog.scdit.com/solved-cannot-start-microsoft-outlook/">Solved &#8211; &#8220;Cannot start Microsoft Outlook.&#8221;</a> appeared first on <a href="http://blog.scdit.com">SCD Information Technology</a>.</p>
]]></description>
		
					<wfw:commentRss>http://blog.scdit.com/solved-cannot-start-microsoft-outlook/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Exchange &#8211; Your message can&#8217;t be delivered because delivery to this address is restricted.</title>
		<link>http://blog.scdit.com/exchange-your-message-cant-be-delivered-because-delivery-to-this-address-is-restricted/</link>
					<comments>http://blog.scdit.com/exchange-your-message-cant-be-delivered-because-delivery-to-this-address-is-restricted/#respond</comments>
		
		<dc:creator><![CDATA[Dwayne Grimes]]></dc:creator>
		<pubDate>Tue, 24 Oct 2017 13:05:41 +0000</pubDate>
				<category><![CDATA[Email]]></category>
		<category><![CDATA[Exchange]]></category>
		<guid isPermaLink="false">http://blog.scdeval.com/?p=140</guid>

					<description><![CDATA[<p>We had a customer getting this bounce back error occasionally. Research lead me to an Exchange distribution group restriction. I went into the exchanged and examined the Group Distribution List. I wasn&#8217;t able to just add the email address so I left it checked with &#8220;Accept messages from&#8221;  and checked &#8220;All senders&#8221;. I then unchecked [&#8230;]</p>
<p>The post <a href="http://blog.scdit.com/exchange-your-message-cant-be-delivered-because-delivery-to-this-address-is-restricted/">Exchange &#8211; Your message can&#8217;t be delivered because delivery to this address is restricted.</a> appeared first on <a href="http://blog.scdit.com">SCD Information Technology</a>.</p>
]]></description>
		
					<wfw:commentRss>http://blog.scdit.com/exchange-your-message-cant-be-delivered-because-delivery-to-this-address-is-restricted/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
