Users March 2018

users@lists.ciphermail.com

7 participants
9 discussions

Re: [Djigzo users] Mail routing, when external & internal relay host are the same

by Stefan Michael Guenther

> On 22-03-18 18:23, Stefan Günther via Users wrote: > > we just installed Ciphermail as virtual machine on a Univention Corporate Server (UCS). > > > > The idea is that UCS grabs emails via fetchmail, sends them to the Ciphermail VM and finally stores them in the local Kopano installation. > > > > In the configuration of postfix@UCS I have defined the following transport map: > > > > in-put.cm smtp:[192.168.0.229] > > > > in-put.cm is defined as a relay domain in Ciphermail. > > > > The problem now is, that the email loops between UCS and Ciphermail: Everytime Ciphermail returns the email to postfix@UCS the email is forwarded to Ciphermail due to the transport map. > > > > I have no idea, whether we could change anything in the Ciphermail configuration, so that postfix@UCS recognizes that the email already has been forwarded once or do we have to change the configuration of postfix@UCS? > > > > Thanks for any hint or suggestion, > > I do not completely understand your setup but I might have some suggestions. > > Option 1. rewrite the recipients domain to some internal name after the > message has been handled by CipherMail. > > For example rewrite from input.cm to input.cm.handled. The postfix@UCS > should be configured to also handle the domain input.cm.handled and not > only forward email to CipherMail if the recipient domain is input.cm > (and not input.cm.internal) > > Option 2. Add an additional smtpd handler (on a different port) to > master.cf of postfix@UCS and set transport_maps for that port to an > empty value (note I have not tested whether you can override > transport_maps for an smtpd service). Then tell CipherMail to deliver to > that special port. > What about Option 3: TCP/IP communication between postfix on UCS and Ciphermail in the virtual machine? Instead of using content_filter=djigzo:[127.0.0.1]:10025 I defined content_filter=djigzo:[192.168.0.229]:10025 In master.cf I defined the djigzo transport and told postfix to listen on 192.168.0.9:10025 instead of 127.0.0.1:10025, configured Ciphermail to listen on 192.168.0.229:10025 and forward emails to 192.168.0.9:10025. Finally I deactivated all firewall rules for testing. Then I send an email from the command line of the UCS: Mar 29 13:50:14 ucs postfix/qmgr[26618]: A40FF481158: from=<root(a)ucs.ciphermail.intranet>, size=327, nrcpt=1 (queue active) Mar 29 13:50:14 ucs postfix/smtp[26689]: A40FF481158: to=<m.mustermann(a)in-put.solutions>, relay=192.168.0.229[192.168.0.229]:10025, delay=0.28, delays=0.11/0.04/0.06/0.06, dsn=5.7.1, status=bounced (host 192.168.0.229[192.168.0.229] said: 550 5.7.1 Requested action not taken: relaying denied (in reply to RCPT TO command)) As we can see, the email is forwarded to Ciphermail and according to netstat, a java process is listening on 192.168.0.229:10025. But this connection attempt is not recorded in /var/log/djigzo.log. Is the some line in the configuration of Ciphermail that limits connections only to ip 127.0.0.1? I guess this setup, with a separation of postfix and Ciphermail on two different hosts would solve my problem. Thanks for any hints/suggestions, Stefan

4 years, 3 months

[Djigzo users] Question - PGP/MIME and PGP/INLINE <Virus checked>

by Robert.Wiegand＠kvt.de

I have a question about incoming connections for my domain. If I activate PGP/INLINE is PGP/MIME still working? Or if there is a sender just sending PGP/INLINE I have to setup a second ciphermail server to support PGP/INLINE? Greetings Robert Wiegand

4 years, 3 months

[Djigzo users] Deleting expired certificate

by Markus Zimmermann

