Am 2015-11-03 um 09:40 schrieb Stefan G. Weichinger via Info-cyrus:
> I run with disabled sievedir now and try to fix the few users with
> problematic scripts.
I looked through them and rm-ed them all ;) (bofh)
They were outdated and inactive anyway.
Cyrus Home Page
Am 2015-11-02 um 23:01 schrieb Ken Murchison:
> I haven't used it in a long time but you could try tools/masssievec in
> the Cyrus distro
As mentioned that script fails for some users as well, maybe even for
the same reason than lmtpd at runtime.
How could I debug these scripts?
If I cd into th
Am 2015-11-02 um 23:19 schrieb Stefan G. Weichinger via Info-cyrus:
> Am 2015-11-02 um 23:01 schrieb Ken Murchison:
>
>> I haven't used it in a long time but you could try tools/masssievec in
>> the Cyrus distro
>
> digging ...
btw:
masssievec fails as wel
Am 2015-11-02 um 23:01 schrieb Ken Murchison:
> I haven't used it in a long time but you could try tools/masssievec in
> the Cyrus distro
digging ...
aside from that: should that one be filed as a possible bug somewhere?
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http:/
Am 2015-11-02 um 22:53 schrieb Ken Murchison:
> You could try changing the sievedir option in imapd.conf to something
> other than where your sieve scripts currently reside.
more than 10 hrs of fiddling ... and now mails are getting delivered.
thank you thank you thank you!
mailq empty now. cool
Am 2015-11-02 um 22:47 schrieb Ken Murchison:
> lmtpd is crashing inside of the sieve code. It looks like its trying to
> compile a regular expression that appears in the recipient's sieve script.
>
> I don't know if this is a bug, a bad sieve script, or if your version of
> Cyrus wasn't compile
Am 2015-11-02 um 22:38 schrieb Ken Murchison:
> gdb /usr/local/cyrus/lmtpd /tmo/core.XXX (use proper locations)
>
> At the (gdb) prompt run the backtrace command (bt)
>
> It should give you info that you can post here.
tmp # gdb /usr/lib64/cyrus/lmtpd core.32682
Using host libthread_db libra
Am 2015-11-02 um 22:28 schrieb Ken Murchison:
> You shouldn't have to run master in gdb.
>
> Do something like this:
>
> cd /tmp
> ulimit -c unlimited
> /usr/lib64/cyrus/master &
>
> Hopefully any lmtpd cores will end up in /tmp
they do! how to interpret them?
They are ~2megs in size so I don't
Am 2015-11-02 um 21:45 schrieb Ken Murchison:
> On 11/02/2015 03:34 PM, Stefan G. Weichinger wrote:
>> Am 2015-11-02 um 21:26 schrieb Ken Murchison:
>>
>>> Can you get a backtrace from a lmtpd core dump?
>> if you tell me what to do ;)
>> I am not that experienced in doing that, sorry.
>
> Is lmt
Am 2015-11-02 um 21:34 schrieb Stefan G. Weichinger via Info-cyrus:
> Am 2015-11-02 um 21:26 schrieb Ken Murchison:
>
>> Can you get a backtrace from a lmtpd core dump?
>
> if you tell me what to do ;)
> I am not that experienced in doing that, sorry.
I installed gd
Am 2015-11-02 um 21:26 schrieb Ken Murchison:
> Can you get a backtrace from a lmtpd core dump?
if you tell me what to do ;)
I am not that experienced in doing that, sorry.
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To
Am 2015-11-02 um 20:06 schrieb Dave McMurtrie via Info-cyrus:
> On Mon, 2015-11-02 at 19:11 +0100, Stefan G. Weichinger via Info-cyrus
> wrote:
>> Am 2015-11-02 um 14:06 schrieb Stefan G. Weichinger via Info-cyrus:
>>>
>>> gentoo server here,
>>>
>>>
Am 2015-11-02 um 14:06 schrieb Stefan G. Weichinger via Info-cyrus:
>
> gentoo server here,
>
> yesterday I upgraded cyrus-imapd from 2.4.x to 2.5.6
> Alongside I reinstalled glibc, cyrus-sasl, postfix ... and corrected all
> the new config options etc in cyrus.conf etc
>
gentoo server here,
yesterday I upgraded cyrus-imapd from 2.4.x to 2.5.6
Alongside I reinstalled glibc, cyrus-sasl, postfix ... and corrected all
the new config options etc in cyrus.conf etc
I now see problems with lmtpd.
# cyrus.conf
lmtpunixcmd="lmtpd" listen="/var/imap/socket/lmtp" p
14 matches
Mail list logo
