Could you please do the command below in the terminal of your nethserver
host piler.mydomain2.de
Obviously replace with the real domain name of your second email domain
Could you please do the command below in the terminal of your nethserver
host piler.mydomain2.de
Obviously replace with the real domain name of your second email domain
the answer is empty
This was expected, I set a host definition piler.firstdomain to the IP of the docker container, the ns doesnt know how to reach your second fqdn.
I honestly donât know how it could work
I repeated the installation sometimes because piler didnât archive the emails from the second domain.
Only the procedure described above fixed the problem.
I also honestly donât know how it could work
check in /var/log/maillog if you forward by email to archive@piler.mydomain2.de and what the smtp service says
probably the expected result
cat /var/log/maillog | grep archive@piler.mydomain2.de
Mar 1 19:04:26 MDOL-NethServer postfix/smtp[14041]: AFF9AF4D0B: to=<archive@piler.mydomain2.de>, relay=none, delay=1.7, delays=1.7/0.01/0/0, dsn=5.4.4, status=bounced (Host or domain name not found. Name service error for name=piler.mydomain2.de type=AAAA: Host found but no data record of requested type)
mydomain2.de substituted by real domain
Yes postfix states that it doesnt know where to direct the email
âŠand inexplicably, piler works as it should for the first time.
@capote would you test the next version 1.3.11
yum install https://mirror.de-labrusse.fr/NethDev/nethserver-piler/nethserver-piler-0.1.3-1.ns7.sdl.x86_64.rpm
your issue is not fixed relative to the
add the following to /etc/sudoers: 'www-data all=nopasswd: /etc/init.d/rc.piler reload'
I have to make a bug report to @jsuto
Relative to above we could add it to the documentation
I will test it. Can I update the package or do I need a fresh installation?
update should be fine, I tested it
I donât know if this is a bug or a featureâŠ
Search filters are saved only if they are defined manually, not via the advanced search form.
This misbehavior is not new, but is also known from the previous version.
the update needs to pull a new container and install it, it could be long
we need to ask if the community version could have an update, only the enterprise version has been updated since 2021
Maybe you can update the documentation about the uninstallation. I remember the need to remove artifacts manually, for example:
corrected a typo from
db domains setprop mydomain2.de AlwaysBccAddress archive@piler.mydomain2.de AlwaysBccStatus enabled
to
db domains setprop mydomain2.de AlwaysBccAddress archive@piler.mydomain1.de AlwaysBccStatus enabled
yes, also external DNS as mail.mydomain1.de and rDNS
mydomain1.de=dargels.de
mydomain2.de=myancestry.de