>>> Simon Matter pravi:
The rpms are using the mail facility, so you may put mail.* something
in
syslog.conf.
I tried using deliver on RHEL4 now with the autocreate feature and it
has
worked fine. What is the exact deliver command line which fails?
>>> postfi
Thanks!
Mitja
Simon Matter wrote:
Opened a bug report for it, this is really an issue for all those using
deliver instead of LMTP.
https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=2786
Simon
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
>> Simon Matter pravi:
>>> The rpms are using the mail facility, so you may put mail.* something
>>> in
>>> syslog.conf.
>>>
>>> I tried using deliver on RHEL4 now with the autocreate feature and it
>>> has
>>> worked fine. What is the exact deliver command line which fails?
>>>
>> postfix's master
> Simon Matter pravi:
>> The rpms are using the mail facility, so you may put mail.* something in
>> syslog.conf.
>>
>> I tried using deliver on RHEL4 now with the autocreate feature and it
>> has
>> worked fine. What is the exact deliver command line which fails?
>>
> postfix's master.cf:
> cyrus
Simon Matter pravi:
The rpms are using the mail facility, so you may put mail.* something in
syslog.conf.
I tried using deliver on RHEL4 now with the autocreate feature and it has
worked fine. What is the exact deliver command line which fails?
postfix's master.cf:
cyrus unix - n
> Simon Matter pravi:
>>> I have one problem :)
>>>
>>> After RHEL4 box upgrade (2.2.12) to 2.3.1, deliver crashes with sig
>>> 11...
>>>
>>> Jan 24 10:01:21 mail postfix/pipe[25836]: 40F23C0002: to=<[EMAIL
>>> PROTECTED]>,
>>> relay=cyrus, delay=0, status=deferred (Command died with signal 11:
>>
Simon Matter pravi:
I have one problem :)
After RHEL4 box upgrade (2.2.12) to 2.3.1, deliver crashes with sig 11...
Jan 24 10:01:21 mail postfix/pipe[25836]: 40F23C0002: to=<[EMAIL PROTECTED]>,
relay=cyrus, delay=0, status=deferred (Command died with signal 11:
"/usr/lib/cyrus-imapd/deliver")
Then it is quite unlikely that it is autocreate patch's fault since:
1. The patch is disabled
2. Mailbox exists
3. lmtpd is not involved in the delivery
To be on the safe side, check your logs. Cyrus logs by default in local4
facility (I am not sure if Simon has or has not changed it in his
HI,
createonpost is disabled and mailbox exists.
Hm, if I use LMTP, then mail is delivered just fine...
How can I enable debug level?
Putting mail.* in syslog.conf doesn't show anything more...
Mitja
Christos Soulios pravi:
Hi,
I would like to check out if it is the autocreate patch's fault
Simon Matter pravi:
Simon Matter pravi:
I am pleased to announce the release of Cyrus IMAPd 2.3.1 as Invoca RPM
designed for RedHat/Fedora Core based distributions. The RPM builds on
Simon, thanks for your work!
I have one problem :)
After RHEL4 box upg
Hi,
I would like to check out if it is the autocreate patch's fault for this
situation.
So, do you have the createonpost option enabled in your imapd.conf Do
you get the same error if you disable it? Does the mailbox to which you
deliver the mail exist or is it created at that time?
Could y
> Simon Matter pravi:
>> I am pleased to announce the release of Cyrus IMAPd 2.3.1 as Invoca RPM
>> designed for RedHat/Fedora Core based distributions. The RPM builds on
>>
>
> Simon, thanks for your work!
> I have one problem :)
>
> After RHEL4 box upgrade (2.2.12) to 2.3.1, deliver crashes with
Simon Matter pravi:
I am pleased to announce the release of Cyrus IMAPd 2.3.1 as Invoca RPM
designed for RedHat/Fedora Core based distributions. The RPM builds on
Simon, thanks for your work!
I have one problem :)
After RHEL4 box upgrade (2.2.12) to 2.3.1, deliver crashes with sig 11...
Ja
I am pleased to announce the release of Cyrus IMAPd 2.3.1 as Invoca RPM
designed for RedHat/Fedora Core based distributions. The RPM builds on
everything from RedHat 6.2 to RHEL4 and Fedora Core 1 to 4. The package is
designed to allow simple upgrades from any previous Invoca Cyrus IMAPd RPM
releas
14 matches
Mail list logo
