headers
Sam Varshavchik | 1 Jul 2002 01:07
Gravatar

Re: ident lookup

Robert Penz writes: 

> Hi! 
> 
> How can I disable the ident lookup? I know that there is an command line 
> option for couriertcpd, but where can I set that?

The esmtpd configuration file. 

> and if I change a non config file (e.g. a script) it will get lost at the next 
> update of the deb or rpm files (I've servers running on debian and redhat)

Yes.  Which is why you should only change the configuration files. 

--

-- 
Sam 

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
courier-users mailing list
courier-users <at> lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Permalink | Reply | 0 comments |
headers
Administrator | 1 Jul 2002 02:26
Favicon

Re: imapd: /usr/lib/courier-imap/bin/imapd: Permission denied

Ok, this is a debian system and courier is attempting to authenticate against vpopmail.  I don't really know
much more then that right now.  A friend took a look at it and said that it looks like there could be a problem
with the zlib, but was unable to elaborate more then that.  Any suggestions are greatly appreciated.

Thank you.

Michael

----- Original Message ----- 
From: "John Runnels" <jrunnels <at> piglet.networkcloud.com>
To: "Administrator" <lists <at> digitalplace.org>
Cc: <courier-users <at> lists.sourceforge.net>
Sent: Sunday, June 30, 2002 6:09 PM
Subject: Re: [courier-users] imapd: /usr/lib/courier-imap/bin/imapd: Permission denied


> it would help if you give a little info on your config. there are around 20000 reasons you would be getting
that error without any details.
> 
> 
> John
> "Administrator" <lists <at> digitalplace.org> wrote ..
> > I am getting this error and do not know what is wrong.  I have hit a dead
> > end and would really appreciate an answer:
> > 
> > Jun 30 14:08:05 posiedon imapd: /usr/lib/courier-imap/bin/imapd: Permission
> > denied
> > 
> > I am unable to log into my mail server with this error.  This is a new
> > installation on this box, but I do have courier running successfully on
(Continue reading)

Permalink | Reply | 1 comment |
headers
Daniel Higgins | 1 Jul 2002 05:15

Re: imapd: /usr/lib/courier-imap/bin/imapd: Permission denied

i'm not sure how you friend came to the conclusion that courier trying to
auth against vpopmail would have ANY relation to zlib, but he`s totally out
of whack.

look in the config files authdaemond and esmtpd, all the auth modules are
there, remove vpopmail from it

----- Original Message -----
From: "Administrator" <lists <at> digitalplace.org>
To: <courier-users <at> lists.sourceforge.net>
Sent: Sunday, June 30, 2002 8:26 PM
Subject: Re: [courier-users] imapd: /usr/lib/courier-imap/bin/imapd:
Permission denied

> Ok, this is a debian system and courier is attempting to authenticate
against vpopmail.  I don't really know much more then that right now.  A
friend took a look at it and said that it looks like there could be a
problem with the zlib, but was unable to elaborate more then that.  Any
suggestions are greatly appreciated.
>
> Thank you.
>
> Michael
>
> ----- Original Message -----
> From: "John Runnels" <jrunnels <at> piglet.networkcloud.com>
> To: "Administrator" <lists <at> digitalplace.org>
> Cc: <courier-users <at> lists.sourceforge.net>
> Sent: Sunday, June 30, 2002 6:09 PM
> Subject: Re: [courier-users] imapd: /usr/lib/courier-imap/bin/imapd:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Joshua E Warchol | 1 Jul 2002 05:35

Re: Courier 0.39.1, Courier-IMAP 1.5.1

Sam,

Thanks for coming out with a fixed version so quickly, very nice work.

I've upgraded my custom RPM to 1.5.1 and now I am not getting an
authentication error. If you recall my previous problem with authldap
in 1.5.0, authldap was not connecting to my ldap server. Well, your
change fixed this and it now seems to do lookups successfully. 

But here is the kicker. After doing the lookup, it just closes the
connection. No error, no log message. This used to happen when the
maildir didn't exist, but in later versions courier-imap outpust a
good error in that case. 

So I'm a little stumped (suprise suprise). Could this still have
something to do with LDAP_MAILROOT? In my setup I set LDAP_HOMEDIR to
a base (/mnt/mail, NFS mounted user mailbox volume), and set 
LDAP_MAILDIR to the remainder of their path. LDAP_MAILROOT is still
commented out. 

Thanks again. I look forward to figuring this out.

On Thu, Jun 27, 2002 at 09:55:57AM -0400, Sam Varshavchik wrote:
> These Courier builds fix the broken authldap module in 0.39/1.5.  Don't 
> bother unless you're using authldap.  As an alternative, apply the 
> following patch: 
> 
> http://www.courier-mta.org/beta/patches/authldaplib-fix/authldap.patch.txt 
> 
>
(Continue reading)

Permalink | Reply | 6 comments |
headers
John Runnels | 1 Jul 2002 05:46

Re: imapd: /usr/lib/courier-imap/bin/imapd: Permission denied

help me here daniel but if he removes vpopmail from the authdaemond won't that remove his ability to use it ???

just curious.

John
"Daniel Higgins" <dhiggins <at> netc.net> wrote ..
> i'm not sure how you friend came to the conclusion that courier trying
> to
> auth against vpopmail would have ANY relation to zlib, but he`s totally
> out
> of whack.
> 
> look in the config files authdaemond and esmtpd, all the auth modules are
> there, remove vpopmail from it
> 
> ----- Original Message -----
> From: "Administrator" <lists <at> digitalplace.org>
> To: <courier-users <at> lists.sourceforge.net>
> Sent: Sunday, June 30, 2002 8:26 PM
> Subject: Re: [courier-users] imapd: /usr/lib/courier-imap/bin/imapd:
> Permission denied
> 
> 
> > Ok, this is a debian system and courier is attempting to authenticate
> against vpopmail.  I don't really know much more then that right now. 
> A
> friend took a look at it and said that it looks like there could be a
> problem with the zlib, but was unable to elaborate more then that.  Any
> suggestions are greatly appreciated.
> >
(Continue reading)

Permalink | Reply | 1 comment |
headers
Daniel Higgins | 1 Jul 2002 06:06

Re: imapd: /usr/lib/courier-imap/bin/imapd: Permission denied

yes of course, i just assumed he doesnt use vpopmail as an auth method :P

else it`s just misconfigured

----- Original Message -----
From: "John Runnels" <jrunnels <at> piglet.networkcloud.com>
To: "Daniel Higgins" <dhiggins <at> netc.net>
Cc: "Administrator" <lists <at> digitalplace.org>;
<courier-users <at> lists.sourceforge.net>
Sent: Sunday, June 30, 2002 11:46 PM
Subject: Re: [courier-users] imapd: /usr/lib/courier-imap/bin/imapd:
Permission denied

help me here daniel but if he removes vpopmail from the authdaemond won't
that remove his ability to use it ???

just curious.

John
"Daniel Higgins" <dhiggins <at> netc.net> wrote ..
> i'm not sure how you friend came to the conclusion that courier trying
> to
> auth against vpopmail would have ANY relation to zlib, but he`s totally
> out
> of whack.
>
> look in the config files authdaemond and esmtpd, all the auth modules are
> there, remove vpopmail from it
>
> ----- Original Message -----
(Continue reading)

Permalink | Reply | 0 comments |
headers
Sam Varshavchik | 1 Jul 2002 07:00
Gravatar

Re: Courier 0.39.1, Courier-IMAP 1.5.1

Joshua E Warchol writes: 

> But here is the kicker. After doing the lookup, it just closes the
> connection. No error, no log message. This used to happen when the

Well, that's what should happen with authldap: it binds, looks up the 
account, disconnects. 

> So I'm a little stumped (suprise suprise). Could this still have
> something to do with LDAP_MAILROOT? In my setup I set LDAP_HOMEDIR to

No. 

--

-- 
Sam 

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
courier-users mailing list
courier-users <at> lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Permalink | Reply | 5 comments |
headers
Joshua E Warchol | 1 Jul 2002 07:11

Re: Re: Courier 0.39.1, Courier-IMAP 1.5.1

I may have not been clear. After authldap does the lookup, pop3d
disconnects the session from the user. I didn't mean to say that
authldap disconnects from the LDAP server, of course it does that.

After the lookup is done, pop3d exits without giving an error. What
is an effective process for troubleshooting this? The same LDAP 
setup is used on my 1.4.5 systems and works perfectly. It only seems
reasonable that something changed with 1.5.0(1). 

Does authldap or pop3d report why it exists? I don't mean to badger
you over this, but without a logged error message, troubleshooting
becomes a black art. 

Thanks for your help Sam. I hope you've got an idea or two left that
might help move this troubleshooting forward. 

On Mon, Jul 01, 2002 at 01:00:08AM -0400, Sam Varshavchik wrote:
> Joshua E Warchol writes: 
> 
> 
> >But here is the kicker. After doing the lookup, it just closes the
> >connection. No error, no log message. This used to happen when the
> 
> Well, that's what should happen with authldap: it binds, looks up the 
> account, disconnects. 
> 
> >So I'm a little stumped (suprise suprise). Could this still have
> >something to do with LDAP_MAILROOT? In my setup I set LDAP_HOMEDIR to
> 
> No.
(Continue reading)

Permalink | Reply | 4 comments |
headers
Sam Varshavchik | 1 Jul 2002 07:18
Gravatar

Re: Courier 0.39.1, Courier-IMAP 1.5.1

Joshua E Warchol writes: 

> I may have not been clear. After authldap does the lookup, pop3d
> disconnects the session from the user. I didn't mean to say that
> authldap disconnects from the LDAP server, of course it does that. 
> 
> After the lookup is done, pop3d exits without giving an error. What
> is an effective process for troubleshooting this? The same LDAP 
> setup is used on my 1.4.5 systems and works perfectly. It only seems
> reasonable that something changed with 1.5.0(1).  
> 
> Does authldap or pop3d report why it exists? I don't mean to badger
> you over this, but without a logged error message, troubleshooting
> becomes a black art. 

The only thing that comes to mind is that pop3 now checks the sticky bit on 
the home directory and exits, like IMAP.  A message is logged both to syslog 
and to the mail client if that's the case, though. 

--

-- 
Sam 

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
courier-users mailing list
courier-users <at> lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
(Continue reading)

Permalink | Reply | 3 comments |
headers
Joshua E Warchol | 1 Jul 2002 07:34

Re: Re: Courier 0.39.1, Courier-IMAP 1.5.1

I'm pretty sure all the permissions are proper. Nothing appears
to have the sticky bit set. And nothing is being logged, so that
probably isn't it. Hmm. 

It definately seems to be after authentication, since I get an error
(password error) if I put in the WRONG password. I've installed 1.4.5 
on the same server, same ldap, same mailboxes and it works. I've
cross checked the authldaprc files and they are set exactly the
same (except for a few new items that I have not touched, such as
email maps, etc). 

I'm going to try building a completely stock courier-imap rpm, installing
that and then configuring it in place (since part of my custom RPM
is a patch for default config changes). I'll post how that goes.

Thanks, and if you have any other ideas, let me know and I'll give
them a shot.

On Mon, Jul 01, 2002 at 01:18:40AM -0400, Sam Varshavchik wrote:
> Joshua E Warchol writes: 
> 
> >I may have not been clear. After authldap does the lookup, pop3d
> >disconnects the session from the user. I didn't mean to say that
> >authldap disconnects from the LDAP server, of course it does that. 
> >
> >After the lookup is done, pop3d exits without giving an error. What
> >is an effective process for troubleshooting this? The same LDAP 
> >setup is used on my 1.4.5 systems and works perfectly. It only seems
> >reasonable that something changed with 1.5.0(1).  
> >
(Continue reading)

Permalink | Reply | 2 comments |

Gmane