OK. I'm getting further now thanks to the help received by several list
members. Thanks everyone! But we're not outta da woods yet Snoopy...
I've nailed it down to a call to "maildir_tmpcreate_fd(&createInfo)"
failing in imapscanclient.c.
Adding some debug code to the maildir_tmpcreate_fd_do(...) function I
now know the following:
info->maildir='.' (current dir =
/home/vpopmail/domains/cybermedix.co.nz/mail/Maildir)
info->uniq='imapuid_0'
info->hostname='nzh1.nzhosting.co.nz'
So we ARE getting to the right directory. Great!
So... here are the contents of
/home/vpopmail/domains/cybermedix.co.nz/mail/Maildir
drwxr----- 2 vpopmail vchkpw 4096 Sep 23 18:27 cur
drwxr----- 2 vpopmail vchkpw 12288 Sep 23 18:27 new
-rw-r----- 1 vpopmail vchkpw 15 Jul 29 2002
sqwebmail-pass
drwxr----- 2 vpopmail vchkpw 4096 Sep 23 20:13 tmp
Hmmm. tmp is there and it has the right permissions (I think).
So I try two things.
1. chmod a+rw tmp
(and test again)
2. rm -rf tmp
(and test again)
Neither of these results in a change of symptom.
maildir_tmpcreate_fd_do(...) still fails.
So now I'm more baffled than ever. Can't see the forest for the trees?
Seems that way :(
Thanks again for any further assistance - at least we're making some
progress now :)
Bryan.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Malcolm
Weir
Sent: Tuesday, 23 September 2003 08:01
To: [EMAIL PROTECTED]
Subject: RE: [courier-users] Perhaps I should just give up on imapd with
vpopmail :(
> -----Original Message-----
> From: Three Letter Acronym
> Sent: Monday, September 22, 2003 12:26 PM
> Bryan Rentoul wrote:
> > Well, after running
> >
> > find . -type f -exec grep "No such file or directory" {} \;
>
> "No such file or directory" is a message from a library routine.
>
> From /usr/include/errno.h:
>
> #define ENOENT 2 /* No such file or directory
*/
>
> I can only assume that the text itself is compiled into libc:
> [EMAIL PROTECTED] /usr/lib >> strings /usr/lib/libc.a | grep "No such file" No
> such file or directory [EMAIL PROTECTED] /usr/lib >>
Yep. That's it. It's "part of" perror and strerror that the test of
"errno" is defined, often in something called "sys_errlist[]".
So your best bet is to go looking for "Fatal Error" (which is *not* part
of errno), and/or "perror" and strerror and sys_errlist...
And... with all respect, Bryan, this is fairly elementary Unix
programming environment stuff, and you may be less frustrated by
obtaining the services of a regular Unix hacker (in the positive sense)
rather than beat your head against the wall much more...
> --tla
> > Bryan J. Rentoul
> > Director
> > NZ Hosting Limited
Malc.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf _______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users