Hello Josef,
[email protected] wrote:
|Steffen Nurpmeso <[email protected]> writes:
|> Dear Josef, first of all it is good to know that S-nail users can
|> still access gmail.com from within the command line! All *i* can
|> But whatever i do, this won't go away.
|> (It seems that Google always classifies my mails as SPAM, which
|Oh; your mail was not classified as spam to me. Sorry about the
Maybe it is joke from some Google guy: i know where i can find my
messages, shall i want to have a look ;-)
Astonishing how flexible such a giant system can be, then.
|delay in my response. Sorry to hear about your woes trying
|to access gmail from the commandline. Perhaps you can
|use the .mailrc file I posted as a template.
That turned out to be some new Google policy!
I had to enable "lessersecure" (or the like) application support
in the HTTPS web interface, and that made it work again!
Only in private i said that this is fascism and incitement of the
people: S-nail uses OpenSSL over TLSv1.2, and i still think that
is the most secure protocol available. Not the lessersecure.
|
|> May i suggest to you -- in case you plan to stay with S-nail from
|Thank you for the tip.
|
|> And then, while you are changing your configuration anyway,
|> account gmail {
|> set v15-compat
|> set ssl-verify=strict ssl-method=tls1.2
|> set smtp-use-starttls smtp-auth=plain \
|> smtp=josef.jurek%[email protected]:587
|>}
|> account gmail
|
|I have implemented this and apparently, it is working.
Good.
Note that i've just outdated *ssl-method*, so the above needs at
least one more adjustment (plus drop of *v15-compat*) to be future
proof -- ha-ha-ha.
But OpenSSL v1.0.2 and above introduce a new configuration
interface that can be passed strings, as in "ALL,-SSLv3,-SSLv2",
and i also sent enhancement requests to extend this by "NEWEST"
and "VULNERABLE" so that it would be possible to say "-ALL,NEWEST"
or "ALL,-VULNERABLE".
So this will allow users -- like you -- to stay secure by simply
updating your OpenSSL library (and most often this will even
happen transparently via a normal system upgrade). No more need
for source code changes, no need for recompilation from the S-nail
side of the road. (However, for the current OpenSSL v1.0.1
i have written a wrapper that only knows what it knows -- say.)
So from S-nail v14.8 on there will be a new *ssl-protocol* with
values as above, and *ssl-method* will vanish with S-nail v15.0.
|> By the way, i've never used an account name with @ (over SMTP),
|> does this really work?
|
|Well, the .mailrc file I posted does work.
Good to know, thanks.
|Thank you for your input and suggestions.
My pleasure!
--steffen
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
S-nail-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/s-nail-users
