Re: [Dovecot] Dovecot config

[Timo Sirainen]

On Apr 4, 2008, at 7:27 AM, Dien Phan wrote:
We are using a web mail software that allows users to login either  
as us 'abc' or '[EMAIL PROTECTED]'. The problem is: when a user logs in as  
'abc' (without domain part) dovecots creates a directory /var/ 
MailRoot/domains/abc and check mail there (as I understand because  
%d is blank).
My question is how to config dovecot so it automatically add default  
domain %d is blank.


auth_default_realm = domain



PGP.sig
Description: This is a digitally signed message part

Re: [Dovecot] LDAP auth_bind hangs and times out

[Timo Sirainen]

On Apr 4, 2008, at 12:50 AM, Jack McKinney wrote:

Hmmm... what versions of OpenLDAP and Dovecot are you using?


A lot of people have them working with different LDAP versions. I've  
Debian unstable's OpenLDAP 2.1.30.dfsg-13.5.



I note
that you got a result of "uid(user)=foo", from which I guess that you
had pass_attrs set to user=uid or some such.
I tried adding a pass_attrs of user=mail, in case the problem is that
without requested fields, the code in dovecot doesn't return anything.
It didn't work; it still hangs and times out after 3 minutes.


Check with wireshark if it shows that LDAP server really sends the  
reply. Then you could find out if it's a problem on the OpenLDAP  
client side or server/network side.




PGP.sig
Description: This is a digitally signed message part

Re: [Dovecot] mail_chroot problems / dovecot 1.1rc4

[Timo Sirainen]

On Apr 3, 2008, at 11:33 AM, Michal Soltys wrote:

dovecot will try to chroot into /home/home/admin with the following  
message in logs, in my case:


Fatal: chdir(/home/home/admin) failed with uid 1999: No such file or
directory

The same happens if I use per-user chroot= option in userdb, f.e. in  
passwd-file


Right. If you use mail_chroot or chroot, the home directory points  
under the chroot. I guess it might be also useful for it not to do  
that, but I can't change that without breaking backwards  
compatibility, and I'm not sure if it's worth it to add yet another  
setting just for that.




PGP.sig
Description: This is a digitally signed message part

Re: [Dovecot] shared Sent and Junk folders {Scanned}

[Tolga]

Scott Silva wrote:

on 4-2-2008 11:51 PM Tolga spake the following:

Scott Silva wrote:
  

on 4-2-2008 4:01 AM Tolga spake the following:


Charles Marcus wrote:
  

On 4/2/2008 3:38 AM, Tolga wrote:


For some odd reason, two of my users share the same Sent and Junk
folders, therefore I keep getting errors about Sent folder reading
permissions and one user reading the other user's Junk folder. What
can I do about this odd problem?
  

Do you really think anyone can even guess what might cause something
like this based on the information given?

How about some hints, like:

dovecot version, platform, output of dovecot -n, and maybe even -
gasp - some log entries given when these users are experiencing the
problem...


Dovecot version is 1.0.7, on Linux gentoo, below is dovecot -n

log_path: /var/log/dovecot.log
info_log_path: /var/log/dovecot.log
listen: [::]
ssl_cert_file: /etc/ssl/dovecot/server.pem
ssl_key_file: /etc/ssl/dovecot/server.key
disable_plaintext_auth: no
login_dir: /var/run/dovecot/login
login_executable: /usr/libexec/dovecot/imap-login
mail_extra_groups: mail
mail_location:
mbox:/var/mail/:INBOX=/var/mail/%u:INDEX=/var/mail/folders/%u
  

Here you need something like mbox:/var/mail/%u/ or mbox:/var/%u/mail/
to keep all the users other mailboxes separate.


I did like you said, and now I get IMAP(tolga): open() failed with
subscription file /var/mail/tolga/.subscriptions: Not a directory. btw,
/var/mail/tolga is a file, but what I want is to have all the other
folders in /var/mail/folders/tolga. Should I modify it like
mbox:/var/mail/folders/%u/ ?

  

That should work.

It indeed work, thanks :)


--

Scott Silva
Network Administrator
San Gabriel Valley Water Company
11142 Garvey Ave. El Monte CA 91733
626.448.6183 x.296
[EMAIL PROTECTED]
  


--
This Message has been scanned for
viruses and dangerous content by
the San Gabriel Valley Water Co.MailScanner 
and is believed to be clean.



--
Stay with *nix :)

Re: [Dovecot] Dovecot config

[Asheesh Laroia]

On Fri, 4 Apr 2008, Dien Phan wrote:

We are using a web mail software that allows users to login either as us 
'abc' or '[EMAIL PROTECTED]'. The problem is: when a user logs in as 'abc' (without 
domain part) dovecots creates a directory /var/MailRoot/domains/abc and check 
mail there (as I understand because %d is blank).
My question is how to config dovecot so it automatically add default domain 
%d is blank.


I don't know off-hand, but I will offer an alternate possibility: It 
should be easy to modify the webmail package to add the suffix you want.


Note that this is not me saying you cannot or should not do this at the 
Dovecot layer; just trying to help how I can.


-- Asheesh.

--
Your happiness is intertwined with your outlook on life.

Re: [Dovecot] Icedove (Thunderbird) crashes when reading IMAP messages

[cam]

>
> A mail client that crashes when reading mail is either broken is
> running on a broken system, and fixes *to what is broken* are the
> right way to prevent that even if there happens to be something odd
> and/or wrong on the server side that is triggering the crash.  This
> is not a Debian testers or Icedove list, so you are likely to not get
> a fix for your problem here.   Even in that case the fix
> would not be in Dovecot.

I have thought so from the beginning, but lacking full knowledge, I wanted
to eliminate as much as I could from consideration.
>
> Dovecot rawlogs come in pairs: the --.in files are
> what the client sent in, the --.out are what the
> server sent out as  response. Each of those pairs of files is from
> one session between the client and the server, and IMAP clients will
> often run multiple sessions in parallel. They also sometimes hold a
> session open in IDLE mode, waiting to be notified by the server of a
> change to a mailbox.

That seems to be the case - once I paired the log statements, it was clear
that the communication between the two was OK.  In fact, Dovecot was in
IDLE mode when Icedove crashed, consistently.

> Many people on this list speak IMAP and could help explain the chat
> between the client and server if you need a deep explanation, but in
> all likelihood the real  use of those logs would be in the bug report
> opened with the Icedove and/or Thunderbird developers. Just the tails
> of a pair of logfiles that are from a session where Icedove crashed
> should be adequate to show what Icedove was asking for and what
> Dovecot was sending back when Icedove crashed, although a clear path
> to *why* it crashed probably isn't in those logs.

Well, they're definitely going to come in handy.  :-)
>
> You haven't mentioned any memory-relevant details about your system,
> but the phrase 'folder is too large for memory' sounds a bit
> suspicious. How many messages would that be?

A couple of thousand.  Actually, the memory thing was a red herring, and I
should not have mentioned it.  My laptop, which I use only when away from
the office, has half a gig.  Squirrelmail tries to read everything into
memory, and there's a point past which it won't go.

> You also mentioned that
> fiddling with the Icedove configuration caused trouble in KDE,
> specifically KMail, and that does not make a lot of sense either
> *unless* you have a deeper problem on your system like simple memory
> starvation.

The KMail problem was solved by careful upgrading - I say "careful"
because it meant avoiding bugs in related software.  It now works fine,
except that it can't cope with sending email either through my ISP or
through Exim.  Another problem to solve.  The ISP is having problems of
its own, with regard to mail.

Anyway, I purged Icedove, installed Tbird from scratch, and though the
crashes no longer occur, I cannot send from it either, so it's back to
Squirrelmail.

Thank you for the insight, and depth of discussion.  At least I know more
than I did 3 hours ago,

Cam


-- 
Cam Ellison, PhD RPsych (BC #01417)
Cam Ellison & Associates Ltd.
3446 Beach Avenue
Roberts Creek BC  V0N 2W2
Phone 604.885.4806
Fax 694.885.4809
Cell 604.989.0635

[Dovecot] Dovecot config

[Dien Phan]

Hi,

I've installed dovecot 1.0.13 on FreeBSD 6.3 RELEASE and now trying to 
configure it. Below is my config file:


$ dovecot -n
# 1.0.13: /usr/local/etc/dovecot.conf
log_path: /var/log/dovecot.log
info_log_path: /var/log/dovecot-info.log
protocols: imap
ssl_disable: yes
disable_plaintext_auth: no
login_dir: /var/run/dovecot/login
login_executable: /usr/local/libexec/dovecot/imap-login
mail_location: maildir:~/Maildir
dotlock_use_excl: yes
maildir_copy_with_hardlinks: yes
mail_plugins: antispam
imap_client_workarounds: delay-newmail outlook-idle netscape-eoh 
tb-extra-mailbox-sep

auth default:
  verbose: yes
  passdb:
driver: checkpassword
args: /var/MailRoot/bin/dovecot_xmail
  userdb:
driver: static
args: uid=vxmail gid=vxmail home=/var/MailRoot/domains/%d/%n 
allow_all_users=yes

  socket:
type: listen
master:
  path: /var/run/dovecot/auth-master
  mode: 384
  user: vxmail
plugin:
  antispam_signature: X-DSPAM-Signature
  antispam_trash: Trash
  antispam_spam: SPAM
  antispam_dspam_binary: /usr/local/bin/dspam
  antispam_dspam_args: --user;%u

We are using a web mail software that allows users to login either as us 
'abc' or '[EMAIL PROTECTED]'. The problem is: when a user logs in as 'abc' 
(without domain part) dovecots creates a directory 
/var/MailRoot/domains/abc and check mail there (as I understand because 
%d is blank).
My question is how to config dovecot so it automatically add default 
domain %d is blank.


Thank you for help.
Dien Phan

Re: [Dovecot] Icedove (Thunderbird) crashes when reading IMAP messages

[Bill Cole]

At 11:18 AM -0700 4/3/08, Cam Ellison wrote:
This is a Debian lenny/sid installation.  Dovecot has been installed 
on it for over a year, with no problems.  Lately (i.e. the past few 
months), if I attempt to read a message, Icedove crashes.  It does 
not do this when I read a message downloaded from the ISP's POP3 
server (not that I do this very often - almost all my mail goes 
through Dovecot).


A mail client that crashes when reading mail is either broken is 
running on a broken system, and fixes *to what is broken* are the 
right way to prevent that even if there happens to be something odd 
and/or wrong on the server side that is triggering the crash.  This 
is not a Debian testers or Icedove list, so you are likely to not get 
a fix for your problem here. It is also not likely that configuring 
Dovecot differently will be able to work around such a crash, as 
Dovecot doesn't seem to notice that anything at all is wrong. However 
evil the data flowing from Dovecot to Icedove might have been, a 
crash would not be a reasonable response, with the possible 
exceptional case of Icedove trying to handle what it got from Dovecot 
and being mistreated by the OS in doing so. Even in that case the fix 
would not be in Dovecot.


That said...

At 4:45 PM -0700 4/3/08, [EMAIL PROTECTED] wrote:

I hate replying to my own emails, but progress is being made.  I now have
rawlogs.  What do I do with them?  How do I make sense of them?


Dovecot rawlogs come in pairs: the --.in files are 
what the client sent in, the --.out are what the 
server sent out as  response. Each of those pairs of files is from 
one session between the client and the server, and IMAP clients will 
often run multiple sessions in parallel. They also sometimes hold a 
session open in IDLE mode, waiting to be notified by the server of a 
change to a mailbox.


Many people on this list speak IMAP and could help explain the chat 
between the client and server if you need a deep explanation, but in 
all likelihood the real  use of those logs would be in the bug report 
opened with the Icedove and/or Thunderbird developers. Just the tails 
of a pair of logfiles that are from a session where Icedove crashed 
should be adequate to show what Icedove was asking for and what 
Dovecot was sending back when Icedove crashed, although a clear path 
to *why* it crashed probably isn't in those logs.




I have more or less reverted to the original setup with icedove, but it
now crashes more readily than before.  I think it's important to note that
the only problem I have with squirrelmail, which I'm now using, and which
accesses dovecot only, is when a folder is too large for memory.  No
crashes, no mis-filing, no problems basically.


You haven't mentioned any memory-relevant details about your system, 
but the phrase 'folder is too large for memory' sounds a bit 
suspicious. How many messages would that be? You also mentioned that 
fiddling with the Icedove configuration caused trouble in KDE, 
specifically KMail, and that does not make a lot of sense either 
*unless* you have a deeper problem on your system like simple memory 
starvation. That could be enough to cause the crash with a segfault 
under the right sort of stress. Maybe I missed you saying otherwise, 
but it sounds like you are running Dovecot on the same machine that 
you are using Icedove on, and that might be adequate to spike memory 
demand for both at the same time and hence for the system as a whole. 
If you are running the whole system tight on memory, that sort of 
simultaneous spike could mean that one of the processes demanding 
more won't be able to get it, and sometimes that will trigger a 
segfault. You may simply be asking this machine to do more than it 
can, although  you'd have to look at the memory/swap configuration 
and usage to know for sure. Since you are running an unstable/test OS 
distribution, it would also not be particularly shocking if something 
on that system had a memory leak that is the real root cause.



--
Bill Cole  
[EMAIL PROTECTED]

Re: [Dovecot] Icedove (Thunderbird) crashes when reading IMAP messages

[Asheesh Laroia]

On Thu, 3 Apr 2008, [EMAIL PROTECTED] wrote:

I hate replying to my own emails, but progress is being made.  I now 
have rawlogs.  What do I do with them?  How do I make sense of them?


Well, they're transcripts of what Dovecot said to Icedove and vice versa. 
Is there some pattern?  Maybe Dovecot sends Icedove a message called "YOU 
WEASEL" and Icedove crashes in response.


But truth be told, I think that this is unrelated to Dovecot.

I have more or less reverted to the original setup with icedove, but it 
now crashes more readily than before.  I think it's important to note 
that the only problem I have with squirrelmail, which I'm now using, and 
which accesses dovecot only, is when a folder is too large for memory. 
No crashes, no mis-filing, no problems basically.


Can you try adding a new user to your system, and then running Icedove 
with this configuration?


I know it looks like I'm grasping at straws here, but I vaguely remember 
similar Icedove issues and them seeming very strange.  (And what version 
of Icedove?  "dpkg -l icedove" should say.)


-- Asheesh.

--
Will Rogers never met you.

Re: [Dovecot] Icedove (Thunderbird) crashes when reading IMAP messages

[cam]

I hate replying to my own emails, but progress is being made.  I now have
rawlogs.  What do I do with them?  How do I make sense of them?

I have more or less reverted to the original setup with icedove, but it
now crashes more readily than before.  I think it's important to note that
the only problem I have with squirrelmail, which I'm now using, and which
accesses dovecot only, is when a folder is too large for memory.  No
crashes, no mis-filing, no problems basically.

Cheers

Cam


-- 
Cam Ellison, PhD RPsych (BC #01417)
Cam Ellison & Associates Ltd.
3446 Beach Avenue
Roberts Creek BC  V0N 2W2
Phone 604.885.4806
Fax 694.885.4809
Cell 604.989.0635

Re: [Dovecot] Strange dmesg messages

[Uldis Pakuls]

Raphael Bittencourt S. Costa wrote:

I moved the maildir location from Hitachi's storage to local sas disk
and got the same erro using imaptest. Debug doesn't show any usable
information. :-(

Any ideas? 

  
To trace your problem you need to debug kernel... as it is kernel level 
crash.

Try ask for help in kernel.org  newsgroups.

from your logs:
Pid: 24319, comm: imap Tainted: P U 2.6.16.21-0.8-smp #1

this line means - kernel is "tainted": 
P - A module with a Proprietary license has been loaded

U - An Unsupported module has been loaded, i.e. a module which is not supported 
by Novell (SuSE specific flag)

[ see: 
https://secure-support.novell.com/KanisaPlatform/Publishing/250/3582750_f.SAL_Public.html
 ]

Try unload propertary and unsupported modules ; then run imaptest again.

Re: [Dovecot] Icedove (Thunderbird) crashes when reading IMAP messages

[cam]

> Have you tried creating a new account with the same settings as the normal
> Dovecot account?  Maybe Icedove/Thunderbird has corrupted some local data.

I moved the entire directory out of mozilla-thunderbird, deleted the
account, and then created a new one.  Performance is now even worse. 
There are few things that I can do without triggering a crash.  At the
moment I'm using Squirrelmail, since there's something wrong with KDE:
KMail now fails to start.

> If it persists, then get a raw log from Dovecot and let's see what has to
> be done from there.

Let's do that.  I need a pointer or two.  I assume that protocols = imap
is equivalent to protocol { ...imap }.  Is this correct?  I shall try it
and see what happens, but I don't want to make things worse.

Thanks

Cam




-- 
Cam Ellison, PhD RPsych (BC #01417)
Cam Ellison & Associates Ltd.
3446 Beach Avenue
Roberts Creek BC  V0N 2W2
Phone 604.885.4806
Fax 694.885.4809
Cell 604.989.0635

Re: [Dovecot] Strange dmesg messages

[Raphael Bittencourt S. Costa]

That is true, it was a considence. I got an error after that. Now I'm
lost. :-|
What more tests can I do to know where the problem is? I want do more
tests before recompile dovecot with --with-notify.


On Thu, 2008-04-03 at 23:41 +0300, Timo Sirainen wrote:

> On Thu, 2008-04-03 at 16:55 -0300, Raphael Bittencourt S. Costa wrote:
> > The erro stops when I uncomment 
> > 
> > mail_max_userip_connections = 10
> > 
> > does it make any sence?
> 
> The default is 10, so commenting or uncommenting it should make no
> difference at all.

Re: [Dovecot] LDAP auth_bind hangs and times out

[Jack McKinney]

Hmmm... what versions of OpenLDAP and Dovecot are you using? I note
that you got a result of "uid(user)=foo", from which I guess that you
had pass_attrs set to user=uid or some such.
I tried adding a pass_attrs of user=mail, in case the problem is that
without requested fields, the code in dovecot doesn't return anything.
It didn't work; it still hangs and times out after 3 minutes.

On Fri, 2008-04-04 at 00:11 +0300, Timo Sirainen wrote:
> No, I mean this appears to be a bug somewhere since a LDAP request is  
> sent, but it's never received by Dovecot. So either Dovecot does  
> something wrong, OpenLDAP library does something wrong or your network  
> blocks the reply for some reason. For example on my system:
> 
> auth(default): ldap(foo,127.0.0.1): bind search: base=...
> auth(default): ldap(foo,127.0.0.1): result: uid(user)=foo
> 
> If Dovecot receives a reply to the "bind search", it logs the "result"  
> line, which your logs show is missing.
> 
> On Apr 4, 2008, at 12:06 AM, Jack McKinney wrote:
> > I am not sure that I understand you, here. Are you saying that I am
> > missing something from my configuration after the "filter=" line  
> > like a
> > pass_attrs listing fields to return?  I do not have one, as there  
> > are no
> > fields that I need returned.  The only thing that dovecot needs is the
> > DN of the match itself.
> >
> > According to http://wiki.dovecot.org/AuthDatabase/LDAP ,
> >
> > "The pass_filter is used to find the LDAP entry, and the DN is taken
> > from the reply."
> >
> > Should I add a dummy pass_attrs entry?  What field is safe to grab?
> > E.g., I do not want to overwrite "user"...
> >
> > On Thu, 2008-04-03 at 23:59 +0300, Timo Sirainen wrote:
> >> On Thu, 2008-04-03 at 09:46 -0500, Jack McKinney wrote:
> >>
> >>> ldap([EMAIL PROTECTED],y.y.y.y): bind search: base=ou=users,
> >>> dc=lorentz,dc=com
> >>> filter=(&(objectClass=inetOrgPerson)([EMAIL PROTECTED]))
> >>
> >> Here should be a line saying "result: ". Since there
> >> isn't, Dovecot never appears to receive the reply. You could verify  
> >> this
> >> by adding to src/auth/db-ldap.c ldap_input() around line 372:
> >>
> >>msgid = ldap_msgid(res);
> >> // added line:
> >>i_info("LDAP: Received reply %d", msgid);
> >>
> >> msgid might be the same as this tag:
> >>
> >>> Apr  3 08:13:30 fourier slapd[14039]: conn=7 op=3 SEARCH RESULT  
> >>> tag=101
> >>
> >> But I'm not sure. If you anyway receive a reply after the "bind  
> >> search",
> >> there's something wrong in Dovecot's error handling.
> >>
> > -- 
> > Jack McKinney
> > GPG 1024D/99C6A174
> > [EMAIL PROTECTED] YM:lfaatsnat2006 AIM:jackmclorentz
> > "There is no parameter that makes it impossible for you to perform  
> > still
> > more excellently."
> >   -Mario Cuomo, on the lack of a clock in baseball
> 
-- 
Jack McKinney
GPG 1024D/99C6A174
[EMAIL PROTECTED] YM:lfaatsnat2006 AIM:jackmclorentz
"There is no parameter that makes it impossible for you to perform still
more excellently."
   -Mario Cuomo, on the lack of a clock in baseball


signature.asc
Description: This is a digitally signed message part

Re: [Dovecot] LDAP auth_bind hangs and times out

[Jack McKinney]

I added the i_info line below and copied over the new dovecot-auth. It
is hanging at the same place; the "LDAP: Received reply" line is not in
the log.  Again, exactly 180 seconds after the last log entry, the
connection drops.  However, that line _does_ appear in the log back at
startup...

Apr  3 15:19:05 fourier dovecot: Dovecot v1.0.12 starting up
Apr  3 15:19:05 fourier dovecot: auth(default): LDAP: Received reply 1
Apr  3 15:19:06 fourier dovecot: auth(default): new auth connection:
pid=30934
Apr  3 15:19:06 fourier dovecot: auth(default): new auth connection:
pid=30935
Apr  3 15:19:06 fourier dovecot: auth(default): new auth connection:
pid=30936
Apr  3 15:19:21 fourier dovecot: auth(default): new auth connection:
pid=30974
Apr  3 15:19:28 fourier dovecot: auth(default): client in:
AUTH^I1^IPLAIN^Iservice=IMAP^Isecured^Ilip=x.x.x.x^Irip=y.y.y.y^Iresp=
Apr  3 15:19:28 fourier dovecot: auth(default):
ldap([EMAIL PROTECTED],y.y.y.y): bind search: base=ou=users,
dc=lorentz,dc=com
filter=(&(objectClass=inetOrgPerson)([EMAIL PROTECTED]))
Apr  3 15:22:28 fourier dovecot: imap-login: Disconnected: Inactivity:
method=PLAIN, rip=y.y.y.y, lip=x.x.x.x, TLS



On Fri, 2008-04-04 at 00:11 +0300, Timo Sirainen wrote:
> No, I mean this appears to be a bug somewhere since a LDAP request is  
> sent, but it's never received by Dovecot. So either Dovecot does  
> something wrong, OpenLDAP library does something wrong or your network  
> blocks the reply for some reason. For example on my system:
> 
> auth(default): ldap(foo,127.0.0.1): bind search: base=...
> auth(default): ldap(foo,127.0.0.1): result: uid(user)=foo
> 
> If Dovecot receives a reply to the "bind search", it logs the "result"  
> line, which your logs show is missing.
> 
> On Apr 4, 2008, at 12:06 AM, Jack McKinney wrote:
> > I am not sure that I understand you, here. Are you saying that I am
> > missing something from my configuration after the "filter=" line  
> > like a
> > pass_attrs listing fields to return?  I do not have one, as there  
> > are no
> > fields that I need returned.  The only thing that dovecot needs is the
> > DN of the match itself.
> >
> > According to http://wiki.dovecot.org/AuthDatabase/LDAP ,
> >
> > "The pass_filter is used to find the LDAP entry, and the DN is taken
> > from the reply."
> >
> > Should I add a dummy pass_attrs entry?  What field is safe to grab?
> > E.g., I do not want to overwrite "user"...
> >
> > On Thu, 2008-04-03 at 23:59 +0300, Timo Sirainen wrote:
> >> On Thu, 2008-04-03 at 09:46 -0500, Jack McKinney wrote:
> >>
> >>> ldap([EMAIL PROTECTED],y.y.y.y): bind search: base=ou=users,
> >>> dc=lorentz,dc=com
> >>> filter=(&(objectClass=inetOrgPerson)([EMAIL PROTECTED]))
> >>
> >> Here should be a line saying "result: ". Since there
> >> isn't, Dovecot never appears to receive the reply. You could verify  
> >> this
> >> by adding to src/auth/db-ldap.c ldap_input() around line 372:
> >>
> >>msgid = ldap_msgid(res);
> >> // added line:
> >>i_info("LDAP: Received reply %d", msgid);
> >>
> >> msgid might be the same as this tag:
> >>
> >>> Apr  3 08:13:30 fourier slapd[14039]: conn=7 op=3 SEARCH RESULT  
> >>> tag=101
> >>
> >> But I'm not sure. If you anyway receive a reply after the "bind  
> >> search",
> >> there's something wrong in Dovecot's error handling.
> >>
> > -- 
> > Jack McKinney
> > GPG 1024D/99C6A174
> > [EMAIL PROTECTED] YM:lfaatsnat2006 AIM:jackmclorentz
> > "There is no parameter that makes it impossible for you to perform  
> > still
> > more excellently."
> >   -Mario Cuomo, on the lack of a clock in baseball
> 
-- 
Jack McKinney
GPG 1024D/99C6A174
[EMAIL PROTECTED] YM:lfaatsnat2006 AIM:jackmclorentz
"There is no parameter that makes it impossible for you to perform still
more excellently."
   -Mario Cuomo, on the lack of a clock in baseball


signature.asc
Description: This is a digitally signed message part

Re: [Dovecot] LDAP auth_bind hangs and times out

[Timo Sirainen]

No, I mean this appears to be a bug somewhere since a LDAP request is  
sent, but it's never received by Dovecot. So either Dovecot does  
something wrong, OpenLDAP library does something wrong or your network  
blocks the reply for some reason. For example on my system:


auth(default): ldap(foo,127.0.0.1): bind search: base=...
auth(default): ldap(foo,127.0.0.1): result: uid(user)=foo

If Dovecot receives a reply to the "bind search", it logs the "result"  
line, which your logs show is missing.


On Apr 4, 2008, at 12:06 AM, Jack McKinney wrote:

I am not sure that I understand you, here. Are you saying that I am
missing something from my configuration after the "filter=" line  
like a
pass_attrs listing fields to return?  I do not have one, as there  
are no

fields that I need returned.  The only thing that dovecot needs is the
DN of the match itself.

According to http://wiki.dovecot.org/AuthDatabase/LDAP ,

"The pass_filter is used to find the LDAP entry, and the DN is taken
from the reply."

Should I add a dummy pass_attrs entry?  What field is safe to grab?
E.g., I do not want to overwrite "user"...

On Thu, 2008-04-03 at 23:59 +0300, Timo Sirainen wrote:

On Thu, 2008-04-03 at 09:46 -0500, Jack McKinney wrote:


ldap([EMAIL PROTECTED],y.y.y.y): bind search: base=ou=users,
dc=lorentz,dc=com
filter=(&(objectClass=inetOrgPerson)([EMAIL PROTECTED]))


Here should be a line saying "result: ". Since there
isn't, Dovecot never appears to receive the reply. You could verify  
this

by adding to src/auth/db-ldap.c ldap_input() around line 372:

msgid = ldap_msgid(res);
// added line:
i_info("LDAP: Received reply %d", msgid);

msgid might be the same as this tag:

Apr  3 08:13:30 fourier slapd[14039]: conn=7 op=3 SEARCH RESULT  
tag=101


But I'm not sure. If you anyway receive a reply after the "bind  
search",

there's something wrong in Dovecot's error handling.


--
Jack McKinney
GPG 1024D/99C6A174
[EMAIL PROTECTED] YM:lfaatsnat2006 AIM:jackmclorentz
"There is no parameter that makes it impossible for you to perform  
still

more excellently."
  -Mario Cuomo, on the lack of a clock in baseball




PGP.sig
Description: This is a digitally signed message part

Re: [Dovecot] LDAP auth_bind hangs and times out

[Jack McKinney]

I am not sure that I understand you, here. Are you saying that I am
missing something from my configuration after the "filter=" line like a
pass_attrs listing fields to return?  I do not have one, as there are no
fields that I need returned.  The only thing that dovecot needs is the
DN of the match itself.

According to http://wiki.dovecot.org/AuthDatabase/LDAP ,

"The pass_filter is used to find the LDAP entry, and the DN is taken
from the reply."

Should I add a dummy pass_attrs entry?  What field is safe to grab?
E.g., I do not want to overwrite "user"...

On Thu, 2008-04-03 at 23:59 +0300, Timo Sirainen wrote:
> On Thu, 2008-04-03 at 09:46 -0500, Jack McKinney wrote:
> 
> > ldap([EMAIL PROTECTED],y.y.y.y): bind search: base=ou=users,
> > dc=lorentz,dc=com
> > filter=(&(objectClass=inetOrgPerson)([EMAIL PROTECTED]))
> 
> Here should be a line saying "result: ". Since there
> isn't, Dovecot never appears to receive the reply. You could verify this
> by adding to src/auth/db-ldap.c ldap_input() around line 372:
> 
>   msgid = ldap_msgid(res);
> // added line:
>   i_info("LDAP: Received reply %d", msgid);
> 
> msgid might be the same as this tag:
> 
> > Apr  3 08:13:30 fourier slapd[14039]: conn=7 op=3 SEARCH RESULT tag=101
> 
> But I'm not sure. If you anyway receive a reply after the "bind search",
> there's something wrong in Dovecot's error handling.
> 
-- 
Jack McKinney
GPG 1024D/99C6A174
[EMAIL PROTECTED] YM:lfaatsnat2006 AIM:jackmclorentz
"There is no parameter that makes it impossible for you to perform still
more excellently."
   -Mario Cuomo, on the lack of a clock in baseball


signature.asc
Description: This is a digitally signed message part

Re: [Dovecot] LDAP auth_bind hangs and times out

[Timo Sirainen]

On Thu, 2008-04-03 at 09:46 -0500, Jack McKinney wrote:

> ldap([EMAIL PROTECTED],y.y.y.y): bind search: base=ou=users,
> dc=lorentz,dc=com
> filter=(&(objectClass=inetOrgPerson)([EMAIL PROTECTED]))

Here should be a line saying "result: ". Since there
isn't, Dovecot never appears to receive the reply. You could verify this
by adding to src/auth/db-ldap.c ldap_input() around line 372:

msgid = ldap_msgid(res);
// added line:
i_info("LDAP: Received reply %d", msgid);

msgid might be the same as this tag:

> Apr  3 08:13:30 fourier slapd[14039]: conn=7 op=3 SEARCH RESULT tag=101

But I'm not sure. If you anyway receive a reply after the "bind search",
there's something wrong in Dovecot's error handling.



signature.asc
Description: This is a digitally signed message part

Re: [Dovecot] Icedove (Thunderbird) crashes when reading IMAP messages

[Cam Ellison]

Charles Marcus wrote:

On 4/3/2008, Cam Ellison ([EMAIL PROTECTED]) wrote:

Dovecot has been installed on it for over a year, with no problems.


What version?


1.0.13

I think it's some weird communication thing between icedove and dovecot. 
 Valgrind (memcheck) gives me this:


/usr/lib/icedove/run-mozilla.sh: line 131: 18624 Segmentation fault 
 "$prog" ${1+"$@"}


The relevant parts of the dovecot log are:

dovecot: Apr 03 13:46:25 Info: auth(default): new auth connection: pid=18723
dovecot: Apr 03 13:46:26 Info: auth(default): client in: AUTH   1 
PLAIN   service=IMAPsecured lip=24.207.104.15   rip=24.207.104.15

dovecot: Apr 03 13:46:26 Info: auth(default): client out: CONT  1
dovecot: Apr 03 13:46:26 Info: auth(default): client in: CONT
dovecot: Apr 03 13:46:26 Info: auth(default): pam(cam,24.207.104.15): 
lookup service=dovecot
dovecot: Apr 03 13:46:26 Info: auth(default): client out: OK1 
user=cam
dovecot: Apr 03 13:46:26 Info: auth(default): master in: REQUEST 
51  18653   1
dovecot: Apr 03 13:46:26 Info: auth(default): passwd(cam,24.207.104.15): 
lookup
dovecot: Apr 03 13:46:26 Info: auth(default): master out: USER  51 
cam system_user=cam uid=1000gid=1000home=/home/cam
dovecot: Apr 03 13:46:26 Info: imap-login: Login: user=, 
method=PLAIN, rip=24.207.104.15, lip=24.207.104.15, secured
dovecot: Apr 03 13:46:26 Info: IMAP(cam): Effective uid=1000, gid=1000, 
home=/home/cam
dovecot: Apr 03 13:46:26 Info: IMAP(cam): maildir: 
data=/var/mail/cam/Maildir
dovecot: Apr 03 13:46:26 Info: IMAP(cam): maildir: 
root=/var/mail/cam/Maildir, index=/var/mail/cam/Maildir, control=, inbox=

dovecot: Apr 03 13:46:28 Info: auth(default): new auth connection: pid=18728
dovecot: Apr 03 13:46:28 Info: auth(default): client in: AUTH   1 
PLAIN   service=IMAPsecured lip=24.207.104.15   rip=24.207.104.15

dovecot: Apr 03 13:46:28 Info: auth(default): client out: CONT  1
dovecot: Apr 03 13:46:28 Info: auth(default): client in: CONT
dovecot: Apr 03 13:46:28 Info: auth(default): pam(cam,24.207.104.15): 
lookup service=dovecot
dovecot: Apr 03 13:46:28 Info: auth(default): client out: OK1 
user=cam
dovecot: Apr 03 13:46:28 Info: auth(default): master in: REQUEST 
52  18723   1
dovecot: Apr 03 13:46:28 Info: auth(default): passwd(cam,24.207.104.15): 
lookup
dovecot: Apr 03 13:46:28 Info: auth(default): master out: USER  52 
cam system_user=cam uid=1000gid=1000home=/home/cam
dovecot: Apr 03 13:46:28 Info: imap-login: Login: user=, 
method=PLAIN, rip=24.207.104.15, lip=24.207.104.15, secured
dovecot: Apr 03 13:46:28 Info: IMAP(cam): Effective uid=1000, gid=1000, 
home=/home/cam
dovecot: Apr 03 13:46:28 Info: IMAP(cam): maildir: 
data=/var/mail/cam/Maildir
dovecot: Apr 03 13:46:28 Info: IMAP(cam): maildir: 
root=/var/mail/cam/Maildir, index=/var/mail/cam/Maildir, control=, inbox=

dovecot: Apr 03 13:46:33 Info: IMAP(cam): Disconnected in IDLE
dovecot: Apr 03 13:46:33 Info: IMAP(cam): Disconnected in IDLE
dovecot: Apr 03 13:46:40 Info: auth(default): new auth connection: pid=18764
dovecot: Apr 03 13:46:40 Info: auth(default): client in: AUTH   1 
PLAIN   service=IMAPsecured lip=24.207.104.15   rip=24.207.104.15

dovecot: Apr 03 13:46:40 Info: auth(default): client out: CONT  1
dovecot: Apr 03 13:46:40 Info: auth(default): client in: CONT
dovecot: Apr 03 13:46:40 Info: auth(default): pam(cam,24.207.104.15): 
lookup service=dovecot
dovecot: Apr 03 13:46:40 Info: auth(default): client out: OK1 
user=cam
dovecot: Apr 03 13:46:40 Info: auth(default): master in: REQUEST 
53  18728   1
dovecot: Apr 03 13:46:40 Info: auth(default): passwd(cam,24.207.104.15): 
lookup
dovecot: Apr 03 13:46:40 Info: auth(default): master out: USER  53 
cam system_user=cam uid=1000gid=1000home=/home/cam
dovecot: Apr 03 13:46:40 Info: imap-login: Login: user=, 
method=PLAIN, rip=24.207.104.15, lip=24.207.104.15, secured
dovecot: Apr 03 13:46:40 Info: IMAP(cam): Effective uid=1000, gid=1000, 
home=/home/cam
dovecot: Apr 03 13:46:40 Info: IMAP(cam): maildir: 
data=/var/mail/cam/Maildir
dovecot: Apr 03 13:46:40 Info: IMAP(cam): maildir: 
root=/var/mail/cam/Maildir, index=/var/mail/cam/Maildir, control=, inbox=
dovecot: Apr 03 13:46:51 Info: auth(default): client in: AUTH   1 
PLAIN   service=IMAPsecured lip=24.207.104.15   rip=24.207.104.15

dovecot: Apr 03 13:46:51 Info: auth(default): client out: CONT  1
dovecot: Apr 03 13:46:51 Info: auth(default): client in: CONT
dovecot: Apr 03 13:46:51 Info: auth(default): pam(cam,24.207.104.15): 
lookup service=dovecot
dovecot: Apr 03 13:46:51 Info: auth(default): client out: OK1 
user=cam
dovecot: Apr 03 13:46:51 Info: auth(default): master in: REQUEST 
54  16801   1
dovecot: Apr 03 13:46:51 Info: auth(default): passwd(cam,24.207.104.15): 
lookup
dovecot: Apr 03 13:46:51 Info: auth(default): master out: USER  54 
cam system_user=cam uid=1000gid=1000home=/home/cam
dovecot: Apr 0

Re: [Dovecot] LDAP auth_bind hangs and times out

[Jack McKinney]

Red Hat Linux release 7.2 (Enigma)
OpenLDAP 2.3.38
Dovecot 1.0.12

On Thu, 2008-04-03 at 23:43 +0300, Timo Sirainen wrote:
> On Thu, 2008-04-03 at 09:46 -0500, Jack McKinney wrote:
> > I have _almost_ got Dovecot working!  One little snag...
> 
> What version?
> 
-- 
Jack McKinney
GPG 1024D/99C6A174
[EMAIL PROTECTED] YM:lfaatsnat2006 AIM:jackmclorentz
"There is no parameter that makes it impossible for you to perform still
more excellently."
   -Mario Cuomo, on the lack of a clock in baseball


signature.asc
Description: This is a digitally signed message part

Re: [Dovecot] LDAP auth_bind hangs and times out

[Timo Sirainen]

On Thu, 2008-04-03 at 09:46 -0500, Jack McKinney wrote:
>   I have _almost_ got Dovecot working!  One little snag...

What version?



signature.asc
Description: This is a digitally signed message part

Re: [Dovecot] Strange dmesg messages

[Timo Sirainen]

On Thu, 2008-04-03 at 16:55 -0300, Raphael Bittencourt S. Costa wrote:
> The erro stops when I uncomment 
> 
> mail_max_userip_connections = 10
> 
> does it make any sence?

The default is 10, so commenting or uncommenting it should make no
difference at all.



signature.asc
Description: This is a digitally signed message part

Re: [Dovecot] Icedove (Thunderbird) crashes when reading IMAP messages

[Charles Marcus]

On 4/3/2008, Cam Ellison ([EMAIL PROTECTED]) wrote:

Dovecot has been installed on it for over a year, with no problems.


What version?

--

Best regards,

Charles

Re: [Dovecot] Strange dmesg messages

[Raphael Bittencourt S. Costa]

The erro stops when I uncomment 

mail_max_userip_connections = 10

does it make any sence?

On Thu, 2008-04-03 at 16:34 -0300, Raphael Bittencourt S. Costa wrote:

> I moved the maildir location from Hitachi's storage to local sas disk
> and got the same erro using imaptest. Debug doesn't show any usable
> information. :-(
> 
> Any ideas? 
> 
> 
> 
> On Thu, 2008-04-03 at 19:01 +0300, Uldis Pakuls wrote: 
> 
> > Raphael Bittencourt S. Costa wrote:
> > > On Thu, 2008-04-03 at 09:25 +0300, Uldis Pakuls wrote:
> > >
> > >   
> > >> Raphael Bittencourt S. Costa wrote:
> > >> 
> > >>> Guys,
> > >>>
> > >>> I'm getting strange messages on my new server with dovecot-1.1rc4 + lda
> > >>> + sieve + ldap + postfix + suse10.  This server is in production since
> > >>> monday, and worked fine until today. The only thing I had changed was
> > >>> dovecot from 1.1rc3 to 1.1rc4. I already enabled mail_debug, but I got
> > >>> any erros after that.
> > >>>
> > >>> Does anyone have any idea of what is happening?
> > >>>
> > >>> Unable to handle kernel NULL pointer dereference at 0020
> > >>> RIP:
> > >>> {sys_inotify_rm_watch+280}
> > >>>   
> > >>>   
> > >> It is a kernel level crash  in function sys_inotify_rm_watch.; 
> > >>
> > >> */*/fs/inotify_user.c - inotify support for userspace/*/*
> > >>
> > >>  I don't think its dovecot's fault. Have you installed any vendor 
> > >> specific/propertary storage drivers?
> > >>
> > >> 
> > >
> > > Just using Hitachi's HDLM for multipath and failover.
> > >
> > >   
> > It's looks like problem with storage drivers (kernel modules) ; crash
> > after attempt to free inotify data.
> > As workaroud I may sugest to use difrenet notify method. (configure
> > option "--with-notify=")
> > 
> > Uldis
> > 
> > p.s.
> > I have 9 production servers running different versions of SuSE linux and
> > never have such a problem.
> > Something like this I got only once: after adding LSI pseudo raid
> > adapter useing LSI propertary drivers./**/*/*/
> > 
> > /*/*

Atenciosamente,










Raphael Bittencourt S. Costa
Engenharia
---
ALOG Data Centers do Brasil
Excelência em Projetos de Hosting
R Voluntários da Pátria 360 - RJ -
CEP 22270-010
Telefone: 21 3083-3364 - Fax: 21
3083-3300 http://www.alog.com.br 
<>

signature.asc
Description: This is a digitally signed message part

Re: [Dovecot] Strange dmesg messages

[Raphael Bittencourt S. Costa]

I moved the maildir location from Hitachi's storage to local sas disk
and got the same erro using imaptest. Debug doesn't show any usable
information. :-(

Any ideas? 



On Thu, 2008-04-03 at 19:01 +0300, Uldis Pakuls wrote:

> Raphael Bittencourt S. Costa wrote:
> > On Thu, 2008-04-03 at 09:25 +0300, Uldis Pakuls wrote:
> >
> >   
> >> Raphael Bittencourt S. Costa wrote:
> >> 
> >>> Guys,
> >>>
> >>> I'm getting strange messages on my new server with dovecot-1.1rc4 + lda
> >>> + sieve + ldap + postfix + suse10.  This server is in production since
> >>> monday, and worked fine until today. The only thing I had changed was
> >>> dovecot from 1.1rc3 to 1.1rc4. I already enabled mail_debug, but I got
> >>> any erros after that.
> >>>
> >>> Does anyone have any idea of what is happening?
> >>>
> >>> Unable to handle kernel NULL pointer dereference at 0020
> >>> RIP:
> >>> {sys_inotify_rm_watch+280}
> >>>   
> >>>   
> >> It is a kernel level crash  in function sys_inotify_rm_watch.; 
> >>
> >> */*/fs/inotify_user.c - inotify support for userspace/*/*
> >>
> >>  I don't think its dovecot's fault. Have you installed any vendor 
> >> specific/propertary storage drivers?
> >>
> >> 
> >
> > Just using Hitachi's HDLM for multipath and failover.
> >
> >   
> It's looks like problem with storage drivers (kernel modules) ; crash
> after attempt to free inotify data.
> As workaroud I may sugest to use difrenet notify method. (configure
> option "--with-notify=")
> 
> Uldis
> 
> p.s.
> I have 9 production servers running different versions of SuSE linux and
> never have such a problem.
> Something like this I got only once: after adding LSI pseudo raid
> adapter useing LSI propertary drivers./**/*/*/
> 
> /*/*

[Dovecot] Patch for zlib and maildir for 1.0.13

[Richard Platel]

When using the zlib plugin with maildir and copying with hardlinks,  
if a compressed message is copied, the 'Z' suffix on the file isn't  
copied, so the new message isn't uncompressed when it's fetched.


I wasn't smart enough to figure out a clean way to carry a file  
suffix through a copy, so I changed how the zlib-plugin detects if a  
message is compressed.  This patch peeks at the first two bytes of  
the message looking for the zlib header.


--
Richard Platel
Tucows


zlib-plugin.c.patch
Description: Binary data

Re: [Dovecot] Icedove (Thunderbird) crashes when reading IMAP messages

[Cam Ellison]

Asheesh Laroia wrote:

On Thu, 3 Apr 2008, Cam Ellison wrote:

This is a Debian lenny/sid installation.  Dovecot has been installed 
on it for over a year, with no problems.  Lately (i.e. the past few 
months), if I attempt to read a message, Icedove crashes.  It does not 
do this when I read a message downloaded from the ISP's POP3 server 
(not that I do this very often - almost all my mail goes through 
Dovecot).


Have you tried creating a new account with the same settings as the 
normal Dovecot account?  Maybe Icedove/Thunderbird has corrupted some 
local data.


Icedove won't allow that - I have just tried it.  Interestingly, I was 
able to read your message with no problems, but Icedove crashed when I 
attempted to read a recent message in another folder.  I expect you may 
be right about corruption.


If it persists, then get a raw log from Dovecot and let's see what has 
to be done from there.


As to getting a log, this is a Debian installation, and everything goes 
to syslog.  I have made the necessary change in dovecot.conf,
and will see what I can generate.  No luck so far with valgrind: I must 
be setting it up wrong.


Thanks for the help

Cam


--
Cam Ellison  Ph.D.  R.Psych. #01417

Cam Ellison & Associates Ltd.
Management Psychology

3446 Beach Avenue
Roberts Creek  BC  V0N 2W2

Phone: 604.885.4806
Fax:   604.885.4809
Cell:  604.989.0635

Re: [Dovecot] Icedove (Thunderbird) crashes when reading IMAP messages

[Asheesh Laroia]

On Thu, 3 Apr 2008, Cam Ellison wrote:

This is a Debian lenny/sid installation.  Dovecot has been installed on it 
for over a year, with no problems.  Lately (i.e. the past few months), if I 
attempt to read a message, Icedove crashes.  It does not do this when I read 
a message downloaded from the ISP's POP3 server (not that I do this very 
often - almost all my mail goes through Dovecot).


Have you tried creating a new account with the same settings as the normal 
Dovecot account?  Maybe Icedove/Thunderbird has corrupted some local data.


If it persists, then get a raw log from Dovecot and let's see what has to 
be done from there.


-- Asheesh.

--
An age is called Dark not because the light fails to shine, but because
people refuse to see it.
-- James Michener, "Space"

[Dovecot] Icedove (Thunderbird) crashes when reading IMAP messages

[Cam Ellison]

This is a Debian lenny/sid installation.  Dovecot has been installed on 
it for over a year, with no problems.  Lately (i.e. the past few 
months), if I attempt to read a message, Icedove crashes.  It does not 
do this when I read a message downloaded from the ISP's POP3 server (not 
that I do this very often - almost all my mail goes through Dovecot).


I am now having to read email with KMail, but cannot send from it - 
that's another story.


Googling for the past month or so reveals nothing: there seems to be no 
bug filed for this, and indeed I think it is an odd communication 
problem with dovecot that has not been seen before.


Has anyone any experience with this, or any ideas how I should go about 
resolving it?  I have not done so (because I don't know how to use the 
data, not being a coder), but can run strace and/or valgrind on icedove 
if that will help.


Thanks in advance

Cam


--
Cam Ellison  Ph.D.  R.Psych. #01417

Cam Ellison & Associates Ltd.
Management Psychology

3446 Beach Avenue
Roberts Creek  BC  V0N 2W2

Phone: 604.885.4806
Fax:   604.885.4809
Cell:  604.989.0635

Re: [Dovecot] Strange dmesg messages

[Uldis Pakuls]

Raphael Bittencourt S. Costa wrote:
> On Thu, 2008-04-03 at 09:25 +0300, Uldis Pakuls wrote:
>
>   
>> Raphael Bittencourt S. Costa wrote:
>> 
>>> Guys,
>>>
>>> I'm getting strange messages on my new server with dovecot-1.1rc4 + lda
>>> + sieve + ldap + postfix + suse10.  This server is in production since
>>> monday, and worked fine until today. The only thing I had changed was
>>> dovecot from 1.1rc3 to 1.1rc4. I already enabled mail_debug, but I got
>>> any erros after that.
>>>
>>> Does anyone have any idea of what is happening?
>>>
>>> Unable to handle kernel NULL pointer dereference at 0020
>>> RIP:
>>> {sys_inotify_rm_watch+280}
>>>   
>>>   
>> It is a kernel level crash  in function sys_inotify_rm_watch.; 
>>
>> */*/fs/inotify_user.c - inotify support for userspace/*/*
>>
>>  I don't think its dovecot's fault. Have you installed any vendor 
>> specific/propertary storage drivers?
>>
>> 
>
> Just using Hitachi's HDLM for multipath and failover.
>
>   
It's looks like problem with storage drivers (kernel modules) ; crash
after attempt to free inotify data.
As workaroud I may sugest to use difrenet notify method. (configure
option "--with-notify=")

Uldis

p.s.
I have 9 production servers running different versions of SuSE linux and
never have such a problem.
Something like this I got only once: after adding LSI pseudo raid
adapter useing LSI propertary drivers./**/*/*/

/*/*

[Dovecot] LDAP auth_bind hangs and times out

[Jack McKinney]

I have _almost_ got Dovecot working!  One little snag...

My users login using their email address as username. Each domain has
their own LDAP subtree.  Each user has an entry in the ou=users subtree
of the domain subtree, and has a mail: field (inetOrgPerson) listing
their email address/login name.
I am trying to use auth_bind: when I login with [EMAIL PROTECTED],
dovecot should search for [EMAIL PROTECTED] in the onelevel below
ou=users,dc=lorentz,dc=com and find me as "cn=Jack
McKinney,ou=users,dc=lorentz,dc=com".
I have created an entry in LDAP (varmail) that should be able to do
this query.  Indeed, from the command line, it works:

ldapsearch -h ldap.lrtz -b 'ou=users, dc=lorentz, dc=com' -D
'cn=varmail,ou=users,dc=lorentz,dc=com' -x -W -s onelevel
'(&(objectClass=inetOrgPerson)([EMAIL PROTECTED]))'
Enter LDAP Password: 
# extended LDIF
#
# LDAPv3
# base  with scope oneLevel
# filter: (&(objectClass=inetOrgPerson)([EMAIL PROTECTED]))
# requesting: ALL
#

# Jack McKinney, users, lorentz.com
dn: cn=Jack McKinney,ou=users,dc=lorentz,dc=com
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: inetOrgPerson
cn: Jack McKinney
givenName: Jack McKinney
sn: McKinney
mail: [EMAIL PROTECTED]

# search result
search: 2
result: 0 Success

# numResponses: 2
# numEntries: 1


'   However, it appears that dovecot performs the above query
successfully, but then never uses the password and retrieved DN to
attempt to bind and authenticate the user.  Instead, it just times out.

My dovecot-ldap.conf is:

hosts = ldap.lrtz
dn = cn=varmail,ou=users,dc=lorentz,dc=com
dnpass = *
ldap_version = 3
auth_bind = yes
pass_filter = (&(objectClass=inetOrgPerson)(mail=%Lu))
base = ou=users, dc=%Dd
scope = onelevel

The dovecot log shows:

Apr  3 08:13:21 fourier dovecot: auth(default): new auth connection:
pid=15774
Apr  3 08:13:30 fourier dovecot: auth(default): client in:
AUTH^I1^IPLAIN^Iservice=IMAP^Isecured^Ilip=x.x.x.x^Irip=y.y.y.y^Iresp=
Apr  3 08:13:30 fourier dovecot: auth(default):
ldap([EMAIL PROTECTED],y.y.y.y): bind search: base=ou=users,
dc=lorentz,dc=com
filter=(&(objectClass=inetOrgPerson)([EMAIL PROTECTED]))
Apr  3 08:16:30 fourier dovecot: imap-login: Disconnected: Inactivity:
method=PLAIN, rip=y.y.y.y, lip=x.x.x.x, TLS

The OpenLDAP log shows that the query is received and that it returns a
match:

Apr  3 08:13:30 fourier slapd[14039]: conn=7 op=3 SRCH
base="ou=users,dc=lorentz,dc=com" scope=1 deref=0
filter="(&(objectClass=inetOrgPerson)([EMAIL PROTECTED]))"
Apr  3 08:13:30 fourier slapd[14039]: conn=7 op=3 SRCH attr=uid
Apr  3 08:13:30 fourier slapd[14039]: conn=7 op=3 SEARCH RESULT tag=101
err=0 nentries=1 text=

When I do the query from the command line, there is an additional pair
of lines:

Apr  3 08:18:10 fourier slapd[16106]: conn=22 op=2 UNBIND
Apr  3 08:18:10 fourier slapd[16106]: conn=22 fd=28 closed

I thus conclude that Dovecot is not closing the connection.

-- 
Jack McKinney
GPG 1024D/99C6A174
[EMAIL PROTECTED] YM:lfaatsnat2006 AIM:jackmclorentz
"There is no parameter that makes it impossible for you to perform still
more excellently."
   -Mario Cuomo, on the lack of a clock in baseball


signature.asc
Description: This is a digitally signed message part

Re: [Dovecot] Strange dmesg messages

[Raphael Bittencourt S. Costa]

On Thu, 2008-04-03 at 09:25 +0300, Uldis Pakuls wrote:

> Raphael Bittencourt S. Costa wrote:
> > Guys,
> >
> > I'm getting strange messages on my new server with dovecot-1.1rc4 + lda
> > + sieve + ldap + postfix + suse10.  This server is in production since
> > monday, and worked fine until today. The only thing I had changed was
> > dovecot from 1.1rc3 to 1.1rc4. I already enabled mail_debug, but I got
> > any erros after that.
> >
> > Does anyone have any idea of what is happening?
> >
> > Unable to handle kernel NULL pointer dereference at 0020
> > RIP:
> > {sys_inotify_rm_watch+280}
> >   
> 
> It is a kernel level crash  in function sys_inotify_rm_watch.; 
> 
> */*/fs/inotify_user.c - inotify support for userspace/*/*
> 
>  I don't think its dovecot's fault. Have you installed any vendor 
> specific/propertary storage drivers?
> 

Just using Hitachi's HDLM for multipath and failover.



> Uldis

[Dovecot] mail_chroot problems / dovecot 1.1rc4

[Michal Soltys]

Hello

I've noticed a little strange behaviour of that option. For example with
following settings:

system user: admin, with its home directory as /home/admin
dovecot options: as reported by dovecot -n (in attachment)

dovecot will try to chroot into /home/home/admin with the following 
message in logs, in my case:


Fatal: chdir(/home/home/admin) failed with uid 1999: No such file or
directory

The same happens if I use per-user chroot= option in userdb, f.e. in 
passwd-file


I've noticed it's just now, as I've always used explicit chroot dirs
specified through passwd-file with /./ (which works perfectly fine, 
except harmless double slashes in logs), and didn't bother with single 
system user (I made some chroot/lock related bugreports in distant 
1.0rcXX past).


Cheers

Michal

# 1.1.rc4: /etc/dovecot.conf
base_dir: /var/dovecot/
protocols: imap imaps pop3 pop3s
ssl_listen: *
ssl_ca_file: /etc/ssl/cert_bundle.pem
ssl_cert_file: /etc/ssl/ca_ppgk/certs/fetch_crt.pem
ssl_key_file: /etc/ssl/ca_ppgk/private/fetch_key.pem
verbose_ssl: yes
login_dir: /var/dovecot/login
login_executable(default): /usr/local/libexec/dovecot/imap-login
login_executable(imap): /usr/local/libexec/dovecot/imap-login
login_executable(pop3): /usr/local/libexec/dovecot/pop3-login
login_greeting: Dovecot IMAP server ready.
login_greeting_capability(default): yes
login_greeting_capability(imap): yes
login_greeting_capability(pop3): no
login_process_size: 32
valid_chroot_dirs: /home
mail_chroot: /home
verbose_proctitle: yes
first_valid_uid: 1999
first_valid_gid: 10
mail_location: 
maildir:~/mspace/maildir:INDEX=~/mspace/index:INBOX=~/mspace/inbox:CONTROL=~/mspace/control
mail_debug: yes
fsync_disable: yes
lock_method: flock
mbox_read_locks: flock
mbox_write_locks: flock
mail_executable(default): /usr/local/libexec/dovecot/imap
mail_executable(imap): /usr/local/libexec/dovecot/imap
mail_executable(pop3): /usr/local/libexec/dovecot/pop3
mail_plugins(default): quota imap_quota
mail_plugins(imap): quota imap_quota
mail_plugins(pop3): quota
mail_plugin_dir(default): /usr/local/lib/dovecot/imap
mail_plugin_dir(imap): /usr/local/lib/dovecot/imap
mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3
imap_client_workarounds(default): outlook-idle delay-newmail 
tb-extra-mailbox-sep
imap_client_workarounds(imap): outlook-idle delay-newmail tb-extra-mailbox-sep
imap_client_workarounds(pop3):
pop3_client_workarounds(default):
pop3_client_workarounds(imap):
pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh
namespace:
  type: private
  separator: /
  inbox: yes
  list: yes
  subscriptions: yes
auth default:
  mechanisms: plain login
  verbose: yes
  debug: yes
  passdb:
driver: passwd-file
args: /etc/dovecot.z1.passwd
  passdb:
driver: passwd-file
args: /etc/dovecot.passwd
  passdb:
driver: passwd
  userdb:
driver: passwd-file
args: /etc/dovecot.z1.passwd
  userdb:
driver: passwd-file
args: /etc/dovecot.passwd
  userdb:
driver: passwd
  socket:
type: listen
client:
  path: /var/spool/postfix/private/auth
  mode: 432
  user: postfix
  group: postfix
plugin:
  quota: maildir