You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the trash folder is placed in a hierachy, the upmost directory will be set as folderNameOfTrash effectively making it the Trash. This is caused in folderFromResponse
The text was updated successfully, but these errors were encountered:
In ICEndpoint>>folderFromResponse: the folder name for Trash is always the first member of the folderPath array.
If we have a trash folder below Inbox called Inbox.Trash e.g., currently we only take the first member Inbox.
See this loc: (responseLine includesSubstring: '\Trash') ifTrue: [self folderNameOfTrash: folderPath first].
The idea of simply using ICEndpointFolder>>folderPath which holds Inbox.Trash in the example did not work, because on many sites we get protocol errors for many (strange) reasons. It seems to be more complicated than that.
If the trash folder is placed in a hierachy, the upmost directory will be set as
folderNameOfTrash
effectively making it the Trash. This is caused infolderFromResponse
The text was updated successfully, but these errors were encountered: