Zimbra mail send failure как исправить

deon1sk4
( 30.11.16 16:51:27 MSK ) автор топика

обновись, хотя бы до 1178

fbiagent ★★★
( 30.11.16 17:43:56 MSK )

В /opt/zimbra/log/mailbox.log ни чего подозрительного нет?

julixs ★★★
( 30.11.16 20:35:38 MSK )
Mamin_simpotyaga ★
( 01.12.16 07:58:02 MSK )
Ответ на: комментарий от julixs 30.11.16 20:35:38 MSK

2016-12-01 00:00:06,380 INFO [qtp509886383-530:https://127.0.0.1:7071/service/admin/soap/AuthRequest] [name=zimbra;ip=127.0.0.1;ua=zmprov/8.6.0_GA_1153;] soap - AuthRequest elapsed=206 2016-12-01 00:00:08,558 INFO [qtp509886383-529:https://127.0.0.1:7071/service/admin/soap/GetAllServersRequest] [name=zimbra;ip=127.0.0.1;ua=zmprov/8.6.0_GA_1153;] soap - GetAllServersReques$ 2016-12-01 00:00:16,372 INFO [MailboxPurge] [name=tkalich@domen.ru;mid=14;] purge - Purging messages. 2016-12-01 00:00:56,745 INFO [ImapServer-6] [name=griovsky@domen.ru ;mid=3;ip=192.168.13.26;ua=Thunderbird/45.5.0;] imap - IDLE elapsed=1 2016-12-01 00:00:56,747 INFO [ImapServer-6] [name=griovsky@domen.ru belgorod.ru;mid=3;ip=192.168.13.26;ua=Thunderbird/45.5.0;] imap - NOOP elapsed=0 2016-12-01 00:00:56,749 INFO [ImapServer-6] [name=griovsky@domen.ru ;mid=3;ip=192.168.13.26;ua=Thunderbird/45.5.0;] imap - GETQUOTAROOT elapsed=0 2016-12-01 00:00:56,751 INFO [ImapServer-6] [name=griovsky@domen.ru ;mid=3;ip=192.168.13.26;ua=Thunderbird/45.5.0;] imap - UID FETCH elapsed=0 2016-12-01 00:00:56,812 INFO [ImapServer-6] [name=griovsky@domen.ru ;mid=3;ip=192.168.13.26;ua=Thunderbird/45.5.0;] imap - IDLE elapsed=1 2016-12-01 00:01:16,383 INFO [MailboxPurge] [name=spam.oqw3jflb@domen.ru;mid=15;] purge - Purging messages. 2016-12-01 00:02:16,389 INFO [MailboxPurge] [name=ham.vxosgpjx@domen.ru;mid=16;] purge - Purging messages. 2016-12-01 00:02:32,381 INFO [ImapServer-6] [name=tkaich@domen.ru ;mid=14;ip=192.168.13.28;ua=Thunderbird/45.5.0;] imap - IDLE elapsed=0 2016-12-01 00:02:32,384 INFO [ImapServer-6] [name=tkalich@domen.ru ;mid=14;ip=192.168.13.28;ua=Thunderbird/45.5.0;] imap - NOOP elapsed=0 2016-12-01 00:02:32,387 INFO [ImapServer-6] [name=tkaich@domen.ru ;mid=14;ip=192.168.13.28;ua=Thunderbird/45.5.0;] imap - GETQUOTAROOT elapsed=1 2016-12-01 00:02:32,389 INFO [ImapServer-6] [name=tkaich@domen.ru ;mid=14;ip=192.168.13.28;ua=Thunderbird/45.5.0;] imap - UID FETCH elapsed=1 2016-12-01 00:02:32,446 INFO [ImapServer-6] [name=tkaich@domen.ru ;mid=14;ip=192.168.13.28;ua=Thunderbird/45.5.0;] imap - CHECK elapsed=0 2016-12-01 00:02:32,480 INFO [ImapServer-6] [name=tkaich@domen.ru ;mid=14;ip=192.168.13.28;ua=Thunderbird/45.5.0;] imap - IDLE elapsed=0 2016-12-01 00:03:16,398 INFO [MailboxPurge] [name=kk@domen.ru;mid=22;] purge - Purging messages. 2016-12-01 00:04:16,405 INFO [MailboxPurge] [name=may@domen.ru;mid=24;] purge - Purging messages. 2016-12-01 00:05:16,418 INFO [MailboxPurge] [name=galsync.u6xqin95v9@domen.ru;mid=1;] purge - Purging messages.

deon1sk4
( 01.12.16 07:58:18 MSK ) автор топика
Ответ на: комментарий от fbiagent 30.11.16 17:43:56 MSK

так а смысл в обновлении, работало все стабильно.

deon1sk4
( 01.12.16 08:02:48 MSK ) автор топика

Ну если по порядку, то если это denisiteum@gmail.com не придуманный адрес, то его не существует.

[url=]Проблема Zimbra (комментарий), это кусок лога при ошибке? Что говорят другие логи? При отправке сообщений из thunderbird ошибки возникают?

julixs ★★★
( 01.12.16 09:12:33 MSK )
Ответ на: комментарий от julixs 01.12.16 09:12:33 MSK

у меня такая же проблема после обновления, тут решение

Zimbra, почта не доходит на яндекс почту

Добрый день, проблема следующая, установил почтовый сервер зимбра, настроил записи днс, но проблема в том, что письма с зимбры не доходят до почты яндекса. на майлру, рамблер, гугл почту письма доходят, на яндекс нет, подскажите, в чем проблема может быть?

Mar 23 10:47:16 mail postfix/smtps/smtpd[1349423]: connect from unknown[46.148.40.142] Mar 23 10:47:17 mail postfix/smtps/smtpd[1349423]: Anonymous TLS connection established from unknown[46.148.40.142]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits) Mar 23 10:47:22 mail postfix/smtps/smtpd[1349423]: warning: unknown[46.148.40.142]: SASL LOGIN authentication failed: authentication failure Mar 23 10:47:23 mail postfix/smtps/smtpd[1349423]: lost connection after AUTH from unknown[46.148.40.142] Mar 23 10:47:23 mail postfix/smtps/smtpd[1349423]: disconnect from unknown[46.148.40.142] ehlo=1 auth=0/1 rset=1 commands=2/3 Mar 23 10:47:25 mail postfix/postscreen[1357029]: CONNECT from [127.0.0.1]:39136 to [127.0.1.1]:25 Mar 23 10:47:25 mail postfix/postscreen[1357029]: ALLOWLISTED [127.0.0.1]:39136 Mar 23 10:47:25 mail postfix/smtpd[1357030]: connect from localhost[127.0.0.1] Mar 23 10:47:25 mail postfix/smtpd[1357030]: NOQUEUE: filter: RCPT from localhost[127.0.0.1]: : Sender address triggers FILTER smtp-amavis:[127.0.0.1]:10026; from= to= proto=ESMTP helo= Mar 23 10:47:25 mail postfix/smtpd[1357030]: A86F51D2EE: client=localhost[127.0.0.1] Mar 23 10:47:25 mail postfix/cleanup[1357031]: A86F51D2EE: message-id= Mar 23 10:47:25 mail postfix/smtpd[1357030]: disconnect from localhost[127.0.0.1] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 Mar 23 10:47:26 mail postfix/qmgr[1000378]: A86F51D2EE: from=, size=1461, nrcpt=1 (queue active) Mar 23 10:47:26 mail postfix/amavisd/smtpd[1357033]: connect from localhost[127.0.0.1] Mar 23 10:47:26 mail postfix/amavisd/smtpd[1357033]: 104BD1D36F: client=localhost[127.0.0.1] Mar 23 10:47:26 mail postfix/cleanup[1357031]: 104BD1D36F: message-id= Mar 23 10:47:26 mail postfix/qmgr[1000378]: 104BD1D36F: from=, size=1838, nrcpt=1 (queue active) Mar 23 10:47:26 mail postfix/smtp[1357032]: A86F51D2EE: to=, relay=127.0.0.1[127.0.0.1]:10026, delay=0.6, delays=0.31/0.01/0/0.28, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 104BD1D36F) Mar 23 10:47:26 mail postfix/qmgr[1000378]: A86F51D2EE: removed Mar 23 10:47:26 mail postfix/amavisd/smtpd[1357033]: disconnect from localhost[127.0.0.1] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 Mar 23 10:47:37 mail postfix/submission/smtpd[1357038]: connect from unknown[45.12.253.13] Mar 23 10:47:38 mail postfix/submission/smtpd[1357038]: Anonymous TLS connection established from unknown[45.12.253.13]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits) Mar 23 10:47:38 mail postfix/submission/smtpd[1357038]: warning: unknown[45.12.253.13]: SASL LOGIN authentication failed: authentication failure Mar 23 10:47:38 mail postfix/submission/smtpd[1357038]: disconnect from unknown[45.12.253.13] ehlo=2 starttls=1 auth=0/1 quit=1 commands=4/5 Mar 23 10:47:41 mail /postfix-script[1357152]: the Postfix mail system is running: PID: 1000376 Mar 23 10:47:43 mail postfix/submission/smtpd[1357038]: connect from unknown[45.12.253.129] Mar 23 10:47:44 mail postfix/submission/smtpd[1357038]: Anonymous TLS connection established from unknown[45.12.253.129]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits) Mar 23 10:47:44 mail postfix/submission/smtpd[1357038]: warning: unknown[45.12.253.129]: SASL LOGIN authentication failed: authentication failure Mar 23 10:47:44 mail postfix/submission/smtpd[1357038]: disconnect from unknown[45.12.253.129] ehlo=2 starttls=1 auth=0/1 quit=1 commands=4/5 Mar 23 10:48:02 mail /postfix-script[1357661]: the Postfix mail system is running: PID: 1000376 Mar 23 10:48:06 mail postfix/smtp[1356616]: connect to yandex.ru[213.180.193.56]:25: Connection timed out Mar 23 10:48:07 mail postfix/smtp[1356616]: 104BD1D36F: to=, relay=none, delay=40, delays=0.21/0/40/0, dsn=4.4.1, status=deferred (connect to yandex.ru[213.180.193.56]:25: Connection timed out) Mar 23 10:48:45 mail postfix/smtps/smtpd[1349423]: connect from unknown[46.148.40.191] Mar 23 10:48:45 mail postfix/smtps/smtpd[1349423]: Anonymous TLS connection established from unknown[46.148.40.191]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits) Mar 23 10:48:53 mail postfix/smtps/smtpd[1349423]: warning: unknown[46.148.40.191]: SASL LOGIN authentication failed: authentication failure Mar 23 10:48:55 mail postfix/smtps/smtpd[1349423]: lost connection after AUTH from unknown[46.148.40.191] Mar 23 10:48:55 mail postfix/smtps/smtpd[1349423]: disconnect from unknown[46.148.40.191] ehlo=1 auth=0/1 rset=1 commands=2/3 Mar 23 10:49:03 mail postfix/smtps/smtpd[1349423]: connect from unknown[46.148.40.141] Mar 23 10:49:04 mail postfix/smtps/smtpd[1349423]: Anonymous TLS connection established from unknown[46.148.40.141]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits) Mar 23 10:49:12 mail postfix/smtps/smtpd[1349423]: warning: unknown[46.148.40.141]: SASL LOGIN authentication failed: authentication failure Mar 23 10:49:14 mail postfix/smtps/smtpd[1349423]: lost connection after AUTH from unknown[46.148.40.141] Mar 23 10:49:14 mail postfix/smtps/smtpd[1349423]: disconnect from unknown[46.148.40.141] ehlo=1 auth=0/1 rset=1 commands=2/3 Mar 23 10:49:55 mail postfix/smtps/smtpd[1349423]: connect from unknown[46.148.40.58] Mar 23 10:49:55 mail postfix/smtps/smtpd[1358501]: connect from unknown[46.148.40.147] Mar 23 10:49:56 mail postfix/smtps/smtpd[1349423]: Anonymous TLS connection established from unknown[46.148.40.58]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits) Mar 23 10:49:56 mail postfix/smtps/smtpd[1358501]: Anonymous TLS connection established from unknown[46.148.40.147]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits) Mar 23 10:49:58 mail postfix/smtps/smtpd[1349423]: warning: unknown[46.148.40.58]: SASL LOGIN authentication failed: authentication failure Mar 23 10:49:58 mail postfix/smtps/smtpd[1349423]: lost connection after AUTH from unknown[46.148.40.58] Mar 23 10:49:58 mail postfix/smtps/smtpd[1349423]: disconnect from unknown[46.148.40.58] ehlo=1 auth=0/1 rset=1 commands=2/3 Mar 23 10:50:01 mail postfix/smtps/smtpd[1358517]: connect from unknown[46.148.40.143] Mar 23 10:50:01 mail postfix/smtps/smtpd[1358517]: Anonymous TLS connection established from unknown[46.148.40.143]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits) Mar 23 10:50:04 mail /postfix-script[1358798]: the Postfix mail system is running: PID: 1000376 Mar 23 10:50:04 mail postfix/smtps/smtpd[1358501]: warning: unknown[46.148.40.147]: SASL LOGIN authentication failed: authentication failure Mar 23 10:50:08 mail postfix/smtps/smtpd[1358501]: lost connection after AUTH from unknown[46.148.40.147] Mar 23 10:50:08 mail postfix/smtps/smtpd[1358501]: disconnect from unknown[46.148.40.147] ehlo=1 auth=0/1 rset=1 commands=2/3 Mar 23 10:50:08 mail postfix/smtps/smtpd[1358517]: warning: unknown[46.148.40.143]: SASL LOGIN authentication failed: authentication failure Mar 23 10:50:11 mail postfix/smtps/smtpd[1358517]: lost connection after AUTH from unknown[46.148.40.143] Mar 23 10:50:11 mail postfix/smtps/smtpd[1358517]: disconnect from unknown[46.148.40.143] ehlo=1 auth=0/1 rset=1 commands=2/3 Mar 23 10:50:19 mail postfix/smtps/smtpd[1349423]: connect from unknown[46.148.40.136] Mar 23 10:50:19 mail postfix/smtps/smtpd[1349423]: Anonymous TLS connection established from unknown[46.148.40.136]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits) Mar 23 10:50:24 mail postfix/smtps/smtpd[1349423]: warning: unknown[46.148.40.136]: SASL LOGIN authentication failed: authentication failure Mar 23 10:50:25 mail postfix/smtps/smtpd[1349423]: lost connection after AUTH from unknown[46.148.40.136] Mar 23 10:50:25 mail postfix/smtps/smtpd[1349423]: disconnect from unknown[46.148.40.136] ehlo=1 auth=0/1 rset=1 commands=2/3 

