Hi Paul,
Yeah that is fine, I understand you completely but as this software is
just as different as others in a good way I would like to keep it
running and hope we can make more people enthousiastic about it and go
futher from there. I'm more active on Github now too, so that's nice
and i see th
On 10-01-16 21:58, Matt. wrote:
> Good to see you back Paul!
Just don't expect me to put in the 1000+ hours per year as I did before
I took my current job.
There are some interesting merge-request on github I will start adding
though. Nice!
> I will compile some new packages very soon for 3.1
Good to see you back Paul!
I will compile some new packages very soon for 3.1.17 as my new
installs won't start DBmail on Ubuntu 14.04, one existing one still
works, and there is no logging about it.
Or is it advised to move to 3.2.x ?
I will report back!
2016-01-10 20:10 GMT+01:00 Reindl Hara
welcome back - will give it a try ASAP
did not happen ot for a long itme, somehow unpredictablem but when it
happend than very often in a short timeframe
thanks!
Am 10.01.2016 um 20:07 schrieb Paul J Stevens:
There is only one place where this is called.
I've just pushed a fix to prevent th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There is only one place where this is called.
I've just pushed a fix to prevent this, on dbmail_3_1, dbmail_3_2 and
master branches.
On 29-10-15 13:36, Reindl Harald wrote:
> DAMNED!
>
> dbmail-imapd: dm_string.c:161: p_string_erase: Assertion `
I don't have great C skills (well, really few actually), but if he's too
busy I'm available to just test, merge and push out incoming patches to
the main tree.
Plus I have some developers in my company who can back-end me in doing
that.
We're a bit struck right now and have at least two diff
OK, I didn't see that happening on 3.1.17 as far as I know, but I need
to investigate that. IMAP can crash too easy on it's auth backend, it
doesn't even try 5 times as the code says.
I have dropped Paul an email about a week ago with the question what
we can expect and what we can do to keep this
It happens with 3.2.3.
You see it coming and going because it's related to some malformed
messages, when a malformed message comes in every time an user try to
fetch it dbmail crashes. As time passes by the malformed message usually
get deleted by the user or just "goes down" in the download l
Am 30.10.2015 um 03:23 schrieb Reindl Harald:
>
>
> Am 30.10.2015 um 02:57 schrieb Curtis Maurand:
>> I had the same problem. It went away when I upgraded to 3.2.3
>
> fine, that's no excuse don't fix it for 3.1.x
>
> i was alpha/beta tester for 3.0/3.1 and as currently Paul seems not to
> be
Am 30.10.2015 um 02:57 schrieb Curtis Maurand:
I had the same problem. It went away when I upgraded to 3.2.3
fine, that's no excuse don't fix it for 3.1.x
i was alpha/beta tester for 3.0/3.1 and as currently Paul seems not to
be ctive i won't play betatester for 3.2.x on production servers
I had the same problem. It went away when I upgraded to 3.2.3
On Thu, Oct 29, 2015 at 8:46 PM, Reindl Harald
wrote:
> no idea - sometimes not for days, sometimes multiple times within a few
> minutes resulting in dbmail-imapd crashing with 3.1.17 and it makes me
> really tired
>
> Am 30.10.2015
no idea - sometimes not for days, sometimes multiple times within a few
minutes resulting in dbmail-imapd crashing with 3.1.17 and it makes me
really tired
Am 30.10.2015 um 01:18 schrieb Matt.:
When does this happen Harald ?
2015-10-29 13:36 GMT+01:00 Reindl Harald :
DAMNED!
dbmail-imapd: d
When does this happen Harald ?
2015-10-29 13:36 GMT+01:00 Reindl Harald :
> DAMNED!
>
> dbmail-imapd: dm_string.c:161: p_string_erase: Assertion `pos + len <=
> S->used' failed.
>
>
>
> ___
> DBmail mailing list
> DBmail@dbmail.org
> http://mailman.fastx
DAMNED!
dbmail-imapd: dm_string.c:161: p_string_erase: Assertion `pos + len <=
S->used' failed.
signature.asc
Description: OpenPGP digital signature
___
DBmail mailing list
DBmail@dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
i just hate it, sometimes a few crashes, sometimes no one for a few days
and sometimes crashes multiple times each hour
dbmail-imapd: dm_string.c:161: p_string_erase: Assertion `pos + len <=
S->used' failed.
dbmail-imapd: dm_string.c:161: p_string_erase: Assertion `pos + len <=
S->used' failed
Hi All,
I'm encountering the same issue and the problem seems to be the function
"p_string_erase" in "dm_string.c"
The assertion around line 160 fails because the 'len' is bigger than the
S->used (pos is always 0 as far as i've seen).
I'm assuming this is because 'len' represents the line-c
that's not funny and leads in multiple crashes and systemd-restart of
dbmail-imapd for two days now and it appears to be triggered by specific
clients because it was away for many hours and started again in the
evening every few minutes
Sep 27 11:09:46 mail systemd: dbmail-imapd.service: main
We're having the same problem here.
FreeBSD 10.x, dbmail 3.2.3, MySQL 5.6...
Il 28/05/15 12:41, Peter Milesson ha scritto:
Hi folks,
I've got a problem that dbmail-imapd stops working a few times a day.
It started a few months ago about once in a while, but now occurs more
and more often.
Hi folks,
I've got a problem that dbmail-imapd stops working a few times a day. It
started a few months ago about once in a while, but now occurs more and
more often.
The only trace it leaves behind is in /var/log/dbmail.err:
dbmail-imapd: dm_string.c:160: p_string_erase: Assertion `pos + le
Hey, we're already three different installation having the same problem
now!
Pa!!! :-)
Il 2015-01-11 10:39 Marek ?ernocký ha scritto:
Daemon dbmail-imapd on my server crashes with this message in system
log:
kernel: pid 78148 (dbmail-imapd), uid 65534: exited on signal 11
OS is FreeB
Daemon dbmail-imapd on my server crashes with this message in system
log:
kernel: pid 78148 (dbmail-imapd), uid 65534: exited on signal 11
OS is FreeBSD 9.2. It comes with upgrade to 3.2.1 (from 3.0.2) with
FreeBSD ports. I tried to compile 3.2.2 from sources and result is the
same.
Unfortunatel
what makes me wonder for a longer time is that stop dbmail-imapd takes way
too long and to prevent that be problematic i told systemd if it is not
down 5 seconds after SIGTERM to send a SIGKILL
that below is my home-machine, i am the only user, so unlikely high connection
load and typically that h
I would say the Imap connection is for the copy in the sent folder
Ursprüngliche Nachricht
Von: Paul J Stevens
Gesendet: 16. Februar 2014 10:52:27 MEZ
An: DBMail mailinglist
Betreff: Re: [Dbmail] dbmail-imapd and Acrobat Pro XI
On 16-02-14 09:42, Ralph Ballier wrote
On 16-02-14 09:42, Ralph Ballier wrote:
> Hello,
>
> we use dbmail 2.2.18. It works well so far. But now I've been trying to send
> mail with the mechanism of Acrobat Pro XI a PDF file directly from the
> program. This is not possible.
> In dbmail.err gives the following message (dbmail-imapd -v
Hello,
we use dbmail 2.2.18. It works well so far. But now I've been trying to send
mail with the mechanism of Acrobat Pro XI a PDF file directly from the program.
This is not possible.
In dbmail.err gives the following message (dbmail-imapd -vv):
Feb 15 22:09:05 ods3 dbmail-imapd[27371]: Info
On 06-11-13 13:08, Reindl Harald wrote:
> not sure if strace to binaries without debuginfos could help in any
> way, we are speaking from production environment :-(
No need to increase logging, or including debug symbols. Strace will
show the system calls executed. That will give me a clear indic
Am 06.11.2013 08:09, schrieb Paul J Stevens:
> On 01-11-13 13:58, Reindl Harald wrote:
>> latest "news" on that:
>>
>> as woke up dbmail-imapd consumed all cores with 100% CPU
>> however, from the users side it was still normally working
>> so this affects not the whole daemon, only specific thre
On 01-11-13 13:58, Reindl Harald wrote:
> latest "news" on that:
>
> as woke up dbmail-imapd consumed all cores with 100% CPU
> however, from the users side it was still normally working
> so this affects not the whole daemon, only specific threads
>
> after SIGKILL and restart it until now it di
On 01-11-13 04:15, Reindl Harald wrote:
> hmpf - again one thread with 100%
>
> is there a chance to get the coberity-fixes which where done
> in HEAD also in the dbmail-3.1 tree - i have the strong feeling
> there is a hidden bug and i can't setup the production machine
> for debug-logging
No. T
dbmail-imapd is after some days of peace again
spinning with 100% CPU on all cores and consuming
11000 MHz this time
something went terrible wrong in 3.1 because this
did happen with 3.0.2 once a month and not that
regulary
the machine has enough power to appear like idle
but the alarm-mails from
latest "news" on that:
as woke up dbmail-imapd consumed all cores with 100% CPU
however, from the users side it was still normally working
so this affects not the whole daemon, only specific threads
after SIGKILL and restart it until now it did not happen again
active (running) since Fr 2013-11-0
hmpf - again one thread with 100%
is there a chance to get the coberity-fixes which where done
in HEAD also in the dbmail-3.1 tree - i have the strong feeling
there is a hidden bug and i can't setup the production machine
for debug-logging
maybe some idiot out there is triggering this intentional
maybe one helpful information:
on the production machine dbmail-imapd usually is not interested
in SIGTERM and can only be killed with SIGKILL, indendent of the
spin-locks, that's "normal" behavior here after some days production
load
Am 01.11.2013 02:42, schrieb Reindl Harald:
> hm - the last fe
hm - the last few hours 5a9d6ba3645a235531ea32b2576fc21e2eb7b860 tries
repeatly to benchmark the production server with high CPU load
* the service works normally and is responsible
* TLS not configured
* proxy in front
* nothing special in the maillog, no user load
* looks like the threads spinni
hmm - recently dbmail-imapd crashed with out-of-memory
dbmail-abac5b58c94f270e534320ff264054bc79530b78
wondering that it did not happen the last days and a few hours after
update to kernel 3.10.13 dbmail sucked that much memory while the
last commits promised to fix two leaks, i guess there are st
On 2013-09-09 10:08, Paul J Stevens wrote:
On 09-09-13 08:27, Thomas Raschbacher wrote:
write(13, "Q", 1) = -1 EAGAIN (Resource
temporarily unavailable)
read(25, 0x1843e70, 11) = -1 EAGAIN (Resource
temporarily unavailable)
Thomas,
could you please test
On 09-09-13 13:43, Harald Leithner wrote:
> this could be normal, but strange normal this high cpu usage is for a
> short time. Now its much longer.
Looks ok to me. Using locks will result in higher CPU, but hopefully no
more spin-locks.
Must find a better inter-thread notification mechanism tha
On 09-09-13 15:41, Harald Leithner wrote:
> does this mean I have 50 user connections running?
>
No. Some of them will be database connection, but most indeed will be
client-connections.
Use netstat, not lsof to find out which is which:
netstat -anlp|grep `pidof dbmail-imapd`
--
___
does this mean I have 50 user connections running?
l-wx-- 1 root root 64 Sep 9 15:38 0 -> /var/log/dbmail/dbmail.log
l-wx-- 1 root root 64 Sep 9 15:38 1 -> /var/log/dbmail/dbmail-imap.log
lrwx-- 1 root root 64 Sep 9 15:38 10 -> anon_inode:[eventfd]
lr-x-- 1 root root 64 Sep 9
you could have a look at what those file handles are (pipe, file,
socket,..)
e.g. I get this for imapd:
ls -l /proc//fd
insgesamt 0
lr-x-- 1 root root 64 9. Sep 14:06 0 -> /dev/null
l-wx-- 1 root root 64 9. Sep 14:06 1 -> /var/log/dbmail.log
lrwx-- 1 root root 64 9. Sep 14:06 10
I'm not sure but it seam to need much more cpu time now.
also pop3d at 100% with:
write(16, "gkJCTwvZGljdD4KCQk8L2Fy\r\ncmF5Pgo"..., 262143) = -1 EAGAIN
(Resource temporarily unavailable)
imapd at 200% with:
write(13, "Q", 1) = 1
write(34, "\27\3\1\0 \247\310\373\364\20
On 2013-09-09 11:18, Reindl Harald wrote:
Am 09.09.2013 11:22, schrieb Thomas Raschbacher:
On 2013-09-09 11:12, Reindl Harald wrote:
Am 09.09.2013 11:16, schrieb Thomas Raschbacher:
On 2013-09-09 10:08, Paul J Stevens wrote:
On 09-09-13 08:27, Thomas Raschbacher wrote:
write(13, "Q", 1)
Am 09.09.2013 11:22, schrieb Thomas Raschbacher:
> On 2013-09-09 11:12, Reindl Harald wrote:
>> Am 09.09.2013 11:16, schrieb Thomas Raschbacher:
>>> On 2013-09-09 10:08, Paul J Stevens wrote:
On 09-09-13 08:27, Thomas Raschbacher wrote:
>> write(13, "Q", 1) = -1
On 2013-09-09 11:12, Reindl Harald wrote:
Am 09.09.2013 11:16, schrieb Thomas Raschbacher:
On 2013-09-09 10:08, Paul J Stevens wrote:
On 09-09-13 08:27, Thomas Raschbacher wrote:
write(13, "Q", 1) = -1 EAGAIN (Resource
temporarily unavailable)
read(25, 0x1843e70, 11)
Am 09.09.2013 11:16, schrieb Thomas Raschbacher:
> On 2013-09-09 10:08, Paul J Stevens wrote:
>> On 09-09-13 08:27, Thomas Raschbacher wrote:
>>
write(13, "Q", 1) = -1 EAGAIN (Resource
temporarily unavailable)
read(25, 0x1843e70, 11) = -1 EAGAI
On 2013-09-09 10:08, Paul J Stevens wrote:
On 09-09-13 08:27, Thomas Raschbacher wrote:
write(13, "Q", 1) = -1 EAGAIN (Resource
temporarily unavailable)
read(25, 0x1843e70, 11) = -1 EAGAIN (Resource
temporarily unavailable)
Thomas,
could you please test
Am 09.09.2013 10:08, schrieb Paul J Stevens:
> On 09-09-13 08:27, Thomas Raschbacher wrote:
>
>>> write(13, "Q", 1) = -1 EAGAIN (Resource
>>> temporarily unavailable)
>>> read(25, 0x1843e70, 11) = -1 EAGAIN (Resource
>>> temporarily unavailable)
>
> Thomas,
On 09-09-13 08:27, Thomas Raschbacher wrote:
>> write(13, "Q", 1) = -1 EAGAIN (Resource
>> temporarily unavailable)
>> read(25, 0x1843e70, 11) = -1 EAGAIN (Resource
>> temporarily unavailable)
Thomas,
could you please test 4c23432cc270554557f9e130331214d8116
On 2013-09-09 08:10, Thomas Raschbacher wrote:
hi.
It happened again at ~ 03:00 this morning.
I did save a proper core file + more strace this time:
strace:
...
write(13, "Q", 1) = -1 EAGAIN (Resource
temporarily unavailable)
read(25, 0x1843e70, 11) = -1
hi.
It happened again at ~ 03:00 this morning.
I did save a proper core file + more strace this time:
strace:
...
write(13, "Q", 1) = -1 EAGAIN (Resource
temporarily unavailable)
read(25, 0x1843e70, 11) = -1 EAGAIN (Resource
temporarily unavailable)
...
On 09/05/2013 04:10 PM, Thomas Raschbacher wrote:
> write(13, "Q", 1) = -1 EAGAIN (Resource
This is the one I wanted to see.
--
Paul J Stevenspjstevns @ gmail, twitter, skype, linkedin
* Premium
On 2013-09-05 13:53, Paul J Stevens wrote:
On 09/05/2013 01:18 PM, Thomas Raschbacher wrote:
strace shows exactly the same again.
Sure?? Please show me.
I don't have a lot anymore but basically this again over and over:
read(4, 0x1efbca0, 11) = -1 EAGAIN (Resource
temporar
On 09/05/2013 01:18 PM, Thomas Raschbacher wrote:
> strace shows exactly the same again.
Sure?? Please show me.
--
Paul J Stevenspjstevns @ gmail, twitter, skype, linkedin
* Premium Hosting Services and Web Applicatio
still the same problem with 3.1.4
strace shows exactly the same again.
Anything I can do to help you debug this selfpipe problem?
On 2013-08-28 20:58, Thomas Raschbacher wrote:
FYI, this just happened again a few minutes ago.
I do have a daily cron script that does restart dbmail daemons, even
On 09/03/2013 05:27 PM, Ronald Moesbergen wrote:
> Is there anything I can do to help
> debug this? I'm running on Ubuntu 12.04, version 3.1.4, gmime 2.6.7-1.
I use:
G_SLICE=all valgrind \
--leak-check=full \
--suppressions=contrib/dbmail.supp
--log-file=/tmp/vg.log src/dbmail-imapd -D
ke
Hi,
I've been testing dbmail for quite some time now to see if it's usable in
production. The latest version (3.1.4) seems to be quite OK, except for one
issue: it seems to leak pretty large amounts of memory. I have a test
environment that can simulatie some heavy mail traffic being delivered via
On 09/03/2013 06:27 PM, Ronald Moesbergen wrote:
Is there anything I can do to help debug this? I'm
running on Ubuntu 12.04, version 3.1.4, gmime 2.6.7-1.
Thanks,
Ronald.
That would be great to have some king of a wiki page like Asterisk have:
https://wiki.asterisk.org/wiki/display/AST/Valgri
FYI, this just happened again a few minutes ago.
I do have a daily cron script that does restart dbmail daemons, even so
dbmail-imapd does crash
occasionally. (afaik only my and my wife's phone were even checking
mails atm)
On 2013-08-21 13:42, Thomas Raschbacher wrote:
On 2013-08-21 12:03, P
On 2013-08-21 12:03, Paul J Stevens wrote:
On 21-08-13 10:48, Thomas Raschbacher wrote:
Hi.
I just had a problem as well where dbmail-imapd died on me.
Since It is just my server I did take a bit of time to create memory
dumps and core files
strace showed me this (again and again so some loop)
On 21-08-13 10:48, Thomas Raschbacher wrote:
> Hi.
>
> I just had a problem as well where dbmail-imapd died on me.
> Since It is just my server I did take a bit of time to create memory
> dumps and core files
>
> strace showed me this (again and again so some loop):
> ...
> read(4, 0x1efbca0, 11)
Hi.
I just had a problem as well where dbmail-imapd died on me.
Since It is just my server I did take a bit of time to create memory
dumps and core files
strace showed me this (again and again so some loop):
...
read(4, 0x1efbca0, 11) = -1 EAGAIN (Resource
temporarily unavail
On 07/12/2012 11:05 AM, DIXLOR wrote:
> Debian 6.0.5 x86_64
> DBMail version 2.2.11
2.2.11 was released a very long time ago (feb 2009)
Please try a later version.
--
Paul J Stevenspjstevns @ gmail, twitter, skype, linke
Debian 6.0.5 x86_64
DBMail version 2.2.11
---
[1509178.399342] dbmail-imapd[17668]: segfault at 38 ip 7effd4ed3bb4 sp
7fff8722a600 error 4 in libdbmail.so.0.0.0[7effd4ec1000+4a000]
[1509272.371177] dbmail-imapd[17702]: segfault at 38 ip 7effd4ed3bb4 sp
7fff8722a600 error 4 in l
orted this to Paul - I'm sure he's looking into it.
Regards to All, Lou Picciano
- Original Message -
From: "Sergey Spiridonov"
To: dbmail@dbmail.org
Cc: "dbmail-post gmame org"
Sent: Monday, October 4, 2010 5:27:05 AM
Subject: Re: [Dbmail] dbmai
Hi Marcus
On 08/02/2010 11:13 PM, Markus Alexander Kuppe wrote:
>> I have here Debian Lenny 32 bit with dbmail-mysql 2.2.10-1+b1 and 3
>> networks.
>
> With Lenny 64bit/dbmail 2.2.16-1 I see the same issue with occasional hangs.
I added cronjob which restarts dbmail after 3 days. This helps.
--
Hi Marcus
On 08/02/2010 11:13 PM, Markus Alexander Kuppe wrote:
>> I have here Debian Lenny 32 bit with dbmail-mysql 2.2.10-1+b1 and 3
>> networks.
>
> With Lenny 64bit/dbmail 2.2.16-1 I see the same issue with occasional hangs.
I added cronjob which restarts dbmail after 3 days. This helps.
--
On 09/01/2010 07:54 AM, Ralph Ballier wrote:
> Harald,
>
> thanks for your hints. But see below...
>
> ursprüngliche Nachricht-
> Von: "Reindl Harald" h.rei...@thelounge.net
> An: "DBMail mailinglist" dbmail@dbmail.org
> Datum: Tue, 31 Aug 2010 22:58:41 +0200
> --
Harald,
thanks for your hints. But see below...
ursprüngliche Nachricht-
Von: "Reindl Harald" h.rei...@thelounge.net
An: "DBMail mailinglist" dbmail@dbmail.org
Datum: Tue, 31 Aug 2010 22:58:41 +0200
-
> It is, gl
It is, globally or for every single service
[LMTP]
BINDIP= 127.0.0.1
PORT = 24
TIMEOUT = 180
MAXCHILDREN = 40
NCHILDREN = 4
MINSPARECHILDREN = 4
MAXSPARECHILDREN = 10
BANNER= LMTP-Service
[POP]
BINDIP
ursprüngliche Nachricht-
Von: "Reindl Harald" h.rei...@thelounge.net
An: "DBMail mailinglist" dbmail@dbmail.org
Datum: Sat, 28 Aug 2010 11:07:40 +0200
-
>
> Am 28.08.2010 10:47, schrieb raba34:
>> I mean, that
Am 28.08.2010 11:25, schrieb raba34:
>
> This is an other line in the configuration file. I have set:
>
> listen_address 127.0.0.1
>
> but this is no port.
Port is still 143
We are using dovecot as proxy for handling more auth-mechanisms
as dbmail supports and sasl-ath for postfix
dbmail is l
This is an other line in the configuration file. I have set:
listen_address 127.0.0.1
but this is no port.
Ralph
Bugzilla from h.rei...@thelounge.net wrote:
>
>
> Am 28.08.2010 10:47, schrieb raba34:
>> I mean, that the same port is not possible. Therefore I had changed
>> server_port to 80
Am 28.08.2010 10:47, schrieb raba34:
> I mean, that the same port is not possible. Therefore I had changed
> server_port to 8085. Is that ok so?
you must configure dbmail-imapd to listen only on 127.0.0.1
the sense of a proxy is that nobody has to know about him :-)
signature.asc
Description:
Hello,
I don't know if this is a question for dbmail-imapd, because the real cause
are perhaps somewhere else.
I use ProfiMail as mail client on HTC HD2 . Mostly some seconds the mail
transfer works, but then it disconnects and I see the message "Error!
Connection terminated by server". After th
Paul,
I have installed imapproxy and I mean, it's better. I can not say it
exactly, because my access providers has now problems with his own servers.
In the default imapproxy.conf I find this both lines
listen_port 143
server_port 143
I mean, that the same port is not possible. Therefore I h
Ralph,
I suspect this is unrelated to the error message you posted earlier.
You might be running into connection limits where too many connections
are coming in too fast. Webmail systems typically trigger many short
lived connections in a rapid succession.
Users of webmail systems talking to db
Paul J Stevens wrote:
>
> On 08/22/2010 11:37 AM, raba34 wrote:
>>
>> Hello,
>>
>> I use dbmail-imapd 2.2.16 and have the same problem: imapd occasionally
>> times out.
>
> You mean it stops accepting connections, or what?
>
>
For example: I click in eGroupware at button "eMail". Then I
On 08/22/2010 11:37 AM, raba34 wrote:
>
> Hello,
>
> I use dbmail-imapd 2.2.16 and have the same problem: imapd occasionally
> times out.
You mean it stops accepting connections, or what?
>
> In dbmail.err I found this line:
>
> dbmail-imapd[23122]: Error:[imapsession]
> dbmail-imapsession.c
Hello,
I use dbmail-imapd 2.2.16 and have the same problem: imapd occasionally
times out.
In dbmail.err I found this line:
dbmail-imapd[23122]: Error:[imapsession]
dbmail-imapsession.c,dbmail_imap_session_printf(+1518): write to client
socket failed
and I have to restart imapd.
This happens
On 08/03/2010 10:39 PM, Lou Picciano wrote:
> Name | Owner| Encoding | Collation |
> Ctype| Access privileges
> -++--+-+-+-
> | | UTF8 | en_US.UTF-8 |
> en_US.UTF-
Paul,
Some info you requested (all of our databases are UTF8):
Verification of encoding:
Name | Owner | Encoding | Collation | Ctype | Access privileges
-++--+-+-+-
| | UTF8 | en_US.UTF-8 | en_US.UTF-8 | (etc)
Sergey Spiridonov gmail.com> writes:
>
> Hi
>
> I have here Debian Lenny 32 bit with dbmail-mysql 2.2.10-1+b1 and 3
> networks.
With Lenny 64bit/dbmail 2.2.16-1 I see the same issue with occasional hangs. If
necessary I can provide debug/trace logs too, but a quick look at the logs
didn't sho
Hi
I have here Debian Lenny 32 bit with dbmail-mysql 2.2.10-1+b1 and 3
networks.
From time to time, but mostly on weekend imapd stops working if a
following way:
If I telnet to it, for example
$ telnet dbmailhostname imap
It does not print as usual message "* OK dbmail imap (protocol versio
Hello,
thank you very much! The patch below works!!
Ralph
ursprüngliche Nachricht-
Von: "Paul J Stevens"
An: "DBMail mailinglist" dbmail@dbmail.org
Datum: Wed, 14 Apr 2010 23:04:44 +0200
-
>
> Someone posted a
Someone posted a patch that might fix this (haven't tested). Afaik, this
problem only occurs if you enable ipv6. It might help to specify:
bind=0.0.0.0
rather than
bind=*
in dbmail.conf. But it may well also be architecture dependent.
So try the patch
http://dbmail.org/mantis/view.php?id=84
Hello,
in dbmail-2.2.14 and dbmail-2.2.15 dbmail-imapd don't work. I cannot get a
connection from client.
In file messages I find the error message
Apr 11 17:45:19 ods3 kernel: lt-dbmail-imapd[30640]: segfault at 100017b ip
b78b1ab0 sp bfb980ec error 4 in libauth_ldap.so.0.0.0[b78b+8000]
Ca
We have detected the same problem and behaviour with POP3 and IMAP servers on
RHEL5 i386.
Looks like the cause of stack smashing is too small size returned by
sizeof(struct sockaddr_storage) function in case if IPv6 protocol is enabled.
Our quick fix patch which has solved the problem:
--- dbmai
Paul J Stevens nfg.nl> writes:
>
> nick ivanov wrote:
> > Hi all.
> >
> > I have dbmail 2.2.10-1 installed on Debian lenny. Mysql used as backend and
> > running on localhost. Dbmail-imapd is unstable. I set TRACE_SYSLOG = 4 and
> > restart service. Now I see errors in the /var/log/dbmail/dbma
nick ivanov wrote:
> Hi all.
>
> I have dbmail 2.2.10-1 installed on Debian lenny. Mysql used as backend and
> running on localhost. Dbmail-imapd is unstable. I set TRACE_SYSLOG = 4 and
> restart service. Now I see errors in the /var/log/dbmail/dbmail.err:
>
> Mar 31 23:29:28 mail01.pe1 dbmail-i
Hi all.
I have dbmail 2.2.10-1 installed on Debian lenny. Mysql used as backend and
running on localhost. Dbmail-imapd is unstable. I set TRACE_SYSLOG = 4 and
restart service. Now I see errors in the /var/log/dbmail/dbmail.err:
Mar 31 23:29:28 mail01.pe1 dbmail-imapd[31843]: Error:[imapsession]
On 03/25/2010 02:51 AM, Paul J Stevens wrote:
> Could someone please file a bug for this one, so I won't forget to deal
> with this when I get around to it. Thanks.
Bug 842 filed based on Jan Marc Hoffmann's original report.
___
DBmail mailing list
DBma
Could someone please file a bug for this one, so I won't forget to deal
with this when I get around to it. Thanks.
Bernard Johnson wrote:
> On 03/20/2010 09:16 AM, Jan Marc Hoffmann wrote:
>> The problem seems to be in the usermap related code.
>>
>> http://git.dbmail.eu/cgit/cgit.cgi/paul/dbmail
On 03/20/2010 09:16 AM, Jan Marc Hoffmann wrote:
> The problem seems to be in the usermap related code.
>
> http://git.dbmail.eu/cgit/cgit.cgi/paul/dbmail/commit/?id=0c08dd0a56d7326b99b19af2a95b3b5cacf55524
>
> This function causes the problem. The stack smash isn't fixed in trunk.
I'd say it's d
This patch does only work partly. It works internally but wont display
mail addresses with dbmail-users -l.
http://www.dbmail.org/mantis/view.php?id=742
greetings
Jan
On 20.03.2010 16:16, Jan Marc Hoffmann wrote:
> The problem seems to be in the usermap related code.
>
> http://git.dbmail.eu/cg
The problem seems to be in the usermap related code.
http://git.dbmail.eu/cgit/cgit.cgi/paul/dbmail/commit/?id=0c08dd0a56d7326b99b19af2a95b3b5cacf55524
This function causes the problem. The stack smash isn't fixed in trunk.
And there is an additional bug in trunk:
In db.c the query:
snprintf(qu
Hey List,
I compiled the latest 2.2 stable (and trunk) which worked fine. But as
soon as I connect with an imap client, the imapd daemon crashes. The
packaged version 2.2.9 didnt crash but threw tons of TO_DATE('2010-03-03
00:00:00','-MM-DD') SQL errors.
Any idea?
LOG:
http://pastebin.com/2A
rc1 was released yesterday, as announced on this list.
Michael Monnerie wrote:
> Hi Paul, any news on this?
>
> On Montag, 26. November 2007 Michael Monnerie wrote:
>> On Donnerstag, 22. November 2007 10:59 Paul J Stevens wrote:
>>> revision 2846 fixes this.
>>> I'll release 2.2.8-rc1 asap.
>> Hi
Hi Paul, any news on this?
On Montag, 26. November 2007 Michael Monnerie wrote:
> On Donnerstag, 22. November 2007 10:59 Paul J Stevens wrote:
> > revision 2846 fixes this.
> > I'll release 2.2.8-rc1 asap.
>
> Hi Paul, thanks for the fix(es). Should I got to svn #2846, or is
> 2.2.8-rc1 on the way
On Donnerstag, 22. November 2007 10:59 Paul J Stevens wrote:
> revision 2846 fixes this.
> I'll release 2.2.8-rc1 asap.
Hi Paul, thanks for the fix(es). Should I got to svn #2846, or is
2.2.8-rc1 on the way? I'd love to have the fix before the first
problem, as our service is vital to some peopl
umask wrote:
> a005 FETCH -14:1 (UID FLAGS)
This actually pointed me to a whole class of possible problems in the
codebase.
Thanks for reproducing this problem.
--
Paul Stevens paul at nfg
1 - 100 of 205 matches
Mail list logo
