On Fri, Jun 26, 2009 at 5:46 PM, Michael Orlitzky wrote:
> A typical "TLS" session will work as follows:
>
> 1 The client connects to the IMAP service on port 143, unencrypted.
> 2 The server announces that it speaks TLS.
> 3 The client says "Ok, let's talk encrypted."
> 4 Magic occurs, and the
Timo Sirainen wrote:
On Fri, 2009-06-26 at 23:39 +0400, Proskurin Kirill wrote:
SSL just binds to special port(like 993 in IMAP by default).
No, SSL is a protocol, just like TLS. It doesn't bind to any ports.
http://wiki.dovecot.org/SSL
To illustrate, both SSL and TLS as implemented in Dove
On Fri, 2009-06-26 at 23:39 +0400, Proskurin Kirill wrote:
> SSL just binds to special port(like 993 in IMAP by default).
No, SSL is a protocol, just like TLS. It doesn't bind to any ports.
http://wiki.dovecot.org/SSL
signature.asc
Description: This is a digitally signed message part
Carlos Williams пишет:
Is it talking about a actual SSL certificate or TLS?
You should read this:
http://en.wikipedia.org/wiki/Transport_Layer_Security
Your certificate is ok and will work with SSL&TLS.
SSL just binds to special port(like 993 in IMAP by default).
--
Best regards,
Proskurin Ki
On 6/26/2009 2:53 PM, Carlos Williams wrote:
> http://wiki.dovecot.org/SSL/DovecotConfiguration
>
> Is it talking about a actual SSL certificate or TLS?
>
> Thanks for any clarification!
There's no such thing as a 'TLC Certificate'... TLS uses standard SSL
certs, so just use your current one no
I am running Postfix and Dovecot on my mail server. I am required now
to have SSL/TLS on my mail server. I did check and found out that I
have a SSL certificate with Verisign issued to my mail servers FQDN.
Now my question is when reading the Dovecot Wiki, I noticed it said
that it is not common to
Hello,
On Thu, 2009-06-25 at 00:49 +0200, Mij wrote:
> I modified the wrapper to perform this escaping. With the new wrapper
> and dovecot v1.2rc6, authentication works fine for "dot users" too.
> See
> http://mij.oltrelinux.com/net/dovecot-qmail-vmailmgr/
> for further instructions.
Many thanks
Charles,
I haven't tested it with IMAP so I'm not sure. I was going to play with
that later. It could also be modified to ban failed SASL SMTP auths as
well. Here is the line in my /etc/fail2ban/filter.d/dovecot.conf file that
makes it work:
failregex = (?: Disconnected|Aborted
login).*r
On 6/26/2009, Rodman Frowert (rod...@thefrowerts.com) wrote:
> If anyone wants to see the fail2ban config file I am using for Dovecot, let
> me know...
Does it also work for IMAP ligins? I'd like to see it regardless... thanks!
--
Best regards,
Charles
Well concerning my problem, I adjusted fail2ban so that it can parse the
maillog and ban IP's that have 6 incorrect pop3 logins. I had another
"attack" last night, but fail2ban got him only have 6 attempts and banned
his sorry ass.
If anyone wants to see the fail2ban config file I am using fo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 26 Jun 2009, Robert Schetterer wrote:
Hallo Robert,
Hi Steffen, did you use a setup like described by example
acl sql
http://wiki.dovecot.org/SharedMailboxes/Shared
with mysql?
this is what i will need
but couldnt found any time yet to t
Steffen Kaiser schrieb:
> Hello,
>
> I noticed that entries added to the ACL dict are not removed, when an
> user no longer has explicit ACLs to another user, e.g.:
>
> [at the beginning no ACLs for "user"]
> 1 login testuser pwd
> 2 setacl INBOX user lp
> 3 deleteacl INBOX user
>
> Although "us
> > > Doing a "ps aux" on my Slackware box, I have approx 100 PID's of
> > > "pop3-login's going on. This is a production mail server, but it is
> > > getting VERY low traffic. In fact, only 3 people can "pop3" into it.
> > > I've check their e-mail clients, and they are not checking mail a
I was going to experiment with ACLs when I faced a small problem.
It is just sufficient to enable the acl plugin for getting the
behavior described hereafter.
When launching dovecot from the command line, one gets:
sh-3.2# /usr/local/dovecot/sbin/dovecot -F
ILoading modules from dire
14 matches
Mail list logo