Тех поддержка яндекса ответила «такая ошибка возникает, когда при отправке писем на ящики Яндекса не происходит попыток передачи письма на наши сервера или сервер-отправитель пытается передать письмо не нашему серверу.»

bogkronas
27.03.23 17:12:33 MSK

• Ответить на это сообщение
• Ссылка

Unable to send mail after fresh install

I just set up Carbonio CE server for the 1st time to try it out. Immediately after install I tried sending an email to myself, which originated from the newly installed Carbonio CE server and was to an account on an already existing Zimbra server. The mail did not send, it went immediately to drafts. Upon checking /var/log/carbonio.log, I did not see an attempt to send the mail. What i did notice was the following error:

Oct 16 18:46:40 cmail zmconfigd[28722]: File "/opt/zextras/common/lib/jylibs/state.py", line 796, in rewriteConfig for line in open(fr).readlines():
Oct 16 18:46:40 cmail zmconfigd[28722]: Rewrite failed: [Errno 2] No such file or directory: '/opt/zextras/mailboxd/etc/zimbra.web.xml.in' ([Errno 2] No such file or directory: '/opt/zextras/mailboxd/etc/zimbra.web.xml.in')

Can someone tell me if these errors are related to sending mail?

Receiving mail appears to work just fine.

Thanks for the help.

