Timo Sirainen wrote:
Changes since rc29:
* PAM: Lowercase the PAM service name when calling with "args = *".
Linux PAM did this internally already, but at least BSD didn't.
If your PAM file used to be in /etc/pam.d/IMAP or POP3 file you'll
need to lowercase it now.
+ Send list of CA names to client when using
ssl_verify_client_cert=yes.
- IMAP: If message body started with line feed, it wasn't counted
in BODY and BODYSTRUCTURE replies' line count field.
- deliver didn't load plugins before chrooting
Timo, in rc30, deliver is not creating user directories properly. It
looks like it goes straight to creating the maildir, without creating
the home directory first if it doesn't exist. It also seems to be doing
this before chrooting, as the following errors occur even after manually
creating the home directory (with proper permissions):
Apr 6 10:26:23 node7 postfix/qmgr[21815]: D2242D39A5: from=<>,
size=556, nrcpt=1 (queue active)
Apr 6 10:26:23 node7 deliver([EMAIL PROTECTED]): mkdir(/cur) failed:
Permission denied
Apr 6 10:26:23 node7 deliver([EMAIL PROTECTED]): mkdir(/cur) failed:
Permission denied
Apr 6 10:26:23 node7 postfix/pipe[26800]: D2242D39A5:
to=<[EMAIL PROTECTED]>, relay=dovecot, delay=232, delays=232/0/0/0.01,
dsn=4.3.0, status=deferred (temporary failure)
Also, the convert plugin seems to assume the home dir exists when it
tries to create it's lock file. However, manually creating the home dir
does allow convert to continue successfully.
Apr 6 10:42:15 node7 dovecot: POP3([EMAIL PROTECTED]):
open(/var/mailstore/af/4f/510590/.temp.node7.neonova.net.26842.6454b11667006c6f)
failed: No such file or directory
Apr 6 10:42:15 node7 dovecot: child 26842 (pop3) returned error 89
The 510590 directory did not exist in both of these examples, and I'm
using %h as the mail location (but adding a subdir to that didn't make a
difference).
