mirror of
https://github.com/opensolutions/ViMbAdmin.git
synced 2026-04-26 08:45:54 +03:00
[GH-ISSUE #205] Doesn't create maildir anymore #160
Labels
No labels
bug
feature
feature
improvement
improvement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ViMbAdmin-opensolutions#160
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 @schwindelbub on GitHub (Sep 9, 2016).
Original GitHub issue: https://github.com/opensolutions/ViMbAdmin/issues/205
Hi,
the ViMbAdmin doesn't create maildirs anymore. It creates the datebase entry but nothing on the filesystem. If i try to delete it, it doesn't delete the database entry. So if i try to create the same mailbox again, an error message is shown.
A few weeks ago everything works fine. I created some mailboxes. I have no idea, what changed on the system.
Has anybody an idea? Or an hint for me?
Debian 8
PHP 5.6
Thanks and best regards
Schwindelbub
@PhrozenByte commented on GitHub (Sep 9, 2016):
ViMbAdmin never created directories on the filesystem, this is up to your MDA/LDA. ViMbAdmin just tells your MDA/LDA where to create the directories. What did you delete (the filesystem folder or the database entry? what exactly?) and what exact error message is shown? Check your webserver's error.log and if necessary enable ViMbAdmin's debugging feature (see https://github.com/opensolutions/ViMbAdmin/wiki/Configuration#logging)
@barryo commented on GitHub (Sep 10, 2016):
Hi @schwindelbub - @PhrozenByte is correct, ViMbAdmin never created any filesystem entries (this is because we never assumed ViMbAdmin and the mail server are necessarily on the same server).
I'm closing this as it's neither a bug nor a feature request but feel free to continue the conversation (or, more appropriately, move it to the mailing list).