Messages

1

Installation and Upgrades / Re: Recipient address rejected: User unknown in local recipient table

« on: March 03, 2017, 02:51:38 pm »

Recently upgraded Zentyal to 5.0, it was some pain, but our main service (postfix) is worked. Mostly. Until today.
Now it`s refuse to send messages to local virtual domain:
"Recipient address rejected: User unknown in local recipient table".

2

Email and Groupware / Re: Mail to amavis@myhostname bounced (user unknown) (Zentyal 5.07)

« on: March 01, 2017, 08:40:18 am »

UPDATE:  For investigation, I did alias of this unknown address to my work mail, get this messages, and that is what I see:

1. Sender: Cron daemon
2. Subject of message: "Cron <amavis@mail> test -e /usr/sbin/amavisd-new-cronjob && /usr/sbin/amavisd-new-cronjob sa-sync"
3. Text content of message: "Wide character in print at /usr/share/perl5/Razor2/Logger.pm line 107."

3

Email and Groupware / Mail to amavis@myhostname bounced (user unknown) (Zentyal 5.07)

« on: February 20, 2017, 01:07:42 pm »

Hi all.

I see subject message regularly in mail logs.  Sender is the same - amavis@myhostname
How can I fix it, allow postfix to relay messages to local domain or add this address to aliaces, at last?
This happened after upgrade from 4.1.12 Zentyal to 5.0 version.

4

Installation and Upgrades / Re: Zentyal 5.0 and network module.

« on: February 20, 2017, 12:50:06 pm »

Hi.
Maybe this topic can help:
https://forum.zentyal.org/index.php/topic,30716.0.html

5

Installation and Upgrades / Fetchmail not started after upgrade from 4.1.12 to 5.0

« on: February 17, 2017, 03:30:28 pm »

Hi all!

After upgrade can`t get external mail. In syslog I see errors:

Code: [Select]

Feb 16 14:04:33 mail systemd[1]: Started Zentyal fetchmail daemon.
Feb 16 14:04:33 mail systemd[1]: zentyal.fetchmail.service: Main process exited, code=exited, status=1/FAILURE
Feb 16 14:04:33 mail systemd[1]: zentyal.fetchmail.service: Unit entered failed state.
Feb 16 14:04:33 mail systemd[1]: zentyal.fetchmail.service: Failed with result 'exit-code'.
Feb 16 14:04:33 mail systemd[1]: zentyal.fetchmail.service: Service hold-off time over, scheduling restart.
Feb 16 14:04:33 mail systemd[1]: Stopped Zentyal fetchmail daemon.
...
Feb 16 14:04:34 mail systemd[1]: zentyal.fetchmail.service: Start request repeated too quickly.
Feb 16 14:04:34 mail systemd[1]: Failed to start Zentyal fetchmail daemon.

After many tries to fix it, I found why, on this forum:
https://forum.zentyal.org/index.php?topic=21633.0
The problem was that fetchmail user doesn`t have shell.

Code: [Select]

fetchmail:x:115:65534::/var/lib/fetchmail:/bin/false

Then I found solution on this forum too (https://forum.zentyal.org/index.php?topic=4447.0):

Code: [Select]

sudo chsh -s /bin/sh fetchmail

But, service "External retrieval service" in Zentyal web-admin control panel marked as stopped. If I try to start it,
I see in syslog:

Code: [Select]

Feb 17 16:21:00 mail systemd[1]: Stopping Zentyal fetchmail daemon...
Feb 17 16:21:00 mail fetchmail[2715]: terminated with signal 15
Feb 17 16:21:00 mail su[2673]: Session terminated, terminating shell... ...terminated.
Feb 17 16:21:00 mail systemd[1]: zentyal.fetchmail.service: Main process exited, code=exited, status=143/n/a
Feb 17 16:21:00 mail systemd[1]: Stopped Zentyal fetchmail daemon.
Feb 17 16:21:00 mail systemd[1]: zentyal.fetchmail.service: Unit entered failed state.
Feb 17 16:21:00 mail systemd[1]: zentyal.fetchmail.service: Failed with result 'exit-code'.
Feb 17 16:21:00 mail systemd[1]: Started Zentyal fetchmail daemon.
Feb 17 16:21:00 mail fetchmail[27754]: starting fetchmail 6.3.26 daemon
Feb 17 16:21:01 mail cron[631]: (*system*ebox-mail) RELOAD (/etc/cron.d/ebox-mail)
Feb 17 16:21:01 mail CRON[27905]: (root) CMD ([ -x /usr/share/zentyal-mail/fetchmail-update ] && /usr/share/zentyal-mail/fetchmail-update)

As I see, fetchmail is started & worked, external mail is receiving, but, service "External retrieval service" in Zentyal web-admin still marked as stopped!
How Zentyal is determine status of services, and how can I fix it?

6

Russian / Re: Автоудаление пакетов zentyal-mail, zentyal-openchange после обновления.

« on: April 24, 2016, 11:03:43 am »

Проблема неудовлетворенных зависимостей решилась только переустановкой на 64-битную версию Zentyal.

7

Russian / Автоудаление пакетов zentyal-mail, zentyal-openchange после обновления.

« on: October 10, 2015, 09:18:02 pm »

Установлен Zentyal Development Edition v.4.1. После последнего обновления пакетов, от 9 октября, apt автоматически удалил модули почты, почтового фильтра и OpenChange - как оказалось, вследствие неудовлетворенных зависимостей, а именно - внезапно отсутствующего в репозитории Zentyal пакета openchange-ocsmanager, Примечательно, что физически пакет в репозитарии есть ( и на том спасибо, хоть вручную смог установить), а вот в пакетной базе, насколько я понял, он присутствует лишь как зависимость (см. файл http://archive.zentyal.org/zentyal/dists/4.1/main/binary-i386/Packages ).

8

Installation and Upgrades / Re: Using eBox as DNS master and DNS slave

« on: October 15, 2010, 07:16:43 pm »

...
Then I restarted DNS in the eBox webinterface. The file /etc/bind/named.conf.local was updated and the file /etc/bind/slave.domain.local appeared.
...

Thanks, Andy for it, but by now (in Zentyal v2.0.4)  it`s solution not works. After some googling and looking in configs, I conclude it`s because apparmor :

Code: [Select]

cat /etc/apparmor.d/usr.sbin.named
....
# /etc/bind should be read-only for bind
  # /var/lib/bind is for dynamically updated zone (and journal) files.
  # /var/cache/bind is for slave/stub data, since we're not the origin of it.
  # See /usr/share/doc/bind9/README.Debian.gz
  /etc/bind/** r,
  /var/lib/bind/** rw,
  /var/lib/bind/ rw,
  /var/cache/bind/** rw,
  /var/cache/bind/ rw,
....

Well, I just changed in named.conf.local.mas slave zone path, so that it point to /var/cache/bind:

Code: [Select]

zone "domain.local" {
    type slave;
    masters { 192.xxx.xxx.xxx; };
    file "slave.domain.local";
};
(to note: path to /var/cache/bind already exist in named.conf.options)
 Then I also restarted DNS in the eBox webinterface, the file /var/cache/bind/slave.domain.local appeared.
 That's it!