search for: 10143

> The C5x and C6x output diverges in build 10143, which has log message "lpc > floor converted to fixed-point." Also, the measured SNR changed from 11.05 > in builds 9854-10141 to 9.22 and 9.24 in 10143. Actually, build 10143 introduced another bug, that was the reason for the 1.1.11.1 release. > There is just four lines...

Is it possible to have multiple Listen directives in a dovecot configuration file for the same protocol? I am running dovecot-1.2.11 and I want to be able to use the "standard port" as well as a test port: protocol imap { listen = *:143 listen = *:10143 ssl_listen = *:993 ssl_listen = *:10993 for example. Or is this more preferably done by pointing dovecot at different configuration files?

Q1: My imap server has 4 interfaces, but only one is used for imap traffic. Can I do this: listen = 10.20.30.40:10143 (when imap.mycollege.edu is 10.20.30.40) Or is there even any benefit to doing this? Q2: Can I specify more than one port....during test eval, I've had the IT dept using port 1043 for listen....which I will, of course, change to 143 when DC goes production. So my department isn't cut of...

Hi, I want to change ports that Dovecot uses to listen for connections. I have listen = [::] in global section and listen = 0.0.0.0:10143 and listen = 0.0.0.0:10110 in protocol imap and protocol pop3 sections. The problem is that it doesn't seem to work for SSL ports of the two protocols and I get following error when I try to start the service: Fatal: listen(993) failed: Address already in use This is because I still have IMA...

Jean Marc, >> The C5x and C6x output diverges in build 10143, which has log message >> "lpc >> floor converted to fixed-point." Also, the measured SNR changed from >> 11.05 >> in builds 9854-10141 to 9.22 and 9.24 in 10143. > >Actually, build 10143 introduced another bug, that was the reason for >the 1.1.11.1 rel...

...:41:23 Error: IMAP(username): Next message unexpectedly lost from 337928 The message is not moved/copied. My config (dovecot -n): base_dir: /var/run/dovecot_test/ log_path: /var/log/dovecot/test_log info_log_path: /var/log/dovecot/test_info_log protocols: pop3s imaps pop3 imap listen(default): *:10143 listen(imap): *:10143 listen(pop3): *:10110 ssl_listen(default): *:10993 ssl_listen(imap): *:10993 ssl_listen(pop3): *:10995 ssl_cert_file: /etc/ssl/anxur.pem ssl_key_file: /etc/ssl/anxur.pem ssl_parameters_regenerate: 24 login_dir: /var/run/dovecot_test/login login_executable(default): /packages/r...

...taleas *----- haproxy configuration ------ *frontend frontend_mail.company.org-143 bind 10.100.189.34:143 mode tcp default_backend backend_mail.company.org-143 backend backend_mail.company.org-143 mode tcp balance source server dovecot-proxy01.company.org dovecot-proxy01.company.org:10143 check send-proxy-v2 server dovecot-proxy02.company.org dovecot-proxy02.company.org:10143 check send-proxy-v2 backup *----- config Dovecot Proxy -----* /root at dovecot-proxy01:~# dovecot -n # 2.2.24 (a82c823): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.13 (7b14904) # OS: Linux 3.16....

...tested the 1.0.7 configuration previously using a standard IMAP mail client. When I try with 1.2.17 I can't seem to get logged in. ==> /var/log/maillog <== Jul 27 21:48:26 email dovecot: auth(default): client in: AUTH 1 PLAIN service=imap secured lip=192.168.1.10 rip=202.81.69.135 lport=10143 rport=58641 resp=ADYxNDE0NjI3NDM2AFExcjQwNHVD Jul 27 21:48:26 email dovecot: auth-worker(default): pam(john,202.81.69.135): lookup service=dovecot Jul 27 21:48:26 email dovecot: auth-worker(default): pam(john,202.81.69.135): #1/1 style=1 msg=Password: Jul 27 21:48:28 email dovecot: auth-worker(def...

...c/postfix/vmailbox virtual_minimum_uid = 100 virtual_transport = dovecot virtual_uid_maps = static:5000 #dovecot -n # /etc/dovecot/dovecot.conf log_path: /var/log/dovecot.info info_log_path: /var/log/dovecot.info log_timestamp: %d-%m-%Y %H:%M:%S protocols: imap pop3 imaps pop3s listen(default): *:10143 listen(imap): *:10143 listen(pop3): * disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login login_greeting: Mail POP...

...ything that appears in your logs should be > *interesting*. Constant port knocking from worms and script kiddies is > not interesting. > > In case you've not done ssh tunelling, Anne, the command that does what > you want, having done all the above is: > > $ ssh -p22022 -L10143:my.server.com:143 anne at my.server.com > > This sets up port 10143 on the local system to be redirected through the > ssh session to the IMAP port on your home server. You don't want to > redirect 143 to 143 because that would require you to run ssh as root. > It also prevents...

...esieve.log info_log_path(default): /var/log/dovecot-test/info.log info_log_path(imap): /var/log/dovecot-test/info.log info_log_path(pop3): /var/log/dovecot-test/info.log info_log_path(managesieve): /var/log/dovecot-test/managesieve.log protocols: imap imaps pop3 pop3s managesieve listen(default): *:10143 listen(imap): *:10143 listen(pop3): *:10110 listen(managesieve): *:12000 ssl_listen(default): *:10943 ssl_listen(imap): *:10943 ssl_listen(pop3): *:10995 ssl_listen(managesieve): ssl_cert_file: /etc/ssl/certs/imap-cert.pem ssl_key_file: /etc/ssl/private/imap-key.pem shutdown_clients: no login_dir:...

...all, I need your insight. I've been testing Dovecot on an AIX 5.2 system. Compiled and running fine. We have some users on an AIX 5.1 system, so I'm working on installing it there, so we can do further testing. I'm using Dovecot 1.0 RC15 with OpenSSL 9.0.7e, configured to use port 10143 (imap) and 10993 (imaps). The error I'm seeing in the log is: dovecot: Nov 28 09:23:54 Info: imap-login: Login: user=<jackie>, method=PLAIN, r ip=xx.x.xxx.xxx, lip=xxx.xx.xxx.xx, TLS dovecot: Nov 28 09:23:54 Error: IMAP(jackie): We couldn't drop root group privil eges (wanted=200, g...

...| |----------|------|-------|------|-------|------|-------|------|-------| | 10151 | Pass | 848/3 | Fail | | Pass | | Pass | 851/0 | | | | (1,2) | (7) | | | | | | |----------|------|-------|------|-------|------|-------|------|-------| | 10143 | Pass | 849/2 | Fail | | Pass | | Pass | 851/0 | | | | (1,2) | (7) | | | | | | |----------|------|-------|------|-------|------|-------|------|-------| | 10068 | Pass | 848/3 | Fail | | Pass | | Pass | 851/0 | | |...

...vecot-sql.conf has: driver = sqlite connect = /etc/dovecot/empty.db password_query = select 'y' as proxy, \ NULL as password, \ 'y' as nopassword, \ case '%a' \ when '110' then '10110' \ when '995' then '10110' \ when '143' then '10143' \ when '993' then '10143' end \ as port; (where empty.db is completely empty; this is just used since there's no other way to handle the port mapping, as described elsewhere on the list). A static proxy setup does work, with the normal imap / pop3 listeners. # 2.0.9: /etc...

...t/dovecot-sql.conf] driver = sqlite connect = /etc/dovecot/empty.db password_query = select 'y' as proxy, \ NULL as password, \ 'y' as nopassword, \ case '%a' \ when '110' then '10110' \ when '995' then '10110' \ when '143' then '10143' \ when '993' then '10143' end \ as port; This works, but I was getting a failure on usernames, since director instance didn't have a userdb. So I tried the following: [in config] passdb { driver = sql args = /etc/dovecot/dovecot-sql.conf } userdb { driver = prefetc...

...". > and..... > > If you want to specify ports for each service, you will need to > configure these settings inside the *protocol* imap/pop3 { ... } > section, so you can specify different ports for IMAP/POP3. For example: > > # *protocol* imap { > # listen = *:10143 > # ssl_listen = *:10943 > # .. > # } > So if I want to run both imap and imaps AND configure the port, do I do: # *protocol* imap { # listen = *:143 # ssl_listen = *:10943 # } OR # *protocol* imap { # listen = *:143 # } # *protocol* imaps { # l...

I have setup director and a backend dovecot service on the same machine using different ports. The backend service is listening on the default 24, 110 and 143 for lmtp, pop3 and imap respectively. Director is listening on 10024, 10110 and 10143 for the same respective services. I can get this setup to work if I have one backend server on a different IP listening on 10024, it seems director tries to use the same port it is listening on when making backend connections. If I point it to the local backend server, it tries to connect to itse...

...a minute or longer to delete a single message from the INBOX to Trash. This is happening for him from multiple IMAP clients so it appears to be server-side. I wanted to start up a test instance of dovecot alongside the production one and test there. So I copied dovecot.conf, put imap on port 10143, and started up the test server like this: # strace -tt dovecot -F -c /etc/dovecottest.conf (I could not find the docs for -F but without it dovecot would quickly detatch into a daemon and I could no longer strace it... so is -F for putting dovecot in the foreground like I think? :-) I notic...

@2.0's master.conf, there's, e.g., service config { type= config executable =config unix_listener { path = config mode = 0666 } } can someone please explain function/usage for the 'type', 'executable' & 'path' fields? and, for any file paths, are the presumed to be _relative_ to the dovecot executable? in $PATH? can they accept full/absolute

...local/www/data/Email/RefCont/etc pwd_mkdb -d ${etc_path} ${etc_path}master.passwd pw useradd -V ${etc_path} -n $1 -g mailusers -s /tmp/email/bin/nonexistance echo "$2" | pw usermod -V ${etc_path} -n $1 -h 0 My config: # /usr/local/etc/dovecot.conf protocols: imap pop3 listen(default): *:10143 listen(imap): *:10143 listen(pop3): *:10110 ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot...