Active Topics

 


Reply
Thread Tools
Posts: 145 | Thanked: 32 times | Joined on Dec 2007
#11
sorry I wasn't very clear

after you know you are root type

Code:
cd /usr/local/lib/
(plus enter of course)

then

Code:
ls sas*
(plus enter)

let us know what the output is. If it really
is "no such file ..." then for sure your installation
is corrupted.

BTW, my output from the "ls sas*" command looks
like this:

Code:
/usr/local/lib $ ls sas*
libanonymous.la         libcrammd5.so.2.0.22    libotp.so.2
libanonymous.so         libdigestmd5.la         libotp.so.2.0.22
libanonymous.so.2       libdigestmd5.so         libplain.la
libanonymous.so.2.0.22  libdigestmd5.so.2       libplain.so
libcrammd5.la           libdigestmd5.so.2.0.22  libplain.so.2
libcrammd5.so           libotp.la               libplain.so.2.0.22
libcrammd5.so.2         libotp.so
 

The Following User Says Thank You to albright For This Useful Post:
Posts: 322 | Thanked: 28 times | Joined on Feb 2007
#12
Originally Posted by albright View Post
sorry I wasn't very clear

after you know you are root type

Code:
cd /usr/local/lib/
(plus enter of course)

then

Code:
ls sas*
(plus enter)

let us know what the output is. If it really
is "no such file ..." then for sure your installation
is corrupted.

BTW, my output from the "ls sas*" command looks
like this:

Code:
/usr/local/lib $ ls sas*
libanonymous.la         libcrammd5.so.2.0.22    libotp.so.2
libanonymous.so         libdigestmd5.la         libotp.so.2.0.22
libanonymous.so.2       libdigestmd5.so         libplain.la
libanonymous.so.2.0.22  libdigestmd5.so.2       libplain.so
libcrammd5.la           libdigestmd5.so.2.0.22  libplain.so.2
libcrammd5.so           libotp.la               libplain.so.2.0.22
libcrammd5.so.2         libotp.so
Thanks for the step by step help albright. I appreciate it.

OK, when I enter as root
cd /user/local/lib/

xterm tells me :

-sh : cd: can't cd to /user/local/lib

I tried several times and made sure I was root. So any idea what that output means?

Thanks,
Neil
 
Posts: 145 | Thanked: 32 times | Joined on Dec 2007
#13
why are you typing "user" - please read
the command as it is given
 
Posts: 322 | Thanked: 28 times | Joined on Feb 2007
#14
Originally Posted by albright View Post
why are you typing "user" - please read
the command as it is given
Hi Albright

Darn good question. Sorry about that. My mistake. OK, I got the command right this time and xterm gave me the same output as yours except one. The 'libplain.so.2.0' that you had at the end of your list reads 'libplain.so.2.0.22' in my list.

lol, apparently I have 22 extra whatevers in my library

I also went back and made sure I had input PB's original command line and I got 'usage : ln (option) TARGET...LINK_NAME/DIRECTORY'

Does this line look like what yours was? Of course that would be pretty easy to forget.

Anyway, Thanks for the help. I've had a lesson in how to use xterm from you Albright

Cheers,
Neil
 
Posts: 145 | Thanked: 32 times | Joined on Dec 2007
#15
I don't follow you. I have libplain.so.2.0.22 in my system
and on the directory listing above as well ... (that's a
version number BTW)

Anyway, the command PB gave was this:

Code:
ln -s /usr/local/lib/sasl2 /usr/lib
You have to be root to issue this command, so
that is why you start with the command

Code:
sudo su
(after which, as before, whoami will confirm that you
are now root)

Frankly, it looks like you are not entering the command
exactly as it is specified (no "user" in it at all e.g.)

(What you are doing with this is creating what is called
a symbolic link from the already existing sasl libraries
to the place kmail is looking fro this libraries (which is
/usr/lib))
 
