Thank you for the affirmation.
The purpose in this instance is to work around a Microsoft Hosted Exchange service that made it impossible to connect using a Local Outlook Granted, the reasons from Microsoft may be legitimate, they are not in the eyes of users. At 5:00 PM all is good then 15 minutes later, Local Outlook cannot connect to the Exchange Server. The first work-a-round was to use Outlook Web Access. However, the proliferation of Google Chrome has so many using it but when opening OWA, Chrome does not allow send of attachments. It gets more convoluted as FIreFox will work and Internet Explorer will work. The proposed work-a-round is intended to allow the local Outlook to send attachments and have reply come back to the original email address so it appears in the Inbox which is opened by OWA. I may be causing more trouble than worth for a short term solution. A proposal may be going on the table to migrate away from MSHE and move to SmarterMail so the idea is an interim step approach. However one looks at the situation, it is not nice! Thanks for the feedback From: community@mailsbestfriend.com [mailto:community@mailsbestfriend.com] On Behalf Of Darin Cox Sent: Thursday, January 28, 2016 3:30 PM To: community@mailsbestfriend.com Subject: [MBF] Re: Different Send | Receive Accounts This is a common setup for using external MX filtering services. One example is customers on Hosted Exchange who use us for filtering, so our servers are the MX records, then we relay to a subdomain to get the mail to the Hosting Exchange environment... e.g. example.com has MX pointed to us and we relay email sent to u...@example.com to u...@onmicrosoft.example.com. Another example is where outgoing mail is not allowed on the incoming mail server. In that case, to avoid confusion with multiple accounts, we would typically set up the outgoing server with the same email account addresses, but on the sending server have the accounts relay to the primary incoming server via a subdomain as above. That protects against local mail delivery on the sending server. Setting the sending server up with the same account addresses also give you the ability to switch quickly in the event of an outage at the primary incoming mail server. So, yes, what you are mentioning is common, but at least in our case typically done with the same addresses, not different ones. Hope this helps, Darin. From: Martin Margheim <mailto:ad...@kodot.com> Sent: Thursday, January 28, 2016 1:10 PM To: community@mailsbestfriend.com Subject: [MBF] Different Send | Receive Accounts Is it reasonable to think one could set a second email account on a different server for the purposes of sending but have replies returned to the first email account. Why? A recent change by Microsoft Hosted Exchange Servers has disabled the ability to send via the Exchange server. Thus, if a domain was setup on a SmarterMail server that would use that server for sending but have the account reply to the original Exchange server would retain continuity in email processing but still provide the ability to use Outlook and send messages as opposed to using Outlook Web Access which has issues sending attachments, particularly when using Google Chrome. At 5:00 P.M., Friday, January 22, email worked fine. At 5:15 following Microsoft Updates to Hosted Exchange Servers, the Outlook clients were not able to connect. Then attempting to use Outlook Web Access, attachments cannot be sent if using Google Chrome. Rather a mess for the senders. Thus, the reason for the sending email address would relieve situations until an alternate email solution can be established and stop using Microsoft Hosted Exchange altogether. Thanks for thoughts Martin Margheim Independent PC Consultant ad...@kodot.com 727-365-3372