Hello, i would like to delete an expired certificate of an internal user. Unfortunetly i fail with an error message: "some certificates could not be deleted because they are still in use". Can you gibe me advice how to delete this certificate? Thank you in advance, Markus Mit freundlichen Grüßen mareco gmbh & co.kg Dipl.-Ing.(FH) Markus Zimmermann Geschäftsführer der Komplementärin Rothelebuch 7, 87637 Seeg Tel. +49 (8364) 984009-0 Fax. +49 (8364) 984009-9 E-Mail. info(a)mareco.biz Internet. www.mareco.biz mareco-blog: Interessantes aus unseren Beratungsfällen: www.mareco.biz/blog.html <http://www.mareco.biz/blog.html> Besuchen Sie uns auch Facebook: http://www.facebook.com/Unternehmensberatung.mareco <http://www.facebook.com/Unternehmensberatung.mareco> Sitz Seeg, HRA8889 Amtsgericht Kempten Persönlich haftende Gesellschafterin CRM Verwaltungs-GmbH Sitz Seeg, HRB9745 Amtsgericht Kempten Geschäftsführer Markus Zimmermann

4 years, 3 months

[Djigzo users] Mail routing, when external & internal relay host are the same

by Stefan Günther

Hello, we just installed Ciphermail as virtual machine on a Univention Corporate Server (UCS). The idea is that UCS grabs emails via fetchmail, sends them to the Ciphermail VM and finally stores them in the local Kopano installation. In the configuration of postfix@UCS I have defined the following transport map: in-put.cm smtp:[192.168.0.229] in-put.cm is defined as a relay domain in Ciphermail. The problem now is, that the email loops between UCS and Ciphermail: Everytime Ciphermail returns the email to postfix@UCS the email is forwarded to Ciphermail due to the transport map. I have no idea, whether we could change anything in the Ciphermail configuration, so that postfix@UCS recognizes that the email already has been forwarded once or do we have to change the configuration of postfix@UCS? Thanks for any hint or suggestion, Stefan

4 years, 3 months

[Djigzo users] DLP features

by Dino Edwards

Hi, I have a general question about the DLP functionality. Is there a way to import lists of sensitive data into it from a database source or something along those lines? As far as I can tell, the DLP works on patterns but not actual sensitive data. Thanks

4 years, 3 months

Re: [Djigzo users] Upgrade from 2.8.6.2 to 3.3.1.0 fails: Could not load mailet (SenderDKIMVerify)

by Stefan Günther