Posts: 322 | Thanked: 28 times | Joined on Feb 2007
#16
[QUOTE=albright;137131]I don't follow you. I have libplain.so.2.0.22 QUOTE]

Sorry for the confusion. When I closely look again at the list of your libraries above I see that the page had simply cut off the last two numbers. ( I really need to learn to be more observant )
So its confirmed that I have the same libraries.

I'm not sure if you noticed that I wrote what my xterm output was to PBs command line.

It was:
ln (option) TARGET...LINK_NAME/DIRECTORY

That sounds like the right sort of output for a 'symbolic link' right?

BTW-after doing this command last night I tried Kmail again and I get no mail flow in either direction. I have no idea at this point why.

Anyway, Thanks for the help ALbright. Please don't feel obligated to work on this any more. It's just interesting to work on this to see about getting it going.

Neil
 
Posts: 145 | Thanked: 32 times | Joined on Dec 2007
#17
ln (option) TARGET...LINK_NAME/DIRECTORY

That sounds like the right sort of output for a 'symbolic link' right?
No, actually that looks like the ln command complaining
that it does not understand what you asked it to do.

It's telling you to provide an option, a target and the link name.

the command was supposed to be this:

Code:
ln -s /usr/local/lib/sasl2 /usr/lib
That is: the option is "-s" (a symbolic link)

the target is "/usr/local/lib/sasl2" - the directory where
the sasl files live

and the link name is "/usr/lib" - which is where
kmail looks for sasl, and after the link is made
will jump to the target's location.

Now, if the symbolic link exists then when you do
this:

Code:
cd /usr/lib
ls -l sasl2
you should get:

Code:
lrwxrwxrwx    1 root     root           20 Jan 31 13:51 sasl2 -> /usr/local/lib/sasl2
You should check whether the link exists (I doubt it) and
if it does not then create it (follow PB's instructions again,
to the letter).
 

The Following 2 Users Say Thank You to albright For This Useful Post:
Posts: 322 | Thanked: 28 times | Joined on Feb 2007
#18
Originally Posted by albright View Post

you should get:

Code:
lrwxrwxrwx    1 root     root           20 Jan 31 13:51 sasl2 -> /usr/local/lib/sasl2
You should check whether the link exists (I doubt it) and
if it does not then create it (follow PB's instructions again,
to the letter).
Albright , you are a gem man. I owe you one. Thanks to you my kmail is now working. It can send and receive emails! I appreciate your patience and time spent helping me out here. It's been a fun education for me too. And thanks to Penguinbait too.

Cheers
Neil

Last edited by sungrove; 2008-02-03 at 06:25.
 
Posts: 3 | Thanked: 0 times | Joined on Apr 2008
#19
Hello
I am having trouble sending mail as well using Kmail
I get an error saying:
"Authentication failed
An error occured during authentication SASL(-4) No mechanisms available
No worthy mechs found
Authentication not supported"

I have followed the instructions above
when I try "ln -s /usr/local/lib/sasl2 /usr/lib" it says the file exists
when I try "ls -l sasl2" i get see the file exists

I am new to linux and the n810 and have just started to get KDE going
Its potential amazed me

Thanks in advance
 
Posts: 425 | Thanked: 132 times | Joined on Mar 2008 @ California
#20
@jaksn - I don't think you need to follow the directions here if you just installed KDE, I think these corrections were present in the updated SUP that you downloaded/installed.

Try these instructions here:
http://blog.linuxoss.com/2007/11/13/...onnected-imap/

I was having a lot of problems connecting to the Gmail server, but after I followed these instructions Kmail worked beautifully.

Just as a warning, my tablet choked and ran out of diskspace trying to download all 7500 of my Gmail messages using dIMAP, so try just using normal IMAP or POP3
 

The Following 2 Users Say Thank You to josiahg777 For This Useful Post:
Reply

Tags
deprecated, kde, kde35, kmail


 
Forum Jump


All times are GMT. The time now is 16:23.