Answers.Body: <p>See the 'Support for Plus Addressing in Office 365' roadmap item for Exchange Online... due July 2020</p>
  
  <p>"Plus Addressing is a great way to quickly create custom (or disposable) email addresses based off your standard email address, by simply adding a "+" suffix string to an existing email address in Office 365. For example, a plus address for kimakers@contoso.com could be something like kimakers+northwind@contoso.com that she could use to sign up for the newsletter at the Northwind web site. Then when Northwind sends a newsletter to kimakers+northwind@contoso.com it will route directly to kimakers@contoso.com. Kim could create an Inbox rule that then moves messages sent to this + address into the "Northwind" folder. Plus addressing support in Office 365 is a great way to more easily manage your Inbox, and even track mail like marketing and sales campaigns.</p>
  
  <p>Featured ID: 59441
  Added to Roadmap: 12/6/2019
  Last Modified: 6/2/2020</p>
  
  <p><a href="https://www.microsoft.com/en-US/microsoft-365/roadmap?featureid=59441" rel="nofollow noreferrer">https://www.microsoft.com/en-US/microsoft-365/roadmap?featureid=59441</a></p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-06-11T05:17:22.803Z
Answers.LastActivityDate: 2020-06-11T05:17:22.803Z
Answers.UserDisplayName: Jonathan Richardson
Answers.Body: <p>ah, yes, Exchange. That mail server that behaves almost like the others, but not quite.</p>
  
  <p>You have 3 paths out of that:</p>
  
  <p>1) use a separate "normal" email server, eg postfix for sending your emails and set up a catch all email address on 365 to handle the bounces</p>
  
  <p>2) use a mail provider for your mass mailing (sendgrid, mailjet, amazon aws...). They probably all need you to install a civicrm extension to handle the bounce events</p>
  
  <p>3) contribute a feature to civicrm so it doesn't need VERP. This isn't that far away, the data of the VERP is already added as an extra line in the mail header and for what I've seen, most of the bounce emails copy it.</p>
  
  <p>So the "only" things you'd need: prevent civi to rewrite the from email with a VERP and change the bounce processor to look at the extra header instead of the envelope email.</p>
  
  <p>I'd suggest you 2, mostly because you are likely to have a better deliverability on your mass mailings than relying on exchange.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-07-27T17:18:29.887Z
Answers.Text: We've resorted to using our old email provider which can handle VERP messages. I suspect that Exchange doesn't like a VERP type return path.  Various people have asked about this from time to time, but it seems our friends in Microsoft haven't responded.
Answers.UserDisplayName: Stephen Palmstrom
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-07-30T17:39:29.273Z
Answers.Text: Which mail provider is that? Might be in the market...
Answers.UserDisplayName: jimcrist
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-07-26T10:37:56.500Z
Answers.LastActivityDate: 2018-07-26T10:37:56.500Z
Answers.UserDisplayName: Xavier
Body: <p>We use Office 365 Exchange Online for our emails.  Whilst you can configure CiviCRM outbound mail to use it, you can't actually send mail using it.  I have done some investigation, and the reason is that packages/Mail/smtp.php replaces the From address with the Return-Path.  CiviCRM adds a VERP component, so Exchange Online rejects the email because the From address is invalid.  Exchange overwrites the Return-Path with the From address anyway, so VERP doesn't work.</p>
  
  <p>Any comments or thoughts?  I assume someone will say that we should use another Mail Transport Agent.</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-07-20T17:52:53.227Z
Comments.Text: You're right - use another MTA!  CiviMail has always required an MTA that supports VERP, and Exchange is the only major MTA that doesn't.  When I have clients using Exchange, I'll usually configure Postfix on their CiviCRM server to handle these mails.
Comments.UserDisplayName: Jon G - Megaphone Tech
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-07-21T20:41:13.493Z
Comments.Text: Thanks, we are using another MTA.  I suppose Exchange is configured for human clients to send emails rather than systems.
Comments.UserDisplayName: Stephen Palmstrom
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-07-24T00:29:33.783Z
Comments.Text: Related thoughts... 
  I've got a CiviCRM install, where the client uses 365 Exchange Online. I'm using sendmail on the server to send and that seems to work just fine with a well set up SPF record.
  
  The only thing I haven't come to terms with is the bounce email address. I'm not sure how best to handle that.
