Re: Solaris 8 - Configuring sendmail relay (NoAuth inbound -> SSL outbound)



"Dave.Anderson-NOSPAM" <dave.anderson.qa@xxxxxxxxx> writes:

SSL is a requirement. The specific auth mechanism I am unsure of, but
if I don't have my username/password correctly entered, mail doesn't
get sent. I can find some time to look into this over the weekend,

Per has already mentioned telnetting to port 25 and port 587. What did
you get there? If it showed STARTTLS you may be in good shape.

You may like a little tool I just learned about called swaks
(swiss army knife smtp)

I just used gentoo linux portage setup to install it but on solaris
you may need to google up a suitable package or build from source.

Telnet should tell the story but if you want a nifty little tool that
will give a bit more info try swaks.

Be sure to aim telnet or swaks at port 587 on the server. I just
found out with Per H's prompting that on a cable (comcast) ISP that
the normal sendmail with compiled in ssl STARTTLS support works when I
was thinking I needed to do exactly what you are thinking about;
cobbling up some kind of stunnel or other ssl wrapper to talk to part
465 that will be no fun to maintain.

All it really took was a line Per posted in:
Message-ID: <g0kmsb$2ddp$1@xxxxxxxxxxxx>
that makes sendmail contact the smarthost on port 587.

My isp had been ok with plain authentication until just a couple weeks
ago and guess who my isp was just before I switched to comcast
.... ATT. Up until about 2 mnths ago and again plain password auth was
ok with them then.

So I'm thinking some of the big players in the ISP field may be doing
the same kind of things on there mail servers... If your problems
arose quite recently ... that seems even more likely.

.



Relevant Pages

  • Re: Solaris 8 - Configuring sendmail relay (NoAuth inbound -> SSL outbound)
    ... Per has already mentioned telnetting to port 25 and port 587. ... You may like a little tool I just learned about called swaks ... the normal sendmail with compiled insslSTARTTLS support works when I ... My isp had been ok with plain authentication until just a couple weeks ...
    (comp.mail.sendmail)
  • Re: POP3 Error 10060 - desperate
    ... After failing to telnet to my ISP ... port 110, ... >packet filter in ISA and Javier recommended. ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: large number of messages in outbound queue
    ... If you can Telnet on port 25 to other clients and they are ... NOT on your same ISP then you are not being blocked on ... specific queues. ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange incoming email issue
    ... If you get a blank screen when you telnet on port 25 something is not right. ... Your ISP is probably routing port 25 to some other system. ... I built an SBS 2003 R2 server a couple of weeks ago, ...
    (microsoft.public.windows.server.sbs)
  • Re: OWA-IE6 Access denied
    ... OWA works on port 443. ... you should get a blinking cursor if you run "telnet mail.mycompany.com 443" from a command prompt on the remote client. ... As this happened when you changed ISPs, and OWA still works from other locations, then the ISP should help you resolve it. ...
    (microsoft.public.windows.server.sbs)