> On 07-03-18 21:34, Stefan Günther via Users wrote: > > -----Ursprüngliche Nachricht----- > >> Von:Martijn Brinkers via Users <users(a)lists.djigzo.com> > >> Gesendet: Mon 5 März 2018 13:08 > >> An: users(a)lists.djigzo.com > >> Betreff: Re: [Djigzo users] Upgrade from 2.8.6.2 to 3.3.1.0 fails: Could not load mailet (SenderDKIMVerify) > >> > >> > >> > >> On 02-03-18 19:47, Stefan Günther via Users wrote: > >>> Hello, > >>> > >>> yesterday I tried to update an "old" Ciphermail installation from version 2.8.6.2 to version 3.3.1.0 by installing the three packages as suggested in the documentation: > >>> > >>> dpkg -i djigzo_3.3.1-0_all.deb > >>> dpkg -i djigzo-postgres_3.3.1-0_all.deb > >>> dpkg -i djigzo-web_3.3.1-0_all.deb > >>> > >>> Then I deleted the cache (rm -r /var/cache/tomcat6/Catalina/web) and restarted Tomcat6. > >>> > >>> Nevertheless it is not possible to start Ciphermail due to the following error: > >>> > >>> James Mail Server 2.3.1 > >>> 01 Mar 2018 18:57:33 | INFO Initializing matcher: MaxRelay (mitm.application.djigzo.james.matchers.MaxRelay) [Phoenix-Monitor] > [SNIP] > >>> Unable to init mailet SenderDKIMVerify > >>> Check spool manager logs for more details. > >>> org.apache.avalon.phoenix.containerkit.lifecycle.LifecycleException: Component named "spoolmanager" failed to pass through the Starting stage. (Reason: org.apache.mailet.MailetException: Could not load mailet (SenderDKIMVerify); > >>> nested exception is: > >>> java.lang.ClassNotFoundException: Requested mailet not found: SenderDKIMVerify. looked in [, mitm.application.djigzo.pro.james.mailets., mitm.application.djigzo.james.mailets., org.apache.james.transport.mailets.]). > >>> at org.apache.avalon.phoenix.containerkit.lifecycle.LifecycleHelper.fail(LifecycleHelper.java:354) > >>> at org.apache.avalon.phoenix.containerkit.lifecycle.LifecycleHelper.startup(LifecycleHelper.java:226) > >>> at org.apache.avalon.phoenix.components.application.DefaultApplication.startup(DefaultApplication.java:530) > >>> at org.apache.avalon.phoenix.components.application.DefaultApplication.doRunPhase(DefaultApplication.java:478) > >>> at org.apache.avalon.phoenix.components.application.DefaultApplication.runPhase(DefaultApplication.java:409) > >>> at org.apache.avalon.phoenix.components.application.DefaultApplication.start(DefaultApplication.java:180) > >>> at org.apache.avalon.framework.container.ContainerUtil.start(ContainerUtil.java:260) > >>> at org.apache.avalon.phoenix.components.kernel.DefaultKernel.startup(DefaultKernel.java:295) > >> > >> Some classes have been renamed. For example: > >> > >> SenderDKIMVerify -> SenderPropertyDKIMVerify > >> SenderDKIMSign -> SenderPropertyDKIMSign > >> > >> The xml file that defines the mail flow was also updated to reflect > >> those changes. I guess your config.xml file has been locally changed and > >> you chose not to accept the new config.xml (keeping the modified one). > >> > >> If you want to keep your modified config.xml, the best is to do a diff > >> and check the differences or manually rename the mailets. > >> > > the timestamp of /usr/share/djigzo/conf/james/SAR-INF/config.xml ist Jul 28. 2016 and the size 129780 bytes. I don't think/remember that I changed this file in any way. > > > > I repeated "dpkg -i djigzo_3.3.1-0_all.deb", but there still isn't a complain about a changed config.xml. > > Could it be that you have enabled a diversion? > > dpkg-divert --list > root@ciphermail:~# dpkg-divert --list diversion of /usr/share/man/man1/pod2latex.1.gz to /usr/share/man/man1/pod2latex.bundled.1.gz by libpod-latex-perl diversion of /usr/bin/pod2latex to /usr/bin/pod2latex.bundled by libpod-latex-perl diversion of /usr/share/vim/vim74/doc/tags to /usr/share/vim/vim74/doc/tags.vim-tiny by vim-runtime diversion of /usr/bin/pg_config to /usr/bin/pg_config.libpq-dev by postgresql-common diversion of /usr/share/man/man1/sh.1.gz to /usr/share/man/man1/sh.distrib.1.gz by dash diversion of /usr/share/vim/vim74/doc/help.txt to /usr/share/vim/vim74/doc/help.txt.vim-tiny by vim-runtime diversion of /bin/sh to /bin/sh.distrib by dash > If not then there might be some problem with your debian package > integrity. The updated config.xml file is certainly part of the deb and > it contains the updated names. > > You might try to move config.xml to some other place (or rename) before > reinstalling the deb file to see whether that works. > Renaming the file and installing the package again fixed the problem. Thank you and have a nice weekend, Stefan

4 years, 3 months

Re: [Djigzo users] Upgrade from 2.8.6.2 to 3.3.1.0 fails: Could not load mailet (SenderDKIMVerify)

by Stefan Günther

-----Ursprüngliche Nachricht----- > Von:Martijn Brinkers via Users <users(a)lists.djigzo.com> > Gesendet: Mon 5 März 2018 13:08 > An: users(a)lists.djigzo.com > Betreff: Re: [Djigzo users] Upgrade from 2.8.6.2 to 3.3.1.0 fails: Could not load mailet (SenderDKIMVerify) > > > > On 02-03-18 19:47, Stefan Günther via Users wrote: > > Hello, > > > > yesterday I tried to update an "old" Ciphermail installation from version 2.8.6.2 to version 3.3.1.0 by installing the three packages as suggested in the documentation: > > > > dpkg -i djigzo_3.3.1-0_all.deb > > dpkg -i djigzo-postgres_3.3.1-0_all.deb > > dpkg -i djigzo-web_3.3.1-0_all.deb > > > > Then I deleted the cache (rm -r /var/cache/tomcat6/Catalina/web) and restarted Tomcat6. > > > > Nevertheless it is not possible to start Ciphermail due to the following error: > > > > James Mail Server 2.3.1 > > 01 Mar 2018 18:57:33 | INFO Initializing matcher: MaxRelay (mitm.application.djigzo.james.matchers.MaxRelay) [Phoenix-Monitor] > > 01 Mar 2018 18:57:33 | INFO Relay limit 100 (mitm.application.djigzo.james.matchers.MaxRelay) [Phoenix-Monitor] > > 01 Mar 2018 18:57:33 | INFO catchRuntimeExceptions: true; catchErrors: true (mitm.application.djigzo.james.mailets.CreateMailID) [Phoenix-Monitor] > > 01 Mar 2018 18:57:33 | INFO catchRuntimeExceptions: true; catchErrors: true (mitm.application.djigzo.james.mailets.Log) [Phoenix-Monitor] > > 01 Mar 2018 18:57:33 | INFO Initializing matcher: GlobalVerifyHMACHeader (mitm.application.djigzo.james.matchers.GlobalVerifyHMACHeader) [Phoenix-Monitor] > > 01 Mar 2018 18:57:33 | INFO catchRuntimeExceptions: true; catchErrors: true (mitm.application.djigzo.james.mailets.GotoProcessor) [Phoenix-Monitor] > > 01 Mar 2018 18:57:33 | INFO catchRuntimeExceptions: true; catchErrors: true (mitm.application.djigzo.james.mailets.MailAttributes) [Phoenix-Monitor] > > 01 Mar 2018 18:57:33 | INFO catchRuntimeExceptions: true; catchErrors: true (mitm.application.djigzo.james.mailets.GotoProcessor) [Phoenix-Monitor] > > 01 Mar 2018 18:57:33 | INFO catchRuntimeExceptions: true; catchErrors: true (mitm.application.djigzo.james.mailets.GotoProcessor) [Phoenix-Monitor] > > 01 Mar 2018 18:57:33 | INFO catchRuntimeExceptions: true; catchErrors: true (mitm.application.djigzo.james.mailets.GotoProcessor) [Phoenix-Monitor] > > 01 Mar 2018 18:57:33 | INFO Initializing matcher: SenderEvaluateUserProperty (mitm.application.djigzo.james.matchers.SenderEvaluateUserProperty) [Phoenix-Monitor] > > 01 Mar 2018 18:57:33 | INFO Expression: #{user.subjectFilter.enabled}!='true' (mitm.application.djigzo.james.matchers.SenderEvaluateUserProperty) [Phoenix-Monitor] > > 01 Mar 2018 18:57:33 | INFO catchRuntimeExceptions: true; catchErrors: true (mitm.application.djigzo.james.mailets.GotoProcessor) [Phoenix-Monitor] > > 01 Mar 2018 18:57:33 | INFO Initializing matcher: RecipientEvaluateUserProperty (mitm.application.djigzo.james.matchers.RecipientEvaluateUserProperty) [Phoenix-Monitor] > > 01 Mar 2018 18:57:33 | INFO Expression: #{user.subjectFilter.enabled}!='true' (mitm.application.djigzo.james.matchers.RecipientEvaluateUserProperty) [Phoenix-Monitor] > > 01 Mar 2018 18:57:33 | INFO catchRuntimeExceptions: true; catchErrors: true (mitm.application.djigzo.james.mailets.GotoProcessor) [Phoenix-Monitor] > > 01 Mar 2018 18:57:33 | INFO catchRuntimeExceptions: true; catchErrors: true (mitm.application.djigzo.james.mailets.MailAttributes) [Phoenix-Monitor] > > 01 Mar 2018 18:57:33 | INFO catchRuntimeExceptions: true; catchErrors: true (mitm.application.djigzo.james.mailets.FilterSubject) [Phoenix-Monitor] > > 01 Mar 2018 18:57:33 | INFO catchRuntimeExceptions: true; catchErrors: true (mitm.application.djigzo.james.mailets.Log) [Phoenix-Monitor] > > 01 Mar 2018 18:57:33 | INFO catchRuntimeExceptions: true; catchErrors: true (mitm.application.djigzo.james.mailets.GotoProcessor) [Phoenix-Monitor] > > 01 Mar 2018 18:57:33 | INFO Initializing matcher: RecipientHasLocality (mitm.application.djigzo.james.matchers.RecipientHasLocality) [Phoenix-Monitor] > > 01 Mar 2018 18:57:33 | INFO User locality: internal (mitm.application.djigzo.james.matchers.RecipientHasLocality) [Phoenix-Monitor] > > 01 Mar 2018 18:57:33 | INFO catchRuntimeExceptions: true; catchErrors: true (mitm.application.djigzo.james.mailets.GotoProcessor) [Phoenix-Monitor] > > 01 Mar 2018 18:57:33 | INFO catchRuntimeExceptions: true; catchErrors: true (mitm.application.djigzo.james.mailets.GotoProcessor) [Phoenix-Monitor] > > 01 Mar 2018 18:57:33 | INFO catchRuntimeExceptions: true; catchErrors: true (mitm.application.djigzo.james.mailets.Log) [Phoenix-Monitor] > > Unable to init mailet SenderDKIMVerify > > Check spool manager logs for more details. > > org.apache.avalon.phoenix.containerkit.lifecycle.LifecycleException: Component named "spoolmanager" failed to pass through the Starting stage. (Reason: org.apache.mailet.MailetException: Could not load mailet (SenderDKIMVerify); > > nested exception is: > > java.lang.ClassNotFoundException: Requested mailet not found: SenderDKIMVerify. looked in [, mitm.application.djigzo.pro.james.mailets., mitm.application.djigzo.james.mailets., org.apache.james.transport.mailets.]). > > at org.apache.avalon.phoenix.containerkit.lifecycle.LifecycleHelper.fail(LifecycleHelper.java:354) > > at org.apache.avalon.phoenix.containerkit.lifecycle.LifecycleHelper.startup(LifecycleHelper.java:226) > > at org.apache.avalon.phoenix.components.application.DefaultApplication.startup(DefaultApplication.java:530) > > at org.apache.avalon.phoenix.components.application.DefaultApplication.doRunPhase(DefaultApplication.java:478) > > at org.apache.avalon.phoenix.components.application.DefaultApplication.runPhase(DefaultApplication.java:409) > > at org.apache.avalon.phoenix.components.application.DefaultApplication.start(DefaultApplication.java:180) > > at org.apache.avalon.framework.container.ContainerUtil.start(ContainerUtil.java:260) > > at org.apache.avalon.phoenix.components.kernel.DefaultKernel.startup(DefaultKernel.java:295) > > Some classes have been renamed. For example: > > SenderDKIMVerify -> SenderPropertyDKIMVerify > SenderDKIMSign -> SenderPropertyDKIMSign > > The xml file that defines the mail flow was also updated to reflect > those changes. I guess your config.xml file has been locally changed and > you chose not to accept the new config.xml (keeping the modified one). > > If you want to keep your modified config.xml, the best is to do a diff > and check the differences or manually rename the mailets. > the timestamp of /usr/share/djigzo/conf/james/SAR-INF/config.xml ist Jul 28. 2016 and the size 129780 bytes. I don't think/remember that I changed this file in any way. I repeated "dpkg -i djigzo_3.3.1-0_all.deb", but there still isn't a complain about a changed config.xml. Kind regards, Stefan

