I am having a little problem with the SMS function. I registered with
Clickatell to test and I am able to encrypt and send the message
using Djigzo but when I check the status in the Clickatell webpage,
my messages show a "routing error". After further research (contacted
Clickatell) it appears that I am sending all the appropriate
parameters with the exception of "mo=1". apparently this is a
requirement by Clickatell if you are an U. S. user. All my other
parameters are correct and the "mo" parameter is a fixed (it will
always be 1) regardless of the destination.
My questions is ? is there any where in the code where I can just
enter that parameter (since is not available as a setting). I have
looked at the services.xml file and it looks like the Clickatell
system is constructing an link based on parameters but I cannot find
a way to inject a "&mo=1" without breaking the program.
any help is greatly appreciated.
Tato
Hello
found this today. Looks like a little bit too much logging or is there
a real issue?
10 Feb 2012 22:45:01 | ERROR CRL could not be verified. Hash not
correct (mitm.common.security.crl.PKIXRevocationChecker)
[542503743@qtp-1820539437-132]
java.security.SignatureException: CRL does not verify with supplied
public key.
at org.bouncycastle.jce.provider.X509CRLObject.verify(Unknown Source)
at
mitm.common.security.crl.PKIXRevocationChecker.acceptCRL(PKIXRevocationChecker.java:800)
at
mitm.common.security.crl.PKIXRevocationChecker.findCRLs(PKIXRevocationChecker.java:863)
at
mitm.common.security.crl.PKIXRevocationChecker.getRevocationStatus(PKIXRevocationChecker.java:239)
at
mitm.common.security.certificate.validator.PKITrustCheckCertificateValidatorImpl.isRevoked(PKITrustCheckCertificateValidatorImpl.java:506)
at
mitm.common.security.certificate.validator.PKITrustCheckCertificateValidatorImpl.isValid(PKITrustCheckCertificateValidatorImpl.java:349)
at
mitm.application.djigzo.ws.impl.CertificateValidatorWSImpl.checkValidity(CertificateValidatorWSImpl.java:255)
at
mitm.application.djigzo.ws.impl.CertificateValidatorWSImpl.checkValidity(CertificateValidatorWSImpl.java:191)
at sun.reflect.GeneratedMethodAccessor82.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at
org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:77)
at
mitm.common.hibernate.StartTransactionAdvice.startTransaction(StartTransactionAdvice.java:78)
at
mitm.common.hibernate.StartTransactionAspect.startTransaction(StartTransactionAspect.java:65)
at sun.reflect.GeneratedMethodAccessor79.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at
org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:627)
at
org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:616)
at
org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:64)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:160)
at
org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:77)
at
mitm.application.djigzo.ws.RuntimeExceptionToSoapFaultAdvice.startTransaction(RuntimeExceptionToSoapFaultAdvice.java:70)
at sun.reflect.GeneratedMethodAccessor81.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at
org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:627)
at
org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:616)
at
org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:64)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:160)
at
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy74.checkValidity(Unknown Source)
at sun.reflect.GeneratedMethodAccessor440.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at
org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:166)
at
org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:82)
at org.apache.cxf.jaxws.JAXWSMethodInvoker.invoke(JAXWSMethodInvoker.java:55)
at
org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:68)
at
org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
and so on..
This is Djigzo latest (2.3.1-7) and mail flow is fine before and after
this error messages.
Regards
Andreas
I have a slightly different use case for the PDF encryption and I was
hoping someone might be able to assist before I spend the time to setup a
test environment. I am looking to send PDF attachments through the mail
gateway, and have just PDF's encrypted - not the message as an encrypted
PDF and the attachment as an embedded (nested) PDF. Is this possible?
Thanks,
--Joel
Hopefully this isn't too dumb of a question, but at the moment I can't see anything in the documentation that tells me one way or the other. (It may be there, and if so, I've missed it.)
I'm looking at possibly deploying Djigzo in our environment, our setup would use the PDF encryption, web portal, etc. We would use a subject trigger and DLP to ensure sensitive data is being encrypted. As far as the user setup goes, if I simply set up our internal domain with the "internal" locality, leaving every other domain as external, would I actually need to set up external users in Djigzo if I wasn't going to apply any specific domain or user policies to external users? I.e. we can send to anyone "outside" and the data will go encrypted without issue if the subject trigger or DLP settings are met, and go decrypted without issue otherwise? It's just not clear to me if we would be required to add every recipient email address from external domains that we wanted to send encrypted email to into Djigzo.
Thanks,
Scott Closter
CU Technical & Administrative Services Corp<http://www.cutasc.com/>
T: 1 250 627 3654
F: 1 250 627 3601
CUTASC: lean thinking. member centricity
NOTICE - This email and any files transmitted with it are intended only for the use of the individual or entity to which it is addressed for the purpose for which it is provided and for no other purpose without our permission. This email may contain information that is privileged, confidential and exempt from disclosure under applicable law. Any other distribution, copying or disclosure is strictly prohibited by law. If you have received this message in error, please notify us immediately by telephone at (250) 923-3953 or by return email and destroy/delete any and all copies of this communication.
Is there any option to generate statistical reporting for Djigzo? Just thinking on a basic level such as # of emails encrypted daily, monthly, list of recipients encrypted emails were sent to etc.
Scott Closter
CU Technical & Administrative Services Corp<http://www.cutasc.com/>
T: 1 250 627 3654
F: 1 250 627 3601
CUTASC: lean thinking. member centricity
NOTICE - This email and any files transmitted with it are intended only for the use of the individual or entity to which it is addressed for the purpose for which it is provided and for no other purpose without our permission. This email may contain information that is privileged, confidential and exempt from disclosure under applicable law. Any other distribution, copying or disclosure is strictly prohibited by law. If you have received this message in error, please notify us immediately by telephone at (250) 923-3953 or by return email and destroy/delete any and all copies of this communication.