Re: Save user passwords in clear text
* Lefteris Tsintjelis 2016.08.05 21:01: > Is it possible to save user passwords as clear text through dovecot? Have a look at how schemes can be converted using postlogin scripts: http://wiki2.dovecot.org/HowTo/ConvertPasswordSchemes signature.asc Description: Digital signature
Sieve with many criteria
Hi,
currently I am putting all my filter strings into a big array in my
sieve script. I wonder whether this is the best way to store many
criteria. Any suggestions?
--
Cheers,\\|//
Vince (o o)
ooO-(_)-Ooo-
''' (o)_(o)[ ][0][ ]
ô¿ô (=°o°=) World Domination by Copy and Paste [ ][ ][0]
-(")_(")[0][0][0]
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
Ooo.
---.ooO( )-
( )(_/
\_)
Re: receiving and associating emails to single a/c
Hi Steffen,
Many thanks for your reply. I suspect I will be prevented from using
LMTP as the protocol from DMZ MTA to the Dovecot and will be asked to
use SMTP.
In which case, I am thinking to install PostFix on the same Dovecot
server and associate the email addresses/domains there and use LMTP from
Postfix to Dovecot on local unix socket.
Would this work?
Regards,
David.
On 12-Aug-16 6:50 PM, Steffen Kaiser wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 11 Aug 2016, David Tildesley wrote:
Hi,Looking for advice.Scenario: we have a dmz mta that currently
redirects received emails for a selection of email domains to
specific internal ms exchange servers. We want this mta to redirect
incoming customer emails directed to a set of email addresses
numbering about 30, to a dovecot server and associate these emails to
a single dovecot user account so that a contact Centre platform can
pull these emails on a frequent cycle.How to go about configuring
this on the dovecot? I assume a postfix server needs to be installed
on the dovecot server for the dmz mta to send these emails to dovecot
inbox?
So, you want to sent messages of 30 or so specific mail addresses to
one Dovecot server.
First, configure the Dovecot server so, that those addresses are
mapped to the same (virtual) user account via a userdb.
Second, enabled LMTP in Dovecot.
Third, configure the MTA in the DMZ to drop the messages via LMTP to
Dovecot.
Forth, configure a passdb{} in Dovecot so that the contact people may
access the same mail storage.
There are many different ways for step 1 and for LMTP itself.
- -- Steffen Kaiser
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQEVAwUBV61xvnz1H7kL/d9rAQJEkggApg16h2Xxbxa0Bj1ut3EewqxsfYdtOfE3
yM1URhunMN4YIZ/hwuA9DrUo104+0spnOjNdz5GaDfi3Y3QfwLNTUQrmS24Ih9zG
YGbmtsC0izfudfGeLb5zHRC+GDJV4g2j67pSEg7rwQdfnS6LTgtwPyMrcCxLtRjQ
OCCya26u3TJLwgZ73BTe53HLSlfFYL739rvpk16aLhl/B6i8Ue9PYYNEa6hk2tRe
FMc3QLv3iBvsfDrT38oXpwaoF7J20LH7jWNExgF2ZAeBLdpESCNK6jHNeS9qjAaI
DZY9ZJ6D/oQXnq+iScYBgWLrz8cS6v1TckOxjQSvqUH8gKXJO9PShQ==
=7mdJ
-END PGP SIGNATURE-
Re: Dovecot Director self ip
Hello! Still struggling with setting this up. Is there maybe some fix around it or some other setting I can use? One idea, though not for production, is to add just one IP to the config and then add another Director with "doveadm director add ip", but this is just for development and testing. As far as I understand, the Director tries all IPs in the setting and the first it can bind, it gives it as local IP - self IP. This normally works, because default setting for net.ipv4.ip_nonlocal_bind is set to 0. So there is probably some other way to check local IP and set it as self? This "bug" is here for some years now, does anybody have any idea how would it be possible to fix this? Thank you very much for your help, Thomas On 29. 07. 2016 21:59, Tomaž wrote: Hello everybody! I kindly ask somebody to help me with this problem. I'm trying to configure Dovecot proxy with Director. On the same machine is KeepAlived that needs this configured to bind non local IP: sysctl net.ipv4.ip_nonlocal_bind=1 But as already mentioned in this email: http://www.dovecot.org/list/dovecot/2012-November/087033.html Dovecot Director needs sysctl net.ipv4.ip_nonlocal_bind=0 (if this is set, everything works ok, but we break keepalived) because otherwise the second server uses IP from the first server as "self". Is it possible to configure this some other way, so Dovecot Director doesn't try to bind to all IPs and because of above configuration, uses the first one that binds. This is the result from director status on server 1: root@u1:~# doveadm director ring status director ipport type last failed status 172.16.100.191 9090 self never handshaking 172.16.100.192 9090 never handshaking and server 2: root@u2:/var/log# doveadm director ring status director ipport type last failed status 172.16.100.191 9090 self never handshaking 172.16.100.192 9090 never My dovecot config: http://pastebin.com/RnmHRWhY Thank you very much! Thomas
