On Sat, Jun 14, 2014, at 16:42, Steffen Nurpmeso wrote:
> 
>  |> # required syntax for < 14.7
>  |> set [email protected]@mail.messagingengine.com=PASSWD
>  |> # required syntax for 14.7
>  |> set password-gavtroy%[email protected]=PASSWD
> 
> You are absolutely right, way too often URL percent encoded values
> are assumed when normal strings should be expected instead.
> There is a preliminary patch on [next].

The "password-USER@HOST" still requires %40 in this preliminary patch.
Although, I don't mind either way, as long as it's documented. Also as I
mentioned on the forum:
> url-syntax is off-by-one. I must use
> > set folder="imaps://[email protected]@mail.messagingengine.com"
> where X is any character that gets ignored.
I wonder how you used it successfully.

>  |> set password-mail.messagingengine.com:465=PASSWD
>  |
>  |which I think is not the desired behavior.
> 
> Didn't Heirloom mailx(1) also used the entire HOST part?
> (I thought i saw something like that..   But i'll also look at
> that again.)
> But yes, this behaviour is a conscious decision.
> However, if Heirloom really didn't then it should be covered by
> *v15-compat*.  Damn.

Actually, I don't know what the old/"correct" behaviour is, because I
never used pop/imap with a non-standard port! For smtp(s), the so-called
smtp-auth-user-USER@HOST and smtp-auth-password-USER@HOST settings were
used. Although strangely and misleadingly, "USER@HOST" has always
referred only to the value of "from", so a non-standard port never comes
into question.

When I tried to use this syntax (no-v15-compat) I found that this is
broken too. I would expect this to work:
> set [email protected]="test"
Instead S-nail seems to accept
> set smtp-auth-password-smtps://mail.messagingengine.com:465="test"


> What is not yet conscious is that you have to say :465 to gain
> SMTPS (except on NetBSD, which lists SMTPS in /etc/services) -- it
> would be much nicer if that special case would be handled
> automatically.  Not yet.

Seems like it makes sense. Regardless of what the actual standards say,
465 is the only standard that counts :)

-- 
Gavin

------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
S-nail-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/s-nail-users

Reply via email to