thanks for the pointer, i found the problem. if the new DEBUG_LOGIN_ENV
variable is not present, one cannot connect to imap or pop3 (doesn't have
anything to do with the toolchain update after all). after i added the
variable, everything was right again (maybe i might suggest a less radical
default behaviour).
i looked up the function in authlib/debug.c:
void auth_debug_login_init( void )
{
const char *p=getenv(DEBUG_LOGIN_ENV);
auth_debug_login_level = atoi( p ? p:0 );
}
and wondered if atoi does return zero here when p == NULL?
thanks again
alex
----- Original Message -----
From: "Sam Varshavchik" <mrs...@courier-mta.com>
To: <cour...@lists.sourceforge.net>
Sent: Wednesday, October 16, 2002 12:11 AM
Subject: [courier-users] Re: cannot connect to any port ...
Alexander Gretha writes:
for all i can tell that looks pretty normal (i mean it looks like before
the
upgrade). any suggestions to track the problem down?
You can begin by explaining how you concluded that you cannot connect to
any
non-SSL daemons.