similar to: Dovecot on Solaris

Displaying 20 results from an estimated 3000 matches similar to: "Dovecot on Solaris"

2007 Jan 24
1
[sfs@tc.umn.edu: Re: dovecot-auth file descriptor usage]
I hate to be a pest, but are there any revelations on file descriptor "overusage" by dovecot-auth? ----- Forwarded message from Steven F Siirila <sfs at tc.umn.edu> ----- Date: Sat, 20 Jan 2007 12:42:50 -0600 From: Steven F Siirila <sfs at tc.umn.edu> To: Dovecot Mailing List <dovecot at dovecot.org> User-Agent: Mutt/1.4.2.1i Subject: Re: [Dovecot] dovecot-auth file
2007 Jan 10
1
[sfs: dovecot-auth file descriptor usage]
I am re-posting this message from last Friday, as I have seen no replies. It is critical that we address this problem, since until then we cannot put more than a few hundred users on our server. If Dovecot-auth TRULY needs to keep open a file descriptor for every single login session, we will have to start looking at alternatives. In short: Help! ----- Forwarded message from Steven F Siirila
2006 Oct 26
2
www.dovecot.org misconfigured?
I am having difficulting getting to www.dovecot.org and wiki.dovecot.org. My browser tells me it can't find them. Anyone know what's up? -- Steven F. Siirila Office: Lind Hall, Room 130B Internet Services E-mail: sfs at umn.edu Office of Information Technology Voice: (612) 626-0244 University of Minnesota Fax: (612) 626-7593
2006 Oct 09
2
Dovecot LDA
On Sun, Oct 08, 2006 at 10:25:53PM +0300, Timo Sirainen wrote: > On Fri, 2006-10-06 at 21:00 -0500, Steven F Siirila wrote: > > I am running Dovecot 1.0-rc6 along with dovecot-sieve from 2006-10-05 CVS. > > I am calling dovecot deliver from Postfix (main.cf): > > > > mailbox_command = /opt/dovecot/libexec/dovecot/deliver > > > > Upon switching to dovecot
2007 Jan 09
1
some Maildir files not honoring dovecot-shared
I'm using RC15 on Solaris 9. The wiki indicates that when a dovecot-shared file exists, "Dovecot uses the same permissions and GID when it creates index files, dovecot-uidlist file, new mail files, etc." In my case, Dovecot *is* creating new index files based on dovecot-shared, but dovecot-uidlist and individual message files don't completely match the permissions/group
2007 Mar 19
2
Index files in .imap directory
A few RC releases ago we had a problem where a user's restored home directory contained a .imap folder either from a previous RC release or perhaps it was a different server. In any event, restoration of the user caused problems since Dovecot choked on the restored .imap index files. Removing those index files cleared the problem. I'm wondering if this is still an issue, and therefore
2006 Oct 17
4
Problem with rc10
I just upgraded our test server from rc6 to rc10... ISSUE #1 I noticed that we no longer are getting two "From_" lines. However, the one that was good (had the original sender e-mail address) is now gone. The one with "dovecot.deliver" remains. I attempted to add "-d test" to the mailbox_command line in main.cf as follows: mailbox_command =
2007 Feb 21
4
Solaris/SSLonly/Lots of Users
Anyone running Dovecot on Solaris, requiring only SSL connections, and servicing thousands of simultaneous users? Our past attempts to do so have failed due to dovecot-auth using up all 256 of its file descriptors. I say 256 since we are limited to that by the 32-bit libraries. We are looking at either compiling Dovecot in 64-bit and letting dovecot-auth file descriptors accumulate (not ideal),
2007 Mar 27
3
odd behavior with Dovecot LDA
Okay, to convince myself that quota handling was working okay with Dovecot 1.0-rc27 on Solaris 10, I tested sending a message to an account that was purposely over-quota. The account in question had a vacation message set up. For the first test, there was no $HOME/.imap directory at all. I received the vacation message, but the message which was supposed to be delivered locally queued in Postfix
2007 Jan 02
1
Dovecot 1.0-rc15 on Solaris 10
We are running Dovecot 1.0-rc15 on Solaris 10 and are starting to ramp up our user count and ran into a file descriptor limit: Jan 1 19:38:54 <hostname> dovecot: IMAP(username): Newly created index file is corrupted: /home/username/.imap/foldername/dovecot.index.tmp Jan 1 19:38:54 <hostname> dovecot: IMAP(username): file mail-index.c: line 1806 (mail_index_move_to_memory): assertion
2007 Mar 28
2
assertion failed (1.0-rc27)
Under Dovecot 1.0-rc27 on Solaris 10 we noticed this error today affecting one of our users repeatedly: Mar 28 14:02:01 myhost dovecot: IMAP(myuser): file mbox-sync-rewrite.c: line 423 (mbox_sync_read_and_move): assertion failed: (need_space == (uoff_t)-mails[idx].space) Mar 28 14:02:01 myhost dovecot: IMAP(myuser): Raw backtrace: 0x7ac54 -> 0x42cd4 -> 0x3e968 -> 0x3f54c -> 0x3f980
2007 Mar 21
1
mail looping
We are running Postfix 2.3.3 and Dovecot 1.0-RC27 on a Solaris 10 server. We use the Dovecot LDA for local delivery. Problems arise with looping mail whenever a user's .forward contains a reference to themselves. This most frequently occurs when a user sets up a vacation since it then puts this in their .forward file: \username, "|/usr/bin/vacation username" The vacation program
2007 Jan 05
2
Dovecot rc15 crash in mbox-sync-update.c
Here is another crash we've been seeing recently in rc15 on Solaris 10. (gdb) bt full #0 0xff1c12a4 in ?? () No symbol table info available. #1 0xff140040 in ?? () No symbol table info available. #2 0x000786a8 in t_buffer_alloc (size=688976) at data-stack.c:346 __PRETTY_FUNCTION__ = "file %s: line %" #3 0x00078190 in t_pop () at data-stack.c:149 frame_block = (struct
2007 Mar 23
2
Dovecot LDA issues
We've seen two issues come up with Dovecot LDA, both of which have caused us problems: 1) If the user's home directory does not exist, or is not owned by them, deliver fails and causes the mail message to bounce back to the originator. In our environment this happens when our user is moved to another server (where we move their files, but for up to 24 hours afterwards,
2007 Jun 13
4
Dovecot LDA munging INBOX access times?
We are running Dovecot 1.0.0 using mbox format (currently in the midst of conversion from UW IMAP). We discovered today that the Dovecot LDA is accessing the user's INBOX at delivery time! Not only do our users rely on this access time being when they last accessed their e-mail, we also rely on it to migrate "inactive" users to cheaper disk. I consider this a major bug for us and
2007 Apr 19
4
message-of-the-day feature?
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
2006 Oct 17
1
Index files
I am doing some testing with Dovecot and wondered if it was normal for the deliver program to create index files for an Inbox (the test Inbox is over 7MB), but to not update the index files after the initial creation, even though messages continue to come into the mailbox. Note that during this testing, no IMAP or POP accesses are being made. Would it matter if a command-line program such as
2006 Oct 17
1
Installation of Dovecot
When I configure Dovecot to conform to our directory hierarchy, it insists on adding 'dovecot/' to the prefixes I specify. Is there any way to inhibit this? My configure command is: ./configure --prefix=/opt/dovecot --sysconfdir=/etc/opt/dovecot \ --libexecdir=/opt/dovecot/libexec --localstatedir=/var/opt/dovecot \ --without-sql-drivers --with-ssl=openssl \
2006 Nov 20
1
Problem with rc10, perhaps 11-15
I don't recall if I mentioned this on the list, but when you are configured with mbox format, and a user has no Dovecot index files yet, and the config is such that mbox_min_index_size is set to non-zero, non-default (128 in my test case), dovecot deliver fails. Commenting out "mbox_min_index_size" fixed the problem, and the indexes then get created. This problems exists in RC10 --
2006 Nov 29
1
Logging
In trying to determine why someone was unable to use port 110 w/STLS (POP) I had great difficulty finding the session in which the user switched to this port from using port 995. This is because Dovecot does not log any port number information. Furthermore, it isn't obvious to me if it logs whether a session was negotiated SSL (via STARTTLS w/IMAP or STLS w/POP) or started out SSL (ports 993