I believe this is fixed in the current version. If it's still a
problem, feel free to reopen the bug.
** Changed in: courier (Ubuntu)
Status: Incomplete = Fix Committed
--
maildrop missing maildir path in authldaprc
https://bugs.launchpad.net/bugs/121907
You received this bug
** Changed in: courier (Ubuntu)
Status: Fix Committed = Fix Released
--
maildrop missing maildir path in authldaprc
https://bugs.launchpad.net/bugs/121907
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
** Changed in: courier (Ubuntu)
Status: Invalid = Incomplete
--
maildrop missing maildir path in authldaprc
https://bugs.launchpad.net/bugs/121907
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[Expired for courier (Ubuntu) because there has been no activity for 60
days.]
--
maildrop missing maildir path in authldaprc
https://bugs.launchpad.net/bugs/121907
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
There's a new courier version in gutsy. Is this still an issue.
--
maildrop missing maildir path in authldaprc
https://bugs.launchpad.net/bugs/121907
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Ok, when you run this command everything is fine
here the command wich runs ok
cat /etc/issue | maildrop -V 6 -d [EMAIL PROTECTED]
part of the authlib log running this command
maildrop: authlib: groupid=5000
maildrop: authlib: userid=5000
maildrop: authlib: [EMAIL PROTECTED],
Could this be permissions related? When you run the command by hand what
user are you?
Postfix drops it's root privileges after binding to port 25 for security
reasons.
--
maildrop missing maildir path in authldaprc
https://bugs.launchpad.net/bugs/121907
You received this bug notification
Sorry, in my last message where you see ubil.reduim.cu is domain.tld
--
maildrop missing maildir path in authldaprc
https://bugs.launchpad.net/bugs/121907
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Running the command as root:
[EMAIL PROTECTED]:/srv/vmail/domains/domain.tld# cat /etc/issue | maildrop -V 6
-d [EMAIL PROTECTED]
maildrop: authlib: groupid=5000
maildrop: authlib: userid=5000
maildrop: authlib: [EMAIL PROTECTED], home=/srv/vmail/domains,
mail=domain.tld/testmail/Maildir/
I did, a chmod 777 -R to /srv/vmail/domains, but nothing, maildrop is
only working ok with user root, as vmail fails.
--
maildrop missing maildir path in authldaprc
https://bugs.launchpad.net/bugs/121907
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
For some unknown reason when running as root it gets the home correctly from
ldap in
/srv/vmail/domains
maildrop: authlib: [EMAIL PROTECTED], home=/srv/vmail/domains,
mail=ubil.reduim.cu/testmail/Maildir/
maildrop: Changing to /srv/vmail/domains
but when running as vmail it gets as homedir the
I'm wondering if this bug relates:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=235007
Why don't you see if setting uidNumber and gidNumber in your
/etc/courier/authldaprc makes a difference.
--
maildrop missing maildir path in authldaprc
https://bugs.launchpad.net/bugs/121907
You received
I use in authldaprc
##NAME: LDAP_GLOB_IDS:0
#
# The following two variables can be used to set everybody's uid and gid.
# This is convenient if your LDAP specifies a bunch of virtual mail accounts
# The values can be usernames or userids:
#
# LDAP_GLOB_UID vmail
# LDAP_GLOB_GID
Any way I tried with
LDAP_UID uidNumber
LDAP_GID gidNumber
And still the same
--
maildrop missing maildir path in authldaprc
https://bugs.launchpad.net/bugs/121907
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
My /srv/vmail is a mount point:
/dev/sda2 on /boot type ext3 (rw)
/dev/sda5 on /home type ext3 (rw)
/dev/sda6 on /opt type ext3 (rw)
/dev/sda8 on /srv/www type ext3 (rw)
/dev/sda10 on /tmp type ext3 (rw)
/dev/sda9 on /usr type ext3 (rw)
/dev/sda11 on /usr/local type ext3 (rw)
/dev/sda12 on /var
The only other potentially relevant Debian bug I can find is this one:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=223371
I wonder if it somehow relates to socket permissions.
--
maildrop missing maildir path in authldaprc
https://bugs.launchpad.net/bugs/121907
You received this bug
Bits of this thread might be relevant too:
http://sourceforge.net/mailarchive/forum.php?thread_name=460712F9.4020203%40amfes.comforum_name
=courier-maildrop
--
maildrop missing maildir path in authldaprc
https://bugs.launchpad.net/bugs/121907
You received this bug notification because you are a
Searched for sockets permissions but, it seems no problems, searched the log
for permission deanied but nothing..
[EMAIL PROTECTED]:/var/run/courier/authdaemon# ls -l
total 4
-rw-r--r-- 1 root root 6 2007-06-24 16:55 pid
-rw--- 1 root root 0 2007-06-22 14:52 pid.lock
srwxrwxrwx 1 root root 0
At this point I'd suggest looking in the archives of the Courier mailing
lists for ideas and ask there if you don't find anything. Please let us
know how it works out.
--
maildrop missing maildir path in authldaprc
https://bugs.launchpad.net/bugs/121907
You received this bug notification
Searching courier maildrop install I saw this:
When using the standalone maildrop build with courier-authlib, one of
the following configurations must be used:
* Your mail server must invoke maildrop as the root user (the -d flag
reads the mail account's uid and gid, then drops root) .
*
Well a workaround wich works, but you must consider the security risks is by
allowing user postfix and vmail call aildrop without password in sudoers:
/etc/sudoers
#
vmailALL=NOPASSWD: /usr/bin/maildrop
postfixALL=NOPASSWD: /usr/bin/maildrop
And change in postfix master.cf the maildrop
The first thing I would do is increase the verbosity of the Postfix logs
and find the exact command that Postfix is using. Make sure it's the
same as the one you are using when do this by hand. Please post a log
snipped (not entire verbose logs) showing what Postfix is doing.
** Changed in:
22 matches
Mail list logo
