Patrick Westenberg wrote:
Ed W schrieb:
I'm using NexentaStor (Solaris, ZFS) to export iSCSI-LUNs and I was
thinking about a SSD based LUN for the indexes. As I'm using multiple
servers this LUN will use OCFS2.
Given that the SAN always has the network latency behind it, might you
be better t
I can't imagine running any kind of performance critical app on linux using
fuse! There is a native ZFS port going on, but I don't know how stable it
is yet.
-Original Message-
From: dovecot-boun...@dovecot.org [mailto:dovecot-boun...@dovecot.org] On
Behalf Of Patrick Westenberg
Sent:
that was lame. i tried posting a snippet of the sample dovecot.conf
file to show the part that the OP would want to change, and the mailer
bounced it with:
: permission denied. Command output: Don't post
your whole
dovecot.conf. Use dovecot -n instead.
Fooey...
Lars Täuber wrote:
Hi there.
How can I configure dovecot not to listen for imaps connections on port 143.
Thanks
Lars
You should be able to configure the dovecot.conf file to remove imaps as
one of the protocols.
e.g. like this line:
protocols = imap imaps
Ubuntu has a nice dovecot-postfix combo package.
No ideas? I googled some more and eventually turned up this posting:
http://www.mailinglistarchive.com/html/dovecot@dovecot.org/2011-01/msg00716.html
guy seems to be having the exact problem I am, unfortunately, no-one
replied to his post either :(
Running dovecot 1.2.12 on ubuntu 10.10. Here is the problem: I have
mysql backend for expire. I am using the dovecot-postfix package which
creates /etc/dovecot/conf.d/01-mail-stack-delivery.conf which looks like
this:
# Some general options
protocols = imap imaps managesieve
disable_plaint
Running dovecot 1.2.12 on ubuntu 10.10. Here is the problem: I have
mysql backend for expire. I am using the dovecot-postfix package which
creates /etc/dovecot/conf.d/01-mail-stack-delivery.conf which looks like
this:
# Some general options
protocols = imap imaps managesieve
disable_plaint
Okay, thanks. I'll live with it the way it is.
Dan Swartzendruber wrote:
I am using the antispam plugin and am very happy with it. I also have
a default sieve rule that I found online somewhere that says if you
see a message that is flagged as spam and not reclassified as
innocent, to mark it as seen and move it to the INBOX.SPAM folder
Speaking of "off-list", would you two kindly take this interchange...
off list?
Forgive me if this is a stupid question. I know that when I drag a
message to the SPAM folder, it is being trained properly, since the
stats indicate so. Dragging back to the inbox retrains it as ham. I
happened to notice that despite the fact that dspam says this in the
debug log:
"appe
I am using the antispam plugin and am very happy with it. I also have a
default sieve rule that I found online somewhere that says if you see a
message that is flagged as spam and not reclassified as innocent, to
mark it as seen and move it to the INBOX.SPAM folder. That too works
just fine
First off, I have to say I really like the antispam plugin. I am
running a (relatively) new freebsd 8.0 server with
postfix/dovecot/dspam/squirrelmail and it works great. Create a SPAM
folder and tell the dovecot antispam plugin to use INBOX.SPAM as the
spam folder and drag messages from INBO
14 matches
Mail list logo