Comments.UserDisplayName: Andrew Wasson
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-07-24T11:46:45.770Z
Comments.Text: I have added some rules in Exchange to handle bounce messages, basically routing emails with the recipient starting with the local part to a given mailbox.  You would still need to prevent the from address being the return-path.
Comments.UserDisplayName: Stephen Palmstrom
Tags: <email><smtp>
Title: CiviCRM, SMTP and Office 365?
ThreadText: # CiviCRM, SMTP and Office 365?
  
  (Asked by: username_0 on 2018-07-20)
  
  We use Office 365 Exchange Online for our emails. Whilst you can configure CiviCRM outbound mail to use it, you can't actually send mail using it. I have done some investigation, and the reason is that packages/Mail/smtp.php replaces the From address with the Return-Path. CiviCRM adds a VERP component, so Exchange Online rejects the email because the From address is invalid. Exchange overwrites the Return-Path with the From address anyway, so VERP doesn't work.
  
  Any comments or thoughts? I assume someone will say that we should use another Mail Transport Agent.
  
  **Tags:** email, smtp
  
  > **Comments:**
  > **username_1**: You're right - use another MTA!  CiviMail has always required an MTA that supports VERP, and Exchange is the only major MTA that doesn't.  When I have clients using Exchange, I'll usually configure Postfix on their CiviCRM server to handle these mails.  
  > **username_0**: Thanks, we are using another MTA.  I suppose Exchange is configured for human clients to send emails rather than systems.  
  > **username_2**: Related thoughts...  I've got a CiviCRM install, where the client uses 365 Exchange Online. I'm using sendmail on the server to send and that seems to work just fine with a well set up SPF record.  The only thing I haven't come to terms with is the bounce email address. I'm not sure how best to handle that.  
  > **username_0**: I have added some rules in Exchange to handle bounce messages, basically routing emails with the recipient starting with the local part to a given mailbox.  You would still need to prevent the from address being the return-path.  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_3 on 2020-06-11. Score: 2
  
  See the 'Support for Plus Addressing in Office 365' roadmap item for Exchange Online... due July 2020
  
  "Plus Addressing is a great way to quickly create custom (or disposable) email addresses based off your standard email address, by simply adding a "+" suffix string to an existing email address in Office 365. For example, a plus address for kimakers@contoso.com could be something like kimakers+northwind@contoso.com that she could use to sign up for the newsletter at the Northwind web site. Then when Northwind sends a newsletter to kimakers+northwind@contoso.com it will route directly to kimakers@contoso.com. Kim could create an Inbox rule that then moves messages sent to this + address into the "Northwind" folder. Plus addressing support in Office 365 is a great way to more easily manage your Inbox, and even track mail like marketing and sales campaigns.
  
  Featured ID: 59441
  Added to Roadmap: 12/6/2019
  Last Modified: 6/2/2020
  
  <https://www.microsoft.com/en-US/microsoft-365/roadmap?featureid=59441>
  
  
  ---
  
  ### Answer by username_4 on 2018-07-26. Score: 1
  
  ah, yes, Exchange. That mail server that behaves almost like the others, but not quite.
  
  You have 3 paths out of that:
  
  1) use a separate "normal" email server, eg postfix for sending your emails and set up a catch all email address on 365 to handle the bounces
  
  2) use a mail provider for your mass mailing (sendgrid, mailjet, amazon aws...). They probably all need you to install a civicrm extension to handle the bounce events
  
  3) contribute a feature to civicrm so it doesn't need VERP. This isn't that far away, the data of the VERP is already added as an extra line in the mail header and for what I've seen, most of the bounce emails copy it.
  
  So the "only" things you'd need: prevent civi to rewrite the from email with a VERP and change the bounce processor to look at the extra header instead of the envelope email.
  
  I'd suggest you 2, mostly because you are likely to have a better deliverability on your mass mailings than relying on exchange.
  
  > **Comments:**
  > **username_0**: We've resorted to using our old email provider which can handle VERP messages. I suspect that Exchange doesn't like a VERP type return path.  Various people have asked about this from time to time, but it seems our friends in Microsoft haven't responded.  
  > **username_5**: Which mail provider is that? Might be in the market...  
  
  ---
  
  