Re: [Dovecot] Dovecot mysql replication
+1 On 5/30/13, Edwardo Garcia wdgar...@gmail.com wrote: As oringanal poster, I agree with previouz comment, I too feel thiz dovecot responsibile for thiz work handoff, or should delete ability to use two host, people twitter I ask all along thought this how it work too! On Wed, May 29, 2013 at 6:29 PM, Reindl Harald h.rei...@thelounge.netwrote: so better remove the option to specify more than one host instead let people run over years in troubles until they find out that a logical behavior like for postfix is not given for dovecot's mysql-connections - yes i was one of the who thought hey both works the same way until i realized that dovecot has no fun at reboot the replication slave which was intented only as failover and used regulary *it is* dovecots job if it offers more than one host to handle this in a useful way or not support more than one host, but you can't seriously say it's not dovecots job after having a half-baken support implemented Am 29.05.2013 02:52, schrieb Timo Sirainen: I haven't replied to most of the threads recently. Anyway, after thinking about this, I'm thinking this kind of connection fallback handling isn't really Dovecot's job. A load balancer could be configured to do it just as well (whereas LB couldn't do actual load balancing for multiple sql servers, because Dovecot uses long running TCP connections). On 29.5.2013, at 2.09, Noel Butler noel.but...@ausics.net wrote: But each additional link added to the chain, is one more point of failure, unless he's replied to OP privately I'm amazed Timo has ignored this, since its been brought up from time to time before, if he no longer plans on doing it, he should just say so, so people can look at complete alternatives, we are a long way passed early 1.2 series. On Sun, 2013-05-26 at 17:33 +0200, Daniel Parthey wrote: Edwardo Garcia wrote: Yes indeed, so it seem it does not do at all. For now we disable use two hosts, but thiz not optimum for network. You might try to put mysqlproxy in between dovecot and your mysql cluster and have dovecot connect to the failover proxy (or proxies) instead of connecting the database directly. mysqlproxy makes use of the lua scripting language, where you might want to implement the failover or filter mechanisms you need
Re: [Dovecot] Dovecot mysql replication
On 5/30/13, Robert Schetterer r...@sys4.de wrote: Am 30.05.2013 03:41, schrieb Edwardo Garcia: As oringanal poster, I agree with previouz comment, I too feel thiz dovecot responsibile for thiz work handoff, or should delete ability to use two host, people twitter I ask all along thought this how it work too! where is the problem, nobody presses you to use it, nobody makes us dovecot true, but dovecot works fine and in perfect harmony with postfix, except this one option. I remember the earlier thread and have been waiting for this option, but now I see Timo has decided to drop the idea after earlier saying it would be beneficial, and seems some people have been waiting for long time for no reason, so maybe time to consider all other options, including server software.
Re: [Dovecot] imap/pop problem
I have discovered it. I enabled the namespace inbox and location of mailbox. it all looks good now. thanks for your efforts. -Original Message- From: Steffen Kaiser Sent: Wednesday, May 29, 2013 9:35 AM To: MP Netsai Cc: Dovecot MM Subject: Re: [Dovecot] imap/pop problem -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 28 May 2013, MP Netsai wrote: increase logging, see http://wiki2.dovecot.org/Logging then check out the logs and - if required still, because Dovecot's log message usually speak an understandable tongue - post the logs along. - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBUaWvql3r2wJMiz2NAQIKHAf/Zabc0bCGIXDYwZwnzuRPof/r2wDJPQA6 c7SG3R6HUZmSL5dEHYgwwoK/UhS/p8xJ9TZqjAzUPQ/CGWR8zHX5tSS360gQIMrU hNK59cDFXHr+h5RQUkq7D5JPs/k2U0gE6Z1iMPTVTdAILb56KReuINbeYUsqyWOV 1D23NH86gr/7UzPWxVl1CmwQOOSitMqJ7N6fDiB9D+2F1bHN8+5Lu1S/+VohPyw7 croUdMup8+p/lEYYfkBfMRDICm2uCfuKPVAgJKyC/4mknK6vqPyK8YDmE7NXlD9K UhmZye1enW/lvoiybmyyVOg5rjVdgVxcBoFvIqLc97/5uFSrIRrSoQ== =/0+W -END PGP SIGNATURE-
Re: [Dovecot] IMAP QUOTA
Hi, I read about Snarf plugin, it works if the mail already in spool area, but I want to know whether it is possible if users quota exceeded then instead of mail rejected it should delived to user spool area or somewhere else. Regards, Arun Gupta On Wed, 29 May 2013, Arun Gupta wrote: Hi, Thanks for replying... Dear Steffen I search about slurp plugin but didn't get it if possible kindly provde me the doc, link etc for the same. Regards, Arun Gupta On Tue, 28 May 2013, Arun Gupta wrote: I configured imap quota on dovecot-2.0 with backend Maildir++, after exceeding user quota the sender receiving bounce mails, Is there any way that after exceeding user quota the mail will deliver somewhere else like user spool area? so that after increasing quota user will get the mails. Check out the slurp plugin and let your MTA deliver mails to, say, /var/mail/uid . You will have no Sieve rules then, I think. However, some sort of quota enforcing you will need there, too. - -- Steffen Kaiser -- Regards, Arun Kumar Gupta Mail Administrator National PARAM Supercomputing Facility (NPSF) Centre for Development of Advanced Computing Ganeshkhind Road Pune University Campus PUNE-Maharastra Phone : +91-20-25704347 WEB : http://www.cdac.in/ --- This e-mail is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies and the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email is strictly prohibited and appropriate legal action will be taken. ---
Re: [Dovecot] Dovecot 2.2 build rpm on Centos6
On 27-05-2013 16:56, Nikolaos Milas wrote: On 27/5/2013 1:07 μμ, Birta Levente wrote: I tried to build rpm based on dovecot-2.2.2-2.fc20.src.rpm on Centos 6.4 You may want to try: dovecot-2.2.2-2.noa.el6.src.rpm which produces: dovecot-2.2.2-2.noa.el6.x86_64.rpm dovecot-debuginfo-2.2.2-2.noa.el6.x86_64.rpm dovecot-devel-2.2.2-2.noa.el6.x86_64.rpm dovecot-mysql-2.2.2-2.noa.el6.x86_64.rpm dovecot-pgsql-2.2.2-2.noa.el6.x86_64.rpm dovecot-pigeonhole-2.2.2-2.noa.el6.x86_64.rpm available at: http://www.noa.gr/rpmfiles/ This package is using LTB Project's Openldap RPMs for LDAP linking: http://ltb-project.org/wiki/download#openldap The above Dovecot SRPM has evolved from fakessh's rpms: http://ns.fakessh.eu/rpms/ and I like it because it is clean and clear (to me, at least). Nick another question.. anybody built dovecot 2.2 on rhel/centos 5 there is any knowhow or any builded pack
Re: [Dovecot] Dovecot 2.2 build rpm on Centos6
-Original Message- From: dovecot-boun...@dovecot.org [mailto:dovecot-boun...@dovecot.org] On Behalf Of Burak GÜRER Sent: Thursday, May 30, 2013 10:34 AM To: Nikolaos Milas Cc: Dovecot Mailing List Subject: Re: [Dovecot] Dovecot 2.2 build rpm on Centos6 On 27-05-2013 16:56, Nikolaos Milas wrote: On 27/5/2013 1:07 μμ, Birta Levente wrote: I tried to build rpm based on dovecot-2.2.2-2.fc20.src.rpm on Centos 6.4 You may want to try: dovecot-2.2.2-2.noa.el6.src.rpm which produces: dovecot-2.2.2-2.noa.el6.x86_64.rpm dovecot-debuginfo-2.2.2-2.noa.el6.x86_64.rpm dovecot-devel-2.2.2-2.noa.el6.x86_64.rpm dovecot-mysql-2.2.2-2.noa.el6.x86_64.rpm dovecot-pgsql-2.2.2-2.noa.el6.x86_64.rpm dovecot-pigeonhole-2.2.2-2.noa.el6.x86_64.rpm available at: http://www.noa.gr/rpmfiles/ This package is using LTB Project's Openldap RPMs for LDAP linking: http://ltb-project.org/wiki/download#openldap The above Dovecot SRPM has evolved from fakessh's rpms: http://ns.fakessh.eu/rpms/ and I like it because it is clean and clear (to me, at least). Nick another question.. anybody built dovecot 2.2 on rhel/centos 5 there is any knowhow or any builded pack http://www.city-fan.org/ftp/contrib/mail/ -arto
Re: [Dovecot] Perfect LDAP tree
Good morning. 28.05.2013 18:06, Steffen Kaiser пишет: mail=b...@example2.com,ou=mail,dc=example2,dc=com Thank you, I lost sight of that. In my opinion, you try make LDAP more complicate is it is designed as. I'm tried to create error-robust structure. For example when schema for mail t...@example.com presents as dn: dc=com dn: dc=example,dc=com dn: mail=test,dc=example,dc=com it looks much better than dn: dc=example.com dn: mail=t...@example.com,dc=example.com because we are don't make a mistake and never get dn: dc=example.com dn: mail=t...@example.org,dc=example.com With best regards, Evgeny Basov.
Re: [Dovecot] Dovecot 2.2 build rpm on Centos6
On 30/05/2013 10:34, Burak GÜRER wrote: On 27-05-2013 16:56, Nikolaos Milas wrote: On 27/5/2013 1:07 μμ, Birta Levente wrote: I tried to build rpm based on dovecot-2.2.2-2.fc20.src.rpm on Centos 6.4 You may want to try: dovecot-2.2.2-2.noa.el6.src.rpm which produces: dovecot-2.2.2-2.noa.el6.x86_64.rpm dovecot-debuginfo-2.2.2-2.noa.el6.x86_64.rpm dovecot-devel-2.2.2-2.noa.el6.x86_64.rpm dovecot-mysql-2.2.2-2.noa.el6.x86_64.rpm dovecot-pgsql-2.2.2-2.noa.el6.x86_64.rpm dovecot-pigeonhole-2.2.2-2.noa.el6.x86_64.rpm available at: http://www.noa.gr/rpmfiles/ This package is using LTB Project's Openldap RPMs for LDAP linking: http://ltb-project.org/wiki/download#openldap The above Dovecot SRPM has evolved from fakessh's rpms: http://ns.fakessh.eu/rpms/ and I like it because it is clean and clear (to me, at least). Nick another question.. anybody built dovecot 2.2 on rhel/centos 5 there is any knowhow or any builded pack I done yesterday with spec that I used on centos 6 without any modification src rpm from http://mstevens.fedorapeople.org/el6/dovecot/2.2/ Levi smime.p7s Description: S/MIME Cryptographic Signature
Re: [Dovecot] Dovecot 2.2 build rpm on Centos6
On 30-05-2013 10:52, Arto Saraniva wrote: -Original Message- From: dovecot-boun...@dovecot.org [mailto:dovecot-boun...@dovecot.org] On Behalf Of Burak GÜRER Sent: Thursday, May 30, 2013 10:34 AM To: Nikolaos Milas Cc: Dovecot Mailing List Subject: Re: [Dovecot] Dovecot 2.2 build rpm on Centos6 On 27-05-2013 16:56, Nikolaos Milas wrote: On 27/5/2013 1:07 μμ, Birta Levente wrote: I tried to build rpm based on dovecot-2.2.2-2.fc20.src.rpm on Centos 6.4 You may want to try: dovecot-2.2.2-2.noa.el6.src.rpm which produces: dovecot-2.2.2-2.noa.el6.x86_64.rpm dovecot-debuginfo-2.2.2-2.noa.el6.x86_64.rpm dovecot-devel-2.2.2-2.noa.el6.x86_64.rpm dovecot-mysql-2.2.2-2.noa.el6.x86_64.rpm dovecot-pgsql-2.2.2-2.noa.el6.x86_64.rpm dovecot-pigeonhole-2.2.2-2.noa.el6.x86_64.rpm available at: http://www.noa.gr/rpmfiles/ This package is using LTB Project's Openldap RPMs for LDAP linking: http://ltb-project.org/wiki/download#openldap The above Dovecot SRPM has evolved from fakessh's rpms: http://ns.fakessh.eu/rpms/ and I like it because it is clean and clear (to me, at least). Nick another question.. anybody built dovecot 2.2 on rhel/centos 5 there is any knowhow or any builded pack http://www.city-fan.org/ftp/contrib/mail/ -arto thanks arto
Re: [Dovecot] Dovecot mysql replication
Am 30.05.2013 05:42, schrieb Robert Schetterer: Am 30.05.2013 03:41, schrieb Edwardo Garcia: As oringanal poster, I agree with previouz comment, I too feel thiz dovecot responsibile for thiz work handoff, or should delete ability to use two host, people twitter I ask all along thought this how it work too! where is the problem, nobody presses you to use it so what - that makes not bugs go away but i agree there should be more docs on it i.e wiki how can whatever documentation repair a broken by design implementation like using the replicaton slave while the master on localhost is available and throw errors if the slave is rebooted in the wrong moment? signature.asc Description: OpenPGP digital signature
Re: [Dovecot] Sieve/pigeonhole with Exim and Dovecot LDA
On 20/05/13 23:40, Gedalya wrote:
On 05/20/2013 05:13 PM, Sebastian Arcus wrote:
On 20/05/13 17:12, Gedalya wrote:
On 05/20/2013 12:02 PM, Sebastian Arcus wrote:
Exim doesn't seem to have any variable expansion for the From field
If using the From header actually makes sense to you... then see
$h_header name at
http://www.exim.org/exim-html-current/doc/html/spec_html/ch-string_expansions.html,
you probably want to restrict the usage of this as much as possible.
The envelope sender must be empty for bounces and auto-replies, pretty
good article here: https://github.com/Exim/exim/wiki/EximAutoReply
Later I'll read through your whole message again and maybe I'll come up
with something more concrete and detailed..
Thanks for that. I've just tried using $header_from: in my exim
authenticator in client mode when talking to the provider's SMTP
server in smart relay mode (instead of $sender_address) - but for some
strange reason it just won't work. I've poured over the exim logs in
debug mode - and so far I can't make sense of what is happening. I'll
try some more to figure it out and get it working.
OK, now I had some more time to look at your situation.
We can ask, do you really need the sender? How do you use it? You're
trying to authenticate using the sender, do you have the passwords in a
lookup file?
Perhaps this can be a good idea: set up a special authenticator with:
client_condition = ${if match_ip{$sender_host_address}{:@[]}{1}{0}}
so that it can only be used for locally submitted messages (this
_should_ work, test it), and statically configure it with credentials
that would work with your upstream SMTP server?
Either way, you shouldn't have an authenticator that would trust the
From: header and do something with it, unless the situation is very
tightly controlled. You probably want to put more restrictions there to
make sure this works only when intended, i.e. dovecot autoreplies.
Now, as for $header_from, first of all, it's $header_from:, with the
colon in the end. Yea, I know.
Secondly, I have no idea if it would be available in an authenticator.
Consider that an authenticator is not really something that is related
to processing an individual message.
One thing is for sure, you would need to set connection_max_messages = 1
in the smtp transport which would be handling these messages. I know
that that helps to make $sender_address available in the authenticator,
try your luck with $h_from: or try to pass that data in somehow, ACL
variables or something, let me know how that goes - I'm curious, but if
you need further help you should probably ask on the exim-users mailing
list (and point me at the thread ;-))
Just a follow-up to my previous messages. I've posted to the exim list,
and the best option seems to be to run a check in the authenticator, and
if the $sender_address is empty, to use a default one instead. Note that
this is probably safe in my setup, on a small lan with tightly
controlled clients and where exim accepts no outside incoming email -
but it might not be safe in some other different arrangements.
Here is my authenticator, in case it helps anybody else (replace
my@default_address.com with something suitable for your setup):
#modified client auth for sieve ($sender_address missing)
fixed_plain_client:
driver = plaintext
public_name = PLAIN
client_send = ^${if eq{$sender_address}{}{my@default_address.com}\
{$sender_address}}^${lookup{${if eq{$sender_address}{}\
{my@default_address.com}{$sender_address}}}\
lsearch{/etc/exim/exim-client.passwd}{$value}{fail}}
And here is a link to the thread on exim list:
https://lists.exim.org/lurker/message/20130523.094659.1dc9fbe2.en.html
Re: [Dovecot] Dovecot mysql replication
On 2013-05-30 2:59 AM, Nick Edwards nick.z.edwa...@gmail.com wrote: nobody makes us dovecot true, but dovecot works fine and in perfect harmony with postfix, except this one option. I remember the earlier thread and have been waiting for this option, but now I see Timo has decided to drop the idea after earlier saying it would be beneficial, and seems some people have been waiting for long time for no reason, so maybe time to consider all other options, including server software. Oh, grow up. I can see if this was something that was super critical to a functioning - and I agree that it should be fixed to either work as expected (best), or no longer support the ability to add multiple hosts - but it isn't up to me or you. Just because 'some' people have been waiting for this feature, doesn't mean that it is important to everyone. Now, if you can provide evidence that a large percentage of people desire this feature and it is important enough to them that they might actually consider switching from dovecot to something else (but what choices do you have, really? I know I have no desire to switch back to courier-imap), then I think Timo may reconsider. In fact, he may already be doing so. But the bottom line is, there are other ways to achieve this feature, and I think it is plain silly and juvenile to threaten to switch from dovecot just because Timo doesn't agree with you. Oh - and of course, the very last point... This *is* open source software. I'd wager an entire months pay that if you coded up a solution and provided a working, properly coded patch (that isn't full of security holes and bad coding practices), Timo would accept/merge it. -- Best regards, Charles
Re: [Dovecot] IMAP QUOTA
On 2013-05-30 3:26 AM, Arun Gupta ar...@cdac.in wrote: I read about Snarf plugin, it works if the mail already in spool area, but I want to know whether it is possible if users quota exceeded then instead of mail rejected it should delived to user spool area or somewhere else. Again, you are tilting at windmills. If you want to use Quotas, *use* them. If you don't, then *don't*. Otherwise you are just asking for headaches. -- Best regards, Charles
[Dovecot] recursive mail_location?
Forgive what may be a newby question, but I'm trying to get a new setup working, and there are many different things confusing me. I'm trying for a gnus + dovecot + mbsync arrangement, with mbsync writing to maildirs, and gnus reading from those dirs with a dovecot invocation. Fairly standard, I think. I have multiple email accounts I'm trying to sync, all of them gmail. My problem is that mbsync creates one maildir structure for each mailbox in each account. So I end up with: ~/mail ├── acc1 │ ├── INBOX │ │ ├── cur │ │ ├── new │ │ └── tmp │ └── OTHERBOX │ ├── cur │ ├── new │ └── tmp └── acc2 ├── INBOX │ ├── cur │ ├── new │ └── tmp └── OTHERBOX ├── cur ├── new └── tmp And so on, for many accounts, and many mailboxes. I believe there's something I can configure in mbsync to collapse this a little, but there's still going to be quite a bit of nesting. Gnus, meanwhile, is meant to invoke dovecot with the -o mail_location switch, and as far as I can tell that needs to be pointed at a maildir structure, which means I would need a separate gnus server for each mailbox in each account. Does anyone have a recommended way of handling this? Is it possible to either flatten the structure further, or somehow tell dovecot to recurse into directories? I don't mind having a separate gnus server for each mail account, but I'd hate to have to do one per mailbox. I'm only just getting started and haven't invested myself in any particular setup, so if the answer is you're doing it all wrong, I would love to hear that. Thanks! Eric
Re: [Dovecot] Dovecot mysql replication
Am 30.05.2013 12:54, schrieb Reindl Harald: Am 30.05.2013 05:42, schrieb Robert Schetterer: Am 30.05.2013 03:41, schrieb Edwardo Garcia: As oringanal poster, I agree with previouz comment, I too feel thiz dovecot responsibile for thiz work handoff, or should delete ability to use two host, people twitter I ask all along thought this how it work too! where is the problem, nobody presses you to use it so what - that makes not bugs go away but i agree there should be more docs on it i.e wiki how can whatever documentation repair a broken by design implementation like using the replicaton slave while the master on localhost is available and throw errors if the slave is rebooted in the wrong moment? Hi Harald, if you declare this broken, why not fix it yourself, instead of barking to the moon, however the current behave should be written in the wiki, to avoid recover the same questions on the list in periods 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: Florian Kirstein
Re: [Dovecot] Dovecot mysql replication
On 2013-05-30 9:10 AM, Robert Schetterer r...@sys4.de wrote: Hi Harald, if you declare this broken, why not fix it yourself, instead of barking to the moon, however the current behave should be written in the wiki, to avoid recover the same questions on the list in periods Well, I'd add that the config itself should complain (with a link to the wiki page explaining the issue) if more than one server is added. In other words, it should tell the admin that it will not work as they may be expecting. -- Best regards, Charles
Re: [Dovecot] recursive mail_location?
On Thursday 30 of May 2013 10:33:01 Eric Abrahamsen wrote: Does anyone have a recommended way of handling this? Is it possible to either flatten the structure further, or somehow tell dovecot to recurse into directories? I don't mind having a separate gnus server for each mail account, but I'd hate to have to do one per mailbox. Maybe setting LAYOUT=fs (and possibly DIRNAME) in mail_location could somehow help you? More on this settings is here: http://wiki2.dovecot.org/MailLocation/Maildir -- Karol Jurak
Re: [Dovecot] IMAP QUOTA
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Arun Gupta wrote: I read about Snarf plugin, it works if the mail already in spool area, but I want to know whether it is possible if users quota exceeded then instead of mail rejected it should delived to user spool area or somewhere else. I understand and you should consider Charles' advice :-) This is something your MDA should do. Neither the Dovecot LMTP server nor the current Dovecot deliver can do so. But deliver is rather small, so you could hack it in. Or use Dovecot deliver in combination with Snarf and a MDA wrapper, e.g.: The wrapper script first checks, if the recipient is over quota, in that case use another maildrop programm, such as procmail, that delivers the message to a spool area; otherwise call Dovecot deliver with the usual arguments. Or if you call Dovecot deliver and it exits with exit code 69 (Tempfailure), call that other MDA. Then let Snarf pull the messages into the INBOX next time. - -- Steffen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEVAwUBUadrp13r2wJMiz2NAQIpiAf+JSeuZns89NoJV5aW2Li4myLp209HycHt j3varTiBYgekw1vMAhDXYH/RKnMwWlOFSe15YIMTcCIY8gjTIqCx6YA/W1cJVZL+ 3zRVA/75t3CsAFx70/+fecrZJnY6u0Ok7VUXJ4DAxdJgsOyqXZy9/6bt+t43TcaT pUlug3nAmIP9GwZ2GQFGkEFxfD74EPVRVg8opAZzTaSPuv/IfKsC8f4RA64JtQ2S EACc/nEC4xVmjDAz/9cpLLsWiLlYfy/cEDIw49XA2MrQsIIS7qkHcDLawuqsVsAk HHXX/iqmcRBtznpO94XS9SCtvUa/5fDkVYv56uuDazEHpy4urBrtyA== =Qo2f -END PGP SIGNATURE-
[Dovecot] Settings: Dovecot + NTLM + Single Sing On + Windows + Outlook or Thunderbird.
I am following the steps listed in:
http://wiki.dovecot.org/HowTo/ActiveDirectoryNtlm
My goal is to have single sign-on for Microsoft Outlook applications.
I working and I have some doubts since I never set up an imap server, hope
I can help :).
The version that I have installed is devecot 2.0.9.
dovecot -n shows the following:
# 2.0.9: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-71.el6.x86_64 x86_64 CentOS release 6.4 (Final)
auth_use_winbind = yes
mbox_write_locks = fcntl
passdb {
driver = pam
}
protocols = imap pop3
ssl = no
userdb {
args = uid=1 gid=1 home=/mail/%d/%n
driver = static
}
I show what I have in /etc/samba/smb.conf
[global]
workgroup = EJEMPLO
realm = EJEMPLO.COM.UY
server string = %h (Samba %v)
security = ADS
password server = ad.domain.dom
username map = /etc/samba/mapeousuarios
map untrusted to domain = Yes
syslog = 0
log file = /var/log/samba/log.%m
max log size = 1000
name resolve order = wins host bcast
local master = No
domain master = No
dns proxy = No
wins server = here active directory ip
panic action = /usr/share/samba/panic-action %d
winbind separator = +
winbind use default domain = Yes
winbind rpc only = Yes
idmap config * : range = 1200-3000
idmap config * : backend = tdb
[usuarios3]
path = /exports/archivos-usuarios
read only = No
map acl inherit = Yes
store dos attributes = Yes
wbinfo -g and wbinfo -u work well.
kinit Administrator work well also.
Some steps of the configuration in dovecot.conf does not recognize:
1) protocols = imap imaps pop3 pop3s.
2) mechanisms = plain ntlm login.
3) allow_all_users=yes y
mail=maildir:/home/vmail/%d/%1Ln/%Ln:INBOX=/home/vmail/%d/%1Ln/%Ln.
I'm not sure I should put in place.
I also have some doubts:
1) I have to create a keytab file containing the principal for
imap and pop?, as it would indicate Dovecot?.
2) That should indicate values uid y el gid?
3) I have to set something in pam?
if I make telnet localhost imap shows the following:
OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE
AUTH=PLAIN] Dovecot ready
NTLM not appears in the options.
I hope I can shed some light on the subject :) Thanks and greetings.
--
Maria José
Re: [Dovecot] Settings: Dovecot + NTLM + Single Sing On + Windows + Outlook or Thunderbird.
The wiki link you refer to is for dovecot v1. You are using v2. Use the correct wiki link... http://wiki2.dovecot.org/HowTo/ActiveDirectoryNtlm Also, you are using an old version of v2 - use the latest 2.1 (2.1.16), or better yet, the latest 2.2 (2.2.2)... Charles On 2013-05-30 11:34 AM, Maria Jose Yañez Dacosta mariajose1...@gmail.com wrote: I am following the steps listed in: http://wiki.dovecot.org/HowTo/ActiveDirectoryNtlm My goal is to have single sign-on for Microsoft Outlook applications. I working and I have some doubts since I never set up an imap server, hope I can help :). The version that I have installed is devecot 2.0.9. dovecot -n shows the following: # 2.0.9: /etc/dovecot/dovecot.conf -- Best regards, Charles Marcus I.T. Director Media Brokers International, Inc. 678.514.6224 | 678.514.6299 fax
Re: [Dovecot] IMAP QUOTA
On 28.5.2013, at 13.42, Arun Gupta ar...@cdac.in wrote: I configured imap quota on dovecot-2.0 with backend Maildir++, after exceeding user quota the sender receiving bounce mails, Is there any way that after exceeding user quota the mail will deliver somewhere else like user spool area? so that after increasing quota user will get the mails. quota_full_tempfail = yes
Re: [Dovecot] Settings: Dovecot + NTLM + Single Sing On + Windows + Outlook or Thunderbird.
Sorry!, And try to install the latest version and tell them. Thanks! 2013/5/30 Charles Marcus cmar...@media-brokers.com The wiki link you refer to is for dovecot v1. You are using v2. Use the correct wiki link... http://wiki2.dovecot.org/**HowTo/ActiveDirectoryNtlmhttp://wiki2.dovecot.org/HowTo/ActiveDirectoryNtlm Also, you are using an old version of v2 - use the latest 2.1 (2.1.16), or better yet, the latest 2.2 (2.2.2)... Charles On 2013-05-30 11:34 AM, Maria Jose Yañez Dacosta mariajose1...@gmail.com wrote: I am following the steps listed in: http://wiki.dovecot.org/HowTo/**ActiveDirectoryNtlmhttp://wiki.dovecot.org/HowTo/ActiveDirectoryNtlm My goal is to have single sign-on for Microsoft Outlook applications. I working and I have some doubts since I never set up an imap server, hope I can help :). The version that I have installed is devecot 2.0.9. dovecot -n shows the following: # 2.0.9: /etc/dovecot/dovecot.conf -- Best regards, Charles Marcus I.T. Director Media Brokers International, Inc. 678.514.6224 | 678.514.6299 fax -- Maria José
Re: [Dovecot] Dovecot mysql replication
Am 30.05.2013 15:17, schrieb Charles Marcus: On 2013-05-30 9:10 AM, Robert Schetterer r...@sys4.de wrote: Hi Harald, if you declare this broken, why not fix it yourself, instead of barking to the moon, however the current behave should be written in the wiki, to avoid recover the same questions on the list in periods Well, I'd add that the config itself should complain (with a link to the wiki page explaining the issue) if more than one server is added. In other words, it should tell the admin that it will not work as they may be expecting. yes , doing such ,sounds ok to me 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: Florian Kirstein
Re: [Dovecot] Dovecot mysql replication
On Thu, 2013-05-30 at 20:24 +0200, Robert Schetterer wrote: Well, I'd add that the config itself should complain (with a link to the wiki page explaining the issue) if more than one server is added. In other words, it should tell the admin that it will not work as they may be expecting. yes , doing such ,sounds ok to me Best Regards MfG Robert Schetterer One thing I have always expected of my people, which was once instilled upon me many many years ago by one of my managers.. is fix the root cause, dont play catch-up patch-up ... in other words, dont apply a bandaid solution when the bandaid will eventually come off. The change to the wiki or print warnings to say this that whatever, is IMHO, only a bandaid solution. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Dovecot mysql replication
On Thu, 2013-05-30 at 07:01 -0400, Charles Marcus wrote: On 2013-05-30 2:59 AM, Nick Edwards nick.z.edwa...@gmail.com wrote: nobody makes us dovecot true, but dovecot works fine and in perfect harmony with postfix, except this one option. I remember the earlier thread and have been waiting for this option, but now I see Timo has decided to drop the idea after earlier saying it would be beneficial, and seems some people have been waiting for long time for no reason, so maybe time to consider all other options, including server software. Oh, grow up. Good 'ol charlie boy, you still havnt learnt have you, maybe you should grow up and stop telling anyone who disagrees with you to grow up There is nothing wrong with Nicks statement about considering all options, in fact any executive officer would expect that of people in sys admin positions, if something does not do what you need, find something that does, fanboi-ism and loyalty dont cut it in teh real world Changes never come about unless you put a case forward, which is what four people at least have done so now in this thread, and at least two others who have under a previous thread, so maybe call it six, take into account the number of members on this list who use multiple boxes with databases, then look at the number of those who are not members of this list who use the software, the OP of this thread made mention of twitter, and had replies there. I can see if this was something that was super critical to a functioning how the fark would you know little SOHO boy whgat is critical to anyone else's operations, when you become responsible for a decent size network which demands 5 9's uptime, maybe then, and only then, will people take your little tangents more seriously, Harold and the OP have already stated, as have I, why such a function in its current state, is flawed. Daniel's comment about mysqlproxy is a good interim bandaid fix, but is not suited as long term fix since it adds extra link in the chain which leads to extra point of failure, be it through program error or exploit, I know that Wietse and Timo take security seriously, far more so than Oracle. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Dovecot mysql replication
On Thu, 2013-05-30 at 15:10 +0200, Robert Schetterer wrote: Hi Harald, if you declare this broken, why not fix it yourself, instead of barking to the moon, however the current behave should be written in the wiki, to avoid recover the same questions on the list in periods Question Robert, if you think something is amiss with bit of software, or think it can be enhanced by a feature, say with dovecot or postfix, or mysql, what do you do? I bet you do not develop the code and submit it, most system admins would not, you ask the dev team but putting your case forward to them, showing justification if need by why feature is good/bad blah blah blah, so why if tis does not affect you, do you pop in with comments saying those people are just barking to the moon... You and others, namely Mr Marcus, should think about that before you put your fingers back on your keyboard with any reply. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] recursive mail_location?
Karol Jurak karol.ju...@gmail.com writes:
On Thursday 30 of May 2013 10:33:01 Eric Abrahamsen wrote:
Does anyone have a recommended way of handling this? Is it possible to
either flatten the structure further, or somehow tell dovecot to
recurse into directories? I don't mind having a separate gnus server
for each mail account, but I'd hate to have to do one per mailbox.
Maybe setting LAYOUT=fs (and possibly DIRNAME) in mail_location could
somehow help you?
More on this settings is here:
http://wiki2.dovecot.org/MailLocation/Maildir
Thanks for this! I've tried a couple of different things now. With the
original mbsync invocation (a top-level ~/.mail, one subdir per account,
another subdir per mailbox), I tried one of these per account, in gnus:
/usr/lib/dovecot/imap -o mail_location=maildir:$HOME/.mail/acc1/:LAYOUT=fs
I get this:
.mail
├── acc1
│ ├── cur
│ ├── dovecot.index.log
│ ├── dovecot-uidlist
│ ├── dovecot-uidvalidity
│ ├── dovecot-uidvalidity.51a7e756
│ ├── [Gmail].Drafts
│ │ ├── cur
│ │ ├── new
│ │ └── tmp
│ ├── [Gmail].Important
│ │ ├── cur
│ │ ├── new
│ │ └── tmp
│ ├── [Gmail].Sent Mail
│ │ ├── cur
│ │ ├── dovecot.index.cache
│ │ ├── dovecot.index.log
│ │ ├── dovecot-uidlist
│ │ ├── new
│ │ └── tmp
│ ├── Inbox
│ │ ├── cur
│ │ ├── new
│ │ └── tmp
│ │(the other usual boxes)
│ ├── new
│ └── tmp
(repeat for other accounts, all exactly the same)
So dovecot makes top-level {cur,new,tmp} directories, but there's
nothing in them. In the mailboxes, only [Gmail].Sent Mail seems to be
properly read. Inside Gnus, only Inbox and [Gmail].Sent Mail are listed
as available boxes, and only Sent Mail actually has mail in it. Inbox
reports as empty (though there are plenty of messages in the cur
directory).
Then I tried changing the dovecot invocations to this:
/usr/lib/dovecot/imap -o
mail_location=maildir:$HOME/.mail/:LAYOUT=fs:DIRNAME=acc1
So each invocation has the same maildir path, but a different account
name in DIRNAME. That got me this:
.mail
├── acc1
│ ├── [Gmail].Drafts
│ │ ├── cur
│ │ ├── new
│ │ └── tmp
│ ├── [Gmail].Important
│ │ ├── cur
│ │ ├── new
│ │ └── tmp
│ │Other boxes
│ └── Inbox
│ ├── cur
│ ├── new
│ └── tmp
├── dovecot.mailbox.log
├── dovecot-uidvalidity
├── dovecot-uidvalidity.51a7eea4
├── acc2
│ ├── [Gmail].Drafts
│ │ ├── cur
│ │ ├── new
│ │ └── tmp
│ ├── [Gmail].Important
│ │ ├── cur
│ │ ├── new
│ │ └── tmp
│ │Other boxes
│ └── Inbox
│ ├── cur
│ ├── new
│ └── tmp
├── INBOX
│ ├── acc1
│ │ ├── cur
│ │ ├── dovecot.index.log
│ │ ├── dovecot-uidlist
│ │ ├── new
│ │ └── tmp
│ └── acc2
│ ├── cur
│ ├── dovecot.index.log
│ ├── dovecot-uidlist
│ ├── new
│ └── tmp
Now *only* the INBOX for each account shows up in gnus, but it's still
empty.
Sorry for this monster posting, but I feel like this would all line up
properly with the right tweaks, either in mbsync or dovecot -- I just
don't know how. Any further advice would be much appreciated!
Eric