Joined: 3 years ago
10/17/2022 10:09
Posted by: @amitchell

I just set up Carbonio CE server for the 1st time to try it out. Immediately after install I tried sending an email to myself, which originated from the newly installed Carbonio CE server and was to an account on an already existing Zimbra server. The mail did not send, it went immediately to drafts. Upon checking /var/log/carbonio.log, I did not see an attempt to send the mail. What i did notice was the following error:

Oct 16 18:46:40 cmail zmconfigd[28722]: File "/opt/zextras/common/lib/jylibs/state.py", line 796, in rewriteConfig for line in open(fr).readlines():
Oct 16 18:46:40 cmail zmconfigd[28722]: Rewrite failed: [Errno 2] No such file or directory: '/opt/zextras/mailboxd/etc/zimbra.web.xml.in' ([Errno 2] No such file or directory: '/opt/zextras/mailboxd/etc/zimbra.web.xml.in')

Can someone tell me if these errors are related to sending mail?

Receiving mail appears to work just fine.

Thanks for the help.

We have forwarded this issue to our team as it needed more investigation. As soon as we hear from them, we will write you back.

Thank you so much for being with us.

Reply Quote
Joined: 2 years ago
10/17/2022 10:24

Meanwhile, could you please help us with some information:

Did you follow all instructions mentioned in the official documentation upto step 7 also including setup of dnsmasq?

