Hi Timo,
Thanks very much for spotting this... 4 hours spent tweaking the wrong
config... Doh! :-).
All working now.
:wq
On 8 Mar 2010, at 22:35, Timo Sirainen wrote:
On Mon, 2010-03-08 at 22:06 +, Greg Frith wrote:
gr...@rhy:/etc/dovecot$ sudo dovecot -n
# 1.1.11:
On Tue, 2010-03-09 at 11:31 +0100, Thomas Leuxner wrote:
On Tue, Mar 09, 2010 at 01:04:44AM +0200, Timo Sirainen wrote:
Yeah, it's this one. I'll probably revert it soon. I did it mostly while
trying to fix istream-zlib bugs, but hopefully zlib won't break when
that change is reverted :)
On 2010-03-08 11:00 AM, Carlos Mennens wrote:
On Mon, Mar 8, 2010 at 10:55 AM, Timo Sirainen t...@iki.fi wrote:
Dovecot supports looking up user information from MySQL, but not
actually storing mails there. If you really wanted to store mails on
MySQL, you'd have to use dbmail instead of
On Tue, Mar 09, 2010 at 01:21:40PM +0200, Timo Sirainen wrote:
With LMTP or also with LDA? What's the backtrace now? It seems to be
working with me.
Only tested with LMTP as not using LDA anymore, but in the same manner, with a
simple handshake:
Program received signal SIGSEGV, Segmentation
On 2010-03-09 6:23 AM, Marcio Merlone wrote:
Anyway, a better solution to handle user account information than mysql
is ldap (which I personally suggest) with pam. This can also handle all
posix accounts, not just mail accounts, and thus improving consistence.
I'd use that for any system with
Hi
We run dovecot 1.2.10 on Solaris 10 and had a few days ago this error
message in the logs:
Mar 6 21:48:55 dovecot: [ID 583609 mail.crit] IMAP(username): Panic: file
istream-raw-mbox.c: line 583 (istream_raw_mbox_get_body_size): assertion
failed: (rstream-body_offset != (uoff_t)-1)
Mar 6
Em 9/3/2010 08:07, Charles Marcus escreveu:
???
You aren't listening. Storing *email* in mysql is a totally different
concept from storing USER DATA in mysql.
You do NOT have to switch to dbmail to change your config to start using
MySQL for managing your user accounts.
Personally, I would
On Tue, 2010-03-09 at 14:41 +0100, Marcus Rueckert wrote:
On 2010-03-09 14:30:14 +0100, Robert Schetterer wrote:
sql storage would be a nice idea anyway for clustering loadbalancing
setups etc
looked into drbd?
DRBD is nice when all your users fit into a single server that is
replicated
Am 09.03.2010 13:33, schrieb Charles Marcus:
On 2010-03-09 6:23 AM, Marcio Merlone wrote:
Anyway, a better solution to handle user account information than mysql
is ldap (which I personally suggest) with pam. This can also handle all
posix accounts, not just mail accounts, and thus improving
On Tue, Mar 09, 2010 at 10:48:59AM -0300, Zilon X wrote:
Hello Thomas,
Thank you - but I found nothing specific to Solaris there.
Already installed Postfix 2.7.0, Mysql 5.1, Dovecot 1.2.10, and
Posfixadmin 2.3 on a Solaris 10 Sparc zone.
Still a lot of quirks on configuration here.
I
Hello Thomas,
Thank you - but I found nothing specific to Solaris there.
Already installed Postfix 2.7.0, Mysql 5.1, Dovecot 1.2.10, and
Posfixadmin 2.3 on a Solaris 10 Sparc zone.
Still a lot of quirks on configuration here.
I also want to configure Roundcube 0.3.1 with this Dovecot/Postfix
With the latest fix from Mercurial it does not crash anymore. The message shows
empty and the container in question 'm.59.broken' stays in the 'storage' dir.
Is this expected behavior and am I save to delete the broken container, or how
would I clean up the corruption?
Regards
Thomas
On Tue, 2010-03-09 at 14:30 +0100, Robert Schetterer wrote:
sql storage would be a nice idea anyway for clustering loadbalancing
setups etc
And NoSQL storage would be even better for that :) My plan is still
http://www.dovecot.org/list/dovecot/2009-August/041983.html, that would
allow adding
On Tue, Mar 09, 2010 at 01:04:44AM +0200, Timo Sirainen wrote:
Yeah, it's this one. I'll probably revert it soon. I did it mostly while
trying to fix istream-zlib bugs, but hopefully zlib won't break when
that change is reverted :) Started my stress test again..
Just tested and does not
Most curious.
Hm, I had two servers NFS-sharing mail data (and, in turn, dovecot.sieve*). One
was at 1.2.3 and a sieve not supporting the date extension, the other one was
at 1.2.7nb1 (meaning 1.2.7 plus e47eb506eebd) and I was getting errors also on
that server. I updated the other one to
On Tue, 2010-03-09 at 16:40 +0100, Thomas Leuxner wrote:
With the latest fix from Mercurial it does not crash anymore. The message
shows empty and the container in question 'm.59.broken' stays in the
'storage' dir. Is this expected behavior and am I save to delete the broken
container, or
On Tue, 2010-03-09 at 12:13 +0100, mailingli...@belfin.ch wrote:
We run dovecot 1.2.10 on Solaris 10 and had a few days ago this error
message in the logs:
Mar 6 21:48:55 dovecot: [ID 583609 mail.crit] IMAP(username): Panic: file
istream-raw-mbox.c: line 583
On 03/09/2010 05:02 PM Greg Frith wrote:
Hi all,
Sorry, I thought a migration to /etc/dovecot/dovecot-postfix.conf would do
the trick, but it would appear (after several hours of grappling with a new
problem) that 'something' is still reading configuration information from
Hi,
apparently the following change in dovecot hg
* New revision (10876:370ee9717a6c) in dovecot Mercurial repository:
- config: Forgot to add header file.
broke
listen = 83.170.6.69, 2001:1b10:1000::110:1:1
mail.svr02.mucip.net:~# dovecot -F -c /etc/dovecot/dovecot.conf
doveconf:
On 9.3.2010, at 20.00, Thomas Leuxner wrote:
Am 09.03.2010 um 18:54 schrieb Thomas Leuxner:
Could not resync it to the Inbox but the message is still in 'm.59.broken'
and the source looks undamaged. Any easy way to restore? No biggie if it is
lost, but just out of curiosity, once an
Am 09.03.2010 um 19:01 schrieb Timo Sirainen:
Is it in the fixed m.59? The fixing/resyncing was supposed to preserve all
mails.
Actually 'm.59' was not rebuilt but it continued with new containers. Grepping
for the content, it remained in the broken container only.
Regards
Thomas
Am 09.03.2010 um 19:02 schrieb Timo Sirainen:
I guess this imap session was open while doveadm was running?
You are right.
Hi there, im currently using dovecot 0.99.11 (dovecot-0.99.11-4.EL4) on
Centos 4.4 i386
/var/log/maillog has started to produce several times per minute this entry:
Mar 9 14:52:44 mail pop3(albrook): Timeout while waiting for release of
fcntl() lock for mbox file /var/mail/albrook
when this
On 2010-03-09 3:03 PM, Erick Perez wrote:
is this a problem in the 0.99 version?
can i safely upgrade to 1.2?
You'll have to , since 0.99 hasn't been supported in a long, long, long
time... ;)
But as long as you can follow the directions for upgrading, you should
be fine:
thanks Charlesim upgrading nowwil do another post if needed!!
On Tue, Mar 9, 2010 at 3:06 PM, Charles Marcus cmar...@media-brokers.comwrote:
On 2010-03-09 3:03 PM, Erick Perez wrote:
is this a problem in the 0.99 version?
can i safely upgrade to 1.2?
You'll have to , since 0.99
hi All,
One of my users created this sieve script via roundcube's avelsieve
implementation:
# This script has been automatically generated by avelsieve
# (Sieve Mail Filters Plugin for Squirrelmail)
# Warning: If you edit this manually, then the changes will not
# be reflected in the users'
On Fri, 05.03.2010 at 09:44:35 +, Ed W li...@wildgooses.com wrote:
I would be all in favour of a setting like this because it's easier
to configure than fail2ban...
There's also denyhosts. http://denyhosts.sourceforge.net/
-Terry
27 matches
Mail list logo
