Re: [Dovecot] Unable to send email out using Dovecot SASL
I am currently using Dovecot 1.0.rc17 with Postfix 2.3.8 on Ubuntu. When you choose to use software with known bugs and security issues that have already been fixed in later versions, you really should make sure you know exactly what all of those issues are and whether or not they affect you. So far I'm able to receive my email using dovecot pop3 but I can't send out the email. Why not? Error messages and a postconf -n might help here. What do I missed out? Have you read: http://www.postfix.org/SASL_README.html what were the results when you went through the troubleshooting steps? -- Kenny Dail [EMAIL PROTECTED]
Re: [Dovecot] dovecot Digest, Vol 50, Issue 54
- SMP kernels: page size cut once in a while does several hundred in about 4 minutes count as once in a while? Got many page size cut on 2.6.17-gentoo-r8 #2 SMP i686 Dual Pentium III (Katmai) no output from a FreeBSD 4.9-RELEASE-p5 single Pentium III (Katmai) -- Kenny Dail [EMAIL PROTECTED]
Re: [Dovecot] Dovecot] dovecot performance question
Hi, using the latest dovecot with pop3/imap. Using mostly outlook 2003 for pop3 and squirrel mail imap. I have a lot of users reporting back that imap is very slow. We average about 300 imap and another 700 pop session at any given time. reporting that imap is slow or that squirrelmail is slow? ;) How is the load average on the server? We found at our site to keep Apache/squirrelmail happy, we dedicated a server for our webmail users. Mostly being a RAM issue in that case. Just how beefy is the server you are using? I am having a time issue on this server and im not sure if its affecting dovecot. May 29 11:42:19 pop dovecot: POP3(xxx): Time just moved backwards by 1 seconds. I'll sleep now until w e're back in present. May 29 11:42:19 pop dovecot: POP3(xxx): Time just moved backwards by 1 seconds. I'll sleep now until w e're back in present. May 29 11:42:31 pop dovecot: POP3(xxx): Time just moved backwards by 1 seconds. I'll sleep now until w e're back in present. May 29 11:42:42 pop dovecot: POP3(xxx): Time just moved backwards by 1 seconds. I'll sleep now until w e're back in present. It'll affect it in that you will be having 1 sec delays frequently it seems. You should definitely look into fixing that. That is bad behavior for a busy mail server. -- Kenny Dail [EMAIL PROTECTED]
Re: [Dovecot] Namespace Problems
Hi all,
after an update from dovecot beta version to 1.0.0.-1 today morning I
had different effects:
thunderbird-, kmail-, Apple-clients, pine and squirrelmail could
receive email correct with imaps. But not MSOutlook!!!
Varying the namespace configurations in dovecot.conf I got different
results with MSOutlook working but with thunderbird, squirrelmail etc.
all folders are displayed but not the root Inbox etc.
Its important to know that I migrated from courier-imap to dovecot.
My well working namespace config BEFORE upgrade to 1.0.0-1:
Here my actual namespace configs:
namespace private {
separator =
prefix = INBOX.
inbox = no
hidden = no
}
namespace private {
separator = /
prefix = INBOX/
inbox = no
hidden = yes
}
namespace private {
separator = .
prefix = INBOX.
inbox = yes
hidden = yes
}
Try it using only one namespace which matches what you are really doing.
With 1.0 this works for me with all clients I've tried, including Apple.
namespace private {
separator = .
prefix = INBOX.
inbox = yes
hidden = no
}
In varying inbox and hidden keywords I found this configuration. Most
things are working with this but in squirrelmal I can't access inbox,
the main folder.
How do I have to configure that everythings works satisfying??
dovecot.conf and dovecot-sql.conf I send in the attachment.
instead of sending dovecot.conf, next time use dovecot -n
--
Kenny Dail [EMAIL PROTECTED]
Re: [Dovecot] Quota handling - v2 - updated FR
This revised proposal for a Feature Request is the result of my desire to implement quotas, but not have the attendant headaches that inevitably accompany its implementation. Ralf Hildebrandt wrote: I have to face it, my users are retards: Is there any other kind of user? ;) snip Thus I need a feature in dovecot that will tell them via email: Level1: You ALMOST exceeded your quota, you're at 90% now Level2: You're very close to exceededin your quota, you're at 95% now Level3: Would you please clean up now? You're at 99% now What I'd *really* like to see implemented is something along the lines outlined below - but of course, this will depend entirely on whether or not Timo thinks it is doable - or desirable... I'm thinking this would be best handled by the Quota plug-in - either as part of the current one, or as a separate/different one... *** 1. Have a 'special' user-specific folder (by special, I mean like the Drafts, Sent, Templates folders) that dovecot controls. For purposes of this FR, call it the 'over-quota' folder. Question: could the .tmp folder be used for this? No sense in reinventing the wheel if necessary... and then if someone migrated from dovecot to something else, and messages were left in there from an over-quota condition, that other solution would most likely just move these to .new the first time it ran, right? Or, possibly, could dovecot create a new one maybe, .oqt (for over-quota), and store the queued messages there until the over-quota condition was rectified? Anyway, the main thing is, this folder should be essentially hidden from the user so they do *not* have access to it, and should temporarily hold messages that come in that are unable to be delivered due to an over-quota condition. *** 2. Make dovecot aware of and use a special 'Quota Status' message that it uses to inform a user that they are over quota. This message should be able to be customized, with variables (like, for example, it should list the messages that are currently being prevented from being moved to the Inbox - including, optionally, the Subject, the sender, date/time, attachments, size, etc - as well as provide general quota information (ie, how close to or over quota they are, and how much they'd need to delete or move to Local Folders to allow delivery of all of the messages being held), and lastly, any custom information the System Admin wanted to provide - like, maybe, specific instructions for how to move messages to Local Folders, how to request additional storage allowance, etc. *** 3. When user is over quota, have LDA deliver to the folder referenced above (# 1) - (yes, accept the message for final delivery from the sending mta), and then update the Quota Status message and move it to the Inbox. Optionally, a bounce/notification could be generated to the sender, informing them that their message is being 'held in queue' or something to that effect, due to the recipient being over-quota. *** 4. Once the user deletes enough mail to come back under quota, dovecot would then move messages from the 'over-quota' folder to his Inbox. Ok, again, am willing to hear *valid* reasons how/why this is a terrible idea... :) How is this different from just telling the customer there quota has been increased by the size of their .oqt box? Quota is there for a reason at my work, to stop accepting mail if the user already has too much mail. As we deal with customers, and can't just fire them for being too stupid, it is much better to give them a clear policy with no fuzzy grey areas. I think this also better in the case of the few employees I have to support as well. A hard bounce is the right way to go in this case, because it will let the sender know right away that there is a problem sending to the user. A soft bounce may take days of retrying before the sender is aware of a problem, especially since very few servers can handle a quota bounce at the smtp level. The recipient is probably going to be oblivious that a problem exists because if they are over quota, it usually means they haven't been checking their mail and will not see a quota warning message. 89% of the cases I see of users over quota, is due to negligence. 10% is for mailboxes that are no longer in use. I wouldn't think it a good idea to allocate extra disk space to either of these cases. The other 1% calls us to ask for more space which we gladly sell to them. -- Kenny Dail [EMAIL PROTECTED]
Re: [Dovecot] Conflict - Dovecot + Maildrop (maildirsize)
As I said in my original mail, this is simply a configuration issue: Looks like you're trying to tell the quota in bytes to Dovecot. Dovecot wants it to be in kilobytes in its configuration file / userdb (it still writes it in bytes to maildirsize, as you can see above it writes 1GB * 1024 value in there). Where do you get the quota value for Dovecot? Divide it by 1024 and it'll work right. I also use maildrop + dovecot. My quotas are stored in a mysql DB in couriers expected format: 5000S (note the S on the end for storage). It makes for a very ugly userdb query trying to get that formatted to dovecot style of maildir:storage=48828:ignore=Trash How much would it take to allow dovecot's quota plugin to alternately accept maildir:5000S:ignore=Trash? -- Kenny Dail [EMAIL PROTECTED]
[Dovecot] Digest settings
Timo, Wonder if you can tweak the digests to hold more messages? In 5 hours this morning, I've received 6 digests, seems a little excessive to me. -- Kenny Dail [EMAIL PROTECTED]
Re: [Dovecot] Moving new email from the mail spool to the inbox
Adrian Barker wrote: We are considering switching from the Washington UW IMAP server to Dovecot for performance reasons, but we make use of the feature in the UW server that automatically moves new email from the mail spool to the IMAP INBOX. Has anyone implemented this in Dovecot, or considered implementing it ? We have a large number of users, so cannot easily change the way that we deliver email. Andy Shellam wrote I'm thinking this is more of an issue with your MTA, as usually that's responsible for delivering into the mailbox's Inbox. You might want to look at Dovecot's LDA, deliver (http://wiki.dovecot.org/LDA). Deliver takes an e-mail piped from your MTA, with appropriate options on the command-line, and delivers it into the relevant mailbox correctly. Adrian Barker wrote: Thanks for replying. We cannot easily change the way we deliver email, as we have over 30,000 users, who use a mixture of imap, pop and Unix email clients, so we have to continue to deliver email to a central mail spool. The MTA that we run is Exim, which has the flexibility to deliver into the 'Inbox', but we need to remain compatible with non-IMAP mailers. This is not clear at all, why does the number of users effect the delivery method? What mailbox format are you using? -- Kenny Dail [EMAIL PROTECTED]
Re: [Dovecot] Courier-imap + dovecot simultaneously?
I have a client I've been trying to talk into switching from courier to dovecot, but the owner of the company wants me to set up two different accounts in Thunderbird (I finally got him switched to that from outlook express), one accessing his account through courier, and one through dovecot, so he can compare the speed... Is this even possible? I've never tried it before, so before I spend a lot of time, I want to know if I'd be wasting it (my time)... Yes, it's possible. You just have to set the 2 servers up on separate ports and make sure the correct ports are set in Thunderbird. I'm not sure what would happen with dovecot's index files but most likely if courier does something goofy they will just get rebuilt. Have you actually done it? I have Dovecot set up on port 10993, but before I actually fire it up, I want to make sure it isn't going to hose anything. I will backup the maildirs in question before I do bring dovecot up, of course, but still wouldn't want to do anything that might mess anything up. The index files are my main concern. Courier will ignore them. So they may be out of sync if you move a lot of messages around with Courier, but Dovecot will update them. I guess the safest thing to do is to tell postfix to queue his mail so nothing gets delivered while he's messing around, then let him play - see how fast folders load, etc (he's got some pretty big ones, 30,000 messages or more)... The safest thing to do, of course, is to back up. Thanks - I'll wait and see if anyone else chimes in - I like to get more than one opinion, and to hear from at least one person who has actually done what I'm about to do, when trying something like this (that I've never done before)... I've done similar, my mailstore is on nfs, and had completely different servers both accessing it. And yes, Dovecot was much much faster. -- Kenny Dail [EMAIL PROTECTED]
Re: [Dovecot] Any plans for storing messages on a database?
Redudancy and recovering from a mailstore failure is one of the concerns I am trying to address where I work. Any plans to have Dovecot store emails in a database? NAS/SAN devices which do automatic replication to a second device are extremely expensive. Worth checking out is openfiler: http://www.openfiler.com/ I also don't see any distributed filesystem which is mature and available for the OS we use (FreeBSD). A well designed NAS/SAN will work well regardless of the client OS. -- Kenny Dail [EMAIL PROTECTED]
Re: [Dovecot] LSUB vs LIST (hacked Apple Mail problem)
On 25. apr. 2007, at 20.06, Robert Schetterer wrote: Hi, as i have one customer on courier only with apple mail i got known of so many bugs with imap that i must say this is a broken client in my eyes I don't disagree, but it's the least broken imap client that I know of for the Mac, and I've learned to live with most of its quirks by now. Eyvind Bernhardsen I agree Apple's mail client is full of crazy bugs, but it has been working just fine for me since I upgraded to Dovecot 1.0.0. I've tried a variety of other IMAP clients on my mac from time to time, but I keep coming back to Apple mail. The second place is probably Opera's mail client, but I don't like the fact it won't use an IMAP trash folder, other than that, it is really quite good. -- Kenny Dail [EMAIL PROTECTED]
Re: [Dovecot] dovecot Digest, Vol 48, Issue 71
* On 19/04/07 10:13 -0500, Steven F Siirila wrote: | For lack of a better name, we are interested in a feature where one could | get a notice out to all Dovecot users as quickly as possible, possibly | without going through an MTA even. Given a message and a list of userids | we could certainly do a mailing on the MDA server itself going through | both Postfix and Dovecot LDA. However, we were wondering what other options | we might have in Dovecot. For example, would it be possible to place the | message into some file which Dovecot periodically checks for, and if the | file exists, either present it to the user as a new message, or automatically | deliver it at that time via Dovecot LDA? It's a really nice feature! We have something like that with tpop3d (Chris Lightfoot's). tpop3d is nolonger maintained but it's rock solid as a POP3 daemon. It gives this feature via some perl hooks (plugin, I'd call it, for lack of the proper word atm) and works very well. It serves the bulletin without any reference to the MTA, and keeps a DB of those users who have received/retrieved/pop-ed the bulletin(s) so that they don't get them twice. It's one feature I will surely miss if I migrated to dovecot 100%. It would seem to me to be easy enough to do this with post-login scripting http://wiki.dovecot.org/PostLoginScripting -- Kenny Dail [EMAIL PROTECTED]
Re: [Dovecot] rc2x seems to break Pegasus Mail
I upgraded from rc7 to rc24 a couple weeks ago, and noticed today that Pegasus Mail's IMAP no longer connects. So I put rc27 in, and it worked, but only for a little while... failure to connect is a bit non-specific. usually when one of my customers tell me that, it's a client/firewall/anti-virus issue. Are the logs showing a connect attempt at all from that IP? Have you tried Pegasus from a different machine? -- Kenny Dail [EMAIL PROTECTED]
