Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • balsa balsa
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 23
    • Issues 23
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOME
  • balsabalsa
  • Issues
  • #54
Closed
Open
Created Jan 31, 2021 by Damian Poddebniak@duesee1

Crash, when server answers with `EXPUNGE 1` directly after greeting.

This is the trace, which leads to a crash:

S: * OK [CAPABILITY IMAP4REV1 STARTTLS LOGINDISABLED] IMAP server ready.\r\n
S: * 1 EXPUNGE\r\n
* 2 EXPUNGE\r\n
* 3 EXPUNGE\r\n
C: 5 StartTLS\r\n
S: 5 OK begin TLS now.\r\n

I am very sorry, that I didn't provide more information. I can take a closer look in a week or so. However, I guess this should be very easy for you to reproduce and find the cause of it.

I havn't looked into the source of balsa, but I strongly recommend, that all untagged responses are just discarded before STARTTLS.

Assignee
Assign to
Time tracking