Thanks and regards,
Sharif

Reply Quote
Joined: 9 years ago
10/17/2022 14:06
Posted by: @amitchell

I just set up Carbonio CE server for the 1st time to try it out. Immediately after install I tried sending an email to myself, which originated from the newly installed Carbonio CE server and was to an account on an already existing Zimbra server. The mail did not send, it went immediately to drafts. Upon checking /var/log/carbonio.log, I did not see an attempt to send the mail. What i did notice was the following error:

Oct 16 18:46:40 cmail zmconfigd[28722]: File "/opt/zextras/common/lib/jylibs/state.py", line 796, in rewriteConfig for line in open(fr).readlines():
Oct 16 18:46:40 cmail zmconfigd[28722]: Rewrite failed: [Errno 2] No such file or directory: '/opt/zextras/mailboxd/etc/zimbra.web.xml.in' ([Errno 2] No such file or directory: '/opt/zextras/mailboxd/etc/zimbra.web.xml.in')

Can someone tell me if these errors are related to sending mail?

Receiving mail appears to work just fine.

Thanks for the help.

Arman Khosravi and Arman Khosravi reacted
Reply Quote
Joined: 1 year ago
Topic starter 10/20/2022 01:11

@shariful-islam Initially I did not install dnsmaq because I was using a real domain name that was pointing to the carbonio server ands had been configured in our dns to do so. Upon receiving your reply I did a fresh new install, following all steps including dnsmasq and disabling systemd-resolved. Unfortunately we are still experiencing the same exact problem. Is there anything else you need to know that would help us resolve this issue?

