[Dovecot] Panic when indexing virtual folder with solr
Hello Timo and everyone, I am using dovecot 2.1 on debian7 with the fts-solr plugin, and everything is working fine. I have a Virtual folder with all emails, and when I run a doveadm index, I have an error if I don't index real folders first. Example: doveadm -v index -u 'andre rodier' 'Search/*' => Panic: file solr-connection.c: line 416 (solr_connection_select): assertion failed: (!conn->posting) Now, if I rune the doveadm index on the real folders first, the next time I do the index on the virtual folder, everything is fine: doveadm -v index -u 'andre rodier' '*' doveadm -v index -u 'andre rodier' 'Search/*' I wonder if dovecot can run the index on the real folder instead of displaying this error? I hope that will help.
Re: [Dovecot] dovecot 2 in ubuntu 12.04 or Debian Squeeze
Hi Jan, Thanks for your response and Sorry for this late reply. I was out of station. And my question is why my mail client is sending the auth details in plain text? how will i make sure, auth is done after starttls only? -- View this message in context: http://dovecot.2317879.n4.nabble.com/dovecot-2-in-ubuntu-12-04-or-Debian-Squeeze-tp40634p40763.html Sent from the Dovecot mailing list archive at Nabble.com.
Re: [Dovecot] Dovecot with sasl/imaps/postfix and thunderbird
On 3/13/2013 10:23 PM, Alex wrote: > Hi, > >>> Can someone else confirm that restarting Thunderbird is a way around >>> having to manually import the certs or change them later through the >>> account settings menu? >>> >>> Does anyone have any experience with configuring Outlook to use >>> self-signed certs? >> >> This sounds like you're working on a fairly big project, so spend >> $20 and 15 minutes to get a REAL certificate for the test domain >> from one of the countless online vendors. > Yeah, tell me about it. The problem is politics and the difference > between when the project is expected to be done and the amount of time > involved with getting the certificate, explaining what is needed, etc. > > It still might be worth it, though. I'll send them an email and see > what they say. > > Thanks, > Alex If they're paying you for this, it's worth $20 out of pocket to just get it done and out of your hair. If they're not paying you, tell them you need to borrow a credit card and they can watch. 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 used this one several times. -- Noel Jones
Re: [Dovecot] Dovecot with sasl/imaps/postfix and thunderbird
Hi, >> Can someone else confirm that restarting Thunderbird is a way around >> having to manually import the certs or change them later through the >> account settings menu? >> >> Does anyone have any experience with configuring Outlook to use >> self-signed certs? > > > This sounds like you're working on a fairly big project, so spend > $20 and 15 minutes to get a REAL certificate for the test domain > from one of the countless online vendors. Yeah, tell me about it. The problem is politics and the difference between when the project is expected to be done and the amount of time involved with getting the certificate, explaining what is needed, etc. It still might be worth it, though. I'll send them an email and see what they say. Thanks, Alex
Re: [Dovecot] Dovecot with sasl/imaps/postfix and thunderbird
On 3/13/2013 9:38 PM, Alex wrote: > Hi guys, > It's relatively easy. On first starting TB with no account, cancel the wizard. The use "Edit" -> "Preferences" or "≡" -> "Options..." -> "Options..." to get to TB's configuration pages. There, use "Advanced" -> "Certificates" -> "View Certificates" -> "Servers" and finally "Import..." After you've imported the needed cert, you can re-open the wizard with "Create new account". You can also use this method to import a self-signed certificate authority if you want to run your own signing operation. >>> How does he do this at scale Phil? > It appears that if you delete all the unsigned certs, then set up the > account using all the proper ports and auth types, then just restart > thunderbird, it works as expected. Upon restarting thunderbird, it > will prompt you to "confirm security exception", then it automatically > imports the cert for 993. It somehow seemed to automatically import > the cert for 587. > > Can someone else confirm that restarting Thunderbird is a way around > having to manually import the certs or change them later through the > account settings menu? > > Does anyone have any experience with configuring Outlook to use > self-signed certs? > > Thanks, > Alex This sounds like you're working on a fairly big project, so spend $20 and 15 minutes to get a REAL certificate for the test domain from one of the countless online vendors. Surely your time is worth something --- you've spent two days futzing around with this already, and aren't done yet. -- Noel Jones
Re: [Dovecot] Dovecot with sasl/imaps/postfix and thunderbird
On 14 Mar 2013 03:38, "Alex" wrote: > > Hi guys, > > >>> It's relatively easy. On first starting TB with no account, cancel the > >>> wizard. The use "Edit" -> "Preferences" or "≡" -> "Options..." -> > >>> "Options..." to get to TB's configuration pages. There, use "Advanced" > >>> -> "Certificates" -> "View Certificates" -> "Servers" and finally > >>> "Import..." > >>> > >>> After you've imported the needed cert, you can re-open the wizard with > >>> "Create new account". > >>> > >>> You can also use this method to import a self-signed certificate > >>> authority if you want to run your own signing operation. > >> > >> How does he do this at scale Phil? > > It appears that if you delete all the unsigned certs, then set up the > account using all the proper ports and auth types, then just restart > thunderbird, it works as expected. Upon restarting thunderbird, it > will prompt you to "confirm security exception", then it automatically > imports the cert for 993. It somehow seemed to automatically import > the cert for 587. > > Can someone else confirm that restarting Thunderbird is a way around > having to manually import the certs or change them later through the > account settings menu? > > Does anyone have any experience with configuring Outlook to use > self-signed certs? > > Thanks, > Alex Import it using internet explorer. Follow the prompts. http://www.google.com/search?hl=en&gl=GB&ie=UTF-8&q=outlook+self+signed+certificate++how-to Simon
Re: [Dovecot] Dovecot with sasl/imaps/postfix and thunderbird
Hi guys, >>> It's relatively easy. On first starting TB with no account, cancel the >>> wizard. The use "Edit" -> "Preferences" or "≡" -> "Options..." -> >>> "Options..." to get to TB's configuration pages. There, use "Advanced" >>> -> "Certificates" -> "View Certificates" -> "Servers" and finally >>> "Import..." >>> >>> After you've imported the needed cert, you can re-open the wizard with >>> "Create new account". >>> >>> You can also use this method to import a self-signed certificate >>> authority if you want to run your own signing operation. >> >> How does he do this at scale Phil? It appears that if you delete all the unsigned certs, then set up the account using all the proper ports and auth types, then just restart thunderbird, it works as expected. Upon restarting thunderbird, it will prompt you to "confirm security exception", then it automatically imports the cert for 993. It somehow seemed to automatically import the cert for 587. Can someone else confirm that restarting Thunderbird is a way around having to manually import the certs or change them later through the account settings menu? Does anyone have any experience with configuring Outlook to use self-signed certs? Thanks, Alex
Re: [Dovecot] Dovecot with sasl/imaps/postfix and thunderbird
Hi guys, >> It's relatively easy. On first starting TB with no account, cancel the >> wizard. The use "Edit" -> "Preferences" or "≡" -> "Options..." -> >> "Options..." to get to TB's configuration pages. There, use "Advanced" >> -> "Certificates" -> "View Certificates" -> "Servers" and finally >> "Import..." >> >> After you've imported the needed cert, you can re-open the wizard with >> "Create new account". >> >> You can also use this method to import a self-signed certificate >> authority if you want to run your own signing operation. > > How does he do this at scale Phil? All of these options suck, frankly. I should have mentioned, however, that this is only for the test server. There's an actual signed cert for the production server, which is really the same server. So, the test server is mail1.prop.example.com, which will be renamed to just mail.prop.example.com after the staff complete their test. The trouble is staff are basically end-users, so documenting these steps really sucks. That's where I'm at right now. The damn software works fine (thanks to everyone's help and clarifications); it's just finding the easiest way to convince them it's working that's become the problem. They're going to want screenshots, blah, blah, blah... I do have other questions (of course), but I'm still reading and absorbing all that everyone has written thus far. Had I had more time, I would have just made them create another cert for the test server, but I didn't anticipate the difficulty with thunderbird and/or outlook and using self-signed certs. Thanks, Alex
Re: [Dovecot] Dovecot with sasl/imaps/postfix and thunderbird
On 3/13/2013 8:01 AM, Phil Turmel wrote: > On 03/13/2013 01:51 AM, Stan Hoeppner wrote: >> On 3/13/2013 12:00 AM, Alex wrote: > >> I just verified that TB (17.0.4) won't do STARTTLS on TCP 143 without >> first accepting the self signed cert. >> >>> I'm really hoping someone can help me to clarify more specifically >>> what's going on here. >> >> You've already clarified it. 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 certificate. I don't know how you'd do this. >> I think you have some research ahead of you. > > It's relatively easy. On first starting TB with no account, cancel the > wizard. The use "Edit" -> "Preferences" or "≡" -> "Options..." -> > "Options..." to get to TB's configuration pages. There, use "Advanced" > -> "Certificates" -> "View Certificates" -> "Servers" and finally > "Import..." > > After you've imported the needed cert, you can re-open the wizard with > "Create new account". > > You can also use this method to import a self-signed certificate > authority if you want to run your own signing operation. How does he do this at scale Phil? That's what I was commenting on. Importing the cert manually into each client profile probably isn't a realistic option here. Alex is not a sysadmin but a solutions provider. He needs to drop the server in place and get out with minimal fuss, and without walking around to each user desktop at his clients' sites. Which is why Alex wanted to use auto configuration to begin with, I'd guess. So assuming these are MS Windows desktops, I'd think he'd need to use one of the Windows specific deployment tools to preload each user profile with the cert. That's why I said he had some research ahead of him. Unless someone here has that answer at hand. -- Stan
Re: [Dovecot] stats plugins causing dns lookup per connection
On 03/12/13 06:58, Axel Luttgens wrote: > started for seemingly unrelated reasons, but ended with some form of cacheing > of the results fetched with gethostbyname(). It is a bit odd that it would totally block unless DNS requests on your hosts weren't working at all - and even then, the requests would timeout eventually and unblock. > Which version of Dovecot are you running? 2.1.13 I see that caching is in 2.2 now too. Timo, if there are any other 2.1.x releases it'd be nice to get this back ported to it as well. -K
Re: [Dovecot] Sieve mark message as read
On Wednesday, March 13, 2013 03:46 PM CDT, "Donny Brooks"
wrote:
>
>
>
> On Wednesday, March 13, 2013 03:28 PM CDT, "Donny Brooks"
> wrote:
>
> >
> >
> >
> > On Wednesday, March 13, 2013 02:43 PM CDT, Robert Schetterer
> > wrote:
> >
> > > Am 13.03.2013 19:51, schrieb Donny Brooks:
> > > > I am trying to get the advanced functionality of managesieve working
> > > > for our users. If this is not the proper place to ask this, please just
> > > > say so. I have enabled sieve and it works just fine for basic moving
> > > > messages to folders. However the problem comes in to play when a user
> > > > selects something like "delete" or "mark as read" in the filter. It
> > > > just simply does not do that function. I have installed the imapflags
> > > > and imap4flags and added the needed parts to the dovecot config but it
> > > > still does not seem to work. We are running Centos 6.3 with
> > > > dovecot-2.0.9-2.el6_1.1.x86_64 and
> > > > dovecot-pigeonhole-2.0.9-2.el6_1.1.x86_64 installed. What could I be
> > > > missing to make this work?
> > > >
> > >
> > > try
> > >
> > > http://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration?highlight=%28flags%29
> > >
> > > sieve_extensions =
> > >
> > > Which Sieve language extensions are available to users. By default,
> > > all supported extensions are available, except for deprecated
> > > extensions, extensions that require explicit configuration or those that
> > > are still under development. Some system administrators may want to> >
> > > disable certain Sieve extensions or enable those that are not available
> > > by default. All supported extensions are listed here. Normally, all> >
> > > enabled extensions must be listed for this setting, but starting with>
> > > Sieve version 0.1.7, this setting can use '+' and '-' to specify
> > > differences relative to the default. For example sieve_extensions =>
> > > +imapflags will enable the deprecated imapflags extension in addition to
> > > all extensions enabled by default.
> > >
> > > ...
> > >
> > > From CMUSieve (Dovecot v1.0/v1.1)
> > >
> > > For the most part, migration from CMUSieve to Pigeonhole Sieve is just a
> > > matter of changing the used plugin name from cmusieve to sieve in the>
> > > mail_plugins option in the protocol lda section of the config file (as
> > > explained above). However, there are a few important differences in the
> > > supported Sieve language features:
> > >
> > > The imapflags extension is now called imap4flags. The CMUSieve
> > > implementation is based on an old draft specification that is not
> > > completely compatible with the new version. Particularly, the mark and
> > > unmark commands were removed from the new specification. For backwards
> > > compatibility, support for the old imapflags extension can be enabled>
> > > using the sieve_extensions setting (as explained above). This is
> > > disabled by default.
> > >
> > > Best Regards
> > > MfG Robert Schetterer
> > >
> > > --
> > > [*] sys4 AG
> > >
> > > http://sys4.de, +49 (89) 30 90 46 64
> > > Franziskanerstraße 15, 81669 München
> > >
> > > Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
> > > Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer
> > > Aufsichtsratsvorsitzender: Joerg Heidrich
> >
> >
> > Right, my line in /etc/dovecot/conf.d/90-sieve.conf looks like this:
> >
> > sieve_extensions = +notify +imap4flags +imapflags
> >
> > I have tried it without the +imapflags, leaving only the first two, also
> > with same results. Part of my sieve script that has the "mark as seen" is
> > as follows:
> >
> > if anyof (header :is "subject" "Check dd") {
> > fileinto "Junk";
> > addflag "\\Seen";
> > }
> >
> > When I send myself an email from a different account with the subject
> > "Check dd" it is properly filed in the Junk folder but it still remains
> > unseen. Any ideas?
> >
> > --
> >
> > Donny B.
> >
>
> I think I see part of my problem. I am using postfix and dovecot. So in the
> postfix main.cf I have this:
>
> mailbox_command = /usr/libexec/dovecot/deliver -a "$RECIPIENT"
>
> While that was fine when we were on the 1.X branch on our old mail server I
> think it needs to be changed to something more like this:
>
> mailbox_command = /usr/libexec/dovecot/dovecot-lda -f "$SENDER" -a
> "$RECIPIENT"
>
> Ideas?
>
> --
>
> Donny B.
>
I found the issue I believe. Instead of my filter filing the message into the
folder first then mark as seen I had to do the opposite. This is the proper
syntax now:
if anyof (header :is "subject" "Check dd") {
addflag "\\Seen";
fileinto "Junk";
}
Sorry for all the noise.
--
Donny B.
Re: [Dovecot] Sieve mark message as read
On Wednesday, March 13, 2013 03:28 PM CDT, "Donny Brooks"
wrote:
>
>
>
> On Wednesday, March 13, 2013 02:43 PM CDT, Robert Schetterer
> wrote:
>
> > Am 13.03.2013 19:51, schrieb Donny Brooks:
> > > I am trying to get the advanced functionality of managesieve working for
> > > our users. If this is not the proper place to ask this, please just say
> > > so. I have enabled sieve and it works just fine for basic moving messages
> > > to folders. However the problem comes in to play when a user selects
> > > something like "delete" or "mark as read" in the filter. It just simply
> > > does not do that function. I have installed the imapflags and imap4flags
> > > and added the needed parts to the dovecot config but it still does not
> > > seem to work. We are running Centos 6.3 with
> > > dovecot-2.0.9-2.el6_1.1.x86_64 and
> > > dovecot-pigeonhole-2.0.9-2.el6_1.1.x86_64 installed. What could I be
> > > missing to make this work?
> > >
> >
> > try
> >
> > http://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration?highlight=%28flags%29
> >
> > sieve_extensions =
> >
> > Which Sieve language extensions are available to users. By default,
> > all supported extensions are available, except for deprecated
> > extensions, extensions that require explicit configuration or those that
> > are still under development. Some system administrators may want to
> > disable certain Sieve extensions or enable those that are not available
> > by default. All supported extensions are listed here. Normally, all
> > enabled extensions must be listed for this setting, but starting with>
> > Sieve version 0.1.7, this setting can use '+' and '-' to specify
> > differences relative to the default. For example sieve_extensions =>
> > +imapflags will enable the deprecated imapflags extension in addition to
> > all extensions enabled by default.
> >
> > ...
> >
> > From CMUSieve (Dovecot v1.0/v1.1)
> >
> > For the most part, migration from CMUSieve to Pigeonhole Sieve is just a
> > matter of changing the used plugin name from cmusieve to sieve in the>
> > mail_plugins option in the protocol lda section of the config file (as
> > explained above). However, there are a few important differences in the
> > supported Sieve language features:
> >
> > The imapflags extension is now called imap4flags. The CMUSieve
> > implementation is based on an old draft specification that is not
> > completely compatible with the new version. Particularly, the mark and
> > unmark commands were removed from the new specification. For backwards
> > compatibility, support for the old imapflags extension can be enabled>
> > using the sieve_extensions setting (as explained above). This is
> > disabled by default.
> >
> > Best Regards
> > MfG Robert Schetterer
> >
> > --
> > [*] sys4 AG
> >
> > http://sys4.de, +49 (89) 30 90 46 64
> > Franziskanerstraße 15, 81669 München
> >
> > Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
> > Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer
> > Aufsichtsratsvorsitzender: Joerg Heidrich
>
>
> Right, my line in /etc/dovecot/conf.d/90-sieve.conf looks like this:
>
> sieve_extensions = +notify +imap4flags +imapflags
>
> I have tried it without the +imapflags, leaving only the first two, also with
> same results. Part of my sieve script that has the "mark as seen" is as
> follows:
>
> if anyof (header :is "subject" "Check dd") {
> fileinto "Junk";
> addflag "\\Seen";
> }
>
> When I send myself an email from a different account with the subject "Check
> dd" it is properly filed in the Junk folder but it still remains unseen. Any
> ideas?
>
> --
>
> Donny B.
>
I think I see part of my problem. I am using postfix and dovecot. So in the
postfix main.cf I have this:
mailbox_command = /usr/libexec/dovecot/deliver -a "$RECIPIENT"
While that was fine when we were on the 1.X branch on our old mail server I
think it needs to be changed to something more like this:
mailbox_command = /usr/libexec/dovecot/dovecot-lda -f "$SENDER" -a "$RECIPIENT"
Ideas?
--
Donny B.
Re: [Dovecot] Sieve mark message as read
On Wednesday, March 13, 2013 02:43 PM CDT, Robert Schetterer
wrote:
> Am 13.03.2013 19:51, schrieb Donny Brooks:
> > I am trying to get the advanced functionality of managesieve working for
> > our users. If this is not the proper place to ask this, please just say so.
> > I have enabled sieve and it works just fine for basic moving messages to
> > folders. However the problem comes in to play when a user selects something
> > like "delete" or "mark as read" in the filter. It just simply does not do
> > that function. I have installed the imapflags and imap4flags and added the
> > needed parts to the dovecot config but it still does not seem to work. We
> > are running Centos 6.3 with dovecot-2.0.9-2.el6_1.1.x86_64 and
> > dovecot-pigeonhole-2.0.9-2.el6_1.1.x86_64 installed. What could I be
> > missing to make this work?
> >
>
> try
>
> http://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration?highlight=%28flags%29
>
> sieve_extensions =
>
> Which Sieve language extensions are available to users. By default,
> all supported extensions are available, except for deprecated
> extensions, extensions that require explicit configuration or those that
> are still under development. Some system administrators may want to
> disable certain Sieve extensions or enable those that are not available
> by default. All supported extensions are listed here. Normally, all
> enabled extensions must be listed for this setting, but starting with
> Sieve version 0.1.7, this setting can use '+' and '-' to specify
> differences relative to the default. For example sieve_extensions =
> +imapflags will enable the deprecated imapflags extension in addition to
> all extensions enabled by default.
>
> ...
>
> From CMUSieve (Dovecot v1.0/v1.1)
>
> For the most part, migration from CMUSieve to Pigeonhole Sieve is just a
> matter of changing the used plugin name from cmusieve to sieve in the
> mail_plugins option in the protocol lda section of the config file (as
> explained above). However, there are a few important differences in the
> supported Sieve language features:
>
> The imapflags extension is now called imap4flags. The CMUSieve
> implementation is based on an old draft specification that is not
> completely compatible with the new version. Particularly, the mark and
> unmark commands were removed from the new specification. For backwards
> compatibility, support for the old imapflags extension can be enabled
> using the sieve_extensions setting (as explained above). This is
> disabled by default.
>
> Best Regards
> MfG Robert Schetterer
>
> --
> [*] sys4 AG
>
> http://sys4.de, +49 (89) 30 90 46 64
> Franziskanerstraße 15, 81669 München
>
> Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
> Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer
> Aufsichtsratsvorsitzender: Joerg Heidrich
Right, my line in /etc/dovecot/conf.d/90-sieve.conf looks like this:
sieve_extensions = +notify +imap4flags +imapflags
I have tried it without the +imapflags, leaving only the first two, also with
same results. Part of my sieve script that has the "mark as seen" is as follows:
if anyof (header :is "subject" "Check dd") {
fileinto "Junk";
addflag "\\Seen";
}
When I send myself an email from a different account with the subject "Check
dd" it is properly filed in the Junk folder but it still remains unseen. Any
ideas?
--
Donny B.
Re: [Dovecot] Sieve mark message as read
Am 13.03.2013 19:51, schrieb Donny Brooks: > I am trying to get the advanced functionality of managesieve working for our > users. If this is not the proper place to ask this, please just say so. I > have enabled sieve and it works just fine for basic moving messages to > folders. However the problem comes in to play when a user selects something > like "delete" or "mark as read" in the filter. It just simply does not do > that function. I have installed the imapflags and imap4flags and added the > needed parts to the dovecot config but it still does not seem to work. We are > running Centos 6.3 with dovecot-2.0.9-2.el6_1.1.x86_64 and > dovecot-pigeonhole-2.0.9-2.el6_1.1.x86_64 installed. What could I be missing > to make this work? > try http://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration?highlight=%28flags%29 sieve_extensions = Which Sieve language extensions are available to users. By default, all supported extensions are available, except for deprecated extensions, extensions that require explicit configuration or those that are still under development. Some system administrators may want to disable certain Sieve extensions or enable those that are not available by default. All supported extensions are listed here. Normally, all enabled extensions must be listed for this setting, but starting with Sieve version 0.1.7, this setting can use '+' and '-' to specify differences relative to the default. For example sieve_extensions = +imapflags will enable the deprecated imapflags extension in addition to all extensions enabled by default. ... >From CMUSieve (Dovecot v1.0/v1.1) For the most part, migration from CMUSieve to Pigeonhole Sieve is just a matter of changing the used plugin name from cmusieve to sieve in the mail_plugins option in the protocol lda section of the config file (as explained above). However, there are a few important differences in the supported Sieve language features: The imapflags extension is now called imap4flags. The CMUSieve implementation is based on an old draft specification that is not completely compatible with the new version. Particularly, the mark and unmark commands were removed from the new specification. For backwards compatibility, support for the old imapflags extension can be enabled using the sieve_extensions setting (as explained above). This is disabled by default. Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Joerg Heidrich
[Dovecot] Sieve mark message as read
I am trying to get the advanced functionality of managesieve working for our users. If this is not the proper place to ask this, please just say so. I have enabled sieve and it works just fine for basic moving messages to folders. However the problem comes in to play when a user selects something like "delete" or "mark as read" in the filter. It just simply does not do that function. I have installed the imapflags and imap4flags and added the needed parts to the dovecot config but it still does not seem to work. We are running Centos 6.3 with dovecot-2.0.9-2.el6_1.1.x86_64 and dovecot-pigeonhole-2.0.9-2.el6_1.1.x86_64 installed. What could I be missing to make this work? -- Donny B.
[Dovecot] Qmail-LDAP/Dovecot Cluster
Hello, I have worked with qmail-ldap and Dovecot for a number of years, and recently wrote up a piece going into great detail about all aspects of our environment. It currently supports a rather small installation of ~10K active users. If it should be of interest: http://fritz.potsdam.edu/projects/email It is intended primarily for system administrators or mail administrators interested in building mail infrastructure on top of open-source technologies, and is inspired by the likes of Life with qmail. Topics include storage, backup, directory integration, local and remote mail exchange, checkpassword SMTP-Auth and Dovecot login, RBLs, content-scanning and anti-spam, quarantine, webmail, etc. Full installation directions and configuration stanzas are provided for nearly every piece of the infrastructure. Comments/criticism welcome. Cheers. -Jeff -- Jeffrey M Hardy Network / Systems Administrator hard...@potsdam.edu
Re: [Dovecot] mail_max_userip_connections
On 03/13/13 05:37 AM, Simon Brereton wrote: On 12 March 2013 18:03, Axel Luttgens wrote: Le 12 mars 2013 à 17:18, Simon Brereton a écrit : [...] I suppose this implies it's the webmail client., So, to be sure: the webmail server is running on the same box as the one running Dovecot? Si. Yes. but even having that open on two different machines shouldn't open 10 connections. Should it? I tended to believe that usually, a webmail application tends to open/close connections sequentially, or to consecutively select relevant mailboxes within a single connection. But who knows... Which webmail app have you installed? I believe that as well, especially as I don't have tons of folders (some of my users do). I'm using Horde. Try imapproxy for Horde. It would keep a single connection to Dovecot open during a webmail session. http://www.horde.org/apps/imp/docs/PERFORMANCE Since Horde and Dovecot are on the same server, you can configure imapproxy on a different port, e.g. 1143. Horde -> imapproxyd (port 1143) -> Dovecot (port 143)
Re: [Dovecot] Limiting size of stored emails
Thanks great advice, while I don't have the resources to go colo at the moment a dedicated server would work much better, and I will start writing a TOS! On 13/03/13 20:06, Stan Hoeppner wrote: On 3/13/2013 3:38 AM, Patrick Joy wrote: On 13/03/13 16:28, Stan Hoeppner wrote: On 3/12/2013 11:30 PM, Patrick Joy wrote: Thanks for the reply. I have been putting off an upgrade as I need to upgrade the complete OS which is not a trivial task unfortunately but is inevitable. Debian is designed for rolling upgrades, thus Ubuntu should be as well. They're painless on Debian so I would assume the same for Ubuntu. Which begs the question: why have not been doing rolling upgrades given your platform is specifically designed for such a model? My provider has me over a barrel on this one. My server is a large VPS and the provider is running an old kernel that isn't supported by the latest versions of Ubuntu/Debian. To upgrade I need to move to a different platform which costs more and will involve moving everything. The move needs to happen I'm just procrastinating. This is a classic example of why it's almost always better to own your own box and colocate it, especially if you have paying customers. Yes, it costs more, but having full control of the system is worth the added rent. And for a 1U chassis it's actually pretty cheap to colo at many facilities. The problem is finding one within sane driving distance with low prices. I may need to setup a nightly cron job to check for files bigger than xmb in the mail store for now. Probably a good idea. As well as educating the user who attached a 4GB file. That's just plain nuts and smacks of ignorance. Honestly I'm surprised Outlook didn't crash when attaching such a file. It's always hard to educate them when they are paying customers but I will try. Your problem here is lack of a TOS agreement. If you're providing a paid service you should already have one. In that TOS you spell out what is/not allowed or supported by your service, such as 4GB attachments.
Re: [Dovecot] Dovecot with sasl/imaps/postfix and thunderbird
On 03/13/2013 01:51 AM, Stan Hoeppner wrote: > On 3/13/2013 12:00 AM, Alex wrote: > I just verified that TB (17.0.4) won't do STARTTLS on TCP 143 without > first accepting the self signed cert. > >> I'm really hoping someone can help me to clarify more specifically >> what's going on here. > > You've already clarified it. 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 certificate. I don't know how you'd do this. > I think you have some research ahead of you. It's relatively easy. On first starting TB with no account, cancel the wizard. The use "Edit" -> "Preferences" or "≡" -> "Options..." -> "Options..." to get to TB's configuration pages. There, use "Advanced" -> "Certificates" -> "View Certificates" -> "Servers" and finally "Import..." After you've imported the needed cert, you can re-open the wizard with "Create new account". You can also use this method to import a self-signed certificate authority if you want to run your own signing operation. Phil
Re: [Dovecot] Dovecot with sasl/imaps/postfix and thunderbird
Interesting, thanks Prof. Looks like I have some experimenting to do to see what about:config options this sets, so I can add them to my list. On 2013-03-13 2:31 AM, Professa Dementia wrote: I just verified that TB (17.0.4) won't do STARTTLS on TCP 143 without first accepting the self signed cert. I'm really hoping someone can help me to clarify more specifically what's going on here. You've already clarified it. 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 certificate. I don't know how you'd do this. I think you have some research ahead of you. You can. 1) Select Menu Tools > Account Settings... 2) Below the left pane click the Account Actions button, then select Add Mail Account... 3) Fill in the first name and email address. Uncheck Remember password and leave the password field blank. Click the Continue button. 4) VERY QUICKLY!!! As soon as the next window opens, click the Manual Config button at the bottom. 5) Fill in the proper data. Under SSL select None and None. Under Authentication, select Normal Password for both fields. 6) Make sure the ports have real numbers, not Auto. For POP use 110, for IMAP use 143, for SMTP use 25. 7) The "Done" button should undim and be clickable. Click it. 8) You will get a red window warning about no encryption. Check the "I understand ..." box and click Done. 9) Select the account you just created in the left pane, then fix all the settings to use SSL, etc. Dem -- Best regards, Charles Marcus I.T. Director Media Brokers International, Inc. 678.514.6224 | 678.514.6299 fax
Re: [Dovecot] Dovecot with sasl/imaps/postfix and thunderbird
On 2013-03-13 12:37 AM, Alex wrote: Is it conventional to use port 143 for encrypted IMAP connections these days, and not just 993? Port 143 uses STARTTLS, port 993 uses SSL/TLS... been that way for a long time, and yes there is a (slight) difference. STARTTLS *begins* as an unencrypted session, but immediately negotiates the encrypted session. SSL is encrypted from the very beginning of the connection. I'm finding that port 25 works with TLS and postfix now too, not just port 587, so I'm really confused. Both ports 25 and 587 have always worked with STARTTLS... although unless you have a very, very specific need, you will never FORCE STARTTLS on port 25, unlike port 587 where you (should) always *require* it. -- Best regards, Charles
[Dovecot] Converting from Cyrus -> Dovecot sdbox
Hello we like to convert a IMAP server with Cyrus 2.2 to Dovecot 2.0.19 and sdbox mail format. From what i have read until now this is a two stage process with converting first from Cyrus to (Dovecot) maildir with for example cyrus2dovecot and than with dsync from maildir to sdbox. Is this correct or are there other possibilities to go in one step from Cyrus format to sdbox? Regards Andreas
Re: [Dovecot] mail_max_userip_connections
On 12 March 2013 18:03, Axel Luttgens wrote: > Le 12 mars 2013 à 17:18, Simon Brereton a écrit : > >> [...] >> >> I suppose this implies it's the webmail client., > > So, to be sure: the webmail server is running on the same box as the one > running Dovecot? Si. Yes. >> but even having that >> open on two different machines shouldn't open 10 connections. Should >> it? > > I tended to believe that usually, a webmail application tends to open/close > connections sequentially, or to consecutively select relevant mailboxes > within a single connection. But who knows... > Which webmail app have you installed? I believe that as well, especially as I don't have tons of folders (some of my users do). I'm using Horde. > When connecting to/making use of the webmail, you should at least see > connect/disconnect entries written in Dovecot's log. > Do they tend to overlap? With two machine and two phones, it's difficult to keep track of that - but I will try. To avoid that I was hoping there was a way to print out in table form which connections for which user were from where. And so now I have another reason to upgrade. I need to fix the mess I made with postfix first though. Simon
Re: [Dovecot] Limiting size of stored emails
On 3/13/2013 3:38 AM, Patrick Joy wrote: > On 13/03/13 16:28, Stan Hoeppner wrote: >> On 3/12/2013 11:30 PM, Patrick Joy wrote: >>> Thanks for the reply. >>> >>> I have been putting off an upgrade as I need to upgrade the complete OS >>> which is not a trivial task unfortunately but is inevitable. >> Debian is designed for rolling upgrades, thus Ubuntu should be as well. >> They're painless on Debian so I would assume the same for Ubuntu. >> Which begs the question: why have not been doing rolling upgrades given >> your platform is specifically designed for such a model? > My provider has me over a barrel on this one. My server is a large VPS > and the provider is running an old kernel that isn't supported by the > latest versions of Ubuntu/Debian. To upgrade I need to move to a > different platform which costs more and will involve moving everything. > The move needs to happen I'm just procrastinating. This is a classic example of why it's almost always better to own your own box and colocate it, especially if you have paying customers. Yes, it costs more, but having full control of the system is worth the added rent. And for a 1U chassis it's actually pretty cheap to colo at many facilities. The problem is finding one within sane driving distance with low prices. >>> I may need to setup a nightly cron job to check for files bigger than >>> xmb in the mail store for now. >> Probably a good idea. As well as educating the user who attached a 4GB >> file. That's just plain nuts and smacks of ignorance. Honestly I'm >> surprised Outlook didn't crash when attaching such a file. > It's always hard to educate them when they are paying customers but I > will try. Your problem here is lack of a TOS agreement. If you're providing a paid service you should already have one. In that TOS you spell out what is/not allowed or supported by your service, such as 4GB attachments. -- Stan
Re: [Dovecot] Limiting size of stored emails
On 13/03/13 16:28, Stan Hoeppner wrote: On 3/12/2013 11:30 PM, Patrick Joy wrote: Thanks for the reply. I have been putting off an upgrade as I need to upgrade the complete OS which is not a trivial task unfortunately but is inevitable. Debian is designed for rolling upgrades, thus Ubuntu should be as well. They're painless on Debian so I would assume the same for Ubuntu. Which begs the question: why have not been doing rolling upgrades given your platform is specifically designed for such a model? My provider has me over a barrel on this one. My server is a large VPS and the provider is running an old kernel that isn't supported by the latest versions of Ubuntu/Debian. To upgrade I need to move to a different platform which costs more and will involve moving everything. The move needs to happen I'm just procrastinating. I may need to setup a nightly cron job to check for files bigger than xmb in the mail store for now. Probably a good idea. As well as educating the user who attached a 4GB file. That's just plain nuts and smacks of ignorance. Honestly I'm surprised Outlook didn't crash when attaching such a file. It's always hard to educate them when they are paying customers but I will try.
