On Dienstag 15 September 2009 Jorge Bastos wrote:
IMAPD crashed, and when I go to start him this happen.
Then the diff seems that the TCP connections are not closed on crash in
the one version, while the other does. Or the crash happens in a
different path, leaving the connections open.
On Dienstag 15 September 2009 Jorge Bastos wrote:
IMAPD crashed, and when I go to start him this happen.
Then the diff seems that the TCP connections are not closed on crash in
the one version, while the other does. Or the crash happens in a
different path, leaving the connections open.
Jorge Bastos wrote:
On Dienstag 15 September 2009 Jorge Bastos wrote:
IMAPD crashed, and when I go to start him this happen.
Then the diff seems that the TCP connections are not closed on crash in
the one version, while the other does. Or the crash happens in a
different path,
My tree is for bug testing only, but still it does not have the IPv6
changes I think. Probably something with the IPv6 stuff is causing an
issue. REUSE flag is probably missing.
-Jon
I see,
Could you write a patch with that? I know nothing about that matter!
If that's possible, I thank you,
Jorge,
please try the latest revision.
Jorge Bastos wrote:
My tree is for bug testing only, but still it does not have the IPv6
changes I think. Probably something with the IPv6 stuff is causing an
issue. REUSE flag is probably missing.
-Jon
I see,
Could you write a patch with that? I
Jorge,
please try the latest revision.
Just tried and no, same symptom.
Steps were:
Compiled new source.
Killed imapd
Started IMAPD (lots of LAST_ACK connections), but it complains about the
same
___
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
I'm working on the more correct way to handle getaddrinfo as it can
return more than 1 address that should have a socket on it. This should
have the sockets with the REUSE flag on it and work correctly. Since the
IPv6 code, my box is completely unhappy with those and SEGFAULTS upon
start up. I
I'm working on the more correct way to handle getaddrinfo as it can
return more than 1 address that should have a socket on it. This should
have the sockets with the REUSE flag on it and work correctly. Since
the
IPv6 code, my box is completely unhappy with those and SEGFAULTS upon
start up.
Your multiple IP's could be handled better with my testing branch. It
all depends on what you are putting in bindip.
My patch make no attempt to detect that we are already listening on an
IP:port pair, so some adjustment may be needed on bindip in some cases.
I was able to test a simple
bindip
On Dienstag 15 September 2009 Jorge Bastos wrote:
Compiled new source.
Killed imapd
Started IMAPD (lots of LAST_ACK connections), but it complains about
the same
For the first time, this is expected, as you killed the old imapd which
leaves the connections open. Once the new compiled imapd
Ug... reading this in the light of morning and it is confused. :-P
When I say it's in I mean CONDSTORE support is in the following
clients!
It's in the Thunderbird trunk:
http://www.rumblingedge.com/2008/10/05/2008-10-05-thunderbird-trunk-builds/
That's pretty big - don't know when it
On Montag 14 September 2009 Jonathan Feally wrote:
innodb_flush_log_at_trx_commit=2
Note:
Everybody who care about their data, you should leave this setting on
it's default 1:
innodb_flush_log_at_trx_commit=1
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
//
Hey Shane,
I'm looking for a way to rsync mail to a second server for mail migration..
I've worked out how to have multiple servers serving the same domain so you
could have users in different locations and either mail server acting as a MX
to the other for failover but need the ability to
Michael Monnerie wrote:
Note:
Everybody who care about their data, you should leave this setting on
it's default 1:
innodb_flush_log_at_trx_commit=1
Also, this will only affect writes - rather than reads.
S
___
DBmail mailing list
Hi,
I am toying with the idea to migrate all my services (login, web, samba, dbmail)
to a centralized ldap setup. While I read a lot about ldap design and general
operation principles, I can't quite wrap my head around it. So here goes:
Is there some recommended/best practice way of seting up
Simon Gray wrote:
Michael Monnerie wrote:
Note:
Everybody who care about their data, you should leave this setting on
it's default 1:
innodb_flush_log_at_trx_commit=1
Also, this will only affect writes - rather than reads.
If you have minimal writes and the server is on a
Jonathan Feally wrote:
Simon Gray wrote:
Michael Monnerie wrote:
Note:
Everybody who care about their data, you should leave this setting on
it's default 1:
innodb_flush_log_at_trx_commit=1
Also, this will only affect writes - rather than reads.
If you
On Dienstag 15 September 2009 Jonathan Feally wrote:
If you have minimal writes and the server is on a UPS, this setting
won't make too much difference
I have a home server on UPS, and can tell you from real experience what
crashes I hade despite all this:
1) Broken power supply - UPS doesn't
Howdy people,
Does anyone has a document on how put postfix delivering messages to dbmail
with dbmail-deliver instead of using LMTPD on both sides?
Thanks in advanced,
Jorge,
___
DBmail mailing list
DBmail@dbmail.org
Jorge Bastos wrote:
Howdy people,
Does anyone has a document on how put postfix delivering messages to
dbmail with dbmail-deliver instead of using LMTPD on both sides?
Thanks in advanced,
Why? I'm not aware of an overwhelming advantage to using LMTP.
signature.asc
Description:
Does anyone has a document on how put postfix delivering messages to
dbmail with dbmail-deliver instead of using LMTPD on both sides?
Thanks in advanced,
Why? I'm not aware of an overwhelming advantage to using LMTP.
I may explained myself wrong,
I'm using LMTPD now, and I'd like to
Why? why do you want to use pipe delivery? I'm not aware of an
overwhelming advantage of pipe delivery over LMTP, including my
understanding that LMTP is faster than pipe delivery.
There's a problem on LMTPD and until it's fixed I need to get rid of the
consequences of that problem.
For day,
docs/README.postfix has it all:
3. Using the Pipe interface (dbmail-deliver)
in /etc/postfix/master.cf add:
dbmail-deliverunix - n n - -
pipe
flags= user=dbmailuser:dbmailgroup
Ops, dumb me!
I didn't even thinked on going check that, sorry for that.
Checking this, I have one question on this:
If you want to decide whether or not to send to DBMail per
domain,
add this in /etc/postfix/transport:
domaindbmail-deliver:
If this
Jorge Bastos wrote:
Howdy people,
Does anyone has a document on how put postfix delivering messages to
dbmail with dbmail-deliver instead of using LMTPD on both sides?
Thanks in advanced,
disregard my previous message...
Why? why do you want to use pipe delivery? I'm not aware of an
On Donnerstag 10 September 2009 Michael Monnerie wrote:
So, this is the query you posted stripped down:
SELECT k.messageblk FROM dbmail_messageblks k WHERE
k.messageblk ILIKE '%multipart/encrypted%';
He's right, that query doesn't work on PG 8.1 either.
OK, this is a bug in dbmail, which
On Dienstag 15 September 2009 Jorge Bastos wrote:
If this needed? I mean, I REALLY have to add a line per domain?
Can I skip that part and stay only with the parts on main.cf
master.cf ?
Jorge, please read each word:
To send all email to DBMail, add this in /etc/postfix/main.cf
27 matches
Mail list logo
