similar to: listen directive changed?

Displaying 20 results from an estimated 10000 matches similar to: "listen directive changed?"

2010 Nov 01
3
Wrong protocol in socket (director-doveadm vs director) ?
I just noticed this error in my logs: director: Error: doveadm not compatible with this server (mixed old and new binaries?) director: Error: director(10.161.192.28:541/right): Wrong protocol in socket (director-doveadm vs director) The first error I removed by changing director_doveadm_port = 541 to director_doveadm_port = 542 Not really sure why that fixed it. The second error I
2019 Dec 11
2
Submission config being ignored
I'm having trouble setting up submission with Dovecot proxy. The submission config seems to be getting ignored, but I'm probably doing something wrong. Expected behaviour: have messages sent to submission ports (25, 465) relayed to `submission_relay_host`. -- root at imapproxy1:~# cat /etc/dovecot/conf.d/20-submission.conf submission_logout_format = in=%i out=%o submission_relay_host =
2016 Dec 29
5
two listeners with different "driver = " configs
Hi, I would like to have two seperate imap listeners, with different authentication settings, but the mailstore and userbase etc will be identical. I know I can do this: > service imap-login { > inet_listener imap { > port = 143 > } > inet_listener imap2 { > port = 144 > } > } But I'm unsure how to configure imap/143 with "driver =
2015 Apr 18
1
Aw: Re: Please help: error after upgrade to version 2.1.16
thanks, but I do not understand was has a new configuration to do with my auth-Problem? My configuration settings has worked before the Update to 2.1.16. I have not see that the update has changed some of my config-files. ? Gesendet:?Samstag, 18. April 2015 um 20:24 Uhr Von:?"Edgar Pettijohn III" <edgar at pettijohn-web.com> An:?"Dovecot Mailing List" <dovecot at
2015 Apr 18
2
Please help: error after upgrade to version 2.1.16
Hallo I can not find a forum at dovecot.org and I get a problem I can not solve. After Updating to the version dovecot2? 2.1.16? I can no more get eMails with my eMail-client. All has been working fine before. Server: FreeBSD 10.0-RELEASE-p18, with perl 5, version 18, subversion 4 (v5.18.4) ? It seems it is an authentication problem with my server. The errors are: #cat dovecot.log Apr 17
2019 Dec 11
3
Lightweight LMTP daemon to avoid overkill MTA
Hi, I was unclear in my question. The spam filter is only able to deliver mail over SMTP, not over LMTP.. So I would still need some kind of daemon that listens for SMTP and then offers incoming email to Dovecot's LMTP socket. Met vriendelijke groeten, William Edwards T. 040 - 711 44 96 E. wedwards at cyberfusion.nl ? ----- Original Message ----- From: Marc Roos (M.Roos at
2019 Dec 11
3
Lightweight LMTP daemon to avoid overkill MTA
Hi, My situation is as follows. -An internet-facing spam filter relays email to destination mail server (Dovecot) with SMTP. - Dovecot should take email and deliver it to user's mailboxes. I guess I'd need LMTP for this. - An external SMTP relay is already in place. I am thinking of using Dovecot submission to relay to the external relaying cluster. So, both relaying and routing are done
2010 Apr 14
5
Dovecot 2.0b4 configuration issue, listen config option?
Hi, In my 1.2 setup I have pop3 running on ip x.x.x.2 and imap on x.x.x.7 In 2.0 how do I say listen x.x.x.2:110 x.x.x.7:143 so that pop3 is not listening on the .7 ip? I tried putting a listen = ip in the listener section but it complained. I cant figure it out and cant seem to find any 2.0 specific documentation, trying to search in the wiki directory of /usr/local/share/doc/dovecot/wiki but
2014 Jun 03
2
director with multiple instances
I'm experiencing some problems similar to those described in http://dovecot.org/list/dovecot/2012-July/137250.html except with 2.0.9. Adding http://dovecot.org/list/dovecot/2012-July/084906.html to the main config didn't seem to help, nor did setting the list of director and backend servers to just the system itself. I get a banner connecting to port 143: [root at retr01 log]# telnet
2014 Apr 17
1
How to disable Director service?
Hi All, Does anyone know how to disable the Director service. In our current running Dovecot 2.2.4, if the director configuration is commented out and Dovecot has no errors nor warnings. But the version 2.2.12 I'm testing with gives out fatal errors. We have dedicated Dovecot Director servers that serve the public frontend and separate dedicated imap/pop3 servers on the backend
2011 Oct 28
6
how to tell dovecot v2.0.1 not to listen on port 143
Hi there. How can I configure dovecot not to listen for imaps connections on port 143. Thanks Lars
2016 Jun 17
2
Mailbox location
I am running a small server with a fixed number of users. Postfix is using dovecot lda so that I can run pigeonhole. I have setup a user file with the ids and passwords and everything authenticates properly. Postfix uses that also. However, mail is consistently delivered to user at domain. How do I tell it to deliver to just user? I have tried setting a variety of different things like:
2016 Oct 12
2
Detect IMAP server domain name in Dovecot IMAP proxy
I?m in the process of setting up a Dovecot IMAP proxy to handle a number of IMAP server domains. At the current time, I have my users divided into 70 different groups of users (call them G1 to G70). I want each group to configure their email client to access their mailboxes at a domain name based on the group they belong to (e.g., g1.example.com <http://g1.example.com/>, g2.example.com
2019 Dec 12
1
Lightweight LMTP daemon to avoid overkill MTA
I ended up 'hacking' LMTP support into the external spam filter. Someone else already contributed 'real' patches to implement LMTP support, so once I go live with this mail platform it should be stable. Met vriendelijke groeten, William Edwards T. 040 - 711 44 96 E. wedwards at cyberfusion.nl ? ----- Original Message ----- From: Marc Roos (M.Roos at f1-outsourcing.eu) Date:
2014 Jan 27
1
Auth socket can't listen using ssl
Hi, I'm using Dovecot 2.2.9 (debian package on testing). It seems that it's not possible to open an auth socket using ssl. I'm using this configuration : service auth { [...] inet_listener authxmpp-client { address = [ips] port = 5220 } inet_listener genericauth-client { ssl = yes address = [ips] port = 5221 } [...] } Both ports are running fine. But
2015 Aug 22
4
PROXY protocol
Op 8/21/2015 om 1:31 PM schreef Nikolaos Milas: > On 20/8/2015 11:09 ??, Nikolaos Milas wrote: > >> As soon as I manage to re-build Dovecot with the latest snapshot, >> I'll test it! > > Hello, > > I've built dovecot with a today snapshot from hg > (dovecot-2-2-9f815e781beb) and I am trying to enable haproxy. > > I configured as follows (lines added
2010 Mar 09
2
2.0beta3 10876:370ee9717a6c broke listen on literal IPv6 address
Hi, apparently the following change in dovecot hg * New revision (10876:370ee9717a6c) in dovecot Mercurial repository: - config: Forgot to add header file. broke listen = 83.170.6.69, 2001:1b10:1000::110:1:1 mail.svr02.mucip.net:~# dovecot -F -c /etc/dovecot/dovecot.conf doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:29: listen=..:port has been replaced by service {
2015 Apr 17
1
ManageSieve Dovecot v2 listen on localhost only
Thanks. I tried that now and added the "address": service managesieve-login { inet_listener sieve { port = 4190 address = 127.0.0.1 } I restarted dovecot but: tcp 0 0 0.0.0.0:4190 0.0.0.0:* LISTEN 0 522413 22288/dovecot Why is this not working? Quoting Gedalya <gedalya at gedalya.net>: >
2012 Oct 05
5
IPv6 & SSL
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have a dual stack server with Dovecot 2.1.10 listening on v4 and v6 Dovecot has a Comodo SSL certificate issued via NameCheap that works as expected with IPv4 in 10-ssl.conf I have enabled these configuraction directives: ssl = yes ssl_cert = < /path/to/file.crt ssl_key = < /path/to/file.key ssl_parameters_regenerate = 202 hours If I
2012 Mar 13
1
upgrade convert omissions
It did not convert over some things: protocol imap { listen = *:143 mail_plugins = quota imap_quota imap_client_workarounds = outlook-idle ssl_listen = *:993 } protocol pop3 { pop3_uidl_format = %f mail_plugins = quota pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } protocol lda { mail_plugins = quota cmusieve