Re: [Dovecot] Dovecot 1.2.16 and Thunderbird 5 - pop3 mails not getting deleted
On 08/06/2011 01:32 AM, Ian Evans wrote: I run a Dovecot 1.2.16 pop3 server and have just started using the Thunderbird 5 email client. Thunderbird is set to leave the messages on the server unless they are over 91 days old. However, I'm not seeing it delete any of the older messages. I'll run a debug run of Thunderbird when I get back home, but I'm just wondering if there's any gotcha's I should be aware of with Thunderbird and Dovecot in a pop3 environment. The Thunderbird folks are wondering if it's the server not the client. Thanks. Perhaps this is related to this bug I posted: http://www.dovecot.org/list/dovecot/2011-August/060461.html We still have no fix or confirmation from the developers. A workaround is to disable creation of indexes.
Re: [Dovecot] Dovecot 1.2.16 and Thunderbird 5 - pop3 mails not getting deleted
On Mon, 2011-08-22 at 09:10 +0300, Kostas Zorbadelos wrote: On 08/06/2011 01:32 AM, Ian Evans wrote: I run a Dovecot 1.2.16 pop3 server and have just started using the Thunderbird 5 email client. Thunderbird is set to leave the messages on the server unless they are over 91 days old. However, I'm not seeing it delete any of the older messages. I'll run a debug run of Thunderbird when I get back home, but I'm just wondering if there's any gotcha's I should be aware of with Thunderbird and Dovecot in a pop3 environment. The Thunderbird folks are wondering if it's the server not the client. if thunderbird follows the same principles of every other pop3 client out there maybe it would delete them, pop3d only does what it is asked to do, it can not be the server if just one single other client that follows relevant RFC's works Many people have always had gripes with thunderbird not doing this or that, there's always something, tell your clients to use a compliant client, or webmail. signature.asc Description: This is a digitally signed message part
[Dovecot] LDA and auth-userdb socket permissions
Hi,
just wanted to check this as the wiki seems to have contradictory
information. With respect to running the LDA as multiple UIDs the wiki
says:
[QUOTE]If you're using more than one UID for users, you're going to
have problems running dovecot-lda, as most MTAs won't let you run
dovecot-lda as root[/QUOTE]
But in the example for the config file the text reads:
[QUOTE]
service auth {
unix_listener auth-userdb {
mode = 0600
user = vmail # User running dovecot-lda
#group = vmail # Or alternatively mode 0660 + dovecot-lda user in
this group
}
}
[/QUOTE]
So it says you can stick the LDA user just in the (vmail or whatever)
group and that is enough. So you aren't restricted to a single UID for
access anymore...
I tested this and the later did not work, that is if I put my LDA user
in the group for the auth-userdb socket with permissions 0660 I got an
error back from dovecot saying that the owner was incorrect.
So, as it stands I guess the bit about setting group should be removed
from the wiki?
Secondly, why doesn't this currently work? Why is the owner all important?
thanks Andy.
Re: [Dovecot] Help With 'No SASL Authentication Mechanisms' Error
On 2011-08-21 4:24 PM, resea...@the10thfloor.com resea...@the10thfloor.com wrote: DOVECOT: # 2.0.beta6 (3156315704ef): /etc/dovecot/dovecot.conf UPGRADE. -- Best regards, Charles
Re: [Dovecot] Duplicate Email with Dovecot Sieve
General Qmail log: @40004e4d1d7b2965966c info msg 1337024: bytes 2257 from testu...@gmail.com qp 15984 uid 113 @40004e4d1d7b2965a60c starting delivery 62510: msg 1337024 to local u...@xx.org @40004e4d1d7b2965b5ac status: local 1/10 remote 0/100 @40004e4d1d7b390469a4 delivery 62510: success: did_1+0+1/ @40004e4d1d7b3905119c status: local 0/10 remote 0/100 @40004e4d1d7b39058ab4 end msg 1337024 Upon reading up on understanding qmail logs, I found out that the did_1+0+1 in my logs means that Qmail was successful in delivering to Maildir (first 1) and also it was able to pass the email to an external program (last 1; in this case Dovecot's deliver). So I guess that is why I am getting 2 emails. However, I do not know why qmail still delivered to Maildir when it should have passed on the delivery to Dovecots deliver program. As I understand it the correct delivery should log did_0+0+1 which means that qmail handed the email to an external program successfully and did not deliver the email to Maildir itself. Is this what is to be expected? Thank you for some pointers. Holden
Re: [Dovecot] Duplicate Email with Dovecot Sieve
On 8/22/2011 8:39 AM, Holden Hao wrote: Upon reading up on understanding qmail logs, I found out that the did_1+0+1 in my logs means that Qmail was successful in delivering to Maildir (first 1) and also it was able to pass the email to an external program (last 1; in this case Dovecot's deliver). So I guess that is why I am getting 2 emails. However, I do not know why qmail still delivered to Maildir when it should have passed on the delivery to Dovecots deliver program. As I understand it the correct delivery should log did_0+0+1 which means that qmail handed the email to an external program successfully and did not deliver the email to Maildir itself. Is this what is to be expected? Thank you for some pointers. Holden As I suspected, this is an MTA issue. Apparently, you have two parallel local delivery transports configured. I have no idea how this is configured in Qmail and what exactly you may have done wrong. Although other people on this list probably do have knowledge of Qmail configuration, MTA-related questions are mostly off-topic, so you may not get an answer here. I suggest you contact the guys at qmail. Regards, Stephan.
Re: [Dovecot] Duplicate Email with Dovecot Sieve
As I suspected, this is an MTA issue. Apparently, you have two parallel local delivery transports configured. I have no idea how this is configured in Qmail and what exactly you may have done wrong. Although other people on this list probably do have knowledge of Qmail configuration, MTA-related questions are mostly off-topic, so you may not get an answer here. I suggest you contact the guys at qmail. Thank you very much for your reply. I have also sent an email to the Qmail list. I will report back if I resolve this issue. Regards, Holden
Re: [Dovecot] mail spool filesystem
On 8/19/2011 10:49 AM, Seth Mattinen wrote: On 8/17/11 7:42 AM, Adrian Ulrich wrote: I read that XFS is a good choice, but is not too reliable... Are you using Maildir or MBOX? In any case: XFS would be my last choice: XFS is nice if you are working with large files ( 2GB), but for E-Mail i'd stick with ext3 (or maybe even reiser3) as it works very well with small files. I'd have to disagree. This is completely anecdotal, but I originally deployed ext3 on all of my mail servers (Dovecot maildir) and spools (Postfix) until they started exhibiting loading issues when busy. Reformatting into XFS resolved the problem with no other changes. I didn't have time to do any comparisons or gather statistics since it was an emergency situation and this was before ext4, but XFS has performed flawlessly for me. ~Seth +1. :) -- Daniel
[Dovecot] Large Mailbox Slow
Doubt if there is any answer to this but will ask anyway. Have a few pop3 accounts with thousands of messages. Its slow when checking email naturally. Are there any tweaks to speed it up? I imagine there is an exchange of the message and header list which is the slow down. Too bad the list could not be compressed with gzip or something first. I think http has an option similar to that. Just asking.
[Dovecot] Default and per-User sieve script
Hi guys, is there any way to configure Dovecot to process the default sieve script and, after that, a user specific script? I have a default script to sort spam into a spam folder but if a user specific script is present, the default script is ignored. sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_global_path = /usr/local/etc/dovecot/sieve/default.sieve Regards Patrick
Re: [Dovecot] Large Mailbox Slow
Doubt if there is any answer to this but will ask anyway. Have a few pop3 accounts with thousands of messages. Its slow when checking email naturally. Are there any tweaks to speed it up? I imagine there is an exchange of the message and header list which is the slow down. Too bad the list could not be compressed with gzip or something first. I think http has an option similar to that. Just asking. I am running Maildir format on CentOS 5.x 64bit with Ext3 on raid1. Often wander if Ext4 would have been better.
Re: [Dovecot] Default and per-User sieve script
On 2011-08-22 4:03 PM, Patrick Westenberg wrote: Hi guys, is there any way to configure Dovecot to process the default sieve script and, after that, a user specific script? I have a default script to sort spam into a spam folder but if a user specific script is present, the default script is ignored. sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_global_path = /usr/local/etc/dovecot/sieve/default.sieve Regards Patrick http://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration see sieve_before= in the Executing Multiple Scripts Sequentially section. -Greg signature.asc Description: OpenPGP digital signature
Re: [Dovecot] Disconnected: Too many invalid IMAP commands
On 08/20/2011 05:25 PM, Sahil Tandon wrote: On Sat, 2011-08-20 at 14:38:25 -0700, Steve Fatula wrote: I see lots of these messages in the log file for one machine and account. Near as I can tell, the client still works (it's mine), but, the messages concern me. Is there some known issue with Apple mail, or, if not, how to capture the information needed to debug? Use tcpdump to packet capture the problematic session. Or Dovecot's rawlog.
Re: [Dovecot] Large Mailbox Slow
Only thing that comes to my mind is to use shorter uidl's to id each email, not sure what method your using now. I would seriously consider just changing it to use imap instead, then you can be notified if there is a new email, instead of downloading the list each time. Quoting Matt lm7...@gmail.com: Doubt if there is any answer to this but will ask anyway. Have a few pop3 accounts with thousands of messages. Its slow when checking email naturally. Are there any tweaks to speed it up? I imagine there is an exchange of the message and header list which is the slow down. Too bad the list could not be compressed with gzip or something first. I think http has an option similar to that. Just asking. I am running Maildir format on CentOS 5.x 64bit with Ext3 on raid1. Often wander if Ext4 would have been better.
Re: [Dovecot] Update indexes with dovecot 1.1
On 19.8.2011, at 12.13, Angel L. Mateo wrote: I have a farm of dovecot 1.1 servers (debian lenny). Mailboxes are in Maildir format. Is there any way to manually update indexes? v2.0 has doveadm index command to do this. There's no other good way to do this. Does it worth? I mean... Our problem is that mail is delivered via dovecot lda, but, because we have a farm of servers, we don't guarantee that mail is delivered through the same server that the user is using for his imap connection, so the imap server could have this index unupdated. So I want to force an update (or at least nearly updated) in order to have the index updated in all servers at the time the user get to work. Doing it via IMAP won't guarantee that everything the user's client needs is indexed/cached. Different clients need different things, Dovecot only indexes stuff that client requests. You'd have to look up from index files what the client wants indexed and then perform IMAP commands requesting those fields. Even the act of doing this may mess up caching decisions, because user may have changed client and now it's indexing unnecessary fields. (Actually now that I think of it, doveadm index has this same problem. Have to get that fixed.) With v2.0 you could if you use Dovecot proxy (or director) you can also proxy doveadm connections through it, so a doveadm index would always go to the correct server. http://wiki2.dovecot.org/Director at the bottom has some info how to set this up (works also with plain proxy, without director).