Reply Quote
Joined: 1 year ago
Topic starter 10/20/2022 01:51

@mgarbo Thank you for the info on fixing those errors in the log. I followed the instructions and it did remove the errors from the log file. Unfortunately it did not have any impact on the issue I am experiencing with sending mail. We tried to send a message from carbonio it immediately goes to drafts, no attempt to send the message is shown in the logfile.

Reply Quote
Joined: 2 years ago
10/20/2022 08:20

Sorry to hear that.
Just to ensure we are on the same page, I am sharing the installation procedure.

Step-1 Update & upgrade the repository database

root@mail~# apt update && apt upgrade -y

Step-2 Set Static IP address

Set static IP on your server

Step-3 Set /etc/hostname

root@mail:~# cat /etc/hostname mail.example.com

Step-4 Set /etc/hosts

Set the hosts file properly

Warning: Do not keep any ipV6 configuration in your /etc/hosts file.

root@mail:~# cat /etc/hosts 127.0.0.1 localhost 161.97.99.162 mail.latestserver.xyz mail root@mail:~#

Reboot The Server

root@mail~# reboot now

Step-5 Add zextras repository

You need to download and add the zextras repository to your system to install the necessary carbonio CE packages.

Head to the Carbonio Community Edition webpage and fill out the form. You will soon receive an e-mail including very easy instructions to add the repository to your operating system.

After you successfully added the repository, upgrade the system.

Step-6 Update & upgrade repository database

root@mail~# apt update && apt upgrade -y

Step-7 Set up dnsmasq

Warning:

• If you have published the DNS records into any public DNS server then you do not need DNSMASQ
• During the installation of dnsmasq, you may face conflict on port 53. To resolve this, remove and disable systemd-resolved.

root@mail:~# systemctl stop systemd-resolved root@mail:~# systemctl disable systemd-resolved root@mail:~# systemctl mask systemd-resolved

Now install dnsmasq: [As you have removed systemd-resolved, you need to set /etc/resolv.conf manually before trying to install dnsmasq]

root@mail:~# apt install dnsmasq -y vi /etc/dnsmasq.conf [ADD THESE LINES AT THE BOTTOM OF THE FILE] server=1.1.1.1 mx-host=example.com,mail.example.com,50 host-record=example.com,192.168.1.152 host-record=mail.example.com,192.168.1.152 #Restart the service# root@mail:~# /etc/init.d/dnsmasq restart root@mail:~# /etc/init.d/dnsmasq status

