After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 641480 - can't connect to groupwise server: Servname not supported for ai_socktype
can't connect to groupwise server: Servname not supported for ai_socktype
Status: RESOLVED WONTFIX
Product: evolution-groupwise
Classification: Deprecated
Component: Groupwise Plugins/Features
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Evolution Groupwise development team
Evolution QA team
gnome[unmaintained]
: 644175 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-02-04 11:54 UTC by Henk
Modified: 2013-07-23 14:38 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Henk 2011-02-04 11:54:00 UTC
When I try to connect to a Novell groupwise 8 server using ssl encryption I get
the following error message:

Error while Scanning folders in 'GroupWise server <groupwise server>'.
Host lookup failed: <groupwise server>: Servname not supported for ai_socktype

I only have problems with the mail, the calendar is working fine.

I've seen this problem in Mandriva Cooker and Ubuntu Natty.

Versions:

Mandriva:
evolution-2.32.1-1mdv2011.0.x86_64

Ubuntu:
evolution-2.32.1-0ubuntu3 x86_64
Comment 1 Akhil Laddha 2011-02-07 04:39:53 UTC
It may be server related problem nothing specific to client.

Have a look at Google query 
http://www.ducea.com/2006/09/11/error-servname-not-supported-for-ai_socktype/
Comment 2 Henk 2011-02-07 09:45:05 UTC
I don't have this problem with evolution 2.30 using the same server and config. So I doubt it is a server related problem.
Comment 3 Akhil Laddha 2011-02-07 09:58:02 UTC
Did you try to follow steps mentioned in the link in comment#1 ?
Comment 4 Henk 2011-02-07 10:53:18 UTC
Which service do I have to add to /etc/services?
Do I have to add it on the server or on the client or both?
Comment 5 Milan Crha 2011-02-28 15:34:28 UTC
(In reply to comment #2)
> I don't have this problem with evolution 2.30 using the same server and config.
> So I doubt it is a server related problem.

Both 2.30.x and 2.32.x is using nss for ssl in camel (mail). I guess some change in nss/nspr made the difference.
Comment 6 Akhil Laddha 2011-03-09 04:05:47 UTC
*** Bug 644175 has been marked as a duplicate of this bug. ***
Comment 7 vok 2011-04-14 08:06:48 UTC
In gentoo I updated to mail-client/evolution-2.32.2-r3 and the problem persists.

Debug output:

evolution-mail-Message: Error occurred while existing dialogue active:
Host lookup failed: gp.ujv.cz: Servname not supported for ai_socktype

(evolution:10129): camel-groupwise-provider-WARNING **: ERROR: Could not get a pointer to the store
(evolution:10129): camel-DEBUG: 0x1489ed0 CamelOperation status stack non-empty
(evolution:10129): camel-DEBUG: 0x1489ed0    Status was "Sending Message"
evolution-mail-Message: Error occurred while existing dialogue active:
Host lookup failed: gp.ujv.cz: Servname not supported for ai_socktype
Comment 8 Vincent van Adrighem 2011-04-14 09:24:53 UTC
Hi, I have further info:
Downstream bug: Ubuntu #708308

I can confirm this probolem is in fact with evolution, not with changes in nss/nspr. Here's my test:

1. Situation is evolution 2.30.3. Groupwise account works as expected
2. Upgrade to 2.32.2 (apt-get install evolution). This does the fopllowing changes on my system:
REMOVED:
   libgtkhtml-editor-common (3.30.3-1)
   libgtkhtml-editor0 (3.30.3-1)
NEWLY INSTALLED:
   libgtkhtml-editor-3.14-0 (3.32.2-2)
   libgtkhtml-editor-3.14-common (3.32.2-2)
UPGRADED:
   evolution (2.30.3-5 => 2.32.2-2)
   evolution-common (2.30.3-5 => 2.32.2-2)
   evolution-data-server (2.30.3-2 => 2.32.2-4)
   evolution-data-server-common (2.30.3-2 => 2.32.2-4)
   libevolution (2.30.3-5 => 2.32.2-2)
   libgtkhtml3.14-19 (3.30.3-1 => 3.32.2-2)

Already on my system:
ii  libcamel-1.2-23                        3.0.0-1                           Evolution MIME message handling library
ii  libcamel1.2-14                         2.30.3-2                          The Evolution MIME message handling library
ii  libcamel1.2-19                         2.32.2-4                          The Evolution MIME message handling library

Now evolution cannot connect, like the reporter of this bug said..the ai_socktype error.

Turning off SSL-support (doing localhost loopback using stunnel), still results in the same ai_socktype error, while I am able to connect just fine using telnet.

Can someone please tell me how to hunt this bug down? I'm all out of ideas here...
Comment 9 Vincent van Adrighem 2011-04-14 09:25:51 UTC
Oh, before I forget, upgrade to version 3.0.0.-1 of evolution and evolution-data-server (debian packages) didn't help. The problem persists.
Comment 10 Vincent van Adrighem 2011-04-15 13:31:49 UTC
The plot thickens...

So, Debian has the bug, Ubuntu has the bug. But Opensuse (11.4) works okay. Just did a check. It works like a charm and uses Evolution 2.32.
Default Opensuse Gnome install.
Comment 11 Henk 2011-04-22 14:04:24 UTC
Adding the following two lines to /etc/services solves the problem:
groupwise 1677/tcp
groupwise 1677/udp
Comment 12 Vincent van Adrighem 2011-04-28 17:03:54 UTC
Ehm...but this is a setting in evolution itself. Why would it need this?
Comment 13 Jeffrey Stedfast 2011-04-28 18:36:47 UTC
Evolution should fall back to using the numeric values for the "groupwise" protocol (as it should with all protocols)
Comment 14 André Klapper 2013-07-23 14:38:21 UTC
evolution-groupwise provides connectivity to Novell Groupwise servers. The last stable release of evolution-groupwise was 3.4.2 which took place a year ago.

evolution-groupwise is not under active development anymore.

It is currently unlikely that there will be any further active development.

Closing this report as WONTFIX as part of Bugzilla Housekeeping.

Please feel free to reopen this bug report in the future if anyone takes the responsibility for active development again.