package dovecot-core 1:2.2.9-1ubuntu5 failed to install/upgrade: Unknown setting: managesieve_max_line_length
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dovecot (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
package dovecot-core 1:2.2.9-1ubuntu5 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 255
ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: dovecot-core 1:2.2.9-1ubuntu5
Uname: Linux 3.18.0-
NonfreeKernelMo
ApportVersion: 2.14.7-0ubuntu8
Architecture: i386
Date: Fri Dec 19 20:26:39 2014
DovecotConf:
Error: command ['/usr/
doveconf: Fatal: Error in configuration file /etc/dovecot/
ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 255
InstallationDate: Installed on 2014-07-30 (145 days ago)
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130213)
SourcePackage: dovecot
Title: package dovecot-core 1:2.2.9-1ubuntu5 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 255
UpgradeStatus: No upgrade log present (probably fresh install)
summary: |
- package dovecot-core 1:2.2.9-1ubuntu5 failed to install/upgrade: sub- - processo script post-installation instalado retornou estado de saída de - erro 255 + package dovecot-core 1:2.2.9-1ubuntu5 failed to install/upgrade: Unknown + setting: managesieve_max_line_length |
Thank you for your report.
This looks like a local configuration problem, rather than a bug in Ubuntu. You can find pointers to get help for this sort of problem here: http:// www.ubuntu. com/support/ community , but please note that the Ubuntu release you are running (14.10 Utopic Unicorn) reached its end of life in 2015 and is not supported anymore.
Since we use this bug tracker to track bugs in Ubuntu rather than configuration problems, and since the report is against an unsupported release of Ubuntu, I'm marking this bug as Invalid. If you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http:// www.chiark. greenend. org.uk/ ~sgtatham/ bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.