for any help anyone can give.
Guy
--
Don't just do something...sit there!
/dev2_aluminati.net/Maildir/.Deleted
Items/dovecot.index.log
Is there anything I can do to compensate for situations like this?
Thanks
Guy
--
Don't just do something...sit there!
On 24/04/2008, Timo Sirainen [EMAIL PROTECTED] wrote:
Have you set maildir_copy_with_hardlinks=yes?
Yes, that's already set. I've also added:
default_mail_env = maildir:%h/Maildir/:INDEX=MEMORY
after reading the suggestion somewhere.
The server is only running one domain so far so it's not
access to both mail stores and I'm assuming
that that is what's causing the problem.
I'm running dovecot 1.0.10 (Ubuntu - so I'm using only packages
provides by aptitude at the moment).
Should dovecot be able to handle access by multiple machines for the indexes?
Thanks
Guy
--
Don't just do
/etc and when I
try and start dovecot it looks for the libexec dir in /usr/local
instead of /usr.
Is there something I'm missing on the configure?
I've very, very little experience (rather obviously) installing
directly from source so any advice would be greatly appreciated.
Thanks
Guy
--
Don't
Thanks for everyone's input. I was already sudoed to root before
running any of the operations so it wasn't that. May have been that
--with-storages error I'd made. I tried your config John, with mods
for my system and besides having to add the dovecot user/group
manually it seems to be running
.
Is there a gotcha that I'm unaware of or have I done something stupid
(which seems the most likely :P)?
Thanks
Guy
--
Don't just do something...sit there!
to
15 seconds it would still fail the allow_nets check and then get a
cache hit and be logged in.
If there's any other information I can provide please let me know.
Thanks
Guy
--
Don't just do something...sit there!
Dovecot/Maildrop/Maildir to
Dovecot/deliver/mdbox if 2.0 is likely to be reasonably safe to use in the
next month or so.
Thanks
Guy
--
Don't just do something...sit there!
to a random mail server (they
both have access to the NFS shares), won't I run into the same index
problem? Should I look at per user transports before then or can director
also be used to effect Dovecot deliver?
Thanks
Guy
--
Don't just do something...sit there!
/syslog or /var/log/mail.log or
similar.
The postfix mailing list is probably what you're looking for:
http://www.postfix.org/lists.html
And you should give this a quick read before posting:
http://www.postfix.org/DEBUG_README.html#mail
Guy
--
Don't just do something...sit there!
:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed
or bad record mac
If this isn't already a known error, is there any extra data I can
collect that would help diagnose what's causing it? I haven't a clue
where to start with this sort of debugging I'm afraid.
Thanks
Guy
--
Don't just do
intermittent I'm not sure where to start. Since there
are no real errors in the Dovecot logs I'm suspecting that haproxy is
perhaps not routing every packet correctly leading to Dovecot not
getting all the data needed for the connection. Are there any other
possibilities I've missed?
Thanks
Guy
r
for the userdb and passdb lookups at the moment. Is it
possible to specify separate auth files with different MySQL lookups
per protocol?
Thanks
Guy
--
Don't just do something...sit there!
NFS. I'm looking for better performance but still
keeping the HA element I have now with shared storage over NFS.
Has anyone had experience with a setup like the one I'm suggesting?
What was performance like with Dovecot using GFS?
Thanks
Guy
--
Don't just do something...sit there!
included dovecot -n below.
Thanks
Guy
#dovecot -n
# 1.1.8: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.24-23-server x86_64 Ubuntu 8.04.2
protocols: imap imaps pop3 pop3s
listen(default): *:143
listen(imap): *:143
listen(pop3): *:110
ssl_listen(default): *:993
ssl_listen(imap): *:993
ssl_listen(pop3
. If the account is
still using over 100% of quota after the 7 days then the 100% quota is
enforced so no new mail will be accepted.
So is something like this burst quota possible in the Dovecot plugin?
Thanks
Guy
--
Don't just do something...sit there!
, which is running just fine, but is there
anything I can do to help trace what was causing the problem?
Unfortunately I don't have a clue where to start.
Thanks
Guy
--
Don't just do something...sit there!
peoples' experience with 2.0 is like
so far? Is it reasonably stable already?
Is there also a page showing the differences in config for dbox over
maildir? Or is it simply just the change in mail_location and nothing else?
Thanks
Guy
--
Don't just do something...sit there!
wouldn't use NFS with multiple servers accessing it again for
Dovecot. Looking at a clustered FS on SAN solution at the moment.
Cheers
Guy
--
Don't just do something...sit there!
installing Dovecot from
source under Ubuntu as they're lagging well behind. Karmic still only has
Dovecot 1.1.11.
Cheers
Guy
--
Don't just do something...sit there!
Hello,
SiS is implemented and stable in the last version ?
Best Regards
Guy
Timo Sirainen tss at iki.fi writes:
On 19.9.2011, at 11.27, Tom Clark wrote:
Is there anyway of whitelisting an IP so that it can ignore
mail_max_userip_connections=10?
With v2.0 in theory:
remote 1.2.3.4 {
mail_max_userip_connections = 0
}
I don't know if it actually works.
23 matches
Mail list logo