[jira] Created: (JAMES-296) James does not handle Source Routing
Message: A new issue has been created in JIRA. - View the issue: http://issues.apache.org/jira/browse/JAMES-296 Here is an overview of the issue: - Key: JAMES-296 Summary: James does not handle Source Routing Type: Bug Status: Open Priority: Major Project: James Components: Mailet API Fix Fors: 2.2.1 Versions: 2.2.0RC5 Assignee: Soren Hilmer Reporter: Soren Hilmer Created: Wed, 9 Jun 2004 1:17 AM Updated: Wed, 9 Jun 2004 1:17 AM Description: Old RFC-821 style addresses like: @YYY.XXX.DK:[EMAIL PROTECTED] Makes James (SMTPServer, but the actual bug is in the mailet api's MailAddress): ERROR smtpserver: Error parsing sender address: @YYY.XXX.DK:[EMAIL PROTECTED]: No local-part (user account) found at position 1 Which is logical as MailAddress is not designed to handle source routes. But according to RFC-2821 appendix F.2: SMTP servers MUST continue to accept source route syntax as specified in the main body of this document and in RFC 1123. They MAY, if necessary, ignore the routes and utilize only the target domain in the address. If they do utilize the source route, the message MUST be sent to the first domain shown in the address. In particular, a server MUST NOT guess at shortcuts within the source route. So to be compliant James actually MUST accept this syntax Proposed fix is to ignore the source routes and use the target domain as suggested in the quote above. This is also the way the Postfix mailserver handles this. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] Release James 2.2.0RC5 as James v2.2.0
+1 -- Søren Hilmer, M.Sc. RD manager Phone: +45 70 27 64 00 TietoEnator IT+ A/S Fax:+45 70 27 64 40 Ved Lunden 12 Direct: +45 87 46 64 57 DK-8230 Åbyhøj Email: soren.hilmer at tietoenator.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release James 2.2.0RC5 as James v2.2.0
Noel J. Bergman wrote: [x] +1 - Release james 2.2.0RC5 as James 2.2.0 [ ] -1 - Do not release due to ___ -- Serge Knystautas Lokitech software . strategy . design http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] Release James 2.2.0RC5 as James v2.2.0
[X] +1 - Release james 2.2.0RC5 as James 2.2.0 -- Steve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (JAMES-276) The url for the ENTITY declarations in config.xml should be just ../conf/file-name
Message: The following issue has been closed. Resolver: Steve Brewin Date: Wed, 9 Jun 2004 1:24 PM Version 2.2.0RC3 is fine. - View the issue: http://issues.apache.org/jira/browse/JAMES-276 Here is an overview of the issue: - Key: JAMES-276 Summary: The url for the ENTITY declarations in config.xml should be just ../conf/file-name Type: Bug Status: Closed Priority: Minor Resolution: FIXED Project: James Components: James Core Fix Fors: 2.2.0RC3 Versions: 2.2.0RC1 2.2.0RC2 Assignee: Reporter: Steve Brewin Created: Sun, 2 May 2004 2:28 PM Updated: Wed, 9 Jun 2004 1:24 PM Description: The url for the ENTITY declarations in config.xml should be just ../conf/file-name to get it relative to the position of config.xml instead of file:../apps/james/conf/file-name. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[GUMP@brutus]: james-server/james-server failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact folk at [EMAIL PROTECTED] Project james-server has an issue affecting its community integration, and has been outstanding for 5 runs. Project State : 'Failed', Reason 'Build Failed' Full details are available at: http://brutus.apache.org:8080/gump/james-server/james-server/index.html That said, some snippets follow: The following annotations were provided: -DEBUG- Sole jar [james.bar] identifier set to project name -INFO- Enable verbose output, due to 4 previous error(s). -INFO- Failed with reason build failed -INFO- Enable debug output, due to build failure. The following work was performed: http://brutus.apache.org:8080/gump/james-server/james-server/gump_work/build_james-server_james-server.html Work Name: build_james-server_james-server (Type: Build) State: Failed Elapsed: 0 hours, 0 minutes, 1 seconds Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xml-apis.jar org.apache.tools.ant.Main -verbose -Dgump.merge=/usr/local/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only [Working Directory: /usr/local/gump/public/workspace/james-server] CLASSPATH : /usr/local/j2sdk1.4.2_04/lib/tools.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-stylebook.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/packages/javamail-1.3/mail.jar:/usr/local/gump/public/workspace/avalon/framework/impl/target/avalon-framework-impl-20040609.jar:/usr/local/gump/public/workspace/avalon/framework/target/avalon-framework-20040609.jar:/usr/local/gump/public/workspace/avalon/framework/api/target/avalon-framework-api-20040609.jar:/usr/local/gump/public/workspace/avalon-components/cornerstone/connection/api/target/cornerstone-connection-api-20040609.jar:/usr/local/gump/public/workspace/checkstyle/target/dist/checkstyle-20040609/checkstyle-20040609.jar:/usr/local/gump/packages/antlr-2.7.3/antlr.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-20040609.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-bcel/bin/bcel.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-20040609.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-20040609.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-20040609.jar:/usr/local/gump/public/workspace/avalon-logkit/target/avalon-logkit-20040609.jar:/usr/local/gump/public/workspace/avalon-components/cornerstone/connection/impl/target/cornerstone-connection-impl-20040609.jar:/usr/local/gump/public/workspace/avalon-components/cornerstone/datasources/api/target/cornerstone-datasources-api-20040609.jar:/usr/local/gump/public/workspace/avalon-components/cornerstone/datasources/impl/target/cornerstone-datasources-impl-20040609.jar:/usr/local/gump/public/workspace/avalon-components/cornerstone/scheduler/api/target/cornerstone-scheduler-api-20040609.jar:/usr/local/gump/public/workspace/avalon-components/cornerstone/scheduler/impl/target/cornerstone-scheduler-impl-20040609.jar:/usr/local/gump/public/workspace/avalon-components/cornerstone/sockets/api/target/cornerstone-sockets-api-20040609.jar:/usr/local/gump/public/workspace/avalon-components/cornerstone/sockets/impl/target/cornerstone-sockets-impl-20040609.jar:/usr/local/gump/public/workspace/avalon-components/cornerstone/store/api/target/cornerstone-store-api-20040609.jar:/usr/local/gump/public/workspace/avalon-components/cornerstone/store/impl/target/cornerstone-store-impl-20040609.jar:/usr/local/gump/public/workspace/avalon-components/cornerstone/threads/api/target/cornerstone-threads-api-20040609.jar:/usr/local/gump/public/workspace/avalon-components/cornerstone/threads/impl/target/cornerstone-threads-impl-20040609.jar:/usr/local/gump/public/workspace/avalon-excalibur/compatibility/target/excalibur-compatibility-20040609.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace
RE: Commons DBCP and Pool 1.2
Dirk, Do we need to immediately issue a DBCP and Pool 1.2.1 with the 1.4 dependencies removed? James has 1.3 as an operational platform, and we have quite a few users who are not on 1.4. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Source Routing
The backend system (apparently it must have a few years on it's back) uses addresses like: @YYY.XXX.DK:[EMAIL PROTECTED] Now James hickups at this issuing: ERROR smtpserver: Error parsing sender address: @YYY.XXX.DK:[EMAIL PROTECTED]: No local-part (user account) found at position 1 So to be compliant James actually MUST accept this syntax ;-( Please see RFC 2821 #3.3, #3.7, and most importantly, #4.1.1.3, which makes it quite clear that we are entitled to reject with a 550 the RCPT TO command that provided a source route. If you want to support it by stripping the source route information, that's fine, but I'm just as comfortable issuing the 550. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
