Hi Matt,
As far as I see you are using James on Windows. I don't know which Win
you are using but some of them have file path length limits. So your
problem may not be directly related to James. Please check your OS for
that limit; for example try to create a file manually which have 255
chars in its path.
Ozgur Eroglu
On 06/11/2015 05:47 PM, Matt Pryor wrote:
Hi all,
We're running Apache James 2.3.2.
Came across a quirk today whereby if an email is submitted to SMTP with a
particularly long domain name, it fails somewhat miserably to create the
file in outgoing:
11/06/15 13:49:43 WARN mailstore: Exception caught while storing a stream
java.io.FileNotFoundException:
D:\james-2.3.2\apps\james\var\mail\outgoing\4D61696C313433343032363935383231342D333437352D746F2D656832387664346D616674356C62657363666237796676386673396A756B796265723665707938346C31683669617877342E632D33757363686561752E637331342E636173652E73616E64626F782E73616C6573666F7263652E636F6D.Repository.FileStreamStore
(The filename, directory name, or volume label syntax is incorrect)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(Unknown Source)
at java.io.FileOutputStream.<init>(Unknown Source)
at
org.apache.james.mailrepository.filepair.AbstractFileRepository.getOutputStream(AbstractFileRepository.java:268)
at
org.apache.james.mailrepository.filepair.File_Persistent_Stream_Repository.put(File_Persistent_Stream_Repository.java:68)
at
org.apache.james.mailrepository.AvalonMailRepository.store(AvalonMailRepository.java:301)
at
org.apache.james.transport.mailets.RemoteDelivery.service(RemoteDelivery.java:1025)
at
org.apache.james.transport.LinearProcessor.service(LinearProcessor.java:424)
at
org.apache.james.transport.JamesSpoolManager.process(JamesSpoolManager.java:405)
at
org.apache.james.transport.JamesSpoolManager.run(JamesSpoolManager.java:309)
at java.lang.Thread.run(Unknown Source)
The address that we were attempting to deliver to was:
*commsf...@eh28vd4maft5lbescfb7yfv8fs9jukyber6epy84l1h6iaxw4.c3uscheau.cs14.case.sandbox.salesforce.com
<commsf...@eh28vd4maft5lbescfb7yfv8fs9jukyber6epy84l1h6iaxw4.c3uscheau.cs14.case.sandbox.salesforce.com>*
I've tried sending to a very long user with a shorter domain and that
causes no problems. So I'm guessing that the filename it generates is based
on an encrypted / hashed version of the domain name, is that correct?
Is there a fix available for this?
Many thanks
Matt Pryor
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
