Hi Kirt,
Easy! Either connect to imap.tib.com instead of mail.tib.com, or create
and install a new security certificate on the server which is for
mail.tib.com instead.
It's as simple as the message says - you've said your mail server is
called "mail.tib.com" but your installed security certi
Is the certificate automatically created, from information in
/etc/postfix/main.cf, when Dovecot is setup? If that is the case, I can
uninstall Dovecot & re-install it unless there is an easy way.
Did I mention that I am pretty new to Postfix & Dovecot (and LINUX in
general).
Thank
WJCarpenter wrote:
Easy! Either connect to imap.tib.com instead of mail.tib.com, or
create and install a new security certificate on the server which is
for mail.tib.com instead.
Another solution is to obtain and install a wildcard certificate
(which will be good for all *.tib.com).
That's
Hi Kirt,
Right in that case, the installation of Dovecot has somewhere created a
certificate with "imap.example.com" as the common name (CN.)
I'm afraid I cannot help further as I don't use SSL in Dovecot, however
what I'll say is lookup how to create a certificate in OpenSSL. Perhaps
someo
Hi Nicola,
I'm guessing Dovecot is failing at your % character in "like
'var/pop3/%' THEN." - notice in the log, it's missing the final
apostrophe from that string ("like '/var/pop3/ THEN.".)
Dovecot is trying to take %' as a substitution character (like %u) and
converting it
Hi Timo and all,
I used to use Dovecot back in the 0.99 days a couple of years ago, had
since moved to Courier IMAP, but with the release of Dovecot 1.0.0, I'm
looking at moving back!
One thing I currently have set up and working with Courier is the use of
the enhanced IDLE mode, whereby Cou
Hi Adrian,
I'm thinking this is more of an issue with your MTA, as usually that's
responsible for delivering into the mailbox's Inbox.
You might want to look at Dovecot's LDA, "deliver"
(http://wiki.dovecot.org/LDA).
Deliver takes an e-mail piped from your MTA, with appropriate options on
th
I think the main question is, why do you have/want a read-only maildir?
By definition a maildir is constantly changing. In your case, dovecot
was trying to class a new e-mail as "read", hence the move from "new" to
"cur." Other ways in which a maildir changes, is the changing of the
message
Hi,
I have around 100 mailboxes (maildirs) to convert from Courier IMAP
(4.1.3) to Dovecot.
(From a recent backup) I've tested a few mailboxes on Dovecot 1.0.0, and
while the client doesn't notice any difference (at least in Thunderbird)
I'm hoping to get rid of the old Courier folders and c
Hi Matt,
That's disappointing to hear as I'm also hoping to get ACLs working
(particularly for shared/public folders.)
I'll be looking into this over the coming few weeks so no doubt you'll
be hearing more off me :)
Andy
Matt Zukowski wrote:
Adam, unfortunately I don't have an answer for yo
Would it be better to have a shared mailbox called "office" with each
user having their own login, and, where appropriate, with ACLs so only
the relevant people can access it.
I'm not sure completely how to do this as I'm in the process of learning
1.0 after a 2 year break from Dovecot, but I'
I love this idea! I know it wouldn't be part of the standard IMAP
specification, and you'd probably have to have an extra capability such
as CUSTOMEXECUTE or something in the IMAP capabilities, which
Thunderbird would have to look for before it allows the use of the plugins.
As you suggested,
Hi Wouter,
We do this already, whereby mail is stored like, for [EMAIL PROTECTED], in
/some/path/domain.com/user. The paths are stored in a virtual user
database in PostgreSQL which Dovecot authenticates against. And yes,
/Maildir is redundant, unless you plan on storing any non-mail stuff i
hunderbird plugins can interact with the IMAP connection,
as most of the plugins I've seen are all client-side functions.
Andy.
Marc Perkel wrote:
Andy Shellam wrote:
I love this idea! I know it wouldn't be part of the standard IMAP
specification, and you'd probably have to have an
Hi Eric,
SSH tunnelling requires an SSH login though, right? Even if that's via
PAM or other authentication method, it's another set of authentication
to set up, why not keep it all in the same system (i.e. Dovecot?) I
wouldn't allow SSH access connections to a public-facing server, mainly
Hi,
I've just started setting up Dovecot 1.0.1, and made an error in my
configuration, which I think has found a potential problem in Dovecot.
I'm using PostgreSQL authentication, and set the database host to
"localhost", which PostgreSQL doesn't listen on, so libpq is throwing
the standard
Hi
I've now got Dovecot 1.0.1 authenticating with PostgreSQL for the IMAP
service, but deliver doesn't seem to work the same.
I'm using the "prefetch" passdb, but deliver doesn't seem to recognise it.
Here's the log for a deliver attempt:
dovecot: Jul 01 16:51:35 Info: auth(default): master
I disagree about SSH.
Firstly, how do virtual users fit into your proposed setup?
Secondly, as a service provider to the general public, the absolute LAST thing
I want to be doing is opening up SSH access to my servers.
Mark has a valid point in that you have to connect to the server via IMAP to
Hi,
I'm using a mixture of Exim, Dovecot and Deliver. Exim receives the
mail and validates the user against our database, then pipes the e-mail
to deliver which puts it in the right mailbox.
We were running Exim 4.67 and Dovecot 1.0.1, and today I did an in-place
upgrade to Dovecot 1.0.5 an
liver into a different directory, made it setuid root, and only the
MTA user can get into that directory, works a treat!
Thanks guys,
Andy
Asheesh Laroia wrote:
On Sun, 21 Oct 2007, Andy Shellam (Mailing Lists) wrote:
deliver([EMAIL PROTECTED]): Oct 21 17:19:49 Fatal:
chroot(/users/mail/[
20 matches
Mail list logo
