Am 18.03.2013 01:02, schrieb Larry Stone:
On Mar 17, 2013, at 4:50 PM, Robert Schetterer r...@sys4.de wrote:
Am 17.03.2013 21:12, schrieb Larry Stone:
Giving complex answers to simple questions creates the impression that the
Dovecot is far more complex than it needs to be.
mail isnt
On 18/03/2013 03:10, Alex wrote:
https://www.rapidsslonline.com/
less than $20/year, takes literally 15 minutes from start to having
a certificate. Well, maybe 30 minutes the first time when you need
to read everything.
There are probably dozens of other sites offering similar services;
I've
Yes,
proxy log says that its over TLS.
but the server is receiving username and password in plain text. I verified
it in wireshark.
I am using squirrelmail web client n had configured it for STARTTLS.
*My dovecot settings for Server:*
suja@mailserver:/etc/dovecot# dovecot -n
# 1.2.15:
Hello,
I'm trying to install dovecot as LDA, IMAP server and Sieve functions,
all of this with a Postfix, Spamassassin and a MySQL Auth.
When I use a Sieve script, it 's loaded but actions are not respect
with this logs :
Mar 18 10:31:19 localhost dovecot: lda(i...@info.xx.com): Debug:
Am 18.03.2013 10:36, schrieb pvsuja:
passdb {
args = host=10.131.1.16
default_fields = userdb_imapc_user=%u userdb_imapc_password=%w
driver = imap
}
Well, I dunno where you listened with wireshark, but as far as I see you
communicate between your proxy and the other server with
Are you sure you wheren't looking at the ldap communication for the
username+password instead of imap?
Is ldap configured to use ssl?
Quoting pvsuja pvs...@gmail.com:
Yes,
proxy log says that its over TLS.
but the server is receiving username and password in plain text. I verified
it in
Hello!
This is probably another basic question and i'm not even sure if it's
something where Dovecot is involved, but i'll give it a shot.
So i've setup Postfix with Dovecot and system-auth on my remote
server. So far it looks like everything is working fine and dandy via
SASL(PLAIN) and TLS.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 18 Mar 2013, Clement PAULET wrote:
When I use a Sieve script, it 's loaded but actions are not respect with this
logs :
The sieve script just trying to redirect to INBOX.Test folder but doesn't
works..
First of all, how does your
On 3/17/2013 5:10 PM, David Benfell wrote:
More words to treasure. (Not that Timo envisions himself any kind of
Fuehrer.) This reaches to a certain deification of certain individuals
and organizations in the community--whether they themselves would be
deified or not; I know examples of
Okay, I wasn't going to try and fix up the messed up mail server I was
given; however, I decided that I might as well try.
Situation:
The system has a Postfix MTA and uses Dovecot for LDA and Cyrus-SASL
for SASL. That works fine.
I decided that I wanted to switch over to Dovecot for SASL.
On Sat, 2013-03-16 at 13:51 +0100, to...@starbridge.org wrote:
Hi Timo,
I've got a crash with dovecot 2.2
dovecot --version
2.2.rc2 (69c26a9e3be5)
It's occured when accessing with imap on a large mailbox (around 50k
messages)
imap(clean-quarant...@spamguard.fr): Panic: Buffer full
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 16 Mar 2013, Nicolas Mora wrote:
I'm currently running dovecot on a debian stable and every day, I see this
message dozens of time in my logs :
Mar 16 11:27:57 hector dovecot-auth: pam_unix(dovecot:auth): authentication
failure; logname=
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 13 Mar 2013, Stan Hoeppner wrote:
You simply can't do account auto
configuration with a self signed cert, at least not with a vanilla TB
setup. The only possible solution I can think of would be to preload
the user profile with the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 18 Mar 2013, Steffen Kaiser wrote:
I create a profile manually, import our self-signed root CA cert, copy
the cert8.db to mozilla program base\defaults\profile\cert8.db . For
notebooks and workstations, that are not administrated centrally,
On 3/17/2013 3:50 PM, Timo Sirainen wrote:
It's the best I can do myself. I have no idea how they could be improved in
any major way. They say that the software developer himself is the worst
possible person to write its documentation, because he can't understand what
others find
On Mon, 18 Mar 2013, Stan Hoeppner wrote:
On 3/17/2013 3:50 PM, Timo Sirainen wrote:
It's the best I can do myself. I have no idea how they could be
improved in any major way. They say that the software developer himself
is the worst possible person to write its documentation, because he
On Mon, 2013-03-18 at 10:33 -0500, Stan Hoeppner wrote:
On 3/17/2013 3:50 PM, Timo Sirainen wrote:
It's the best I can do myself. I have no idea how they could be improved in
any major way. They say that the software developer himself is the worst
possible person to write its
On Mon, Mar 18, 2013 at 11:33 AM, Stan Hoeppner s...@hardwarefreak.com
wrote:
A few things could improve the current docs in a major way.
FWIW I've found the exemplary postconf(1) almost indispensable both
for exploring the Postfix configuration and for applying impromptu
changes.
On Mon, 2013-03-18 at 18:37 +0200, Timo Sirainen wrote:
I don't know who they is. Wietse writes all the Postfix documentation
himself. It comes naturally when one performs formal software
development, not ad hoc, because documentation precedes coding. I would
assume you do ad hoc
Jerry skrev den 2013-03-18 13:48:
smtp_sasl_type = dovecot
smtpd_ vs smtp_ :)
I was going to just bite my tongue, but couldn't let this go...
On 2013-03-18 11:33 AM, Stan Hoeppner s...@hardwarefreak.com wrote:
On 3/17/2013 3:50 PM, Timo Sirainen wrote:
It's the best I can do myself. I have no idea how they could be improved in any
major way. They say that the software
On 2013-03-18 12:38 PM, Ajax aaj...@gmail.com wrote:
FWIW I've found the exemplary postconf(1) almost indispensable both
for exploring the Postfix configuration and for applying impromptu
changes.
I think most everyone would agree that postfix is in a class by itself
when it comes to code
On Mon, 18 Mar 2013 19:43:49 +0100
Benny Pedersen articulated:
Jerry skrev den 2013-03-18 13:48:
smtp_sasl_type = dovecot
smtpd_ vs smtp_ :)
Crap, I looked at the settings for hours and never picked up on
that. I knew it was something exceedingly stupid on my part.
Thanks!
--
Jerry ♔
On 18.03.2013, at 17:37, Timo Sirainen t...@iki.fi wrote:
Because it significantly increases development times, and when you're
basically doing everything yourself there's nobody else reading those
anyway.
From my point of view: do continue the very same way every since writing
your first
Daniel,
Just wanted to respond back and let you know that changing permissions to
dovecot:dovecot as you suggested seems to have resolved the issue; I've
not seen any more occurrences of this error.
Thanks again for your assistance!
Chris
On Sun, March 3, 2013 5:13 pm, Daniel Parthey wrote:
Hi
On 3/18/2013 11:37 AM, Timo Sirainen wrote:
So basically you're saying that the major documentation improvement = an
index listing/describing all settings. Sure, would be useful, but I
don't see having time to write that anytime soon.
The time issue is perfectly understandable Timo.
My
I am using imap passwd driver for proxy and ldap for server.
proxy will contact mail server for authentication which in turn will contact
ldap server.
the server auth with ldap is already tested and its working fine.
now i guess i got the auth working properly; but not the mail retrieval
through
27 matches
Mail list logo
