Hello,
Thanks for your feedback on this problem.
* Josip Rodin <[EMAIL PROTECTED]> [060828 02:28]:
> This was supposed to be delivering to /var/mail, or some other folder?
> What are the permissions on it?
This was /var/mail, with standard permissions. Version 1.5 of maildrop
was working without problem.
> > Also, courier-authlib is not listed in dependencies, so if it is not
> > installed by hand, maildrop fails because it doesn't find authlib.
> maildrop 2.x, available in package since recently, tries to use
> authdaemon when you run it with -d, and even then you need
> a privileged user to run it, I think.
After seeing that 2.0.2 was in experimental --- had not followed it
closely (my tests & bug were from 1.8), I retried installing it again
today, and first got messages like this :
Command died with status 127: "/usr/bin/maildrop -d ${USER}". Command
output: /usr/bin/maildrop: error while loading shared libraries:
libcourierauth.so.0: cannot open shared object file: No such file or
directory
So the problem of dependency on courier-authlib is still the same.
Installing maildrop should have it work by default, not complain on
a missing lib !
After installing courier-authlib, errors messages indicated that
I should install courier-authdaemon... And after installing this one,
messages read like this from the MTA :
temporary failure. Command output: ERR: authdaemon: s_connect() failed:
Permission denied /usr/bin/maildrop: Temporary authentication failure.
So I guess I would again need to configure something else to make it
work, which is inacceptable.
maildrop 1.5 was working like a charm without configuring anything, so
2.0.2 should work the same way. And of course the problems I just
described are not described anywhere in the maildrop debian docs...
Just in case you reply that maildrop 2.0.X works like this, I have to
answer no, because since this bug report last year, as I got no reply,
I compiled maildrop 2.0.2 by hand (some months ago) without any special
option, and it worked flawlessly, like 1.5 (Debian package) was.
So I guess the packaging of 2.0.2 is broken, and that it has been
compiled in "depending on the full courier framework" mode instead of
standalone mode (seems the configure script is trying to detect this,
but this can be bypassed with --disable-authlib --- not I did not have
to use it on my computer to get it right).
* Josip Rodin <[EMAIL PROTECTED]> [060828 02:49]:
> Oh, I think I get it. Do you perhaps use relative paths in your
> .mailfilter file? What is the current working directory of the
> maildrop process at that point?
Just to be precise : no, my paths in .mailfilter are not relative.
If you need more info, do not hesitate to contact me.
Best regards,
--
Damien Wyart
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
