With the huge scale environment I currently work in my team has had some difficulty when it comes to validating customer transport changes, specifically when adding new send connectors or new smart hosts. The same goes for troubleshooting mail flow….you know…whip out good ole’ Telnet, check SMTP status manually and then go on from there. What happens when security bans Telnet? What happens when you have 40 transport servers that you need to validate against 20 – 30 smart hosts over multiple connectors? Or you have a gazillion address spaces over a gazillion send connectors….you need some way of automating the checks to help you with troubleshooting if you need to, or validate a transport change when you make changes to send connectors.
Well, let me introduce a very simple, yet efficient tool I branded PelNet…..yes, that’s my take on PowerShell Telnetting 🙂
So, let’s see what this baby can do.
Before I get into the usages, let’s talk about the parameters the script accepts:
- AddressSpace: Which AddressSpace should the script look for in the Send Connectors?
- sendConnector: Specify if you want the scope to be a single Send Connector.
- SourceTransportServers: Accepts comma separated list of transport servers to test from.
- smartHost: The smarthost you want to test against. Accepts comma separated list value.
- mailSubmissionTest: Use this switch if you want the script to submit the mail to the mailbox. If you omit the parameter the script will skip the DATA portion of the SMTP verb.
- From: From address (firstname.lastname@example.org)
- Rcpt: Recipient Address (email@example.com)
- LogFolderPath: Log file and report location, default will be current path if not specified.
- Port: Default is 25, but you can specify a custom port if you need to.
Read the complete blog at http://blogs.technet.com/b/exchange/archive/2014/04/30/released-introducing-pelnet.aspx
Read my favorites blogs: