You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Benoit Tellier (Jira)" <se...@james.apache.org> on 2022/05/09 02:03:00 UTC
[jira] [Closed] (JAMES-1438) james server signature verification failed
[ https://issues.apache.org/jira/browse/JAMES-1438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benoit Tellier closed JAMES-1438.
---------------------------------
Resolution: Won't Fix
James 2.3 is unmaintained, end of life.
Feel free to reopen if work is planned on this.
> james server signature verification failed
> -------------------------------------------
>
> Key: JAMES-1438
> URL: https://issues.apache.org/jira/browse/JAMES-1438
> Project: James Server
> Issue Type: Bug
> Affects Versions: 2.3.2
> Environment: Production and Test
> Reporter: Ashok Varma
> Priority: Major
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Hello All,
> I recently started working on Apache James Server.
> users reported the following error from our mailet logs.
> 05/10/12 14:58:53 INFO James.Mailet: com.total.eai.mail.transport.mailets.FromMareva: DEBUG update first key signature with content
> 05/10/12 14:58:53 INFO James.Mailet: com.total.eai.mail.transport.mailets.FromMareva: DEBUG read signature1.sig inputStream
> 05/10/12 14:58:53 INFO James.Mailet: com.total.eai.mail.transport.mailets.FromMareva: DEBUG signature size is 135 bytes
> 05/10/12 14:58:53 INFO James.Mailet: com.total.eai.mail.transport.mailets.FromMareva: INFO verify signature of document1.xml
> 05/10/12 14:58:53 INFO James.Mailet: com.total.eai.mail.transport.mailets.FromMareva: DEBUG signature verification failed with 1st public key => try 2nd publ
> ic key
> 05/10/12 14:58:53 INFO James.Mailet: com.total.eai.mail.transport.mailets.FromMareva: DEBUG update second key signature with content
> 05/10/12 14:58:53 INFO James.Mailet: com.total.eai.mail.transport.mailets.FromMareva: WARNING bad signature (checked with both public keys) - process not sto
> pped for now (DELTA acceptance test phase)
> I found the below error in Spool manager Logs :
> 05/10/12 18:29:10 WARN spoolmanager.fromMarevaToEAIDelta: Message MailXXXXXXXXXXXXXXXXX reached the end of this processor, and is automatically deleted. This may indicate a configuration error.
> We are only facing this issue from last two days.
> Can you please let me where should I check .. we have made no changes to the config recently.
> Thanks.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org