mirror of
https://github.com/cypht-org/cypht.git
synced 2026-04-25 13:05:53 +03:00
[GH-ISSUE #138] Failure to create folders #114
Labels
No labels
2fa
I18N
PGP
Security
Security
account
advanced_search
advanced_search
announcement
api_login
authentication
awaiting feedback
blocker
bug
bug
bug
calendar
config
contacts
core
core
devops
docker
docs
duplicate
dynamic_login
enhancement
epic
feature
feeds
framework
github
github
gmail_contacts
good first issue
help wanted
history
history
imap
imap_folders
inline_message
installation
keyboard_shortcuts
keyboard_shortcuts
ldap_contacts
mobile
need-ssh-access
new module set
nux
pop3
profiles
pull-request
question
refactor
release
research
saved_searches
smtp
strategic
tags
tests
themes
website
wordpress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/cypht#114
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jmce on GitHub (Oct 15, 2016).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/138
Originally assigned to: @jasonmunro on GitHub.
With cypht configured for IMAP access to a dovecot server (→ version info at the end),
I was unable to create new folders (both at the top and under pre-existing folders),
getting the following nginx error log entry (edited to change server domain and client IP address to example values)
Version info:
cypht master.zip files from 2016-10-12 14:48:18 +0000 on Debian Jessie [8.6] with
@jasonmunro commented on GitHub (Oct 17, 2016):
Sorry about this. I changed the way we cache IMAP data, and failed to update this module set's calls to the method. Fixed in
github.com/jasonmunro/cypht@7ed6e4c263@jasonmunro commented on GitHub (Oct 17, 2016):
Since I'm pretty sure this is resolved I'm closing this issue. Feel free to re-open if it's still not working for you!