com.sun.mail.iap.CommandFailedException

A66 NO Some of the requested messages no longer exist.

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 web27

  • via Oracle Community by 846590, 11 months ago
    A66 NO Some of the requested messages no longer exist.
  • A415 NO [UNAVAILABLE] FETCH Server error while fetching messages
  • via Oracle Community by 843834, 1 year ago
    A15 NO FETCH could not complete for one or more messages
  • Stack trace

    • com.sun.mail.iap.CommandFailedException: A66 NO Some of the requested messages no longer exist. at com.sun.mail.iap.Protocol.handleResult(Protocol.java:341) at com.sun.mail.iap.Protocol.simpleCommand(Protocol.java:363) at com.sun.mail.imap.protocol.IMAPProtocol.copy(IMAPProtocol.java:1338) at com.sun.mail.imap.protocol.IMAPProtocol.copy(IMAPProtocol.java:1320) at com.sun.mail.imap.IMAPFolder.copyMessages(IMAPFolder.java:1541) at com.bea.wli.sb.transports.email.EmailWorkPartitioningAgent.processPostRead(EmailWorkPartitioningAgent.java:459) at com.bea.wli.sb.transports.email.EmailWorkPartitioningAgent.processInboxMessages(EmailWorkPartitioningAgent.java:261) at com.bea.wli.sb.transports.email.EmailWorkPartitioningAgent.execute(EmailWorkPartitioningAgent.java:100) at com.bea.wli.sb.transports.poller.TransportTimerListener.run(TransportTimerListener.java:74) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:452) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314) at java.util.concurrent.FutureTask.run(FutureTask.java:149) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:109) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:217) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:897) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919) at java.lang.Thread.run(Thread.java:738)

    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

    3 times, 5 months ago