Yes.
While Awans main email address began rejecting mail after it was shut down, the 123 address in Rep Andre Carson's was still accepting mail as of Tuesday.
Mail sent via Gmail fills in the name of the account-holder of 123 as Nathan Bennett, a Carson aide; Bennet's LinkedIn profile says his individual legislative portfolio covers national security and foreign affairs and includes work on the House Permanent Select Committee on Intelligence.
The member Bennett works for, Andre Carson, is a member of both the House Intelligence and House Homeland Security Committees, and previously employed Awan.
Carson is also ranking member of the House intelligence subcommittee on Emerging Threats, which oversees the Office of the Director of National Intelligence. The subcommittee oversight extends to the National Counterterrorism Center and information-sharing programs.
A spokeswoman for Andre Carson, Jessica Gail, did not express concern or surprise when contacted by TheDCNF about Awans still-active email address Monday morning. Bennett said Tuesday morning Gail had not even informed him of the details.
Bennett, who is Carsons deputy chief of staff, told TheDCNF he has no control over the 123 address. However this happened, it was not with my consent or control, he said in an email. For the record, I do not, nor have I ever, had control of the 123@mail.house.gov email account or any other account connected with Imran Awan or his family. That could not be confirmed by the Houses chief administrative officer (CAO) because spokesman Dan Weiser has said the CAO will not comment on matters pertaining to this ongoing investigation.
Bennetts response raises questions about whether Awan was misusing Carsons office, access or staffers.
Gail declined to comment on Awan, or state whether the office is concerned he may have misused Bennetts identity. She also declined to state whether the office has taken any measures to assess its data security since Awans problems came to the attention of the office in September 2016.
Carson had employed Awan since 2015, and did not fire him when his office learned Awan was the subject of an investigation in September. He also did not fire Awan immediately after he was banned from the House computer network by Capitol Police in February, payroll records show.