Outgoing mail is blocked here until I figure out how to adapt to my
ISP's move
from SMTP on port 25 to SMTPS on port 465 for subscriber's outgoing
mail.
 For more than a decade I've run postfix, though an MTA isn't
essential for one user, I'll admit.

Scouring a bunch of search hits came up with only limited info which
boiled down
to a direct edit of /etc/postfix/master.cf to uncomment these SMTPS
lines:

    #smtps     inet  n       -       -      
-       -       smtpd
    #  -o syslog_name=postfix/smtps
    #  -o smtpd_tls_wrappermode=yes
    #  -o smtpd_sasl_auth_enable=yes
    #  -o
smtpd_client_restrictions=permit_sasl_authenticated,reject
    #  -o milter_macro_daemon_name=ORIGINATING

 A quick check of /etc/services shows we already have:
    ssmtp           465/tcp        
smtps           # SMTP over SSL

 So after a "postfix reload", outgoing mail was  ...  still
rejected by mail.internode.on.net

 Hmmm, a "postconf | more"  showed:
        default_transport = smtp

 so I commented out the SMTP line in /etc/postfix/master.cf :
 smtp      inet  n       -       -      
-       -       smtpd

 Another "postfix reload", and outgoing mail is  ...  still
rejected by mail.internode.on.net

Presumably this has been encountered before, so I thought I'd ask if
there's
a working Howto out there somewhere, while I figure out how to aim
netcat through
ssl at the mailhost, and find out if my layman's raw SMTP will evoke
sufficient response to
reverse engineer access, or maybe SMTPS is different syntax?

And, yes, the ISP does post setup guides - for M$ and GUI browser/MUA
apps,
 i.e. form-filling clicky-stuff. But nothing useful.

Erik
(Not thrilled with this webmail stopgap thing.)

Reply via email to