Hello! Dear Gavin!! Gavin Troy <[email protected]> wrote: |Greetings Steffen, list, | |Following Karol's post, I reviewed an earlier problem I was \ |having, and found |it to be related to the encoding of @ within USER when using xxx-USER@HOST |settings. Note that this behavior change is not dependant on v15-compat. | |> # 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. Bug again, ... if that really continues like that i will be offering my services shall Hollywood need some bugs for Mummy 33 1/3 .. or so. There is a preliminary patch on [next]. |I think this is a step backwards, especially considering a raw "@" works in |"folder", "smtp", etc., and so I expect it is an unintended change. USER and PASS should only be URL-encoded when part of an URL, otherwise not. |Furthermore, when trying out v15-compat, I expected the same setting to |authenticate my smtps session. However, S-nail actually requires the port |number to be included. Thus I need eg. | |> 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. 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. |Finally to sign off, I'd just like to say that I don't technically require |user/host-specific settings at all. I simply like being able to source |passwords for multiple accounts from a separate file, so that \ |the guts of the |config can live on bitbucket/github. But this is of course unnecessary. :) I would like to see .netrc support, even better would be some kind of agent support, like gitcredentials(7). |As established by the fact that it was previously broken for a decade before |being fixed by S-nail, it's likely that nobody else uses this \ |feature anyway! Thanks again Gavin -- i didn't realized this problem at all. |-- |Gavin --steffen ------------------------------------------------------------------------------ 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
