Bug 130308 - deliver segfaults when destination folder does not exists
Summary: deliver segfaults when destination folder does not exists
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: cyrus-imapd   
(Show other bugs)
Version: 4.0
Hardware: i386
OS: Linux
Target Milestone: ---
: ---
Assignee: Tomas Janousek
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2004-08-18 22:22 UTC by Zailo Leite
Modified: 2007-11-30 22:07 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-01 12:43:10 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Zailo Leite 2004-08-18 22:22:29 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7)
Gecko/20040626 Firefox/0.9.1

Description of problem:
The patch cyrus-imapd-2.2.6-autocreate-0.2.diff has a bug.
When delivering mail using deliver, running as the cyrus admin, the
process will segfault if teh mail folder specified in -m does not exist.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.change user to the cyrus admin user.
2.cat sometestmail | /usr/local/cyrus/bin/deliver -a somemailuser -m
3.boom. Watch the errors on maillog refering to deliver exiting with
signal 11.

Actual Results:  The "deliver" process crashes with signal 11.

Expected Results:  Creation on the new folder and delivery of the message.

Additional info:

This was discovered durin a migration script run involving thousands
of users, so maybe the rapid-firing of the requests is a factor.
Removing the autocreate patch from the SRPM solves the issue. Messages
are rejected but the process won't crash.

Comment 1 Matthew Miller 2005-04-26 16:08:24 UTC
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.

Comment 2 Daniel Colascione 2006-01-25 02:59:09 UTC
This happens for me too, and I'm running RHEL 4.

Comment 3 Tomas Janousek 2007-05-28 11:13:47 UTC
This bug has been fixed as part of cyrus-imapd update in RHEL 4.5:

Please, check whether it actually was so that we can close this report.

Comment 4 Tomas Janousek 2007-08-14 11:35:44 UTC

Comment 5 Tomas Janousek 2007-10-01 12:43:10 UTC
Closing for no response. (Although it has hopefully been fixed, just lacks

Note You need to log in before you can comment on or make changes to this bug.