View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0006153SOGoWeb Mailpublic2025-10-15 07:232025-10-15 11:31
Reporterhostaant Assigned Toqhivert  
PrioritynormalSeverityminorReproducibilitysometimes
Status feedbackResolutionopen 
PlatformLinuxOSDebianOS Version12
Product Version5.8.0 
Summary0006153: Sending mail results in HTTP 405 and "Sent is not an IMAP4 folder" error
Description

Sometimes when sending mail via the web mail UI an error message "Sent is not an IMAP4 folder" pops up. The email is sent and goes through but is not saved in the "Sent" folder.

Usually the when sending mail it is saved in the same Sent folder just as one would expect, but once for every 20-30 emails or so the issue is triggered. This has happened on multiple separate email accounts and installations.

The IMAP server is Courier.

Steps To Reproduce
  1. In the web mail view, choose to send a new email.
  2. Fill in the recipient address, subject and mail body.
  3. Click the arrow to send the mail.

The error is triggered occasionally, once for every 20-30 emails.

Additional Information

The sogo server shows this 405 error:
Oct 15 06:48:58 sogod [3934536]: 127.0.0.1 "POST /SOGo/so/test@hostaan.li/Mail/0/folderINBOX/folderDrafts/newDraft1760510906-1/send HTTP/1.0" 405 60/151 0.985 - - 4K - 15

The browser tools show the reponse code "405 Method not allowed", and the response body is:
{"status": "failure", "message":"Sent is not an IMAP4 folder"}

TagsNo tags attached.

Activities

hostaant

hostaant

2025-10-15 07:23

reporter  

error.png (54,484 bytes)   
error.png (54,484 bytes)   
qhivert

qhivert

2025-10-15 11:31

administrator   ~0018354

Hello.
To have this error sogo does:

  • check if the mailbox exists by doing the imap command 'status "Sent" (UIDVALIDITY)'
  • If not, create the folder with the 'create' command
    If both fail, you get this error.

If it the fail is random it may be due to a connection error or that your imap server is unavailable. You should check courier log.

You could also try to add this in your sogo.conf to make sure each request make a fresh connection.
NGImap4DisableIMAP4Pooling = YES;

Issue History

Date Modified Username Field Change
2025-10-15 07:23 hostaant New Issue
2025-10-15 07:23 hostaant File Added: error.png
2025-10-15 11:31 qhivert Note Added: 0018354
2025-10-15 11:31 qhivert Assigned To => qhivert
2025-10-15 11:31 qhivert Status new => feedback