I think so, George. When I ran this from home, the task consistently took 10-12 seconds. After I installed it on my client's machine, it took 4 seconds once, and timed out with unable to connect error messages at 30 seconds later. Switching to port 25 (from 587) didn't make any difference.
Not much help on their web site either http://www.mandrill.com
I am not going to pretend to know a lot about what you're doing, but here's some ideas (that you've probably tried already!):
Because you're experiencing quite different results from two different locations this suggests to me something networky.
Originally Posted by http://help.mandrill.com/entries/21738477-What-SMTP-ports-can-I-use-
ISPs may redirect traffic on certain ports, so it's up to you which port you use. It's just a matter of what you prefer and what works for you.
Originally Posted by http://help.mandrill.com/entries/24633717-Why-am-I-getting-a-Relay-Access-Denied-error-trying-to-send-through-SMTP-
Ensure that your hosting provider or internet provider (ISP) allows outbound SMTP connections. Some shared hosting providers only allow outbound SMTP connections on dedicated servers, while others block them completely. In some cases, hosting providers might redirect the connection so instead of connecting to smtp.mandrillapp.com, you connect to their local server instead.
My client was sending out about 500 pay cheque notification emails every two weeks. Their ISP's ISP decided that the emails were spam, and suggested using mandrill.
My first (foolish) thought was to modify sendmail to use mandrill as the smart host.
Payday is Wednesday.