java.io.IOException

system can’t find the specified path。

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web9608

  • via james-server-user by 勐 杨, 9 months ago
    system can’t find the specified path
  • via james-server-user by 勐 杨, 9 months ago
    system can’t find the specified path
  • via james-server-user by 勐 杨, 1 year ago
    system can’t find the specified path
  • Stack trace

    • java.io.IOException: system can’t find the specified path。 at org.apache.james.core.MimeMessageInputStreamSource.<init>(MimeMessageInputStreamSource.java:118) at org.apache.james.smtpserver.JamesDataCmdHandler.doDATA(JamesDataCmdHandler.java:46) at org.apache.james.protocols.smtp.core.DataCmdHandler.onCommand(DataCmdHandler.java:95) at org.apache.james.protocols.smtp.core.DataCmdHandler.onCommand(DataCmdHandler.java:43) at org.apache.james.protocols.api.AbstractCommandDispatcher.onLine(AbstractCommandDispatcher.java:150) at org.apache.james.protocols.impl.AbstractChannelUpstreamHandler.messageReceived(AbstractChannelUpstreamHandler.java:139) at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:545) at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:754) at org.jboss.netty.handler.execution.ChannelEventRunnable.run(ChannelEventRunnable.java:69) at org.jboss.netty.handler.execution.OrderedMemoryAwareThreadPoolExecutor$ChildExecutor.run(OrderedMemoryAwareThreadPoolExecutor.java:316) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.