Just noticed that I never received a copy of my last NSLUG post
detailing successful use of stunnel to access POP3 on port 995.
I was about to resend it when I realized that the NSLUG listserv
distributes posts as From: Originating-user@users-host.
But my ISP's SMTP server regards mail From: user@my-isp (in the MAIL
FROM SMPT protocol exchange) but originating from an IP address not in
their network as spam or otherwise $BAD_STUFF. And won't accept it.
This is compounded by the failure of the SMTP smarthost I'm using for
outgoing mail (not in my-isp's network) to send a bounce mssg. It
just vanishes mssgs that are refused by the destination server.
I have a work-around for corresponding with my-isp's support guy but
no control over how the NSLUG list does things. So I never see my own
posts and can't verify that they've been distributed unless someone
happens to reply.
Why does the listserv only put the NSLUG address in the Reply-to:
field and not also in the From: field? Does anybody else have this
problem? I would also never see posts from other-user@my-isp should
there be such a person on the NSLUG list.
Grateful for the help NSLUGgers offered on my TLS/POP3 problem and was
checking to see that my thank you follow-up had been delivered. Failed
because of above. Grumble.
- Mike
--
Michael Spencer Nova Scotia, Canada .~.
/V\
[hidden email] /( )\
http://home.tallships.ca/mspencer/ ^^-^^
_______________________________________________
nSLUG mailing list
[hidden email]
http://nslug.ns.ca/mailman/listinfo/nslug
Locked
