Colin Manning wrote:
> Thank you Paul for all your time and knowledge.
Glad I could help.
> Was it the fact that I did not run the 2.0 to 2.1 migration script the
> first time?
That's possible, but I only wrote that one after your problems surfaced.
--
__
Paul J Stevens <[EMAIL PROTECTED]> wrote: Colin Manning wrote:
> O.K.
>
> I have been over this many many times. The data looks good in the database.
> If I telnet to the server and
> a login name pass
> a select inbox
> a fetch 1
That doesn't make any sense at all!
a fetch 1
should return:
Colin Manning wrote:
> O.K.
>
> I have been over this many many times. The data looks good in the database.
> If I telnet to the server and
> a login name pass
> a select inbox
> a fetch 1
That doesn't make any sense at all!
a fetch 1
should return:
a BAD missing argument(s) to FETCH
A typo o
O.K.
I have been over this many many times. The data looks good in the database.
If I telnet to the server and
a login name pass
a select inbox
a fetch 1
I get the message - body and all.
However, If I do this from a mail client (evolution, thunderbird, outlook) I
get nothing.
Sigh.
Colin Manning wrote:
> The first entry returns a blank message, the second one returns a
> garbled message (binary) - e.g.
>
> \ ˆP ¨.½0P ˜’g p;¼p;¼X�Ë¿°ü[
Colin,
It just dawned on me. There was one change in the postgres tables
between 2.0 and 2.1 that is probably significant here:
in db
quot; <[EMAIL PROTECTED]>
To: "DBMail mailinglist"
Sent: Wednesday, April 05, 2006 5:52 PM
Subject: Re: [Dbmail] dbmail 2.0 to 2.1 upgrade gone bad - no message body
ine-mails
How about this entry:
Apr 6 05:40:19 mail dbmail/imap4d[14577]: COMMAND: [267 UID fetch 42269
(UID RF
How about this entry:
Apr 6 05:40:19 mail dbmail/imap4d[14577]: COMMAND: [267 UID fetch 42269 (UID
RFC822.SIZE BODY[])]
Apr 6 05:40:19 mail dbmail/imap4d[14577]: arg[0]: 'fetch'
Apr 6 05:40:19 mail dbmail/imap4d[14577]: arg[1]: '42269'
Apr 6 05:40:19 mail dbmail/imap4d[14577]: arg[2]: '('
Paul J Stevens <[EMAIL PROTECTED]> wrote: Colin Manning wrote:
> O.K. The good news is that you know what the problem is
No I don't... sorry.
Bother.
>
> Here is an extract from my maillog when I create a new IMAP client and
> try to get all my old messages...
Again, this looks valid to m
Colin Manning wrote:
> O.K. The good news is that you know what the problem is
No I don't... sorry.
>
> Here is an extract from my maillog when I create a new IMAP client and
> try to get all my old messages...
Again, this looks valid to me.
> Apr 5 15:35:18 mail dbmail/imap4d[30732]: Fet
O.K. The good news is that you know what the problem is
Here is an extract from my maillog when I create a new IMAP client and try to
get all my old messages...
Apr 5 15:35:18 mail dbmail/imap4d[30732]: Fetching msgID 41961 (fetch num
41962)
Apr 5 15:35:18 mail dbmail/imap4d[30732]: db
Colin Manning wrote:
>
>
> And the log for IMAP 2.0.10:
where the last line for the imapd process reads:
> Apr 5 06:35:53 mail dbmail/imap4d[27538]: mime_readheader(): entering
> mime loop
which indicates the 2.0.10 mime parser chokes on this message.
--
_
This 2.1 log looks fine to me.
Colin Manning wrote:
> But wait - there's more!
>
> When I revert back to 2.0.6 executables th mail gets delivered
> correctly!! - I just can't accesses from my client untill I revert to
> the SVN executables.
>
> */Paul J Stevens <[EMAIL PROTECTED]>/* wrote:
>
>
Colin Manning <[EMAIL PROTECTED]> wrote: Date: Wed, 5 Apr 2006 08:39:39 +1000
(EST)
From: Colin Manning <[EMAIL PROTECTED]>
Subject: Re: [Dbmail] dbmail 2.0 to 2.1 upgrade gone bad - no message body in
e-mails
To: DBMail mailinglist
And the log for IMAP 2.0.10:
Apr 5 0
And the log for IMAP 2.0.10:
Apr 5 06:21:22 mail dbmail/imap4d[27395]: pool.c,child_register: register
child [27395]
Apr 5 06:21:22 mail dbmail/imap4d[27395]: pool.c,child_register: initializing
child_state [27395] using slot [0]
Apr 5 06:21:22 mail dbmail/imap4d[27397]: pool.c,child_
But wait - there's more!
When I revert back to 2.0.6 executables th mail gets delivered correctly!! - I
just can't accesses from my client untill I revert to the SVN executables.
Paul J Stevens <[EMAIL PROTECTED]> wrote: Colin Manning wrote:
> Hi All,
>
> I have been running dbmail for some
Colin Manning wrote:
> Hi All,
>
> I have been running dbmail for some time now, and waiting for seive -
> thanks to everyone involved in getting it going.
>
> So I thought that today would be a good day to install 2.1.5 - after
> finally getting it to compile.
>
> So, understanding that it is
Hi All,
I have been running dbmail for some time now, and waiting for seive - thanks
to everyone involved in getting it going.
So I thought that today would be a good day to install 2.1.5 - after finally
getting it to compile.
So, understanding that it is unstable, a backup of the
Jesse Norell wrote:
> Hello,
>
> The format of saved messages is different for 2.1, so all new mail
> would need to be saved in the new format. If you use pop3, not imap,
> you should be able to run the 2.0 pop3 daemon and the 2.1 injector
> (dbmail-lmtpd or dbmail-inject) and be fine while d
Hello,
The format of saved messages is different for 2.1, so all new mail
would need to be saved in the new format. If you use pop3, not imap,
you should be able to run the 2.0 pop3 daemon and the 2.1 injector
(dbmail-lmtpd or dbmail-inject) and be fine while dbmail-util -by
runs. If you use i
PJS> kost wrote:
>> Здравствуйте!
PJS> indeed :-\
>> Is there any sql queries that lock mysql tables in 'dbmail-util -ay'
>> command? For example 'OPTIMIZE TABLE'...
PJS> Yes. If you want to avoid that (makes sense) use 'dbmail-util -by'
As I understand it will be normal if I start migration pr
kost wrote:
> Здравствуйте!
indeed :-\
> Is there any sql queries that lock mysql tables in 'dbmail-util -ay'
> command? For example 'OPTIMIZE TABLE'...
Yes. If you want to avoid that (makes sense) use 'dbmail-util -by'
--
Здравствуйте!
PJS> kost wrote:
>> PJS> kost wrote:
>>
Hi All!
Currently I'm using dbmail 2.0.7 version. In near feature (I hope
after dbmail 2.1.4 release) I'm going to migrate on 2.1.x branch.
But I didn't find any docs about migration from 2.0 to 2.1
Shall it eno
kost wrote:
> PJS> kost wrote:
>
>>>Hi All!
>>>
>>>Currently I'm using dbmail 2.0.7 version. In near feature (I hope
>>>after dbmail 2.1.4 release) I'm going to migrate on 2.1.x branch.
>>>But I didn't find any docs about migration from 2.0 to 2.1
>>>
>>>Shall it enough if I just add new tables
PJS> kost wrote:
>> Hi All!
>>
>> Currently I'm using dbmail 2.0.7 version. In near feature (I hope
>> after dbmail 2.1.4 release) I'm going to migrate on 2.1.x branch.
>> But I didn't find any docs about migration from 2.0 to 2.1
>>
>> Shall it enough if I just add new tables from create_tables_
kost wrote:
> Hi All!
>
> Currently I'm using dbmail 2.0.7 version. In near feature (I hope
> after dbmail 2.1.4 release) I'm going to migrate on 2.1.x branch.
> But I didn't find any docs about migration from 2.0 to 2.1
>
> Shall it enough if I just add new tables from create_tables_innoDB.mys
Hi All!
Currently I'm using dbmail 2.0.7 version. In near feature (I hope
after dbmail 2.1.4 release) I'm going to migrate on 2.1.x branch.
But I didn't find any docs about migration from 2.0 to 2.1
Shall it enough if I just add new tables from create_tables_innoDB.mysql
file?
Could anybody tell
dbmail wrote:
The NCHILDREN will result one more processes
for example: NCHILDREN=2
root 4836 0.0 0.4 2364 796 ?S12:22 0:00 dbmail-imapd
nobody4837 0.0 0.4 2364 820 ?S12:22 0:00 dbmail-imapd
nobody4838 0.0 0.7 2496 1340 ?S12:22
Hello,
> I have tested dbmail.(MTA postfix) on Suse 9.1 (for test on vmware)
>
> If using myisam tables check should be added like
> SELECT *
> FROM dbmail_messages
> LEFT JOIN dbmail_physmessage ON dbmail_messages.physmessage_id =
> dbmail_physmessage.id
> WHERE dbmail_physmessage.id IS NU
The NCHILDREN will result one more processes
for example: NCHILDREN=2
root 4836 0.0 0.4 2364 796 ?S12:22 0:00 dbmail-imapd
nobody4837 0.0 0.4 2364 820 ?S12:22 0:00 dbmail-imapd
nobody4838 0.0 0.7 2496 1340 ?S12:22 0:00 dbmail-imapd
I have tested dbmail.(MTA postfix) on Suse 9.1 (for test on vmware)
If using myisam tables check should be added like
SELECT *
FROM dbmail_messages
LEFT JOIN dbmail_physmessage ON dbmail_messages.physmessage_id =
dbmail_physmessage.id
WHERE dbmail_physmessage.id IS NULL
if there any records,
Hey Sumbry and List:
If you still have orphaned messages I offer a solution.
DBMA will find and mark orphaned messages for deletion.
(DBMA V2.1.2)
http://library.mobrien.com/dbmailadministrator/
Untar it. Open in browser.
Configure from the GUI.
Select "Update Delete Status" checkbox and press "
> orphaned messageblks is exactly the sort of stuff dbmail-util is supposed to
> look for.
>
> if dbmail-util -r doesn't clean out those blks, we have a bug.
I pointed this out on dbmail-dev a little while ago as I had the same
problem. dbmail-util doesn't yet fix these.
select count(*) from dbm
> John,
>
> orphaned messageblks is exactly the sort of stuff dbmail-util
> is supposed to look for.
>
> if dbmail-util -r doesn't clean out those blks, we have a bug.
>
It did not... :(
Note however, that all these orphaned messages are from deleted
mailboxes.
... john
anley
Sent: Thursday, October 21, 2004 11:11 PM
To: DBMail mailinglist
Subject: Re: [Dbmail] DBMail 2.0 final
This worked for me!
cat $USER.mbx | formail -e -f -s
/opt/dbmail2/sbin/dbmail-smtp -u $USER
Course you need to install formail.
Doug
p.s. those are the flags that I used to properly
John,
orphaned messageblks is exactly the sort of stuff dbmail-util is supposed to
look for.
if dbmail-util -r doesn't clean out those blks, we have a bug.
John Hansen wrote:
Weren't there going to be a cleanup tool to get rid of old messages no
longer linked from any mailbox?
I did some
Heh, other way around Create mbox files from a dbmail account...
... John
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Doug Stanley
> Sent: Thursday, October 21, 2004 11:11 PM
> To: DBMail mailinglist
> Subject: Re: [
This worked for me!
cat $USER.mbx | formail -e -f -s /opt/dbmail2/sbin/dbmail-smtp -u $USER
Course you need to install formail.
Doug
p.s. those are the flags that I used to properly parse whatever weirdo
format mailboxes SLmail uses. I beleive their mbx...You might need
different flags...I'd s
Weren't there going to be a cleanup tool to get rid of old messages no
longer linked from any mailbox?
I did some housekeeping, and still have 300.000+ messageblks, tho only
350 messages.
Also,... Has anyone written a dbmail2mbox tool?
Kind Regards,
John
M. J. [Mike] O'Brien wrote:
http://library.mobrien.com/dbmailadministrator
Thanks Mike...
got the ini scripts running as well.
next is SMTP Auth & I'm rocking.
back to the List Archives
Alex
http://library.mobrien.com/dbmailadministrator/
> Next questions:
>
> - What is every one using as a Wev Frontend for DBmail 2 - only found
> one for an older version. Will this work well with 2.0?
> - Have been looking for RedHat compatible init scripts. Haven't found
> any (yet) - anybody go
Paul J Stevens wrote:
Alex Broens wrote:
Oct 16 11:22:16 mail dbmail/maintenance[3433]: dbmysql.c,db_connect:
mysql_real_connect failed: Can't connect to local MySQL server through
socket ' /var/lib/mysql/mysql.sock' (2)
Alex, remove those spaces right after the = sign in the config.
use:
Alex Broens wrote:
Oct 16 11:22:16 mail dbmail/maintenance[3433]: dbmysql.c,db_connect:
mysql_real_connect failed: Can't connect to local MySQL server through
socket ' /var/lib/mysql/mysql.sock' (2)
Alex, remove those spaces right after the = sign in the config.
use:
socket=/var/lib/mysql/mys
of localhost or
> > 127.0.0.0.1
> > Another solution is to remove the chroot or make symlink, or if not chrooted
> > simply to allow that user to red socket dir
> >
> > I hope this helps
> >
> > Peter
> > - Original Message -
> > From: Al
Another solution is to remove the chroot or make symlink, or if not chrooted
> simply to allow that user to red socket dir
>
> I hope this helps
>
> Peter
> - Original Message -
> From: Alex Broens
> To: dbmail@dbmail.org
> Sent: Saturday, October 16, 2004 4:1
Good Day,
I'm a DBmail newbie with a little problemm which has driven me nuts for
a long day and no matter what I do I don't get any further.
--
dbmail-util -tvp produces:
Oct 16 11:22:16 mail dbmail/maintenance[3433]: dbmysql.c,db_connect:
mysql_real_connect failed: Can't connect to
The same happens to me with 3500 messages.
I really think this is related to caching in squirrelmail, but I didn't
look at the code, so I can not confirm this.
[]s, gandhi
Richard Houston wrote:
Hi all,
I have a brand new dbmail 2.0 RC8 install using Fedora Core 2 and Mysql
4.0.20.
Everyth
Hi all,
I have a brand new dbmail 2.0 RC8 install using Fedora Core 2 and Mysql
4.0.20.
Everything seems to work very well. I have been able to copy from one imap
account to the dbmail server with great performance. I am a long time
Cyrus user so speed is something I keep my eye on.
I have foun
I am just wondering if anyone else gets error messages refreshing
folders in Evolution. Mail server has very little load (two users, 4
mail boxes total for two domains). I have turned off auto-refresh in
evolution which does not seem to help. It is not always the same folder
that gives me an error.
Does the Dbmail 2.0 RC7 download include Leif Jackson's
Sort patch?
If not where would be the best place to find it?
Once I have it, should I apply the patch to current CVS or
the source from the dbmail.org download section?
Thanks,
Kevin
We're getting very close to the release of DBMail 2.0 now. Release
candidate 6 is here. These are the major fixes and changes compared to RC5:
* Deliveries are quicker. The mail size of the internal delivery
user is no longer updated on every delivery, avoiding a lot of locking.
* Find
James XMS wrote:
Hi All,
I know i am probably going to get flamed for this, and get responses like 'how long is a bit of string', but does anybody have an e.t.a for DBMail 2.0 Final? Or can anybody say whether
rc4 is the final release candidate before the final?
I am just anxious because i a
Hi All,
I know i am probably going to get flamed for this, and get responses like 'how
long is a bit of string', but does anybody have an e.t.a for DBMail 2.0 Final?
Or can anybody say whether
rc4 is the final release candidate before the final?
I am just anxious because i am planning on roll
The framework is in place, but the code is mostly stubs. Sieve support
is scheduled for 2.1.
Guido wrote:
On Friday 19 March 2004 17:57, Ilja Booij wrote:
DBMail 2.0 Release Candidate 4 can be downloaded from the download page
at http://www.dbmail.org. These bugs were fixed:
We could pr
On Friday 19 March 2004 17:57, Ilja Booij wrote:
> DBMail 2.0 Release Candidate 4 can be downloaded from the download page
> at http://www.dbmail.org. These bugs were fixed:
> We could probably do with some more optimizations in the queries, but
> other than that, we're well on our way to a stable
DBMail 2.0 Release Candidate 4 can be downloaded from the download page
at http://www.dbmail.org. These bugs were fixed:
* LMTP now works, also with cached connections. It turned we were
misinterpreting some things in the RFC
* Mozilla clients now work. It turned out that there were som
Hi all,
We've just released DBMail 2.0 Release Candidate 3
News item on www.dbmail.org:
DBMail 2.0 release candidate 3 can be downloaded from the download page.
This release has quite a lot of fixes:
* dbmail-lmtp returns useful messages to the MTA. A lot of work has
been done on this b
I got following errors anyone recognize it?
SquirrelMail after login:
ERROR : Could not complete request.
Unknown response from IMAP server: 1.
also
Warning: strpos(): Offset not contained in string. in
sqmail/functions/imap_messages.php on line 522
anyway, and the syslog says:
Feb 26 20:40:4
Has anyone else had a chance to test the new changes? I recompiled the
binaries with the pipe.c changes and the maximum file size is still 512K.
- Original Message -
From: "Ilja Booij" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, February 24, 2004 6:05 AM
Subject: Re: [Dbmail
Hi,
Thanks for this fix!
I've made a small additional change. Because the while-loop now also
continues if linemem != 0, I've added a statement to set linemem = 0 if
the end of the message (.\r\n as one line) is reached.
Ilja
all changes to pipe.c:
[EMAIL PROTECTED]:~/dbmail2_0$ cvs diff pi
I found some problem at pipe.c that cannot read "stdin" larger than 512k ..
fixed is the diff below ...
**8
582c582
< while (!feof(instream) && !myeof)
---
> while ((!feof(instream) && (!myeof)) |
Thanks Booil for your reply,
Like i said im not shure if im right or wrong
about the curmail_size in dbmail 2.0.
Im migrating from uwimap to dbmail.
I plan to use HORDE/IMP as webmail.
I had some mysql code in IMP that give me the space use in the
users mail box under dbmail 1.2.3.
Since dbm
Hi,
Jacques, can you give examples of situations in which it does not
calculate the size? (possibly with a trace log)
Ilja
Jacques Beaudoin wrote:
Im not shure of this but curmail_size in the user table
does not seam to calculate the actual size of a uses mailboxes.
Thanks
Jacques Beaudoi
Im not shure of this but curmail_size in the user table
does not seam to calculate the actual size of a uses mailboxes.
Thanks
Jacques Beaudoin
Hi All,
after a week of fixing bugs and creating migration scripts, RC 2 has
arrived. These are the changes:
* RC1 segfaulted on Linux, due to a stupid bug. This has been fixed
* The use of the sendmail program (for bounces and forwards) has
been changed to also work with SendMail (fi
Hi All,
you can find DBMail 2.0 release candidate 1 on the download page of
www.dbmail.org.
For people wanting to migrate from 1.x: There is now migration script
yet for moving all mailboxes. There is a script though that will move
the mailbox (with messages of course) of one user to dbmail
65 matches
Mail list logo
