Jean Charles Delépine écrivait (wrote) :
> Jean Charles Delépine écrivait (wrote) :
>
> > Hello,
> >
> > I'm on the way to migrate one quite big murder config with Cyrus IMAP
> > 3.0.8-Debian-3.0.8-6+deb10u4
> > to Cyrus IMAP 3.2.3-Debian-3.2.3-1~bpo10+1.
> >
> > My plan is to replicate 3.0.8
ellie timoney écrivait (wrote) :
> On Thu, 24 Sep 2020, at 1:44 AM, Jean Charles Delépine wrote:
> > Is this a known problem corrected after 3.0.9 ?
>
> Off the top of my head I no longer remember, but the current release in the
> 3.0 series is 3.0.14. I'd suggest, if you haven't already, that
On Thu, 24 Sep 2020, at 1:44 AM, Jean Charles Delépine wrote:
> Is this a known problem corrected after 3.0.9 ?
Off the top of my head I no longer remember, but the current release in the 3.0
series is 3.0.14. I'd suggest, if you haven't already, that you look in the
release notes from 3.0.8-3.
Jean Charles Delépine écrivait (wrote) :
> Hello,
>
> I'm on the way to migrate one quite big murder config with Cyrus IMAP
> 3.0.8-Debian-3.0.8-6+deb10u4
> to Cyrus IMAP 3.2.3-Debian-3.2.3-1~bpo10+1.
>
> My plan is to replicate 3.0.8's backends on 3.2.3 ones. This plan has work
> before for 2.
cate empty mailboxes. So the conf (attached) seems ok.
But if the mailbox isn't empty here's the result (completes traces attached) :
cyrus/sync_client[3082351]: MAILBOX received NO response:
IMAP_PROTOCOL_ERROR Protocol error
cyrus/sync_client[3082351]: do_folders(): update failed: user.t
.
But I had a bad Cyrus IMAP 2.4 with some mailboxes which had references
in mailboxes.db only, and not in file system and metadata.
Solving above error, then sync_client from 3.2 IMAP host to backupd host
works.
I don't know why I don't see errors in sync_client from 2.4 to 3
Hello,
I would ask an help with a new replication error in backup channel.
I have this never-ending loop error:
2020-07-22T11:35:16.212126+02:00 tst-msg03 cyrus/sync_client[22465]:
MAILBOXES received NO response: IMAP_PROTOCOL_BAD_PARAMETERS Bad parameters
2020-07-22T11:35:16.212185+02:00 tst
Thanks for your answer, but with self build lmtpd I got this error by trying to
receive mails:
May 28 19:28:23 CGSG postfix/lmtp[1514]: AAC857E0037:
to=mailto:j...@company-group.net>>,
relay=groupware.uc-central.net[/local/socket/lmtp], delay=3.2,
delays=3.1/0.01/0.05/0, dsn=4.4.2,
Hello, David.
The code is in imap/lmtp_err..et, according to this bug report:
https://github.com/cyrusimap/cyrus-imapd/issues/3035
Good luck!
Javier.-
El 28/5/20 a las 13:20, David Faller escribió:
>
> Thanks for your solution, could you provide detailed which line did
> you change?
>
> under
Thanks for your solution, could you provide detailed which line did you change?
under imap/lmptd.c or lmtpd.h which line did you adjust?
Best Regards,
David Faller
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
Finally, I downloaded source from
https://github.com/cyrusimap/cyrus-imapd/releases/download/cyrus-imapd-3.2.0/cyrus-imapd-3.2.0.tar.gz
untar into /usr/src
installed dependencies (pkg-config, libsasl2-dev, libicu-dev,
libjansson-dev, libssl-dev, bison, flex...)
edit /usr/src/cyrus-imapd-3.2.
Dear all, we’re running into the same issue after upgrade cyrus to
3.2.0-5~bpo10+1
We had try to downgrade cyrus but after this we got kernel issues which prevent
thunderbird connections.
May 28 15:43:26 CGSG cyrus/master[2136]: process type:SERVICE name:lmtpchroot
path:/usr/lib/cyrus/bin/lmtp
queue.
And, in cyrus log:
cyrus/master[164861]: process type:SERVICE name:lmtpunix
path:/usr/lib/cyrus/bin/lmtpd age:11025.520s pid:217212 *signaled to
death by signal 6 (Aborted)**
*
And, in Cyrus status there's a error when try to access sieve, because
path are duplicated:
On Friday 27 March 2020, you wrote:
> With "reject8bit: yes", sendmail refuses the message with "Message
> contains non-ASCII characters in headers". (Still don't know why it
> doesn't refuse it upfront, but bounces it!).
This is LMTP error between
On 2020-03-28 04.59, Andrea Venturoli wrote:
> Any idea for a similar tool which can use UTF8SMTPS, so I can repeat
> that tests?
I would be going low-tech and using telnet or netcat or socat to
converse directly with your mail server's port 25. Craft the client's
side of the conversation in anot
On 2020-03-17 20:13, Andrea Venturoli wrote:
On 2020-03-17 15:52, Andrea Venturoli wrote:
Also,
https://www.cyrusimap.org/imap/reference/manpages/configs/imapd.conf.html#std:cyrusman-imapd.conf(5),
says "reject8bit: 0" is the default.
From this I understand my setup should NOT reject 8bit h
rwise.
I'd be curious what damage this can do.
In any case, activating it did not solve: I'm still getting "Data format
error" and bounce.
Still trying the other things.
bye & Thanks
av.
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://l
On Tuesday 17 March 2020, Andrea Venturoli wrote:
> > I'm now setting this explicitly and I'll see what happens.
>
> In fact, nothing changed.
I checked my Sendmail's log just in case and didn't find any
"Data format error" messages. I keep a log for
On 2020-03-17 23:49, Andrea Venturoli wrote:
_ sendmail is SMTPUTF8-aware (this is confirmed by EHLO); however
Cyrus isn't?
Could be. This option in imapd.conf might be relevant:
rfc2047_utf8: 0
If enabled, imapd will parse any non-encoded character sequence in MIME
header values as UTF8. T
On 2020-03-17 15:52, Andrea Venturoli wrote:
Also,
https://www.cyrusimap.org/imap/reference/manpages/configs/imapd.conf.html#std:cyrusman-imapd.conf(5),
says "reject8bit: 0" is the default.
From this I understand my setup should NOT reject 8bit headers (but
change non-ASCII characters to X)
/comp.mail.sendmail/xW7S5vXDNtY
May be the first one causes the "Data format error" message.
Thanks for pointing this out!
I've been fighting the "NUL characters" problem on the sendmail side for
a long time: it seems I won about some 10 months ago, since I don't see
any mo
On 2020-03-17 11:58, Deborah Pickett wrote:
Hi Andrea,
Hello and thanks a lot for your interest.
Finally I get some useful information on this!
The status 5.6.7 seems to be related to encodings. It's defined in RFC
6531, SMTP Extension for Internationalized Email:
When the SMTPUTF8-awa
the first one causes the "Data format error" message.
--
Regards, Sergey
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
msgid=,
proto=UTF8SMTPS, daemon=MTA, relay=xxx..net
[37.148.183.222]
sm-mta[97960]: AUTH=client, relay=localhost, mech=, bits=0
sm-mta[97960]: 00DI1r4x097841: to=xx, delay=00:00:11,
xdelay=00:00:00, mailer=cyrusv2, pri=67551, relay=localhost, dsn=5.6.7,
stat=Data format error
s
ata format error
sm-mta[97960]: 00DI1r4x097841: 00DI264w097960: DSN: Data format error
sm-mta[97960]: 00DI264w097960: to=,
delay=00:00:04, xdelay=00:00:04, mailer=esmtp, pri=3,
relay=mx1.slgnt.eu., dsn=5.1.2, stat=Host unknown (Name server:
xxx.x.xx.: no data known)
Most of these message
2020, at 10:22 AM, Zorg wrote:
put every time i this to add event (thunderbird, evolution, curl ) i
have this in the log "HTTP/1.1 500 Internal Server Error" (error=The
server encountered an internal error.)
Do you see any indicative error message in the log file (e.g. syslog)?
On Tue, Jan 28, 2020, at 10:22 AM, Zorg wrote:
> put every time i this to add event (thunderbird, evolution, curl ) i
> have this in the log "HTTP/1.1 500 Internal Server Error" (error=The
> server encountered an internal error.)
Do you see any indicative error message i
erver Error" (error=The
server encountered an internal error.)
What am i missing ?
Here is the mailbox i have and acl
user/myuser1/#calendars/attachme...@my.domain.com (\HasNoChildren)
user/myuser1/#calendars/defa...@my.domain.com (\HasNoChildren)
user/myuser1/#calendars/in...@my.
set conversations: 0
stop squatter
rm -r everything under search/*
change to conversations_db: twoskip
and then set conversations to 1 and restart squatter
?
Quoting Lists Nethead :
This error started after update to 3.0.12 yesterday.
No idea where to start - hints anyone?
Thanks,
Per
Cyrus
This error started after update to 3.0.12 yesterday.
No idea where to start - hints anyone?
Thanks,
Per
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info
not exist
something else is not working correct. Is the configdirectory configured?
Does it exist? Do directory and quotafiles exists?
I hadn't started tackling that error message yet. I will due my due diligence with Google, Stack Exchange, etc... and
come back to the lists if I can
25B:
from=, size=419, nrcpt=1 (queue active)
Dec 6 12:51:39 buttercup cyrus/lmtp[27814]: sieve runtime error for
jim id <20191206175139.07fba2168...@mail.home.lan>:
Fileinto (user/jim/System Messages): Mailbox does not exist
Can you post the sieve script. I don't know if the log shows
ge-id=<20191206175139.07fba2168...@mail.home.lan>
>Dec 6 12:51:39 buttercup postfix/qmgr[27671]: 07FBA216825B:
>from=, size=419, nrcpt=1 (queue active)
>Dec 6 12:51:39 buttercup cyrus/lmtp[27814]: sieve runtime error for
>jim id <20191206175139.07fba2168...@mail.home.lan>:
>F
7fba2168...@mail.home.lan>
Dec 6 12:51:39 buttercup postfix/qmgr[27671]: 07FBA216825B:
from=, size=419, nrcpt=1 (queue active)
Dec 6 12:51:39 buttercup cyrus/lmtp[27814]: sieve runtime error for jim id <20191206175139.07fba2168...@mail.home.lan>:
Fileinto (user/jim/System Messages): Mailb
Hi, Bron. Thanks for your reply.
On 5/2/19 17:21, Bron Gondwana wrote:
> You need to run cyr_expire occasionally to clean up deleted messages!
Checking the syslog, apparently it ran automatically this morning:
--
# grep cyr_expire /var/log/syslog /var/log/syslog.1
/var/log/syslog.1:Feb
You need to run cyr_expire occasionally to clean up deleted messages!
Bron.
On Wed, Feb 6, 2019, at 04:45, Daniel Bareiro wrote:
> Hi, Bron.
>
> On 4/2/19 14:02, Bron Gondwana wrote:
>
> > Awesome - yes, the IOERROR messages are because files it expected to
> > find weren't there. It's frustrat
Hi, Bron.
On 4/2/19 14:02, Bron Gondwana wrote:
> Awesome - yes, the IOERROR messages are because files it expected to
> find weren't there. It's frustrating that reconstruct isn't robust
> enough to bring a slightly bogus cyrus.index back from the dead, but the
> end result is a working mailbox
ing user.admin
> Feb 4 12:04:44 mail cyrus/reconstruct[22990]: reconstructing
> user.admin.Backups
> Feb 4 12:04:44 mail cyrus/reconstruct[22990]: reconstructing
> user.admin.Drafts
> Feb 4 12:04:44 mail cyrus/reconstruct[22990]: reconstructing
> user.admin.Sent
> Feb 4 12:04:44 mail cyrus
s
Feb 4 12:04:44 mail cyrus/reconstruct[22990]: reconstructing
user.admin.Drafts
Feb 4 12:04:44 mail cyrus/reconstruct[22990]: reconstructing
user.admin.Sent
Feb 4 12:04:44 mail cyrus/reconstruct[22990]: reconstructing
user.admin.TareasCron
Feb 4 12:04:44 mail cyrus/reconstruct[22990]: IOERROR:
Oh how frustrating...
On Mon, Feb 4, 2019, at 08:48, Daniel Bareiro wrote:
> Hi, Bron. Thanks for your reply.
>
> On 3/2/19 08:33, Bron Gondwana wrote:
>
> > Wow. A reconstruct should fix that. What version are you running?
>
> I tried using 'reconstruct' as you suggested and this was the resul
Hi, Bron. Thanks for your reply.
On 3/2/19 08:33, Bron Gondwana wrote:
> Wow. A reconstruct should fix that. What version are you running?
I tried using 'reconstruct' as you suggested and this was the result:
--
# /usr/lib/cyrus/bin/reconstruct -r user.admin
user.admin
user.admin.Backup
essage: "Server [servername] has disconnected. The server may have gone
> down or there may be a network problem".
>
> In that access attempt the log shows an entry like this:
>
> --
> Feb 2 21:55:38 mail cyrus/imaps[6510]: Fatal error: Exists wrong 513
> 512
log shows an entry like this:
--
Feb 2 21:55:38 mail cyrus/imaps[6510]: Fatal error: Exists wrong 513
512 483 17057
--
Maybe the index is corrupt and has some duplicate message?
Investigating on the web I found this reference [1]:
--
/* make sure we don't overflo
endmail, also postfix has a compatible sendmail
binary. Only the sendmail config in imapd.conf may not point to it.
Regards,
Simon
>
> On Tue, Dec 18, 2018 at 4:32 AM Simon Matter
> wrote:
>
>> > I'm trying to setup sieve and getting the following error in my logs:
>>
:
> > I'm trying to setup sieve and getting the following error in my logs:
> >
> > Dec 17 10:36:07 bllmail01 cyrus/lmtp[14530]: sieve runtime error for
> > jschaef...@harmonywave.net id
> > :
> > Reject: Sendmail process terminated normally, exit status 2
> I'm trying to setup sieve and getting the following error in my logs:
>
> Dec 17 10:36:07 bllmail01 cyrus/lmtp[14530]: sieve runtime error for
> jschaef...@harmonywave.net id
> :
> Reject: Sendmail process terminated normally, exit status 255
>
>
> I'm foll
I'm trying to setup sieve and getting the following error in my logs:
Dec 17 10:36:07 bllmail01 cyrus/lmtp[14530]: sieve runtime error for
jschaef...@harmonywave.net id
:
Reject: Sendmail process terminated normally, exit status 255
I'm following the documentation h
> "SI" == Stephen Ingram writes:
SI> I did turn it off just to see what happened, but it was not
SI> the problem. Nice though, because I learned how to relabel a volume
SI> to get back in the good graces of SELinux.
Well, just using setenforce doesn't disable selinux; it just disables
enforc
Jason-
That came up clean for my latest config, but it did highlight problems when
I didn't have the auth working. Thank you so much as this is a great search
command to help sleuth out those SELinux issues. I did turn it off just to
see what happened, but it was not the problem. Nice though, beca
If you suspect selinux, please do 'ausearch -m avc -ts today' and see what
you get. You may also wish to do 'setenforce 0' and try again, just to
make sure.
I can provide some basic help with selinux if that's needed.
- J<
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http
on't see anything of consequence there.
>
> Steve
>
> On Fri, Jun 1, 2018 at 10:41 AM, Patrick Boutilier
> wrote:
>
>> Anything in /var/log/audit/audit.log ?
>>
>>
>> On June 1, 2018 2:29:06 PM ADT, Stephen Ingram
>> wrote:
>>>
>>&
t; I'm also trying to get more debugging about he system I/O error, but
>> never see it in the cyrus logs, only in the postfix logs.
>>
>> Steve
>>
>> On Fri, Jun 1, 2018 at 9:37 AM, Patrick Boutilier
>> wrote:
>>
>>> On 06/01/2018 01:31 PM, St
Anything in /var/log/audit/audit.log ?
On June 1, 2018 2:29:06 PM ADT, Stephen Ingram wrote:
>Patrick-
>
>I'm also trying to get more debugging about he system I/O error, but
>never
>see it in the cyrus logs, only in the postfix logs.
>
>Steve
>
>On Fri, Jun 1, 20
Patrick-
I'm also trying to get more debugging about he system I/O error, but never
see it in the cyrus logs, only in the postfix logs.
Steve
On Fri, Jun 1, 2018 at 9:37 AM, Patrick Boutilier
wrote:
> On 06/01/2018 01:31 PM, Stephen Ingram wrote:
>
>> Patrick-
>>
>
et = 682
>> Jun 1 16:48:52 mx postfix/lmtp[18136]: send attr dsn_orig_rcpt =
>> rfc822;x...@x.com
>> Jun 1 16:48:52 mx postfix/lmtp[18136]: send attr notify_flags = 0
>> Jun 1 16:48:52 mx postfix/lmtp[18136]: send attr status = 4.3.0
>> Jun 1 16:48:52 mx postfix/l
stfix/lmtp[18136]: send attr status = 4.3.0
> Jun 1 16:48:52 mx postfix/lmtp[18136]: send attr diag_type = smtp
> Jun 1 16:48:52 mx postfix/lmtp[18136]: send attr diag_text = 451 4.3.0
> System I/O error
> Jun 1 16:48:52 mx postfix/lmtp[18136]: send attr mta_type = dns
> Jun 1 16
18136]: send attr notify_flags = 0
Jun 1 16:48:52 mx postfix/lmtp[18136]: send attr status = 4.3.0
Jun 1 16:48:52 mx postfix/lmtp[18136]: send attr diag_type = smtp
Jun 1 16:48:52 mx postfix/lmtp[18136]: send attr diag_text = 451 4.3.0
System I/O error
Jun 1 16:48:52 mx postfix/lmtp[18136]: send
: send attr notify_flags = 0
Jun 1 16:48:52 mx postfix/lmtp[18136]: send attr status = 4.3.0
Jun 1 16:48:52 mx postfix/lmtp[18136]: send attr diag_type = smtp
Jun 1 16:48:52 mx postfix/lmtp[18136]: send attr diag_text = 451
4.3.0 System I/O error
Jun 1 16:48:52 mx postfix/lmtp[18136]: send at
On 06/01/2018 01:31 PM, Stephen Ingram wrote:
Patrick-
Actually, nothing. I've got everything piped into /var/log/maillog and
not too much there either beyond the actual error message.
Hmmm... Usually when I have seen the System I/O error the log entry also
records what the a
On 6/1/18 12:21 PM, Stephen Ingram wrote:
I'm receiving a 451 4.3.0 System I/O error (in reply to end of DATA
command) error from Postfix when trying to deliver to cyrus-imap and
not really sure why. I'm on CentOS 7 (2.4.17-8) after downgrading from
current version. I'm using
Patrick-
Actually, nothing. I've got everything piped into /var/log/maillog and not
too much there either beyond the actual error message.
Steve
On Fri, Jun 1, 2018 at 9:23 AM, Patrick Boutilier
wrote:
> On 06/01/2018 01:21 PM, Stephen Ingram wrote:
>
>> I'm receiving
On 06/01/2018 01:21 PM, Stephen Ingram wrote:
I'm receiving a 451 4.3.0 System I/O error (in reply to end of DATA
command) error from Postfix when trying to deliver to cyrus-imap and not
really sure why. I'm on CentOS 7 (2.4.17-8) after downgrading from
current version. I'm
I'm receiving a 451 4.3.0 System I/O error (in reply to end of DATA
command) error from Postfix when trying to deliver to cyrus-imap and not
really sure why. I'm on CentOS 7 (2.4.17-8) after downgrading from current
version. I'm using Kerberos GSSAPI to connect to the front end, but
That happens occasionally. As far as I can tell it's not really a problem.
If it isn't logged all the time, I would just ignore it.
--On 6. April 2018 um 10:26:45 +0200 Paul Martin
wrote:
I have this error:
Apr 5 14:23:39 balprta003 cyrus/imap[76531]: IDLE: error sending mess
Hello
I have this error:
Apr 5 14:23:39 balprta003 cyrus/imap[76531]: IDLE: error sending message
NOTIFY to idled for mailbox user.martin.west: Resource temporarily
unavailable.
do you have an idea to solve the problem?
Regards,
Paul
Cyrus Home Page: http://www.cyrusimap.org/
List
Good morning,
I connect to cyrus imap server remotely by Roundcube web client. When
I tried to connect, I get an error from the syslog on imap server:
Nov 1 11:34:36 servername imap[15980]: login: cl.domain.cz
[192.168.24.52] mailarchiv plaintext User logged in
SESSIONID=
Nov 1 11:34:36
On 12.06.2017 20:02, Adam Tauno Williams wrote:
Quoting "Walter H. via Info-cyrus" :
on my CentOS6 I see this error
Jun 12 08:02:33 mail master[1941]: setrlimit: Unable to set file
descriptors limit to -1: Operation not permitted
It is normal-ish.
It might be useful to look at /et
Quoting "Walter H. via Info-cyrus" :
on my CentOS6 I see this error
Jun 12 08:02:33 mail master[1941]: setrlimit: Unable to set file
descriptors limit to -1: Operation not permitted
It is normal-ish.
It might be useful to look at /etc/security/limits.conf and ulimits in
Hi,
Quoting "Walter H. via Info-cyrus" :
Hello,
on my CentOS6 I see this error
Jun 12 08:02:33 mail master[1941]: setrlimit: Unable to set file
descriptors limit to -1: Operation not permitted
This is a common error message that is logged on cyrus start/restart,
which i
Hello,
on my CentOS6 I see this error
Jun 12 08:02:33 mail master[1941]: setrlimit: Unable to set file
descriptors limit to -1: Operation not permitted
what is causing this?
Thanks,
Walter
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu
On Wed, Apr 19, 2017, at 10:51, Frederik Himpe wrote:
> Sometimes I see in the logs messages like this: "same message appears
> twice 2394 2395". Looking at the source code, it does not appear to be
> a big problem, but I am not sure. Does this indicate a real problem?
> Should I run cyrreconstruc
Sometimes I see in the logs messages like this: "same message appears
twice 2394 2395". Looking at the source code, it does not appear to be
a big problem, but I am not sure. Does this indicate a real problem?
Should I run cyrreconstruct on the affected mailbox, and which options
do you recommend?
Dears,
I tried to build cyrus-imapd-3.0.0 on a REHL 7 (23-bit system) and run
into an error.
Error message:
...
/bin/sh ./libtool --tag=CC --mode=link gcc -fPIC -g -O2-o
imap/imapd imap/imap_proxy.o imap/imapd.o imap/mutex_fake.o
imap/pushstats.o imap/proxy.o imap
On Tue, May 31, 2016 at 04:55:03PM +0200, IMAP List Administration via
Info-cyrus wrote:
> talk to the hand?
American holiday weekend. Be patient. The people who frequent these
lists tend to be busy.
> > I've spent a fair amount of time reading the imapd and sasl documentation.
> > Google tur
l-2.1.26p15
>
> My server uses /etc/sasldb2.db for authentication.
>
> In my /etc/imapd.conf file I have:
> sasl_pwcheck_method: auxprop
> sasl_mech_list: CRAM-MD5 DIGEST-MD5
>
> Upon starting the new imapd server, things seem to work, but I noticed two
> e
xprop
sasl_mech_list: CRAM-MD5 DIGEST-MD5
Upon starting the new imapd server, things seem to work, but I noticed two error
messages I have not seen before which spam up my syslog:
imapd/imaps[15690]: SQL engine 'mysql' not supported
imapd/imaps[15690]: auxpropfunc error no mechanism ava
wants to deliver mails directly to the shared Drafts
folder via sieve script:
if anyof (header :contains "to" "mailtest")
{
fileinto "Drafts";
stop;
}
I get the error:
May 24 13:23:24 popc lmtpunix[6959]: sieve runtime error for mailtest
id <201605241123.u4
ts
folder via sieve script:
if anyof (header :contains "to" "mailtest")
{
fileinto "Drafts";
stop;
}
I get the error:
May 24 13:23:24 popc lmtpunix[6959]: sieve runtime error for mailtest id
<201605241123.u4OBMqJK006976@popc.localdomain>: Fileinto: Perm
I wonder if this is an 'altnamespace' issue - are you specifying INBOX/folder?
--
Merlin Hartley
> On 23 May 2016, at 12:52, Sunny via Info-cyrus
> wrote:
>
> Hi,
>
> I'm seeing the following error logs with some users sieve filtering
> May 23 11:41:31 i
>>> should work. If you
> >>> > could give us that and a copy of your lam output again with the
> >>> anyone ACLs set,
> >>> > maybe that will help.
> >>>
> >>> In which version of Cyrus release, 'p' permission is
he
anyone ACLs set,
> maybe that will help.
In which version of Cyrus release, 'p' permission is required even
with "sieve fileinto"?
I know that only direct lmtp deliver with subaddress require it.
Within lmtpd, subaddress delivery and fileinto are identical. I've
j
h version of Cyrus release, 'p' permission is required even with "sieve
fileinto"?
I know that only direct lmtp deliver with subaddress require it.
Within lmtpd, subaddress delivery and fileinto are identical. I've just
checked back to the 2.3 branch and the logic i
that will help.
>
> In which version of Cyrus release, 'p' permission is required even with
> "sieve fileinto"?
> I know that only direct lmtp deliver with subaddress require it.
Within lmtpd, subaddress delivery and fileinto are identical. I've just
checked
On Tue, 24 May 2016 07:25:42 +0900, Bron Gondwana via Info-cyrus
wrote:
On Mon, May 23, 2016, at 22:47, Sundeep Singh Nanuwa via Info-cyrus wrote:
On 23/05/16 13:35, Bron Gondwana via Info-cyrus wrote:
> You need to have "anyone p" acl to fileinto anything other than inbox.
That didn't work u
On Mon, May 23, 2016, at 22:47, Sundeep Singh Nanuwa via Info-cyrus wrote:
> On 23/05/16 13:35, Bron Gondwana via Info-cyrus wrote:
> > You need to have "anyone p" acl to fileinto anything other than inbox.
> That didn't work unfortunately.
Deliver into INBOX works, fileinto doesn't. It's ACLs fo
On 23/05/16 14:09, Jack Snodgrass via Info-cyrus wrote:
file permissions like right.. acl permissions look right... are you
running with selinux set to something other than disabled? Just a
guess... but everything else looks ok.
It's disabled
SELINUX=disabled
Thanks
Cyrus Home Page: ht
file permissions like right.. acl permissions look right... are you
running with selinux set to something other than disabled? Just a
guess... but everything else looks ok.
jack
On 05/23/2016 07:47 AM, Sundeep Singh Nanuwa via Info-cyrus wrote:
On 23/05/16 13:35, Bron Gondwana via Info-cy
On 23/05/16 13:35, Bron Gondwana via Info-cyrus wrote:
You need to have "anyone p" acl to fileinto anything other than inbox.
That didn't work unfortunately.
Thanks
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsub
You need to have "anyone p" acl to fileinto anything other than inbox.
Bron.
On Mon, May 23, 2016, at 21:52, Sunny via Info-cyrus wrote:
> Hi,
>
> I'm seeing the following error logs with some users sieve filtering
> May 23 11:41:31 imap02 lmtpunix[26005]: sieve
Hi,
I'm seeing the following error logs with some users sieve filtering
May 23 11:41:31 imap02 lmtpunix[26005]: sieve runtime error for test2 id
<5742de5a.3040...@org.ac.uk>: Fileinto: Permission denied
Essentially emails are not being put into the specific folders.
Their
/usr/bin/sendmail.sendmail didn't have the correct group or permissions
needed for certain sieve commands such as redirect and vacation
correct permissions - note: group execute needs sticky bit
ls -ls /usr/sbin/sendmail
-rwxr-sr-x 1 root smmsp 833512 Mar 7 13:40 sendmail.sendmail
Cyrus H
Hi,
I'm getting issues with sieve unable to redirect messages for any user
with redirect set.
Any pointers to solve this issue?
Mar 7 11:52:15 imap02 lmtpunix[8635]: sieve runtime error for ssntest2
id <56dd69d8.3040...@ebi.ac.uk>: Redirect: Sendmail process terminated
nor
Master has:
commit 6ef874319ecd98700e682ef30fcad5245ddfdb32 Author: Bron Gondwana
Date: Wed Oct 22 14:51:24 2014 -0400
sync_client: do ALL mailboxes, not just all users, for -A flag
It should be pretty cherry-pickable back to 2.5 I would imagine.
Bron.
On Thu, Mar 3, 2016, at 09:17, Artyom
Hi,
When using the “-A” flag (sync all users) no non-user mailboxes are synced.
As the man page imapd.conf(5) notes, ”... this could be considered a bug
and maybe it should do those mailboxes independently.”
Source: https://cyrusimap.org/imap/admin/sop/replication.html
But how in this case restor
Hello.
I configured IMAP rolling replication from master to slave as was
described in https://cyrusimap.org/imap/admin/sop/replication.html And
everything was fine. Until some strange records appear into logs. Here
is one of them.
Mar 2 04:48:55 hostname cyrus/sync_client[725]: MAILBOX rece
on CentOS 7.2.1511 for appx. 20
mailboxes. I get the following messages every 10-12 days.
imaps TLS negotiation failed: [ip address of a client]
Fatal error: tls_start_servertls() failed
Although cyrus-imapd, saslauthd are still running after this error,
login credentials are not accepted. As I
of a client]
Fatal error: tls_start_servertls() failed
Although cyrus-imapd, saslauthd are still running after this error,
login credentials are not accepted. As I don't know where the problem
is, restart the server fixes the problem, well for another 10-12 days.
I would appreciate any hint yo
On 02/14/2016 02:46 AM, Mufit Eribol via Info-cyrus wrote:
Hi All,
I am running cyrus-imapd-2.4.17 on CentOS 7.2.1511 for appx. 20
mailboxes. I get the following messages every 10-12 days.
imaps TLS negotiation failed: [ip address of a client]
Fatal error: tls_start_servertls() failed
On 12/02/2016 00:34, Patrick Boutilier via Info-cyrus wrote:
It fits because your Cyrus is configured to use BerkleyDB for some 9or
all) of the databases.
You should not have to stop Cyrus. Running this command (with proper -h
location) should show you what log files are no longer used:
db_arch
Hi All,
I am running cyrus-imapd-2.4.17 on CentOS 7.2.1511 for appx. 20
mailboxes. I get the following messages every 10-12 days.
imaps TLS negotiation failed: [ip address of a client]
Fatal error: tls_start_servertls() failed
Although cyrus-imapd, saslauthd are still running after this
1 - 100 of 1265 matches
Mail list logo
