Add an alternate plain port
I'd say about 98% of ISPs BLOCK port 25. Nobody should argue that it's not best to use SSL/TLS. Granted. But there are TONS of applications and libraries that, due to legacy codebases, don't have encryption libraries built in. SendGrid advertises itself as "integrate in 3 minutes" (my paraphrase). And it's true--it is just SMTP, to get started, very easy, very quick. But for some odd reason, SG doesn't do what *everybody* else does (speaking of mail admins and such): simply open up an alternative plain SMTP port (not SSL/TLS). Most use 2500, or 2525. Easy as pie. And then, presto, situations where ISPs are blocking port 25 are a non-issue, because almost none of them block these alternate ports. It's so easy, so trivial, that it's shocking that SG doesn't have a simple, plain alternate port. There are a lot of fish out there (granted, they're old...but big fish usually are) that cannot use SG for this one trivial reason. SSL/TLS is best, by far. But why not open up a simple alternate plain port, too?
-
Hear hear. Every other SMTP provider that we've used before has supported port 2525 for plain SMTP connections. Not having that is really presenting a problem for us.
-
-
No update on this? It's still a major reason why we can't use SendGrid in many situations.
-
-
you can use port 587 with or without tls.
port 2525 is now also setup the same way. -
-
-
-
-
-
Great! Found this thanks to a Google search, but it should probably be added here:
http://sendgrid.com/documentation/set...
That was the first placed I looked, and nothing suggested I could use 587 w/o TLS. -
-
I've updated the documentation to be accurate: http://docs.sendgrid.com/documentatio...
-
Loading Profile...



Twitter,
Facebook, or email.

EMPLOYEE
EMPLOYEE
