Document RjwOb83G53xYwprJK3r2n0L5v

To: kristina_baurn@mail.house.gov[kristina_baum@mail.house.gov] From: Microsoft Outlook Sent: Mon 3/27/2017 12:35:26 PM Subject: Undeliverabie: RE: Lamar Smith mtg w/ Administrator Pruitt RE: Lamar Smith mtg w/ Administrator Pruitt Your message to kristina_baum@mail.house.gov couldn't be delivered. Security or policy settings at rejected your message. have hupp.sydney Sender Office 365 mail.house.gov Action Required Security or policy violation How to Fix It The recipient's email server won't accept your message because it appears to violate their security or policy settings. Check the Reported error below to see if you can determine why it was blocked. Then try one or more of the following: If the error mentions SPF, DKIM, or DMARC issues, forward this message to your email admin for assistance. The recipient's email server might suspect that your message is spam. Follow the guidance in this article: ErA'riiyrifi 51s1 Practices for Senders. Then resend your message. If the error suggests your message is too large, try to reduce the size of your attachment. If that isn't possible, place the file on a publicly accessible cloud storage location, like OneDrive. Then add a link to the file in your message, and resend the message. Contact the recipient (by phone, for example) and tell them to ask their email admin to add you or your email domain to their allowed senders list. If the problem continues, forward this message to your email admin. If you're an email admin, refer to the More Info for Email Admins section below. Was this helpful? Send feedback to Microsoft. 17cv1906 Sierra Club v. EPA ED_001523B_00005007-00001 More Info for Email Admins Status code: 550 5.7.1 This error occurs when the recipient's domain has security or policy settings that reject the sender's message. However, we were unable to determine the specific setting that's causing this rejection. Usually the error is reported by an email server outside of Office 365. Common issues include the following: the receiving server suspects the message is malicious or spam; the Sender Policy Framework (SPF) record for epa.gov is incorrectly configured or doesn't exist; or the message includes an attachment larger than the receiving server will accept. Try one or more of the following: Review the reported error - Check the Reported error shown below to help determine what the issue might be. For example, if the issue is related to an SPF failure, the reported error will usually include the acronym "SPF" or the phrase "Sender Policy Framework." Correctly configure your SPF records - If you're the sender's email admin, make sure your domain's SPF records at your domain registrar are properly configured. Office 365 supports only one SPF record (a TXT record that defines SPF) for your domain. Include the following domain name: spf.protection.outlook.com. If you have a hybrid configuration (some mailboxes in the cloud and some mailboxes on premises) or if you're an Exchange Online Protection standalone customer, add the outbound IP address of your on-premises servers to the TXT record. To learn how, see Customize an SPF record to validate outbound email sent from your domain and External Domain Name System records for Office 365. Unable to relay - If the Reported error indicates a problem with relaying (e.g. "unable to relay"), then the email server that reported the error likely isn't set up correctly to receive and relay messages from the sender's domain. This server will usually be one of your on-premises servers in a hybrid environment, a smart host email service that you're trying to route messages through, or possibly even an email hosting service you used in the past yet still have mail flow settings pointing to (e.g. your MX record at your domain registrar still points to your previous email service provider). Check Error reported by shown below to determine what domain, service, or server is reporting the error. The email server needs to be configured to either accept messages from anonymous users or to include the sending domain or IP in its list of authenticated senders. On an Exchange server, you can set this up in the server's receive connector. If it's a smart host managed by another service or partner, contact the service or partner to configure their servers to accept and relay messages from your senders. Also, work with your domain registrar to make sure your MX records are properly configured. Contact the recipient's email admin - For some scenarios, you can fix the issue by contacting the email admin at the recipient domain to ask them to add the sender's email address or your domain to their allowed senders list, or to relax the setting that's causing the rejection. For more information and tips for fixing this issue, see Fix email delivery issues for error code 5.7.1 in Office 365. Original Message Details Created Date: 3/27/2017 12:35:23 PM 17cv1906 Sierra Club v. EPA ED_001523B_00005007-00002 Sender Address: Recipient Address: kristina_baum@mail.house.gov Subject: Error Details Reported error: RE: Lamar Smith mtg w/ Administrator Pruitt 550 5.7.1 Unable to deliver to <kristina_baum@rnail.house.gov> DSN generated by: DM2PR09MB0413.namprd09.prod.outlook.com Remote server: perseus.house.gov Message Hops HOPTIME FROM TO (UTC) WITH RELAY TIME 3/27/2017 1 25-24 DM2PR09MB0639.namprd09i2BRaftlBB3ainBmprdQSiflbd.outlook.com 1 sec PM 2 ^2^yDM2PR09MB0639.namprda9A2a&aMBK.tibnBmprdCraiiproElaftiSMiec&aiver * pm (version=TLS1_2, HM cipher=TLS_ECDHE_RSA_WITH_AES_256 Original Message Headers DKIM.Signature : v=l; a=rsa.sha25 6 ; c=relaxed/relaxed; d=usepa.onmicrosoft.com; s=s e1e c t o r1.epa.gov; h=From:Date : Sub j ect: Message.ID : Content.Type : MIME.Version ; bh=+21 9 T z vb z t r F s Z T WXwS S t AwT F P f I, s k 7 81 GWXRpvb 2 s 4 = ; b=cVRAjFc/lZOC+VMlJPWVLWWrGOMpcnDs4ZII+P+yU/VQhaGlEbGFLyRpQhaswHpTXlkxaNkQUy8GCbSEQlqak9 Received : from DM2PRO 9MB0 63 9.namprdO 9.prod.outlook.com. (10.161.253.143) by DM2PRO 9MB0 413.namprdO 9.prod.outlook.com (10.160.248.14) with Microsoft SMTP Server (version=TLSl_2, cipher=TLS ECDHE_RS.^WITH_.AES_25 6_CBC_SHA38 4_P384) id 1 5.1.977.11; Mon, 27 Mar 2017 12:35:24 +0000 Received: from DM2PR09MB0639.namprd09.prod.outlook.com, ([10.161.253.143]) by DM2PR09MB0639.namprd09.prod.outlook.com, ([10.161.253.143]) with mapi id 15 .01.0991.020; Mon, 27 Mar 2017 12:35:24 +0000 From: "Hupp, Sydney" <hupp.sydneyhepa.gov> To : "kristina baum@m.ai.l.. house . gov" <kri.sti.na baum@m.ail. house . gov> CC: "Jackson, Ryan" <jackson.ryanOepa.gov> Subject: RE: Lamar Smith mtg w/ Adm..i.n.i.strat.or Pruitt Thread.Topic: Lam.ar Smith mtg w/ Administrator Pruitt Thread.Index: AdKeeU2AOZybu9IoQ3+IBELZJsoMrgHS9+YgACJCyeA= Date: Mon, 27 Mar 2017 12:35:23 +0000 Message.ID : <DM2PR09MB0639783D793FD9332B230E0CF1330@DM2PR09MB0639.namprd09.prod.outlook.com> References : <1E5724544 8 0C7 94CB.A5D6111F3A2736B2E1.87 0 9C@FHOB.HRMO 6 . US . House . gov> CBN3PR0 9MB04 01. 635 81 94 61.182DA2CE03D85300@BN3PR0 9MB0 4 01.. namprdO 9 . prod. outlook . com> In.Reply.To : <BN3PR0 9MB04 01. 635 81. 9 4 61.18 2D.A2CE0 3D8 53 0 0@BN3PR0 9MB0 4 01 . namprdO 9 . prod . outlook . com> Accept.Language: en.US Content.Language : en.US X.MS.Has.Attach: 17cv1906 Sierra Club v. EPA ED_001523B_00005007-00003 17480 63052155) (21532 8162 6 9658) (229425074 6 94992 ) (8121501046) (5005006) (3002001) (10201501046) (6 3 FD 9 3 3 2 B 2 3 0 E 0 CF13 3 0 DM2 PR 0 9MB 0 6 3 9n amp_" e: 27 Mar 2017 12:35:23.9683 Hosted 4867..acf9.7 6aacbeca6a7 amped : DM2PR09MB0413 17cv1906 Sierra Club v. EPA ED_001523B_00005007-00004 To: Cc: From: Sent: Subject: kristina_baum@mail.house.gov[kristina_baum@mail. house, gov] Jackson, Ryan[jackson.ryan@epa.gov] Hupp, Sydney Mon 3/27/2017 12:35:23 PM RE: Lamar Smith mtg w/ Administrator Pruitt Hi Kristina, great to meet you via email! Just called and left you a VM. If you have some time to connect over the phone today, that would be great. My cell is 202.816.1659. Thank you, Sydney From: Jackson, Ryan Sent: Sunday, March 26, 2017 4:12 PM To: Hupp, Sydney <hupp.sydney@epa.gov>; kristina_baum@mail.house.gov Subject: FW: Lamar Smith mtg w/ Administrator Pruitt We would love to do this. Happy to lend support on the Chairman's bill. Syd is the Administrator's scheduler and we will work on this. From: Baum, Kristina [mailto:Kristina.Baum@mail.hoiise.gov] Sent: Thursday, March 16, 2017 1:24 PM To: Jackson, Ryan <jackson.i-yan@epa.gov> Subject: Lamar Smith mtg w/ Administrator Pruitt Hey Ryan! I hope everything is going well over there, and you are getting good and settled over at EPA. Chairman Lamar Smith is interested in meeting Administrator Pruitt in the next week or two. What would be the best possible route to arranging this on Pruitt's schedule? 17cv1906 Sierra Club v. EPA ED-001523B_00005008-00001 We wouldn't anticipate any press involved, but hope to get the conversation started between the two. I know Pruitt testified before our committee last session on climate science, and Lamar is looking to connect with him in Pruitt's new capacity about a few goals he has at the committee regarding EPA. Also - I've been left to eating my York peppermint patties all by myself over here! Sad! Best, Kristina Kristina Baum Communications Director U.S. House Committee on Science, Space, and Technology Twitter: @HouseScience Phone: 202.225.6371 17cv1906 Sierra Club v. EPA ED_001523B_00005008-00002