Am 29.10.2012 07:48, schrieb Nataraj S Narayan: > On 3.0.2. > > Trying to add an ACL from DBMailadministator/DBMA.cgi. Getting this:- > > DBMA v2.5.4 (mysql localhost) from localhost [Help] Menu > Column count doesn't match value count at row 1 ADD ACL Failed > DBI::st=HASH(0x99310f8)
i doubt DBMailadministator is poorly maintained at all 2008 i installed my first dbmail-setup and tried this tool i had 50.000 test messages and used the "cleanup" option two days later ALL via IMAP to the server copied messages were deleted by dbmail-util because DBMA flagged them all wrong the cleanup-option sets the "deleted" flag for any message with status > 0 which is simply worng and the developer refused to realize this, additionally if someone is blocking mailaddresses with a dot in the localpart as invalid in my opinion he has no qualification for a mailserver software after the conversation below i had enough of this crap at all and started to write my own php-backend as module for our commercial CMS, one of the reasons to go with dbamil to have this capability -------- Original-Nachricht -------- Betreff: Re: DBMA Bug Report from Reindl Harald Datum: Tue, 16 Jun 2009 17:31:22 -0400 Von: M. J. [Mike] O'Brien <[email protected]> Antwort an: M. J. [Mike] O'Brien <[email protected]> Organisation: DBMA An: Reindl Harald <[email protected]> Hmmm. You describe nothing that is not intended. The bahviour you describe is correct. You are also describing a non RFC IMAP4 import. The imported messages should not be flagged!!!!!!!!!!! This typically in my experience is an OE mail client error. The purpose of the cleanup is to escalate delete all mail that is marked for deletion. There aer also scripts in the DBMA package for changing the options. There is much literature and help files published. If you use a weak client to import mail and that mail is marked as a 1 or a 2, it is escalated to 3 with the cleanup. That is also in the warning. It;s an import error and I have seen it in MS Outlook Express for Example but not in Office Outlook 2007 etceteras etceteras.... There are screaming warnings in Java telling you that you will escalate the deletion of mail from the system by running the database cleanup. Pleasee read the isntructions. If you want to run a clean up or if you decide you do not want to delete mail, AFTER running the clean up operation, open up the mail box you want saved and select undelete all :o) and [email protected] has a dot before the @ -- because we were being spammed by some russian server that's how we blocked it by doing a few of those types of conditions ----- Original Message ----- From: "Reindl Harald" <[email protected]> To: <[email protected]> Sent: Sunday, June 14, 2009 6:01 PM Subject: DBMA Bug Report from Reindl Harald > From: "Reindl Harald" <[email protected]> > Sent: Sun Jun 14 18:01:52 2009 > > Message: You have a BIG bug in dbmailadmin > Mails transferred via imap/imapsync have status 1 > > "Database Cleanup" marks them with 003 and so ALL your sent and imported > mails are lost! > > 3600: > #"UPDATE $dbmail_messages_table SET status = '003' where deleted_flag = > '1' OR status >0" > "UPDATE $dbmail_messages_table SET status = '003' where deleted_flag = > '1'" > > 6180: > #"SELECT COUNT(*) FROM $dbmail_messages_table WHERE deleted_flag='1' OR > status >0" > "SELECT COUNT(*) FROM $dbmail_messages_table WHERE deleted_flag='1'" > > > What i do not understand is that nobody sees such things :-) > > We play with "dbmail" since friday, have imported a test with 30.000 > messages > and after clicking on the cleanoption den daily cronjob has killed all > of them including all "sent"-messages > > BTW: What is invalid in the address > "[email protected]"
signature.asc
Description: OpenPGP digital signature
_______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
