Re: [Dovecot] Postfix with Deliver (LDA) - user unknown
Let's try to keep this on the list shall we. [EMAIL PROTECTED] wrote: Here is the conversation from my maillog: Oct 3 20:52:15 superman postfix/pickup[179]: B77EA130C28: uid=0 from=root Oct 3 20:52:15 superman postfix/cleanup[232]: B77EA130C28: message-id=[EMAIL PROTECTED] Oct 3 20:52:15 superman postfix/qmgr[98583]: B77EA130C28: from=[EMAIL PROTECTED], size=375, nrcpt=1 (queue active) Oct 3 20:52:15 superman postfix/pipe[234]: B77EA130C28: to=[EMAIL PROTECTED], relay=dovecot, delay=0.25, delays=0.16/0.01/0/0.08, dsn=5.1.1, status=bounced (user unknown) Oct 3 20:52:15 superman postfix/cleanup[232]: E0729130C32: message-id=[EMAIL PROTECTED] Oct 3 20:52:15 superman postfix/bounce[236]: B77EA130C28: sender non-delivery notification: E0729130C32 Oct 3 20:52:15 superman postfix/qmgr[98583]: E0729130C32: from=, size=2294, nrcpt=1 (queue active) Oct 3 20:52:15 superman postfix/qmgr[98583]: B77EA130C28: removed Oct 3 20:52:16 superman postfix/local[237]: E0729130C32: to=[EMAIL PROTECTED], Do you have a user called geekserver. Looks a bit dodgy. orig_to=[EMAIL PROTECTED], relay=local, dovecot is a bit peculiar with the root user. You should always alias that to a real user. Or maybe you have. delay=0.13, delays=0.06/0.01/0/0.06, dsn=5.1.1, status=bounced (unknown user: geekserver) Well, do you have a user called geekserver? Oct 3 20:52:16 superman postfix/qmgr[98583]: E0729130C32: removed dovecot.log has: dovecot: Oct 03 08:57:04 Info: auth(default): passwd([EMAIL PROTECTED]): unknown user That seems to be unrelated to the above. /L dovecot-deliver.log is empty... Thanks for your assistance!!! ;-) glenn System log could help. /L Karin Gregorec wrote: Good Day All! I am attempting to configure deliver as our LDA. I am also configuring the server to use Postfix instead of Sendmail. I have followed the all the documentation and examples I could find. Below are my Dovecot and Postfix configs. Can someone please smack me upside the head and tell me why I am getting user unknown errors? If i don't use deliver as the LDA, all works perfectly. Help... TIA, glenn == *** Dovecot Config *** dovecot -n # 1.0.5: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/maillogs/dovecot.log protocols: imap imaps pop3 pop3s ssl_cipher_list: ALL:!LOW disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/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: GID Ready login_log_format_elements: user=%u service=%s authMethod=%m rIP=%r lIP=%l encryption=%c login_max_processes_count: 256 verbose_proctitle: yes first_valid_uid: 5000 last_valid_uid: 1 first_valid_gid: 0 mail_extra_groups: mail mail_location: maildir:~/Maildir dotlock_use_excl: yes fsync_disable: yes maildir_copy_with_hardlinks: yes 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_process_size: 1024 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): 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): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh pop3_logout_format(default): top=%t/%p, retr=%r/%b, del=%d/%m, size=%s pop3_logout_format(imap): top=%t/%p, retr=%r/%b, del=%d/%m, size=%s pop3_logout_format(pop3): top=%t/%T, retr=%r/%R, del=%d/%m, size=%s auth default: cache_size: 1024 cache_ttl: 604800 verbose: yes passdb: driver: pam args: cache_key=%Lu userdb: driver: passwd socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: maildrop plugin: quota: maildir:storage=1000:ignore=Trash *** Postfix main.cf *** alias_database = hash:/etc/mail/postfix/aliases alias_maps = hash:/etc/mail/postfix/aliases biff = no command_directory = /usr/local/sbin daemon_directory = /usr/local/libexec/postfix debug_peer_level = 2 debugger_command = PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont; echo where) | gdb $daemon_directory/$process_name $process_id 21 $config_directory/$process_name.$process_id.log sleep 5 Dovecot LDA Service -
Re: [Dovecot] autocreate plugin
Lars Stavholm wrote: Did anyone get the autocreate plugin working? I've compiled, installed and configured, but no mailboxes/folders are created. Me stupid, works fine, forgot to subscribe. /L
Re: [Dovecot] Postfix with Deliver (LDA) - user unknown
You have set in the main.cf:
virtual_mailbox_maps = hash:/etc/mail/postfix/vmailboxes
but dovecot deliver is using userdb for this purpose, which you have set to
passwd. Have you equivalent data in both places? Similary nearly all
configuration parameters in the main.cf of the postfix starting with
virtual_??? are not required, but should be provided by userdb for dovecot
deliver.
BB
On 1:26 04/10/07 Karin Gregorec [EMAIL PROTECTED] wrote:
Good Day All! I am attempting to configure deliver as our LDA. I am
also configuring the server to use Postfix instead of Sendmail. I
have followed the all the documentation and examples I could find.
Below are my Dovecot and Postfix configs. Can someone please smack me
upside the head and tell me why I am getting user unknown errors?
If i don't use deliver as the LDA, all works perfectly. Help...
TIA,
glenn
==
*** Dovecot Config ***
dovecot -n
# 1.0.5: /usr/local/etc/dovecot.conf
base_dir: /var/run/dovecot/
log_path: /var/log/maillogs/dovecot.log
protocols: imap imaps pop3 pop3s
ssl_cipher_list: ALL:!LOW
disable_plaintext_auth: no
verbose_ssl: yes
login_dir: /var/run/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: GID Ready
login_log_format_elements: user=%u service=%s authMethod=%m rIP=%r
lIP=%l encryption=%c
login_max_processes_count: 256
verbose_proctitle: yes
first_valid_uid: 5000
last_valid_uid: 1
first_valid_gid: 0
mail_extra_groups: mail
mail_location: maildir:~/Maildir
dotlock_use_excl: yes
fsync_disable: yes
maildir_copy_with_hardlinks: yes
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_process_size: 1024
mail_plugins(default): quota imap_quota
mail_plugins(imap): quota imap_quota
mail_plugins(pop3):
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): delay-newmail outlook-idle
netscape-eoh tb-extra-mailbox-sep
imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh
tb-extra-mailbox-sep
imap_client_workarounds(pop3): outlook-idle
pop3_uidl_format(default):
pop3_uidl_format(imap):
pop3_uidl_format(pop3): %08Xu%08Xv
pop3_client_workarounds(default):
pop3_client_workarounds(imap):
pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh
pop3_logout_format(default): top=%t/%p, retr=%r/%b, del=%d/%m, size=%s
pop3_logout_format(imap): top=%t/%p, retr=%r/%b, del=%d/%m, size=%s
pop3_logout_format(pop3): top=%t/%T, retr=%r/%R, del=%d/%m, size=%s
auth default:
cache_size: 1024
cache_ttl: 604800
verbose: yes
passdb:
driver: pam
args: cache_key=%Lu
userdb:
driver: passwd
socket:
type: listen
master:
path: /var/run/dovecot/auth-master
mode: 384
user: maildrop
plugin:
quota: maildir:storage=1000:ignore=Trash
*** Postfix main.cf ***
alias_database = hash:/etc/mail/postfix/aliases
alias_maps = hash:/etc/mail/postfix/aliases
biff = no
command_directory = /usr/local/sbin
daemon_directory = /usr/local/libexec/postfix
debug_peer_level = 2
debugger_command =
PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
echo where) | gdb $daemon_directory/$process_name $process_id 21
$config_directory/$process_name.$process_id.log sleep 5
Dovecot LDA Service - http://wiki.dovecot.org/LDA/Postfix
dovecot_destination_recipient_limit = 1
home_mailbox = Maildir/
html_directory = no
inet_interfaces = all
mail_owner = postfix
mail_spool_directory = /var/mail
mailq_path = /usr/local/bin/mailq
manpage_directory = /usr/local/man
message_size_limit = 1200
mydestination = $myhostname, localhost.$mydomain, localhost
mydomain = geekinternetdevelopment.com
myhostname = superman.geekinternetdevelopment.com
mynetworks = 72.18.193.0/24, 127.0.0.0/8
newaliases_path = /usr/local/bin/newaliases
queue_directory = /var/spool/postfix
readme_directory = no
sample_directory = /usr/local/etc/postfix
sendmail_path = /usr/local/sbin/sendmail
setgid_group = maildrop
smtpd_banner = $myhostname NO WHAMMIES!!!
virtual_gid_maps = static:5000
virtual_mailbox_base = /var/mailboxes
virtual_mailbox_domains = hash:/etc/mail/postfix/vdomains
virtual_mailbox_maps = hash:/etc/mail/postfix/vmailboxes
virtual_minimum_uid = 1000
virtual_transport = dovecot
virtual_uid_maps = static:5000
unknown_local_recipient_reject_code = 550
*** Postfix master.cf ***
...snip...
dovecot unix - n n - - pipe
flags=DRhu user=maildrop:maildrop
argv=/usr/local/libexec/dovecot/deliver -e -d ${recipient}
Re: [Dovecot] Disable imap proxy access
Scott Silva a écrit : on 10/3/2007 3:25 PM Bazy spake the following: Ed W wrote: How to disable pop3 and imap access during the data migration process (duration 5 minutes to 10 minutes). Can i send a custom error message to our users ? I don't recall the exact details, but I think both options are possible if you check the dovecot wiki. There is a good study regarding the proxy stuff, and some notes on sending custom errors back (along with a note that it's not supported on many clients) If you use SQL then you could simply change the query temporarily Also when I do my migration I change the permissions on the home folders first (root:root say) - this way if I muck something up they don't get logged into the old mailbox. Then I reset the permissions back on the new server and update the proxy settings. This also gives a random error back to the client in the meantime if they try and log in. I should think that the above could even be scripted and run per mailbox for a very subtle downtime period... I use rsync once while the mailbox is online, then change perms so that the user can't login, then do a final rsync to get any changes across. I didn't check whether there is a problem with an existing connection still accessing the data after the perms were changed though... Good luck Ed W I'm not an perl expert, but... you could create a script that listens on port 143, and one for 110, that acts as a server. So right after .login username password the perl script will print an error, telling the client that the server is down for maintenance or something like that. Like when you get the 550 error in smtp and it says die spammer :). I think you can use IO::Socket::Telnet. Take a look over these scripts: http://www-user.tu-chemnitz.de/~uro/perlgoodies/server/ It's just an idea... Or just stop the dovecot running on the proxy and the connections will just die. Thanks for your answer, finaly the best solution is a simple chmod 0 on the /var/mail/domain.com ... migration, chmod 700 on the new disk, update the DB ... and wait about the cache TTL of the dovecot deliver ;-) One bash script and 80% of my 10'000 domains can be migrated to the new disk in less than 5 minutes. Thanks you Dom
[Dovecot] How to upgrade a running Dovecot?
Greetings - Could someone confirm how to perform various upgrades on a live system running Dovecot please? Scenario 1: Change to dovecot.conf === If I make a change to dovecot.conf am I right in thinking I can simply send a HUP signal to the main dovecot process to get it to re- read the configuration file and act on its revised content? Scenario 2: Altered SSL Certificates = I need to replace our current certificates and have prepared new files containing the replacement certificate and private key. Am I right in thinking that I can simply modify dovecot.conf to point at the new files and send a HUP signal to dovecot? Specifically, will new connections use the revised certificates, and existing connections continue to work OK without interruption? Scenario 3: Software Upgrade = I build a particular version of Dovecot into the tree /usr/local/ dovecot-A.B.C and then have a symlink called dovecot pointing at the this directory. To upgrade I can then build the new version into /usr/local/dovecot-X.Y.Z and test. To actually switch over the live service to the new X.Y.Z version do I need to: a) Totally shut down the old A.B.C version of Dovecot, thereby breaking all open connections for users? or b) Assuming I am using shutdown_clients = no can I just kill the master dovecot process and then start up the new version? Ideally I want existing connections to remain running, but new connections to start up using the new X.Y.Z version of Dovecot. The comment for shutdown_clients implies this, but also says: This however means that after master process has died, the client processes can't write to log files anymore. So if I understand this correctly then with shutdown_clients = no in force then the sequence and behaviour is this? ... 1. Old version A.B.C of Dovecot running, clients can log through the master dovecot process to the logfiles. 2. Kill the old master dovecot process, start new X.Y.Z version up. 3. New connections get served by version X.Y.Z. Old connections DON'T get killed and can continue, BUT can no longer write anything to the logfiles? With many thanks, Mike B-) -- The Computing Service, University of York, Heslington, York Yo10 5DD, UK Tel:+44-1904-433811 FAX:+44-1904-433740 * Unsolicited commercial e-mail is NOT welcome at this e-mail address. *
Re: [Dovecot] Dovecot + OCFS2
Hi, The load reaches 20, which is not that far from your MAX_DAEMON_CHILDREN directive in sendmail. You should try to find why the delivery processes are so slow to accomplish. Maybe it's a I/O backend problem. (I have experienced the same kind of problems with drbd writing, and slow hard disks) For example, during a mailling delivery, check the wait (wa) state of your cpu with the command 'vmstat 1'. A high value reflect the cpu time spent in waiting for I/O. Hope this helps, sam Jon Blazquez a écrit : Thank you for your response, With sendmail we have achieved to limit the load : define(`confMAX_DAEMON_CHILDREN', `15') define(`confCONNECTION_RATE_THROTTLE', `2')dnl define(`confQUEUE_LA', `5')dnl define(`confREFUSE_LA', `4')dnl With this configuration the LOAD only reaches 20 ;-) but it’s not the solution. The cluster is formed by 3 nodes. The load balancer sends mails to a node, when it's full (LOAD 4-5) it denies receiving more mails so the load balancer sends them to the following node in the cluster and so on... In the first node the load continues increasing until it reaches roughly 20, then it falls down. This is a temporary solution but we don’t know where exactly the problem is: dovecot’s deliver, ocfs2…. Any help would be appreciated, Jon Tomi Hakala escribió: Jon Blazquez wrote: The system works fine but when there are mailing lists the load increases dramatically. Any suggestions? First thing that I would do is to reduce number of concurrent deliver processes. I have no clue how this is done with Sendmail but with Postfix one could adjust deliver process maxproc value in master.cf. Tomi
Re: [Dovecot] Namespace hidden option not working?
List a mailbox if the requested pattern matches (prefix)(mailbox). should be: Only list a hidden mailbox if it matches the pattern, and the pattern explicitly starts with (prefix) (...and everything starts with )
Re: [Dovecot] Namespace hidden option not working?
On Wed, 3 Oct 2007, Ed W wrote: Hi You shouldn't have inbox = yes on more than one namespace. From the comments in my dovecot.conf: # There can be only one INBOX, and this setting defines which namespace # has it. #inbox = yes Sure. However, if only one has the INBOX, then doesn't this rather break the whole point of having the backwards compatible access to the INBOX? Am I missing the point? The namespace provides backwards compatible access to the folders under INBOX.. It doesn't have anything to do with the actual INBOX (an IMAP special name), which is still specified (for dovecot) by mail_location. I suspect that inbox=yes just tells dovecot what separator to return in: * LIST (\HasChildren) (separator) INBOX by associating INBOX with a separator= setting. I think you're also hiding the wrong namespace. You don't want to advertise the backwards-compatibility namespace to clients. If they're already using the old one, they can still use it, but you don't want new clients to start using it. Namespace-aware clients will adapt (in theory?). Possibly. Actually I decided that personally I prefer to have everything under INBOX., because all the clients I commonly use then nest the folders under INBOX (which I quite like). However, OE and Outlook are too dumb to figure this out and it's pointless telling all our customers to set the folder prefix when we could just support it working without needing to change anything... Anyway, the original question still stands! How come all my folders from both namespaces are being listed?? My guess is that you can't hide a namespace with an empty prefix. I haven't checked the source, but I suspect the logic of the LIST'ing process is along the lines of: List a mailbox if the requested pattern matches (prefix)(mailbox). Then, * can be seen as (empty-prefix)*, so (mailbox) matches. It seems logical. I don't see another way Dovecot could infer that the empty-prefix namespace was being requested. Best, Ben
[Dovecot] Dovceot user pop3 last connect info?
Dovecot experts, I am a newbie to Dovecot. I am in the process of replacing qpopper with dovecot to support pop 3 clients. I have installed the latest version of Dovecot on Fedora Core 6. Everything seems to be working fine using ldap, etc. However, with qpopper, I used to have .pop.username files which would give me a time stamp of the last time a user established a pop3 connection. I know that Dovecot has logs of connection in the /var/log/maillog files, but these files rotate out over a relatively short period of time. Is there a method by which one can keep track of the last time a pop3 connection was established for each user when using Dovecot? Tim Tyler Network Engineer - Beloit College [EMAIL PROTECTED]
Re: [Dovecot] Dovceot user pop3 last connect info?
On Thu, 4 Oct 2007, Tim Tyler wrote:
Dovecot experts,
I am a newbie to Dovecot. I am in the process of replacing qpopper with
dovecot to support pop 3 clients. I have installed the latest version of
Dovecot on Fedora Core 6. Everything seems to be working fine using ldap,
etc.
However, with qpopper, I used to have .pop.username files which would give
me a time stamp of the last time a user established a pop3 connection. I
know that Dovecot has logs of connection in the /var/log/maillog files, but
these files rotate out over a relatively short period of time. Is there a
method by which one can keep track of the last time a pop3 connection was
established for each user when using Dovecot?
You can do this (and many other things) through Post-Login Scripting:
http://wiki.dovecot.org/PostLoginScripting
See in particular “Last-login tracking”:
http://wiki.dovecot.org/PostLoginScripting#line-20
A simple example for your specific request:
In /etc/dovecot/dovecot.conf:
protocol pop3 {
# [etc.]
mail_executable = /full/path/to/custom-pop3.sh
Then, in custom-pop3.sh: (which needs to be chmod +x)
#!/bin/sh
touch /var/mail/.pop.$USER
exec /usr/libexec/dovecot/pop3
Best,
Ben
[Dovecot] Corrupt Message?
Dear List, Am accessing dovecot imap through squirrelmail. Squirrelmail paginates the message list into pages. All works fine except for the page one particular email is in. When I try to open that page (or in fact click 'show all') the server returns: ERROR: Bad or malformed request. Query: FETCH 549,551,555:557,563,565,567:569 (FLAGS UID RFC822.SIZE INTERNALDATE BODY.PEEK[HEADER.FIELDS (Date To Cc From Subject X-Priority Importance Priority Content-Type)]) Server responded: No mailbox selected. Could you possibly let me know what I should do and also how I can find the guilty mail file from that error? Can I just delete the email? Or is there a nice script to repair a dovecot maildir? Many thanks for your advice, Daniel -- Squirrelmail Stable 1.4.8 PHP 5.x Hardened with Eaccelerator Apache 2.x Imapproxy over Dovecot/Maildir all running on Gentoo Linux for ~5,000 users.
Re: [Dovecot] UIDL and IMAP
[I didn't see a response to this on-list. Sorry if I'm repeating someone.] On Mon, 1 Oct 2007, Kenneth Porter wrote: [...] I forgot to change the pop3_uidl_format setting [...] So he was seeing repeated downloads of all his mail (about 300 MBytes) every time he connected. [...] Does this setting in fact get used by IMAP? It's in the POP3 section, so I'm wondering if it takes effect when one is using IMAP from the client. No, it doesn't. IMAP unique identifiers are always 32-bit (unsigned) integers, expressed in base 10. (64 bits when combined with the 32-bit UIDVALIDITY) cf. RFC 3501 - IMAP 4rev1 discussion: http://tools.ietf.org/html/rfc3501#section-2.3.1.1 syntax: uniqueid - http://tools.ietf.org/html/rfc3501#page-91 POP3 UID's have significantly more variation (hence the dovecot setting): [ from RFC 1937 - POP 3 - http://tools.ietf.org/html/rfc1939#page-12 ] “The unique-id of a message is an arbitrary server-determined string, consisting of one to 70 characters in the range 0x21 to 0x7E, which uniquely identifies a message within a maildrop and which persists across sessions.” Best, Ben
Re: [Dovecot] How to upgrade a running Dovecot?
Have you considered sending out a message to each user to the effect that on some day, darned-early a.m. the system will be offline for 30 minutes for maintenance (no incoming email will be lost, etc., etc.). Message: 3 Date: Thu, 4 Oct 2007 13:57:03 +0100 From: Mike Brudenell [EMAIL PROTECTED] Subject: [Dovecot] How to upgrade a running Dovecot? To: Dovecot Mailing List dovecot@dovecot.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Greetings - Could someone confirm how to perform various upgrades on a live system running Dovecot please? Scenario 1: Change to dovecot.conf === If I make a change to dovecot.conf am I right in thinking I can simply send a HUP signal to the main dovecot process to get it to re- read the configuration file and act on its revised content? Yes, this is correct. Scenario 2: Altered SSL Certificates = I need to replace our current certificates and have prepared new files containing the replacement certificate and private key. Am I right in thinking that I can simply modify dovecot.conf to point at the new files and send a HUP signal to dovecot? Specifically, will new connections use the revised certificates, and existing connections continue to work OK without interruption? Ehh not really, the auth child processes can be killed and new ones started. See your next scenario question. Scenario 3: Software Upgrade = I build a particular version of Dovecot into the tree /usr/local/ dovecot-A.B.C and then have a symlink called dovecot pointing at the this directory. To upgrade I can then build the new version into /usr/local/dovecot-X.Y.Z and test. To actually switch over the live service to the new X.Y.Z version do I need to: a) Totally shut down the old A.B.C version of Dovecot, thereby breaking all open connections for users? or b) Assuming I am using shutdown_clients = no can I just kill the master dovecot process and then start up the new version? See the preface, do the update when you typically have few folks using the system -- which gives you fewer complaints from users should things break on their end. Ideally I want existing connections to remain running, but new connections to start up using the new X.Y.Z version of Dovecot. The comment for shutdown_clients implies this, but also says: This however means that after master process has died, the client processes can't write to log files anymore. So if I understand this correctly then with shutdown_clients = no in force then the sequence and behaviour is this? ... 1. Old version A.B.C of Dovecot running, clients can log through the master dovecot process to the logfiles. 2. Kill the old master dovecot process, start new X.Y.Z version up. 3. New connections get served by version X.Y.Z. Old connections DON'T get killed and can continue, BUT can no longer write anything to the logfiles? With many thanks, Mike B-) -- The Computing Service, University of York, Heslington, York Yo10 5DD, UK Tel:+44-1904-433811 FAX:+44-1904-433740 * Unsolicited commercial e-mail is NOT welcome at this e-mail address. * smime.p7s Description: S/MIME cryptographic signature
[Dovecot] Subscribe to root of Maildir namespace?
Our users currently make use of a single namespace, mbox format:
namespace private {
separator = /
prefix =
hidden = no
inbox = yes
location =
mbox:~/:INBOX=/var/spool/mail/%u:INDEX=/var/spool/poptemp/dovecot/%u
}
I'd like to give them access to additional Maildir-format storage area,
so to the above I've added:
namespace private {
separator = /
prefix = archive/
hidden = no
location =
maildir:/newmail/%-3.3i/%u/:INDEX=/var/spool/poptemp/dovecot/%u.a-thumper-mail
}
I can set up subfolders of archive/, and they work as expected.
I can also designate the root of archive/ as INBOX and that works properly.
But SUBSCRIBE archive fails.
Is it possible to subscribe to the root of this new Maildir heirarchy as
if it were just another folder? If not, would this be a useful feature to add?
Thanks,
--
Adam Tilghman | Systems Support / Academic Computing | +1 858 822 0711
[EMAIL PROTECTED] | University of California, San Diego | fax +1 858 534
7018
Re: [Dovecot] Deliver prints passwort to the syslog
Am Dienstag, 18. September 2007 15:52:57 schrieb Timo Sirainen:
On Tue, 2007-09-18 at 12:16 +0200, Dominik Schulz wrote:
Hi,
I've got the problem that dovecot's deliver prints the authentification
information to the syslog.
Like this:
Sep 18 12:11:22 mail deliver([EMAIL PROTECTED]): auth input:
[EMAIL PROTECTED]
Sep 18 12:11:22 mail deliver([EMAIL PROTECTED]): auth input: password=
Sep 18 12:11:22 mail deliver([EMAIL PROTECTED]): auth input:
home=/home/mail/domain.tld/user
Sep 18 12:11:22 mail deliver([EMAIL PROTECTED]): auth input: uid=8
Sep 18 12:11:22 mail deliver([EMAIL PROTECTED]): auth input: gid=8
I guess that it's only a configuration option but right now I can't
figure out which one I need to change to turn this off.
First of all it shouldn't be sent to deliver in the first place. What
userdb do you use and with what kind of a configuration? It shouldn't
return password field.
Once you've got that fixed, you can unset auth_debug=yes.
I'm using passdb sql and userdb prefetch/sql. auth_debug is set to no.
---
passdb sql {
args = /etc/dovecot/dovecot-sql.conf
}
userdb prefetch {
}
userdb sql {
args = /etc/dovecot/dovecot-sql.conf
}
---
Best Regards,
Dominik