4 years, 3 months

[Djigzo users] UNSUBSCRIBE

by Ginter, Darren

[cid:image001.png@01D3B62F.42559720]<http://www.howardandhoward.com/> NOTICE: Information contained in this transmission to the named addressee is proprietary information and is subject to attorney-client privilege and work product confidentiality. If the recipient of this transmission is not the named addressee, the recipient should immediately notify the sender and destroy the information transmitted without making any copy or distribution thereof. ELECTRONIC SIGNATURE: Nothing contained in this communication is intended to constitute an electronic signature unless a specific statement to the contrary is included in this message.

4 years, 4 months

[Djigzo users] Upgrade from 2.8.6.2 to 3.3.1.0 fails: Could not load mailet (SenderDKIMVerify)

by Stefan Günther

Hello, yesterday I tried to update an "old" Ciphermail installation from version 2.8.6.2 to version 3.3.1.0 by installing the three packages as suggested in the documentation: dpkg -i djigzo_3.3.1-0_all.deb dpkg -i djigzo-postgres_3.3.1-0_all.deb dpkg -i djigzo-web_3.3.1-0_all.deb Then I deleted the cache (rm -r /var/cache/tomcat6/Catalina/web) and restarted Tomcat6. Nevertheless it is not possible to start Ciphermail due to the following error: James Mail Server 2.3.1 01 Mar 2018 18:57:33 | INFO Initializing matcher: MaxRelay (mitm.application.djigzo.james.matchers.MaxRelay) [Phoenix-Monitor] 01 Mar 2018 18:57:33 | INFO Relay limit 100 (mitm.application.djigzo.james.matchers.MaxRelay) [Phoenix-Monitor] 01 Mar 2018 18:57:33 | INFO catchRuntimeExceptions: true; catchErrors: true (mitm.application.djigzo.james.mailets.CreateMailID) [Phoenix-Monitor] 01 Mar 2018 18:57:33 | INFO catchRuntimeExceptions: true; catchErrors: true (mitm.application.djigzo.james.mailets.Log) [Phoenix-Monitor] 01 Mar 2018 18:57:33 | INFO Initializing matcher: GlobalVerifyHMACHeader (mitm.application.djigzo.james.matchers.GlobalVerifyHMACHeader) [Phoenix-Monitor] 01 Mar 2018 18:57:33 | INFO catchRuntimeExceptions: true; catchErrors: true (mitm.application.djigzo.james.mailets.GotoProcessor) [Phoenix-Monitor] 01 Mar 2018 18:57:33 | INFO catchRuntimeExceptions: true; catchErrors: true (mitm.application.djigzo.james.mailets.MailAttributes) [Phoenix-Monitor] 01 Mar 2018 18:57:33 | INFO catchRuntimeExceptions: true; catchErrors: true (mitm.application.djigzo.james.mailets.GotoProcessor) [Phoenix-Monitor] 01 Mar 2018 18:57:33 | INFO catchRuntimeExceptions: true; catchErrors: true (mitm.application.djigzo.james.mailets.GotoProcessor) [Phoenix-Monitor] 01 Mar 2018 18:57:33 | INFO catchRuntimeExceptions: true; catchErrors: true (mitm.application.djigzo.james.mailets.GotoProcessor) [Phoenix-Monitor] 01 Mar 2018 18:57:33 | INFO Initializing matcher: SenderEvaluateUserProperty (mitm.application.djigzo.james.matchers.SenderEvaluateUserProperty) [Phoenix-Monitor] 01 Mar 2018 18:57:33 | INFO Expression: #{user.subjectFilter.enabled}!='true' (mitm.application.djigzo.james.matchers.SenderEvaluateUserProperty) [Phoenix-Monitor] 01 Mar 2018 18:57:33 | INFO catchRuntimeExceptions: true; catchErrors: true (mitm.application.djigzo.james.mailets.GotoProcessor) [Phoenix-Monitor] 01 Mar 2018 18:57:33 | INFO Initializing matcher: RecipientEvaluateUserProperty (mitm.application.djigzo.james.matchers.RecipientEvaluateUserProperty) [Phoenix-Monitor] 01 Mar 2018 18:57:33 | INFO Expression: #{user.subjectFilter.enabled}!='true' (mitm.application.djigzo.james.matchers.RecipientEvaluateUserProperty) [Phoenix-Monitor] 01 Mar 2018 18:57:33 | INFO catchRuntimeExceptions: true; catchErrors: true (mitm.application.djigzo.james.mailets.GotoProcessor) [Phoenix-Monitor] 01 Mar 2018 18:57:33 | INFO catchRuntimeExceptions: true; catchErrors: true (mitm.application.djigzo.james.mailets.MailAttributes) [Phoenix-Monitor] 01 Mar 2018 18:57:33 | INFO catchRuntimeExceptions: true; catchErrors: true (mitm.application.djigzo.james.mailets.FilterSubject) [Phoenix-Monitor] 01 Mar 2018 18:57:33 | INFO catchRuntimeExceptions: true; catchErrors: true (mitm.application.djigzo.james.mailets.Log) [Phoenix-Monitor] 01 Mar 2018 18:57:33 | INFO catchRuntimeExceptions: true; catchErrors: true (mitm.application.djigzo.james.mailets.GotoProcessor) [Phoenix-Monitor] 01 Mar 2018 18:57:33 | INFO Initializing matcher: RecipientHasLocality (mitm.application.djigzo.james.matchers.RecipientHasLocality) [Phoenix-Monitor] 01 Mar 2018 18:57:33 | INFO User locality: internal (mitm.application.djigzo.james.matchers.RecipientHasLocality) [Phoenix-Monitor] 01 Mar 2018 18:57:33 | INFO catchRuntimeExceptions: true; catchErrors: true (mitm.application.djigzo.james.mailets.GotoProcessor) [Phoenix-Monitor] 01 Mar 2018 18:57:33 | INFO catchRuntimeExceptions: true; catchErrors: true (mitm.application.djigzo.james.mailets.GotoProcessor) [Phoenix-Monitor] 01 Mar 2018 18:57:33 | INFO catchRuntimeExceptions: true; catchErrors: true (mitm.application.djigzo.james.mailets.Log) [Phoenix-Monitor] Unable to init mailet SenderDKIMVerify Check spool manager logs for more details. org.apache.avalon.phoenix.containerkit.lifecycle.LifecycleException: Component named "spoolmanager" failed to pass through the Starting stage. (Reason: org.apache.mailet.MailetException: Could not load mailet (SenderDKIMVerify); nested exception is: java.lang.ClassNotFoundException: Requested mailet not found: SenderDKIMVerify. looked in [, mitm.application.djigzo.pro.james.mailets., mitm.application.djigzo.james.mailets., org.apache.james.transport.mailets.]). at org.apache.avalon.phoenix.containerkit.lifecycle.LifecycleHelper.fail(LifecycleHelper.java:354) at org.apache.avalon.phoenix.containerkit.lifecycle.LifecycleHelper.startup(LifecycleHelper.java:226) at org.apache.avalon.phoenix.components.application.DefaultApplication.startup(DefaultApplication.java:530) at org.apache.avalon.phoenix.components.application.DefaultApplication.doRunPhase(DefaultApplication.java:478) at org.apache.avalon.phoenix.components.application.DefaultApplication.runPhase(DefaultApplication.java:409) at org.apache.avalon.phoenix.components.application.DefaultApplication.start(DefaultApplication.java:180) at org.apache.avalon.framework.container.ContainerUtil.start(ContainerUtil.java:260) at org.apache.avalon.phoenix.components.kernel.DefaultKernel.startup(DefaultKernel.java:295) Kind regards, Stefan

4 years, 4 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Users March 2018