<div>
Thanks for your postings. &nbsp;Is there way to see when the last time traffic ran through the SMTP connectors?
</div>


<div>
I had tried the &quot;get-messagetrackinglog -start 09/22/2016 -ResultSize unlimited -eventid Send | select *connector* , timestamp&quot; for two different SMTP connectors which both had the same date/time output stamp. &nbsp;I changed the timestamp to a later date but didn't see the output. &nbsp;On the third run- I changed the ...-start 09/22/2016 to 6/22/2016 but only saw part of the entries. &nbsp;Can I pipe the output to txt file? Thanks.
</div>


<div>
When I ran the &quot;get-messagetrackinglog -start 09/22/2016 -ResultSize unlimited -eventid Send | select *connector* , timestamp | export-csv &nbsp;logs.csv&quot;, the output only shows the SMTP connector name and timestamp date. &nbsp;I had tried a different SMTP connector and received the same results. &nbsp;Maybe I'm overlooking something, &nbsp;Is there supposed to be additional information?
</div>


<div>
My bad...I had replaced the &quot;timestamp&quot; to the actual date. &nbsp;Now when I run- get-messagetrackinglog &nbsp;-ResultSize unlimited -eventid Send | select *connector* , timestamp | export-csv &nbsp;logs.csv , &nbsp;I get the additional dates for the SMTP connection. Thank you!
</div>


<div>
Sorry didn't see your posting Amit until after I had posted. &nbsp;When I run the command with the date of 06/22/2016, &nbsp;I see entries for August and September but nothing for June or July. &nbsp;So this information doesn't proved it's in use or not?
</div>


<div>
As I advise, you disable the connector. I have use this method several times and it is much easy to find out, if connector is in use or not. Secondly, you can enable back in few seconds, if you encounter any issue. Back-out plan need to be always in place whenever you are doing changes on servers.
</div>


<div>
Your logs probably do not go back that for but at I would think if you have not seen any traffic through that connector for all of August and September it is a safe bet it is not in use. <br />
<br />
Though Amits method would work I am not a big fan of such an approach. At least in my environment mail is very important and we try not to break it on purpose if we do not have to. :)
</div>


<div>
I tried the command method on an already disabled SMTP connector only to receive the same output results as an SMTP connector that is enabled. &nbsp;It there another method other than disabling and then renable the SMTP connector?
</div>


<div>
I was doing more research and was going through these logs on the Exchange server but didn't see any activity related to the SMTP connectors.<br />
<br />
C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\<wbr />Logs\Proto<wbr />colLog\Smt<wbr />pReceive<br />
C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\<wbr />Logs\Conne<wbr />ctivity<br />
<br />
I rather not disable the SMTP connectors because they could be in use. &nbsp;It will be disruptive. &nbsp;Is there another means to pull the activity for those SMTP connectors? &nbsp;Thanks.
</div>


<div>
<div class="content wysiwyg-content">
Greetings-<br />
<br />
These SMTP connectors were setup before my time with the organization and I would like to retire them. &nbsp;I have tried utilizing the Message Tracking tool but with no valid information. &nbsp;Please advise. &nbsp;<br />
<br />
Thanks in advance.
</div>
</div>


Greetings-

These SMTP connectors were setup before my time with the organization and I would like to retire them.  I have tried utilizing the Message Tracking tool but with no valid information.  Please advise.  

Thanks in advance.

Is there a way to verify that the Exchange 2013 server is still using the other SMTP connectors that have been setup?

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Interactions between email servers and clients are governed by email protocols. The three most common email protocols are POP, IMAP and MAPI. Most email software operates under one of these (and many products support more than one).  The correct protocol must be selected, and correctly configured, if you want your email account to work.