Re: SSL errors after certificate renewal
Separate subject, but couldn't help but notice, SSL3 is being used? Wasn't SSL3 retired because of POODLE exploits? Can someone more knowledgeable confirm? On 9/7/21 11:05, Steve Dondley wrote: On 2021-09-07 01:25 PM, Amol Kulkarni wrote: Hello, After I replaced my certificate with a new one yesterday, I'm seeing some ssl related errors. There are successful pop/imap logins using SSL also. So I think the certificate in itself is fine. No user has complained as yet, so I don't know for sure. However the count of errors has surely increased after installing the new certificate. There are 2 errors seen : dovecot: imap-login: Disconnected (no auth attempts in 1 secs): user=<>, rip=, lip =, TLS handshaking: SSL_accept() failed: error:14094416:SSL routines:SSL3_READ_BYTES:sslv3 alert certificate unknown: SSL alert number 46, session=<9m0AnVnL 2pHf4hso> dovecot: imap-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=, lip =, TLS: SSL_read() failed: error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate: SSL alert number 42, session= Kindly help with some pointers. Thanks and Regards, Amol I assume you tried restarting dovecot, but just in case...
Re: Non-user logins?
As Dave mentioned, Fail2ban. You'll likely want to set up graduated responses with fail2ban so the more they try, the longer it takes for them to get off the ban list. Best N On 1/7/22 20:35, Ken Wright wrote: On Fri, 2022-01-07 at 23:27 -0500, Dave McGuire wrote: On 1/7/22 11:24 PM, Ken Wright wrote: My Dovecot issues continue. Right now I see at least two issues: first, my logs consistently show non-users trying (and failing) to log in, and I'm still unable to log in from my email client (Evolution or Roundcube, either one). I'll post about the second issue later; right now I wonder why I'm getting so many non-users trying to log in. Am I the subject of concerted hacking attacks, or is there something else going on? Some of the attempted logins are more-or-less random names claiming to be @mydomain, but at least one is a username that's really on my server, to wit: Jan 7 22:52:01 grace dovecot: lmtp(776281): Error: lmtp-server: conn unix:pid=776262,uid=117 [3]: rcpt www-d...@mydomain.com: Failed to lookup user www-d...@mydomain.com: Internal error occurred. Refer to server log for more information. (Another quick question: which server log should I check?) So, if anyone can tell me what's going on with all these logins, I'd be much obliged! I see them all the time on the mail servers I run. Typical kids trying to mess with other peoples' stuff. I run fail2ban to catch those log entries and block the source IP address for a month on the first failed login. At any one time I have between 12,000 and 15,000 addresses in my blocked list for IMAP. Dave, that's exactly the kind of answer I was looking for. Fail2ban, huh? I'll have to check that out. Thanks again! Ken
Re: Pay Someone to Take My Online Course?1
I hope you guys took care of the spam from Xotawa earlier today. Also just as an FYI it looks like google is going to be changing their requirements for bulk-mail and mailing list senders effective February 2024. They have a notice on their blog with the specific requirements in the support knowledgebase (linked from their blog post). Also, randomly some of the responses from this mailing list are regularly hitting my spam folder. I count 3 from today, Ironically Xotawa was the only one that got through. Mailing list maintainers, if you aren't already using their postmaster tools you should check out https://support.google.com/mail/answer/9981691 Best Regards, N ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Piping to doveadm pw
Hello everybody, I am using 'doveadm pw' from inside a bash script to generate the salted hash for a user provided password. I call it like: doveadm pw -s SHA256-CRYPT -u $user -p $password Is there any possible way to use piping (so it won't show up in ps for example) to pass the username and password to 'doveadm pw' instead of using arguments? Dovecot version: 2.3.14 Many thanks, Kevin
Re: Piping to doveadm pw
Oscar del Rio wrote:
> On 2021-06-16 5:23 a.m., Kevin N. wrote:
> > I am using 'doveadm pw' from inside a bash script to generate the salted
> > hash for a user provided password.
> > I call it like: doveadm pw -s SHA256-CRYPT -u $user -p $password
> >
> > Is there any possible way to use piping (so it won't show up in ps for
> > example) to pass the username and password to 'doveadm pw' instead of using
> > arguments?
>
> % man doveadm-pw
>
> -p password
> ?? The plain text password for which the hash should
> be
> generated.?? If no password was given doveadm(1)?? will?? prompt interac???
> ?? tively for one.
> -u user
> ?? When the DIGEST-MD5 scheme is used, also the user
> name
> must be given...?? (so -u not needed here)
>
> % doveadm pw -s SHA256-CRYPT
> Enter new password: **
> Retype new password: **
> {SHA256-CRYPT}$5$yatls3zWaSMgSrue$FOlWYSb...
>
> % cat /tmp/test
> test123
> test123
>
> % cat /tmp/test | doveadm pw -s SHA256-CRYPT
> {SHA256-CRYPT}$5$rq.EciaKLycIT61g$smeKtkpQ
Thanks. Reading the manual was the first thing I did before posting to the list.
I'm not sure if this is relevant for the question, but I forgot to mention that
the user enters it's password through a 'dialog --passwordbox'.
I guess my question is: it possible to pipe that into 'doveadm pw' directly
from memory, without using any kind of on-disk temp file?
Re: Piping to doveadm pw
Bernardo Reino wrote:
> On Wed, 16 Jun 2021, Kevin N. wrote:
>
> > Thanks. Reading the manual was the first thing I did before posting to the
> > list.
> >
> > I'm not sure if this is relevant for the question, but I forgot to mention
> > that the user enters it's password through a 'dialog --passwordbox'.
> >
> > I guess my question is: it possible to pipe that into 'doveadm pw' directly
> > from memory, without using any kind of on-disk temp file?
>
> $ dialog --passwordbox .. | sed p | doveadm pw
>
> with "sed p" you print explicitly (p) and implicitly (default in sed) the
> input
> lines (i.e. whatever dialog returns), so doveadm gets the same line twice, as
> required.
>
> Cheers.
Thanks Bernardo. The "sed p" seems to do the trick.
I do have to do some validation before I pass the password to "doveadm pw", so
my code looks something like:
-
input_password=$(dialog --passwordbox ...)
#... some validation here ...
hashed_password=$(echo "${input_password}" | sed p | doveadm pw -s SHA512-CRYPT)
-
In this case will the password still be safe and hidden from a "ps" for example?
I am still new to all this and I wouldn't want to end up with a false sense of
security regarding this password passing :)
Doing an 'strace' on the script does show up the password in some reads, in the
form of: read(3, "password_here", ),
but not in execve(...) as parameter.
Cheers.
Dovecot mailing list and DKIM
Hello everybody, Going through my mail logs I noticed that a couple of messages from the Dovecot mailing list failed DKIM validation. For example, this one has failed: https://markmail.org/message/te7tycmpiutw4kia 'opendkim-testkey' shows that the key is OK. The messages in the example comes from yahoo.com, however other messages from yahoo.com, ones that are not sent through the mailing list, are properly validated. The failure is not specific to yahoo.com since a couple of other messages from other domains, sent though the mailing list, also failed DKIM validation. However, the vast majority of the messages from the list properly pass DKIM validation. From what I have read, mailing lists in general do not play very well with DKIM or SPF and the Dovecot mailing list also had some issues with this in the past. With the Dovecot mailing list, I am a bit curious about why the vast majority of the messages from the list pass DKIM validation while a couple of them fail. Does the Dovecot mailing list software alter the message in a way that causes the failure? Or is there something else going on? Any thoughts? Cheers.
Re: Dovecot mailing list and DKIM
No yahoo specific problem, as I stated in my previous post. An yes, my DKIM record validates successfully. But there are a couple of messages sent from other users, through the Dovecot mailing list, that fail DKIM validation, like the one in the example link. I am just curious why do the vast majority pass while some fail, even if they do have proper DKIM records :) . Cheers. On 20/06/2021 00:01, Benny Pedersen wrote: On 2021-06-19 16:21, Kevin N. wrote: Any thoughts? ARC-Authentication-Results: i=1; talvi.dovecot.org; dkim=pass header.d=notscheduled.eu header.s=vdsce95c9 header.b=lTA5iJYj; spf=pass (talvi.dovecot.org: domain of ke...@notscheduled.eu designates 185.125.111.71 as permitted sender) smtp.mailfrom=ke...@notscheduled.eu what is the problem for yahoo ?
Re: Dovecot mailing list and DKIM
Oh, I see. Thanks for the clarification Andreas. On 20/06/2021 00:58, A. Schulze wrote: Am 19.06.21 um 16:21 schrieb Kevin N.: Going through my mail logs I noticed that a couple of messages from the Dovecot mailing list failed DKIM validation. For example, this one has failed: https://markmail.org/message/te7tycmpiutw4kia dovecot.org use mailman-2.1.15 which is "a little bit (~9 years)" behind latest 2.1.34 Older version of mailman are know to modify some messages which break DKIM. That may be the reason for your observation. BTW: the ARC-Seal added by dovecot.org is invalid here, too Andreas
[BUG] doveadm / mail-crypt: Error when setting new password for a user key
Dovecot version: 2.3.14 When setting a new password for a user key you have the option to prompt the user for the old and the new password, instead of providing them as parameters (using -N and -O instead of -n and -o). However, running: doveadm mailbox cryptokey password -u user@domain -N -O produces an error instead of prompting the user for the old and the new password. The error is: password: option requires an argument -- 'O' You can work around this by providing a dummy input for -O which seems to be properly ignored in the end, but it would be nice to not throw any errors since -O should not expect an argument. Regards.
Re: Dovecot mailing list and DKIM
I never used FuGlu before. I'll take a look at it :) On 20/06/2021 02:38, Benny Pedersen wrote: On 2021-06-19 23:57, Kevin N. wrote: No yahoo specific problem, as I stated in my previous post. An yes, my DKIM record validates successfully. But there are a couple of messages sent from other users, through the Dovecot mailing list, that fail DKIM validation, like the one in the example link. I am just curious why do the vast majority pass while some fail, even if they do have proper DKIM records :) . if ARC specifikation tells more about C= tag in dkim, it would be more easy to see if its just that, relaxed is more simple to make dkim pass with then simple is, there might be alot of other problems giving random pass or fails, i just say its not possible to garenti that mail in transfer on public maillists or stupid sendgrid forwards with phishing netflix emails, it can only be trusted if ARC is done on any forwarders i am glad i do not use any milters currently since gentoo have disabled milter support in postfix so currently i am happy with fuglu :=)
Re: Quota Config With Prefetch Creating Alias Directories
For the first part of the issue maybe you could use Postfix's smtpd_restriction_classes combined with Dovecot's quota_grace, as described in this older thread: https://dovecot.markmail.org/thread/5sa563icpv2os2nb#query:+page:1+mid:gkhwgzfvipzaixtl+state:results I haven't tried it though. Cheers, Kevin On 27/06/2021 05:32, dove...@ptld.com wrote: On 06-26-2021 7:39 pm, dove...@ptld.com wrote: First question: Is this the best way to configure dovecot using quota verification for postfix to work will aliases? Second question: How can i prevent directories and indexes being created for non found user (aliases) accounts? I figured out i was doing it wrong, i removed the "result_failure = return-ok" and used "quota_status_nouser = DUNNO" instead. However, now i have another concern. * I setup an email account for u...@example.com * I setup an alias al...@example.com to forward to u...@example.com * I filled up u...@example.com inbox so it would fail quota. * I sent an email to al...@example.com Postfix did not reject the email, it accepted it and tried to deliver to dovecot/lmtp which then rejected the message for being over quota. This caused postfix to have to send a back splatter bounce email. Anyway to solve that? But worse, the bounce email exposed the forwarded to address of u...@example.com saying mailbox full. " (expanded from )" What can be done about that? Keep the bounce notice from exposing the forward to address? Or is there still a better way to set this up?
Re: Quota Config With Prefetch Creating Alias Directories
On a second thought, the previous suggestion doesn't seem to be what you are looking for. It looks like it only performs selective quota checking. Sorry. On 27/06/2021 10:45, Kevin N. wrote: For the first part of the issue maybe you could use Postfix's smtpd_restriction_classes combined with Dovecot's quota_grace, as described in this older thread: https://dovecot.markmail.org/thread/5sa563icpv2os2nb#query:+page:1+mid:gkhwgzfvipzaixtl+state:results I haven't tried it though. Cheers, Kevin On 27/06/2021 05:32, dove...@ptld.com wrote: On 06-26-2021 7:39 pm, dove...@ptld.com wrote: First question: Is this the best way to configure dovecot using quota verification for postfix to work will aliases? Second question: How can i prevent directories and indexes being created for non found user (aliases) accounts? I figured out i was doing it wrong, i removed the "result_failure = return-ok" and used "quota_status_nouser = DUNNO" instead. However, now i have another concern. * I setup an email account for u...@example.com * I setup an alias al...@example.com to forward to u...@example.com * I filled up u...@example.com inbox so it would fail quota. * I sent an email to al...@example.com Postfix did not reject the email, it accepted it and tried to deliver to dovecot/lmtp which then rejected the message for being over quota. This caused postfix to have to send a back splatter bounce email. Anyway to solve that? But worse, the bounce email exposed the forwarded to address of u...@example.com saying mailbox full. " (expanded from )" What can be done about that? Keep the bounce notice from exposing the forward to address? Or is there still a better way to set this up?
Re: [BUG] doveadm / mail-crypt: Error when setting new password for a user key
Hi Aki, Yes. Without -O the following error is thrown: result: dcrypt_key_load_private(...) failed: password missing Which makes sense since you need the old password for setting a new password for the user key. BTW: the behavior is the same on 2.3.15 too. Cheers, Kevin On 28/06/2021 08:46, Aki Tuomi wrote: On 20/06/2021 01:22 Kevin N. wrote: Dovecot version: 2.3.14 When setting a new password for a user key you have the option to prompt the user for the old and the new password, instead of providing them as parameters (using -N and -O instead of -n and -o). However, running: doveadm mailbox cryptokey password -u user@domain -N -O produces an error instead of prompting the user for the old and the new password. The error is: password: option requires an argument -- 'O' You can work around this by providing a dummy input for -O which seems to be properly ignored in the end, but it would be nice to not throw any errors since -O should not expect an argument. Regards. Hi! Did you try leaving -O/-o out? Aki
Re: [BUG] doveadm / mail-crypt: Error when setting new password for a user key
Super :) . You mentioned the bug number. Is there a publicly available location where Dovecot bugs are listed? Or that number is only an internal tracking number? Cheers, Kevin On 28/06/2021 09:15, Aki Tuomi wrote: Oh duh. Yeah. It's a bug. It's a known bug, DOP-2233. Lets see if we could get this fixed finally. Aki On 28/06/2021 09:12 Kevin N. wrote: Hi Aki, Yes. Without -O the following error is thrown: result: dcrypt_key_load_private(...) failed: password missing Which makes sense since you need the old password for setting a new password for the user key. BTW: the behavior is the same on 2.3.15 too. Cheers, Kevin On 28/06/2021 08:46, Aki Tuomi wrote: On 20/06/2021 01:22 Kevin N. wrote: Dovecot version: 2.3.14 When setting a new password for a user key you have the option to prompt the user for the old and the new password, instead of providing them as parameters (using -N and -O instead of -n and -o). However, running: doveadm mailbox cryptokey password -u user@domain -N -O produces an error instead of prompting the user for the old and the new password. The error is: password: option requires an argument -- 'O' You can work around this by providing a dummy input for -O which seems to be properly ignored in the end, but it would be nice to not throw any errors since -O should not expect an argument. Regards. Hi! Did you try leaving -O/-o out? Aki
[ENHANCEMENT] Doveadm HTTP API and the mail-crypt plugin
Hello everybody, I was wondering, are there any plans for the near future to include the mail-crypt plugin related functions, like changing the user key password, into the doveadm http api? It would probably be possible to implement it in a more secure way than any other external ad-hoc solution. Wouldn't it? Cheers, K.
Re: Dovecot book for a newbie
I am not aware of any Dovecot specific book, but maybe a good starting point would be the Dovecot Quick Configuration guide: https://doc.dovecot.org/configuration_manual/quick_configuration/ For Postfix, a good starting point could be the VIRTUAL_README and ADDRESS_CLASS_README pages: http://www.postfix.org/VIRTUAL_README.html http://www.postfix.org/ADDRESS_CLASS_README.html I've also heard good things about "The Book of Postfix". Even though it is quite old now, most of the parts/concepts/terminology still apply today. Part of it is also available on Google Books. Setting up a mail server for the first time can be a bit challenging and time consuming, but once you get a hold of things, it gets much easier :) Personally, I would take things step by step and not try to install and configure everything all at once. You could create a local isolated virtual environment with multiple VMs (ex: 1 authoritative DNS server for local testdomain1 and testdomain2, 1 mail server for local testdomain1, 1 mail server for local testdomain2) where you could experiment freely until everything works as expected. That way you are in control of the entire environment and you can easily debug any issues. Plus, it can be a good learning experience :) Once messages can be sent between the local test domains without any issues, you could take that configuration and, more or less, apply it to your internet facing mail server. Hi, Please recommend a Dovecot book for a newbie... I have a fair amount of Linux PHP hosting experience - LAMP virtual host configurations. I'm new to BIND, Postfix, and Dovecot. I'm running Ubuntu 20.04lts. Can send but not receive. Assuming everything else is set up correctly, did you check your firewall just to make sure that is not blocking incoming connections on your SMTP port? Cheers, K.
Re: Dovecot book for a newbie
I am not aware of any Dovecot specific book, but maybe a good starting point would be the Dovecot Quick Configuration guide: https://doc.dovecot.org/configuration_manual/quick_configuration/ For Postfix, a good starting point could be the VIRTUAL_README and ADDRESS_CLASS_README pages: http://www.postfix.org/VIRTUAL_README.html http://www.postfix.org/ADDRESS_CLASS_README.html I've also heard good things about "The Book of Postfix". Even though it is quite old now, most of the parts/concepts/terminology still apply today. Part of it is also available on Google Books. Setting up a mail server for the first time can be a bit challenging and time consuming, but once you get a hold of things, it gets much easier :) Personally, I would take things step by step and not try to install and configure everything all at once. You could create a local isolated virtual environment with multiple VMs (ex: 1 authoritative DNS server for local testdomain1 and testdomain2, 1 mail server for local testdomain1, 1 mail server for local testdomain2) where you could experiment freely until everything works as expected. That way you are in control of the entire environment and you can easily debug any issues. Plus, it can be a good learning experience :) Once messages can be sent between the local test domains without any issues, you could take that configuration and, more or less, apply it to your internet facing mail server. > Hi, > > Please recommend a Dovecot book for a newbie... I have a fair amount of Linux PHP hosting experience - LAMP virtual host configurations. I'm new to BIND, Postfix, and Dovecot. > > I'm running Ubuntu 20.04lts. > > Can send but not receive. Assuming everything else is set up correctly, did you check your firewall just to make sure that is not blocking incoming connections on your SMTP port? Cheers, K.
Re: [ENHANCEMENT] Doveadm HTTP API and the mail-crypt plugin
On 29/06/2021 22:58 Kevin N. wrote:
Hello everybody,
I was wondering, are there any plans for the near future to include the
mail-crypt plugin related functions, like changing the user key
password, into the doveadm http api?
It would probably be possible to implement it in a more secure way than
any other external ad-hoc solution. Wouldn't it?
Cheers,
K.
It is already there, you just need to load mail_crypt plugin.
{"command":"mailboxCryptokeyGenerate", "parameters":[
{"name":"allUsers","type":"boolean"},
{"name":"socketPath","type":"string"},
{"name":"user","type":"string"},
{"name":"transFlags","type":"integer"},
{"name":"userFile","type":"string"},
{"name":"userKeyOnly","type":"boolean"},
{"name":"reEncryptBoxKeys","type":"boolean"},
{"name":"force","type":"boolean"},
{"name":"mailbox","type":"string"}
]},
{"command":"mailboxCryptokeyList", "parameters":[
{"name":"allUsers","type":"boolean"},
{"name":"socketPath","type":"string"},
{"name":"user","type":"string"},
{"name":"transFlags","type":"integer"},
{"name":"userFile","type":"string"},
{"name":"userKey","type":"boolean"},
{"name":"mailbox","type":"string"}
]},
{"command":"mailboxCryptokeyExport", "parameters":[
{"name":"allUsers","type":"boolean"},
{"name":"socketPath","type":"string"},
{"name":"user","type":"string"},
{"name":"transFlags","type":"integer"},
{"name":"userFile","type":"string"},
{"name":"userKey","type":"boolean"},
{"name":"mailbox","type":"string"}
]},
{"command":"mailboxCryptokeyPassword", "parameters":[
{"name":"allUsers","type":"boolean"},
{"name":"socketPath","type":"string"},
{"name":"user","type":"string"},
{"name":"transFlags","type":"integer"},
{"name":"userFile","type":"string"},
{"name":"clearPassword","type":"boolean"},
{"name":"askNewPassword","type":"boolean"},
{"name":"newPassword","type":"string"},
{"name":"askOldPassword","type":"string"},
{"name":"oldPassword","type":"string"}
]}
Aki
Perfect. Thank you :)
K.
Notifications to over-quota accounts
Hello! I'm trying to allow a system email address to send notifications to over-quota accounts. Is there a way to do it? Thanks in advance! ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Iteration base for LDAP
Greetings, The iteration machinery uses the LDAP search base set with the "base" directive (typically from dovecot-ldap.conf.ext); the same base used during nominal operations (e.g., passdb/userdb searches). Consider a directory: dc=ROOT |_ dc=foo,dc=com,dc=ROOT(foo.com subtree) |_ dc=bar,dc=net,dc=ROOT(bar.net subtree) A search base setting appropriate for mail operations might be: base = dc=%Dd,dc=ROOT # e.g. dc=foo,dc=com,dc=ROOT for u...@foo.com This fails when iterating, as the variable substitution is meaningless in this context (and even a static subtree search base would only cover a portion of the overall directory during iterative searches). Setting the base to "dc=ROOT" obviously solves the issue at the expense of searching the entire directory for all operations. This is less than optimal. I could not find a way to override this setting at runtime via a doveadm option or similar. Ideally, a separate "iterate_base" setting would solve this issue. Any other solutions? Thanks, /taso
Re: [Dovecot] Dovecot 2, Imap service, client_limit
Hi All Exchange meeting plugin is not working , I am not able to save calendar request .. need help . Can some one help me -Original Message- From: dovecot-boun...@dovecot.org [mailto:dovecot-boun...@dovecot.org] On Behalf Of Mark Moseley Sent: Wednesday, July 20, 2011 4:38 AM Cc: dovecot@dovecot.org Subject: Re: [Dovecot] Dovecot 2, Imap service, client_limit On Tue, Jul 19, 2011 at 3:56 PM, Steve Fatula wrote: > I see back in November of last year, a thread about using client_limit > in the imap service (not imap-login) that would allow each imap > process serve more than one connection. Sounded good, until I tried it! > > When I did, unlike the OP of that thread, I got: > > dovecot: imap(submit.user): Fatal: setuid(503(submit.user) from userdb > lookup) failed with euid=501(links): Operation not permitted (This > binary should probably be called with process user set to > 503(submit.user) instead of > 501(links)) > > So, it would appear that this does not work. Still, the thread was > posting results of their testing even that showed it worked. > > Sample message within the thread, read for more: > > http://www.dovecot.org/list/dovecot/2010-November/054893.html > > I'd love to be able to use a single imap process for more than one connection. > Is this still possible, or, not? If so, how? > > Steve > > In my case, we use a single shared user for all mailboxes, so there's no UID issue. The imap process is always running as that one UID, so it doesn't ever try to setuid to something else. Timo, is there some way/setting to only let client_limit != 1 apply to processes running as the same user? I.e. if a imap process (with client_limit > 1) was running as UID 501 (to use the OP's uids), and imap-login needed to send UID 503 to an imap process, it wouldn't send it to the one running as UID 501, but rather either create new imap proc or if UID 503 already had a imap proc running, then send UID 503 to that one. (I realize that makes almost no grammatical sense, but hopefully you know what I mean). Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html";>http://www.techmahindra.com/Disclaimer.html externally and http://tim.techmahindra.com/Disclaimer.html";>http://tim.techmahindra.com/Disclaimer.html internally within Tech Mahindra.
Re: [Dovecot] Namespace subscription issue
The same issue appears to exist with the shipping version of Dovecot on Mac OS X Server 10.6+. I have shared namespaces that cause this same issue (and your subsequent issues with roundcube). -- Eric N. Jones Sr. Engineer TransWare Enterprises Inc.
[Dovecot] help
Hi I have postfix-2.4.7 and Dovecot 1.0.7 integrated with Windows Active Directory , I have some issue here . can dovecot create the mailbox in the same case which is stored in AD ( eg if my Samaccountname attribute is GuruPrasad or Test123 ) , can the mailbox be created in same case and can it deliver the mail to the same path. Config details attached . 1 Dovecot 1.0.7 2 dovecot -n # 1.0.7: /etc/dovecot.conf login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login mail_location: maildir:~/Maildir mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh imap_client_workarounds(pop3): outlook-idle pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login username_format: %Lu passdb: driver: pam userdb: driver: passwd userdb: driver: static args: uid=502 gid=502 home=/var/mail/%u socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html";>http://www.techmahindra.com/Disclaimer.html externally and http://tim.techmahindra.com/Disclaimer.html";>http://tim.techmahindra.com/Disclaimer.html internally within Tech Mahindra.
[Dovecot] Still virtio problems
Hello! As posted on May 27th this year, dovecot 2.1.7 does not allow for the mailstore to be located in a virtio partition. I still receive fstat()-errors on the lock files in this combination: May 27 12:54:51 host dovecot: imap(test@mydomain): Error: fstat(/var/vmail/mydomain/test/.quotausage.lock) failed: No such file or directory May 27 12:54:51 host dovecot: imap(test@mydomain): Error: file dict commit: file_dotlock_open(/var/vmail/mydomain/test/.quotausage) failed: No such file or directory May 27 12:54:51 host dovecot: imap(test@mydomain): Error: fstat(/var/vmail/mydomain/test/Maildir/dovecot-uidlist.lock) failed: No such file or directory Config includes: mmap_disable=yes dotlock_use_excl=no Any ideas? Thanks Erich
[Dovecot] Permission for /var/run/dovecot
I have just installed my mail server on a Ubuntu Linux V.7.10 box with sendmail and dovecot imap from the Ubuntu packages. Each time the machines boots, I get the following messages: Starting mail server: dovecotWarning: Fixing permissions of /var/run/dovecot to be world readable Warning: Corrected permissions for login directory /var/run/dovecot/login After the boot the permissions visible are: drwxr-xr-x root root/var/run/dovecot drwxr-x--- root dovecot /var/run/dovecot/login What permissions do I need to set so that the warnings do not appear?
