Am 09.07.2012 21:29, schrieb Stan Hoeppner:
SAS is found today almost exclusively in high volume transactional
servers such as mail spools, mail stores, databases, VM image storage,
and applications that need higher reliability, such as medical imaging
systems, etc.
and SAS may not be faster
Am 09.07.2012 21:41, schrieb Reindl Harald:
in these environments you find near to zero SATA
only few people these does are doing bare metal installs in days
where hardware supported virtaliziation has nearly zero overhead
Hi Harald, that simply not true
i have thousends of mailbox users on
Le 10/07/2012 08:13, Robert Schetterer a écrit :
Am 09.07.2012 21:41, schrieb Reindl Harald:
in these environments you find near to zero SATA
only few people these does are doing bare metal installs in days
where hardware supported virtaliziation has nearly zero overhead
Hi Harald, that
Am 10.07.2012 05:59, schrieb Stan Hoeppner:
That's simply not true Reindl.
SATA drives are being used very widely in production today, and
outnumber SAS deployments by a very wide margin.
for SOHO with no public services, yes
Google has more public facing services, servers, than
Is it possible to have mail_max_userip set to a value for localhost
(webmail) and to another value for everything else?
Best regards
Federico Bianchi
Dipartimento di Storia delle Arti
Universita` di Pisa
On 10.7.2012, at 8.31, Frank Bonnet wrote:
Would it be possible to close this thread from Dovecot mailing-list ?
Yeah, enough with this thread.
On 7/10/2012 2:24 AM, Federico Bianchi wrote:
Is it possible to have mail_max_userip set to a value for localhost
(webmail) and to another value for everything else?
mail_max_userip as the name suggests is a per user IMAP socket
connection limit. So you should be able to set it to one value
On Tue, 10 Jul 2012, Stan Hoeppner wrote:
On 7/10/2012 2:24 AM, Federico Bianchi wrote:
Is it possible to have mail_max_userip set to a value for localhost
(webmail) and to another value for everything else?
mail_max_userip as the name suggests is a per user IMAP socket
connection limit.
why does dovecot touch any ever used fuse-mountpoint
and scream at the next start that is no longer mounted?
If this is intentional, remove it with doveadm mount
why if i never called doveadm on any setup at all?
Jul 10 09:10:56 rh dovecot: master: Dovecot v2.1.8 starting up (core dumps
I'm trying to setup per user '+spam' delivery from amavis tags, so that
each user gets any mails tagged as spam to 'spam' Maildir via +spam
Dovecot lmtp delivery.
after say 7 days I want to delete all spams older than 7 days,
if I simply delete mail files from the file system, is that a 'bad
why does dovecot touch any ever used fuse-mountpoint
and scream at the next start that is no longer mounted?
If this is intentional, remove it with doveadm mount
why if i never called doveadm on any setup at all?
Because you never read any docs.
Am 10.07.2012 13:25, schrieb Voytek Eymont:
I'm trying to setup per user '+spam' delivery from amavis tags, so that
each user gets any mails tagged as spam to 'spam' Maildir via +spam
Dovecot lmtp delivery.
i have no amavis, i use a global sieve rule to deliver tagged mail into
special Junk
Am 10.07.2012 13:34, schrieb Robert Schetterer:
Am 10.07.2012 13:25, schrieb Voytek Eymont:
I'm trying to setup per user '+spam' delivery from amavis tags, so that
each user gets any mails tagged as spam to 'spam' Maildir via +spam
Dovecot lmtp delivery.
i have no amavis, i use a global
Dovecot lmtp delivery.
after say 7 days I want to delete all spams older than 7 days,
if I simply delete mail files from the file system, is that a 'bad thing' ?
i don't use lmtp so maybe i'm wrong but if you use maildir format just
deleting/moving files always work properly
On 07/10/2012 01:25 PM, Voytek Eymont wrote:
I'm trying to setup per user '+spam' delivery from amavis tags, so that
each user gets any mails tagged as spam to 'spam' Maildir via +spam
Dovecot lmtp delivery.
after say 7 days I want to delete all spams older than 7 days,
if I simply delete
Hello,
i've found an old thread [1] where it was stated that a whole mailbox
can be made read-only only setting the according permissions on the
filesystem side.
[1]
http://www.mailinglistarchive.com/html/dovecot@dovecot.org/2011-12/msg00300.html
i'd like to check if it's still the only
if I simply delete mail files from the file system, is that a 'bad thing' ?
[...]
IMHO 7 days is dangerously too short. False positives during vacations
happen too ;-)
I would suggest at least 30 days (as used by Gmail).
or use spam system that NEVER actually receive something it thinks it is
On 07/10/2012 07:11 PM, Wojciech Puchar wrote:
if I simply delete mail files from the file system, is that a 'bad
thing' ?
[...]
IMHO 7 days is dangerously too short. False positives during vacations
happen too ;-)
I would suggest at least 30 days (as used by Gmail).
or use spam system
Timo Sirainen wrote:
On 29.6.2012, at 19.21, Daniel Parthey wrote:
Jun 29 15:40:31 10.129.3.249 dovecot: doveadm(use...@domain1.example.org):
Error: user use...@domain1.example.org: Error reading configuration:
net_connect_unix(/var/run/dovecot/config) failed: Permission denied
I've
Hi all,
I'm using dsync for backups. I recently upgraded to 2.1.7 due to issues
with dsync mirror/backups. 2.1.7 fixed the issue with the guid conflict,
but now I'm seeing this error on a couple of mailboxes:
Error: proxy client timed out (waiting for output stream to flush, 0
bytes left)
Rerunning the dsync command right after the timeout (see previous
message) gave me these errors:
dsync-local(vmail): Error: remote: dsync-remote(vmail): Error: Corrupted
dbox file /home/.incoming_mail_migrations/users/user%domain.com/mdbox/s
torage/m.60 (around offset=807789): msg header has bad
21 matches
Mail list logo