Step-8 Install Carbonio CE packages

Install and configure postgresql

root@mail:~# apt install postgresql-12 -y root@mail:~# systemctl reload postgresql

Check out this link to get the details of PostgreSQL configuration.

root@mail:~# apt install service-discover-server \ carbonio-directory-server \ carbonio-proxy \ carbonio-webui carbonio-files-ui \ carbonio-mta \ carbonio-appserver \ carbonio-user-management \ carbonio-files-ce carbonio-files-db \ carbonio-tasks-ce carbonio-tasks-db \ carbonio-tasks-ui \ carbonio-storages-ce \ carbonio-preview-ce \ carbonio-docs-connector-ce carbonio-docs-editor \ carbonio-prometheus -y

Step-9 Use the following command to configure and launch Carbonio CE

carbonio-bootstrap

Step-10 Setup Carbonio Mesh & pending setups

service-discover setup-wizard

pending-setups -a

Step-11 Configure Carbonio CE databases

root@mail:~# read -s -p "Password:" DB_ADM_PWD root@mail:~# su - postgres -c "psql --command=\"CREATE ROLE carbonio_adm WITH LOGIN SUPERUSER encrypted password '$DB_ADM_PWD';\"" root@mail:~# su - postgres -c "psql --command=\"CREATE DATABASE carbonio_adm owner carbonio_adm;\"" root@mail:~# PGPASSWORD=$DB_ADM_PWD carbonio-files-db-bootstrap carbonio_adm 127.0.0.1 root@mail:~# PGPASSWORD=$DB_ADM_PWD carbonio-tasks-db-bootstrap carbonio_adm 127.0.0.1 # To unset the variable value root@mail:~# unset DB_ADM_PWD

Step-13 Bootstrap database of Carbonio files

root@mail:~# su - zextras root@mail:~# su - zextras -c "zmcontrol restart" root@mail:~# systemctl restart carbonio-prometheus-nginx-exporter.service root@mail:~# su - zextras -c "zmcontrol -v" root@mail:~# su - zextras -c "zmcontrol status" root@mail:~# consul members root@mail:~# systemctl list-units carbonio*

With this step, the installation process is completed.

If you followed all of these steps and still not been able to send mail, please check below issues:

1. You server can resolve dns; i.e ping google.com or query mx

2. You have set the server hostname properly.

Zimbra Proxy: Troubleshooting Zimbra Proxy

- This is certified documentation and is protected for editing by Zimbra Employees & Moderators only.

- This is certified documentation and is protected for editing by Zimbra Employees & Moderators only.

- This article is a Work in Progress, and may be unfinished or missing sections.

Proxy Related Log Files

Proxy related errors can be found in the following logs on each proxy server:

• /opt/zimbra/log/nginx.log
• /opt/zimbra/log/nginx.access.log

Slow Proxy Logins - Route Lookup Handles (garpu)

• http://wiki.zimbra.com/wiki/Enabling_Zimbra_Proxy#Proxy_Login_Slow
• http://wiki.zimbra.com/index.php?title=NGINX_Configuration_Tips#View.2FModify_Route_Lookup_Handlers_.28garpu.29

A common nginx misconfiguration is to have incorrectly designated non-mailbox servers as routing/zmlookup handlers. Only mailbox servers can perform route handler functions. To view the zmlookup lookup handlers, review the zm_lookup_handlers parameter in /opt/zimbra/conf/nginx/includes/nginx.conf.zmlookup

grep zm_lookup_handlers /opt/zimbra/conf/nginx/includes/nginx.conf.zmlookup

If a non-mailbox server is listed, set the zimbraReverseProxyLookupTarget server configuration attribute to FALSE for that server.

zmprov ms `zmhostname` zimbraReverseProxyLookupTarget FALSE

Additionally, zimbraReverseProxyLookupTarget is a server inherited attribute from the global configuration, so check if zimbraReverseProxyLookupTarget has been incorrectly designated in global config.

zmprov gcf zimbraReverseProxyLookupTarget

No Route To Host Errors

• http://wiki.zimbra.com/wiki/Ajcody-Proxy-Notes#No_Route_To_Host
• http://wiki.zimbra.com/wiki/Zimbra_Proxy_Guide#No_route_to_host_errors

