[Dovecot] Outlook client timeouts on sending mail
This may be a sendmail question, but I thought I'd ask here first: I set up an Outlook client to use secure IMAP and secure SMTP. When sending a message, the client typically times out once or twice and presents an error message indicating the server isn't configured for secure delivery. With a little persistence, Outlook eventually makes a successful connection, and the message goes on its way (2-3 tries). Any pointers as to where to look for the problem? Thanks, Jay
Re: [Dovecot] Best way to migrate from Qpopper to Dovecot
Torsten wrote: Hi David, thanks for your suggestions. You`re right, if I use rsync the smtp service on the old maschine could be active when copying the mboxes. Without rsync a loss of emails is possible. I think you mean 'POP' or 'IMAP' rather than 'SMTP', but yes. Hmm let`s see, maybe I use my second alternative (no migration of data). In general, I'd advise against that - that way lies madness. In particular, users tend to get confused if they have multiple different mailbox interfaces. Plus you then have to maintain two completely independent mail services rather than just one (including backups and everything else that that entails.) Usually it's much less effort _in the long run_ to migrate the data. Cheers, David -- David McBride [EMAIL PROTECTED]
[Dovecot] pop3 seems to be down sometimes
hello guys,
i am using dovecot v1.0.rc15-1~bpo1 from backports.org on a debian sarge
machine as pop3 pop3s imap and imaps server.
since some days it seems the pop-server will stop randomly. noone is
able get mails, but imap is still working. the logfile says:
dovecot: 2007-03-19 16:44:19 Info: auth(default): password([EMAIL
PROTECTED],212.100.55.y): Requested HMAC-MD5 scheme, but we have only MD5
dovecot: 2007-03-19 16:44:20 Info: pop3-login: Login: user=[EMAIL PROTECTED],
method=PLAIN, rip=212.100.55.y, lip=x.x.x.x, TLS
dovecot: 2007-03-19 16:44:23 Info: POP3([EMAIL PROTECTED]): Disconnected:
Logged out top=0/0, retr=0/0, del=0/0, size=0
dovecot: 2007-03-19 16:44:24 Info: auth(default): password([EMAIL
PROTECTED],212.100.55.y): Requested HMAC-MD5 scheme, but we have only MD5
dovecot: 2007-03-19 16:44:26 Info: pop3-login: Login: user=[EMAIL PROTECTED],
method=PLAIN, rip=212.100.55.y, lip=x.x.x.x, TLS
dovecot: 2007-03-19 16:44:29 Info: POP3([EMAIL PROTECTED]): Disconnected:
Logged out top=0/0, retr=0/0, del=0/0, size=0
dovecot: 2007-03-19 16:47:09 Info: pop3-login: Disconnected: Inactivity:
rip=84.181.7.y, lip=x.x.x.x
dovecot: 2007-03-19 16:48:51 Info: pop3-login: Disconnected: Inactivity:
rip=84.135.196.y, lip=x.x.x.x
dovecot: 2007-03-19 16:49:51 Info: pop3-login: Disconnected: Inactivity:
rip=84.135.196.y, lip=x.x.x.x
dovecot: 2007-03-19 16:50:36 Info: pop3-login: Disconnected: Inactivity:
rip=212.100.55.y, lip=x.x.x.x
dovecot: 2007-03-19 16:50:51 Info: pop3-login: Disconnected: Inactivity:
rip=84.135.196.y, lip=x.x.x.x
dovecot: 2007-03-19 16:50:52 Info: pop3-login: Disconnected: Inactivity:
rip=84.181.7.y, lip=x.x.x.x
dovecot: 2007-03-19 18:06:58 Info: imap-login: Disconnected: rip=195.71.y.z,
lip=x.x.x.x, TLS
dovecot: 2007-03-19 18:06:58 Info: IMAP(user3): Disconnected: Logged out
dovecot: 2007-03-19 18:08:12 Info: pop3-login: Disconnected: Inactivity:
rip=84.181.80.y, lip=x.x.x.x
dovecot: 2007-03-19 18:08:31 Info: pop3-login: Disconnected: Inactivity:
rip=84.135.196.y, lip=x.x.x.x
dovecot: 2007-03-19 18:09:02 Info: pop3-login: Disconnected: Inactivity:
rip=212.100.55.y, lip=x.x.x.x
i dont know when and why this problem occurs.
here is my config:
protocols = imaps imap pop3s pop3
protocol imap {
listen = 127.0.0.1
ssl_listen = x.x.x.x
}
protocol pop3 {
listen = x.x.x.x
ssl_listen = x.x.x.x
}
disable_plaintext_auth = no
log_path = /var/log/dovecot.log
info_log_path = /var/log/dovecot.log
log_timestamp = %Y-%m-%d %H:%M:%S
ssl_disable = no
ssl_cert_file = /etc/ssl/certs/dovecot.pem
ssl_key_file = /etc/ssl/private/dovecot.pem
mail_location =
mbox:/home/vmail/%d/%n:INBOX=/home/vmail/%d/%n:INDEX=/home/vmail/index/%u
protocol imap {
mail_plugins = quota imap_quota
imap_client_workarounds = outlook-idle delay-newmail
}
protocol pop3 {
pop3_uidl_format = %08Xu%08Xv
pop3_client_workarounds = outlook-no-nuls oe-ns-eoh
}
auth_verbose = yes
auth default {
mechanisms = plain digest-md5 cram-md5
passdb passwd-file {
args = /etc/dovecot/mailuser
}
userdb passwd-file {
args = /etc/dovecot/mailuser
}
user = root
}
are there any ideas?
regards
thomas
--
thomas balsfulland [EMAIL PROTECTED]
zwischen mut und dummheit liegt nur ein grat
der sich durch das vorbereitetsein unterscheidet
[Dovecot] invalid mbox
dovecot-1.0-1.1.rc15.fc6 When I attempt to drag spam from one IMAP box to another it tells me that I have an invalid mbox format for some emails. Occasionally too when I click on that email box it gives me the same error. uw-imapd never gave me those problems. I use Thunderbird 1.5.0.10 and have the same problem on Windoze XP and MacOSX. Can I and how do I solve this problem? Marc
Re: [Dovecot] Stalled imaptest10 process
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 20 Mar 2007, Timo Sirainen wrote: Oh, and was imaptest10 also compiled against rc27 sources? Because rc27 fixed this: Yes. I compiled imaptest10 within rc27's source dir. I'll try the patch. Bye, - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBRf/uAi9SORjhbDpvAQKViQgAzBsUO5wcAFiBL4FmPP27Cx7sxCmPuIQG u8lLhY/oUVgz5ge27yJjGril4b2MGBbppPxWXbNtDVVQPtEnsKGGpUPqCarmZwK6 0mCMPOizmoATqhdbZ1kNsrgbu/eY30Fpz2ramluTGuDlOkEbpxDRHMdMvUAEwKiP UGa6BzdnTC/25yKBgZwbw9gAut5bfOr6OWtFBIp5aKpPTdYHl0I5oEBaZ+osnkfw NNYu32WPgAKUm4Qb0OxUM3YtAJvCrsl/UVGMBAO/H4bz8a0/6OT6RuAERzUo9v63 Xsqbd0MJEvPDzByVACAwDxfCQDybeqMtLJOmp49tuMJYog3YvHAApw== =XEtG -END PGP SIGNATURE-
[Dovecot] a blush build/install question
This is probably an idiot (and certainly so basic as to be non-Dovecot) question, but I have been chasing my tail for a day or so on it, so I will, with humiliation, ask for guidance on it. Some time back I had asked if dovecot had to have a whole build tree of stuff to run or if any upgrade could be limited to just the executable and some libraries. I was told the latter, and given this list: dovecot (the executable) dovecot.conf libexec/imap libexec/imap-login libexec/dovecot-auth I had wanted to structure my build and install work so that, when update came out, I could build into a directory that was stamped with the time and version and ssl inclusion status. Every time I built I would create a new directory, and I would be able to everything to fall back with, in the old directories. Being that this is production, I wanted to be able to uplevel (or fall back) quickly. I should say I build on a build machine, since I don't want to have a compiler on the production machines; I specified the stamped unique name of this build directory du jour using the --prefix confiigure parm The configure, make and make install steps all go fine. Now I have to transfer those five files over to the target production machine, where I had planned to reference these essential DC files, dovecot itself, dovecot.conf, etc through links, like this: (while resident in the build directory which has been NFS imported onto the production target machine) cp -p ./sbin/dovecot /usr/sbin/$buildver.dovecot ln -sf /usr/sbin/$buildver.dovecot /usr/sbin/dovecot cp -p ./etc/dovecot-example.conf /etc/dovecot-example.$buildver.conf cp -p ./libexec/dovecot/imap /usr/libexec/$buildver.imap ln -sf /usr/libexec/$buildver.imap /usr/libexec/imap cp -p ./libexec/dovecot/imap-login /usr/libexec/$buildver.imap-login ln -sf /usr/libexec/$buildver.imap-login /usr/libexec/imap-login cp -p ./libexec/dovecot/dovecot-auth /usr/libexec/$buildver.dovecot-auth ln -sf /usr/libexec/$buildver.dovecot-au Alas, when I actually tried to run dovecot, it was asking for its resource /in the original build tree/ location, which wasn't there. Is there some way I can do what I want? It seems like I could run the configure without the --prefix parm and have these five files end up in the standard place, but then you would always be building in the same place. I would rather have them in a sheaf of unique build trees so there was never any confusion as to where an edition of them came from...one could always reference back to the unique build tree and do a sum on them. -- Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 [EMAIL PROTECTED] voice: 845-758-7475, fax: 845-758-7035
Re: [Dovecot] Wiki needs updating: Dovecot LDA + Dovecot Sieve + Exim
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Stephen Usher
Sent: Tuesday, March 20, 2007 4:01 PM
To: dovecot@dovecot.org
Subject: [Dovecot] Wiki needs updating: Dovecot LDA + Dovecot
Sieve + Exim
So as to make sure that Dovecot Sieve's vacation system works
Exim has to be
forced to generate a Reply-To: header in the message (which
it doesn't do
by default). The current example for using the Dovecot LDA
with Exim doesn't
do this.
Here is a replacement example for the local_delivery transport:-
local_delivery:
driver = pipe
command = /usr/local/libexec/dovecot/deliver -d $local_part
message_prefix =
message_suffix =
log_output
delivery_date_add
envelope_to_add
return_path_add
headers_add = Reply-To: ${if
def:header_reply-to:{$h_reply-to:}{$h_from:}}
#group = mail
#mode = 0660
Basically, if the Reply-To: header exists than it merely gets
overwritten with
itself. If it doesn't then the header is created and the
contents of the From
header is put into it.
If this is not done then the libsieve over restrictive rules
(requiring
a Reply-To: header even though the RFC doesn't require it)
will not allow
the vacation system to work.
Steve
The nice thing of Wiki's is that you can update pages YOURSELF. Just
register (if needed at all) and add/change what you want. Me think Timo can
spend his time better on patching the source.
CU
Egbert Jan
Re: [Dovecot] a blush build/install question
Stewart Dean wrote:
Alas, when I actually tried to run dovecot, it was asking for its
resource /in the original build tree/ location, which wasn't there. Is
there some way I can do what I want?
While I haven't done this specifically with Dovecot, you should be able
to manage everything in a simple manner like you want; I currently do
this with Exim and Courier-IMAP on the old production server solely with
switches to ./configure. Here's how it basically works, maybe it'll help
you get dovecot working:
Source:
/opt/build/courer-imap-1.2.3
$ ./configure --prefix=/opt/courier-imap-1.2.3
--with-authchangepwdir=${exec_prefix}/libexec/authlib
--with-makedatprog=${exec_prefix}/libexec/makedatprog (more and more
switches that don't matter for this)
After building, a simple make install places everything in
/opt/courier-1.2.3. Then there's a symlink like so:
/opt/courier-imap - /opt/courier-1.2.3
...and finally the /etc/init.d/ script loads the actual courier
processes using /opt/courier-imap, not the standard /usr based things
(so you'll need to customize to fit the default dovecot init.d script).
When I upgrade (or downgrade) it's as simple as running the same
scenario on the new code (which means a new make install does not
overwrite the old), migrate the config files as needed, stop the old
daemon, switch the symlink, then start the new daemon up. Users don't
see interruption in their email experience and I'm confident of a backup
plan in an emergency.
This has been working great for many years upgrading Courier and Exim on
the same machine; rarely do I have to fall back but when it does happen
it's been as simple as pie.
-te
--
Troy Engel | Systems Engineer
Fluid, Inc | http://www.fluid.com
[Dovecot] Sieve: Conversion script for procmail recipes.
Seeing as many on this list are in the process of migrating their mailsystems not only to dovecot's IMAP/POP3 server but also using dovecot's deliver for delivering e-mail into users' folders I thought that it might be a good idea to share with you the perl script I've been labouring upon for the last few days which will translate a simple(ish) procmail recipe to an equivalent Dovecot-Sieve script. (It handles vacation pipes as well, by the way.) It may even be useful as a basis for a more fully featured translator, who knows. Whatever, if it could be put on the Wiki no doubt it will prevent the wheel being re-invented time and again. The script can be found at the following URL: http://www.earth.ox.ac.uk/~steve/sieve/procmail2sieve.pl It might be worth putting it in a contrib directory in the dovecot-sieve distribution. Steve -- --- Computer Systems Administrator,E-Mail:[EMAIL PROTECTED] Department of Earth Sciences, Tel:- +44 (0)1865 282110 University of Oxford, Parks Road, Oxford, UK. Fax:- +44 (0)1865 272072
Re: [Dovecot] Best way to migrate from Qpopper to Dovecot
we did nearly the same procedure the last time we switched from an old Qpopper maschine to a new Qpopper maschine. The last time we had not so much users (maybe 16000), not so much data (round about 20Gigs) and there was no need of conversion. This time we have new DNS-Names, new environment (Dovecot) and so on. That should not pose any real problems :) So David, may I ask you how long did it take to convert the data? We used a cross-link cable between the two machines to transfer the data over their gigabit link. Both systems had three 10k rpm SCSI disks in hardware RAID 5 which pushed data at around 20 mb/s. That took around 20 minutes. Now for the migration script, that took about 1:30 hours to run on a single Intel Xeon 2.80GHz. Cheers, David -- David Robillard UNIX systems administrator Oracle DBA CISSP, RHCE Sun Certified Security Administrator Montreal: +1 514 966 0122
Re: [Dovecot] a blush build/install question
Stewart Dean wrote: Thanks Timo, that should do it. As always, (as us boorish Americans might say), you da man! Your patience and help are always the best. BTW: my instructions work just the same -- compile on a dev machine, tar and untar on a production machine. It doesn't matter where you compile as long as the OSes are compatible (glibc, etc.). What matters is developing a logical symlink infrastructure to accomplish your needs. I kind of thought that would have been obvious, sorry. -te -- Troy Engel | Systems Engineer Fluid, Inc | http://www.fluid.com
[Dovecot] The perfect Courier - Dovecot conversion tool
I've tested this only with a test user. http://dovecot.org/tools/courier-dovecot-migrate.pl http://wiki.dovecot.org/Migration/Courier # Migrate Courier IMAP (any version) and Courier POP3 (v0.43+) to Dovecot v1.0 # by Timo Sirainen. This is public domain. # Usage: [--quiet] [--convert] [--overwrite] [--recursive] [conversion path] # --quiet: Print only errors # --convert: Do the actual conversion. Without this it only shows if it works. # --overwrite: Ovewrite dovecot-uidlist file even if it exists already. # --recursive: Recursively find maildirs to convert # conversion path: Maildir directory, or with --recursive its parent # directory or its parent's parent # - If courierpop3dsizelist is found, it makes its best effort to keep the #POP3 UIDLs, unless the file is more than 30 days older than #courierimapuiddb (user probably stopped using POP3). # - If courierpop3dsizelist isn't found (or it's old), the dovecot-uidlist #is directly converted keeping all the UIDs. # - Keywords are converted from courierimapkeywords/ to maildir filename #flags and dovecot-keywords file # - Subscriptions from courierimapsubscribed are added to Dovecot's #subscriptions file signature.asc Description: This is a digitally signed message part
Re: [Dovecot] The perfect Courier - Dovecot conversion tool
Timo Sirainen wrote:
I've tested this only with a test user.
http://dovecot.org/tools/courier-dovecot-migrate.pl
Thanks! The initial runs are looking good; could you beef up the
convert_subscriptions() function to spit out debugging info when run in
test mode? I have people with really gnarly folder names that I want to
be sure look like they'll be converted correctly.
So instead of returning, maybe something like:
my ($fin, $fout);
open ($fin, $in_fname) || die $!;
if ($do_conversion)
open($fout, $out_fname) || die $!;
else
$fout = STDOUT;
while ($fin) {
chomp $_;
(warning, I'm not a perl hacker - it looks good on paper to me. :)) This
way it'll spit out to screen what would be going into subscriptions. Or
maybe some better variation of my idea...
thx,
-te
--
Troy Engel | Systems Engineer
Fluid, Inc | http://www.fluid.com
