M. Fioretti a écrit :
> On Thu, Dec 04, 2008 00:02:33 AM +0100, mouss wrote:
>> Roderick A. Anderson a écrit :
>>> Magnus Bäck wrote:
>>>> [snip]
>>>> Why do you insist on testing this with telnet?...
>>> Because I can do it one step at a time and see the results that
>>> Postfix sends back. I hadn't thought of telnet possibly munging
>>> base64 encoded values. They looked like ASCII-only to me.
>> well, you said you tried google and possibly other things. but did
>> you try http://www.postfix.org/SASL_README.html#server_test
>> ...
>
> Sorry to step in, but I already pointed out one year ago or so that
> there is a problem with answers like these. In the results of many
> Postfix-related searches, especially those a newbye may make, the
> official postfix.org pages often are _far_ from being the first
> result: before them you get a screenful or so of links to howtos which
> (seem to) "just work", so you never get to the postfix pages, nor feel
> any need to get there. I posted specific examples of this here last year.
>
> That's why there are, several times a year, cases like the one above:
> for some reason that, sorry, I'm unable to help with, the official
> documentation is quite SEU (Search Engine Unoptimized). Don't ask me
> why, but that's what happens.
>
not sure I undertsand what you have in mind. but lessee.
Firs of all, since you use postfix, the first place to look for is the
postfix site, and you should quickly find
http://www.postfix.org/documentation.html
but let's say you prefer to use google because you like search engines.
I don't know for you, but here is what I do:
1- I load www.google.com and I type: postfix sasl test
2- I click on the first returned link
3- I am on the postfix sasl page.
4- I use CTRL-F to look for "test"
5- I click on the link. which is exactly the one I sent you.
was this really long? difficult?