If your getting "No route to host" errors in /opt/zimbra/log/nginx.log files on the proxy servers, you should check:

1. If the resolution [DNS] to the host from the proxy servers is correct and working. This oversight might when you've deployed a new ZCS server in your environment.
2. Following step one, you also have to confirm there is port level access between proxy servers and the server it's trying to reach. memcache port is 11211 .
3. The server/s [mailbox/webapp servers] are too busy to serve the request.
4. You have a server in the lookup pool list that shouldn't be there or you should remove the trouble server from the pool to avoid any more customer issues to deescalate the situation.

5xx Errors

• http://wiki.zimbra.com/wiki/Ajcody-Proxy-Notes#50X_Errors
• http://wiki.zimbra.com/wiki/Zimbra_Proxy_Guide#5xx_Errors

• 500 Internal Server Error:
  • A generic error message, given when an unexpected condition was encountered and no more specific message is suitable. This might be due to several reasons due to failure on one of the upstream mailstore servers.
  • The server was acting as a gateway or proxy and received an invalid response from the upstream server.
  • The most common reason for this is that the jetty mailboxd process is down on the mailstore server and hence is unable to process the request. Check using 'netstat -an | grep ' to see if the IMAP/POP/HTTP ports used by mailboxd are up and listening for incoming connections. Also check using 'ps -eaf | grep mailboxd'
  • The most common reason for this is that the upstream mailstore server took longer than the configured timeout value and hence the client closed the upstream connection. Try changing the timeout values to a higher value if its expected to take longer for specific kind of requests. If this is not the case, then we should look for reasons why it took longer for a request to get processed.

  These following configuration changes for an upstream mailbox server can improve proxy behavior related to timeouts:

  This will configure proxy to immediately reconnect to all mailbox server on any failure

  $ zmprov mcf zimbraMailProxyReconnectTimeout 125

  $ zmprov ms zimbraMailProxyReconnectTimeout 125

  $ zmprov mcf zimbraMailProxyMaxFails 5

  $ zmprov ms zimbraMailProxyMaxFails 5

  $ zmproxyctl restart

  See the following bug for more details on this recommendation:

  • "Improved proxy timeout defaults"
    • https://bugzilla.zimbra.com/show_bug.cgi?id=80135

    Third Party Issues - Load Balancers, DNS, Etc.

    Bad/Invalid command when proxying to external POP/IMAP servers

    Nginx issues the XOIP command to the upstream POP3 server, and the ID command to the upstream IMAP server, before logging in to upstream. This is for auditing purposes so that the client's IP address is known to the upstream server. The global config attributes zimbraReverseProxySendPop3Xoip and zimbraReverseProxySendImapId control this aspect.

    However, some external IMAP servers may not implement the ID command, and some external POP3 servers may not implement the XOIP command.

    To turn off sending the XOIP command, set zimbraReverseProxySendPop3Xoip to false. To turn off sending the IMAP command, set zimbraReverseProxySendImapId to false.

    zmprov mcf zimbraReverseProxySendPop3Xoip FALSE zmprov mcf zimbraReverseProxySendImapId FALSE

    LDAP/Nginx Won't Start And Asks For A Password

    This tends to happen because Zimbra can't read the key or the certificate of the LDAP/IMAP proxy service on startup. This issue is specific to commercial certificates.

    Here is what you can do:

    • You want to check to make sure the private key is not encrypted.
    • Manually link the cert to the services OR simply redeploy the certificate to relink the cert to the services.

    cp /opt/zimbra/ssl/zimbra/commercial/commercial.key /opt/zimbra/conf/slapd.key 
    cp /opt/zimbra/ssl/zimbra/commercial/commercial.crt /opt/zimbra/conf/slapd.crt 
    cp /opt/zimbra/ssl/zimbra/commercial/commercial.key /opt/zimbra/conf/nginx.key 
    cp /opt/zimbra/ssl/zimbra/commercial/commercial.crt /opt/zimbra/conf/nginx.crt 
    

    • Restart the Zimbra services.
    Похожие публикации:

    1. Как изменить обои на ноутбуке асус
    2. Как подключить три монитора к ноутбуку
    3. Киа кто производитель страна и сборка
    4. Чем отличается скачать mbps от загрузить mbps