Whitelist bug or DB

IceWarp Server User to User Forum

Forums Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

Whitelist bug or DB

Logged in as: Guest

Users viewing this topic: none

Printable Version

All Forums >> [IceWarp Product Configuration] >> IceWarp Mail Server Configuration >> Whitelist bug or DB

Page: [1]

Message

<< Older Topic Newer Topic >>

Whitelist bug or DB - 10/16/2008 4:09:50 AM

Valon

Posts: 2
Score: 0
Joined: 10/13/2008
From: ---
Status: offline

Hi.

One customer of mine whitelists a sender and everything seems fine, but the message doesn't show up. It's gone. It seems that it is added to the whitelist, but the whitelist have a few items from 1899 that I can't delete.
Is the DB corrupted then, or is there something else that's the problem? I do not want to migrate if thoose posts find their way back to the new DB...

_____________________________

Best regards,

Post #: 1

RE: Whitelist bug or DB - 10/18/2008 2:36:24 AM

marciohumpris

Posts: 362
Score: 2
Joined: 5/1/2008
Status: offline

Hi, Valon

1) About whitelisting and not showing up, Ive seen this before, but for me in 9.3.2 its working fine. In which situation does it happen, inside webmail pro? Or in reports? I know they fixed this in reports as it would happen to our customers only sometimes. I think its best you contact support about this and send them access so they can see it happening, etc. Gotta compare to see if its intermitent or happens with all accounts, etc. Try via console, etc. Try to understand a bit further.

2) About 1899, I also have some entries with very old date I cannot delete. Ive deleted them inside the database directly. Something you could mention to support also. I dont know why this happens, in my case I checked now, I have some entries from 1899, in status/spam queues/whitelist, owner and sender fields are empty. Is that what happens to you?

regards,
Marcio

(in reply to Valon)

Post #: 2

RE: Whitelist bug or DB - 11/11/2008 8:24:13 PM

Tapuz

Posts: 8
Score: 0
Joined: 11/11/2008
Status: offline

We have the same problem

(in reply to marciohumpris)

Post #: 3

RE: Whitelist bug or DB - 11/22/2008 3:23:26 AM

marciohumpris

Posts: 362
Score: 2
Joined: 5/1/2008
Status: offline

Hi, Tapuz

Which of the issue? The 1889? If possible I suggest you sent your database to support, so maybe it can help them find a fix.

regards,
Marcio

(in reply to Tapuz)

Post #: 4

RE: Whitelist bug or DB - 11/25/2008 4:25:41 AM

bcasson

Posts: 1
Score: 0
Joined: 9/18/2008
Status: offline

I have this problem in both Whitelist and Blacklist. I have a total of 12 entries in the Blacklist, all of which I would like to delete. Half of them have an 1899 date and the the rest have valid dates, but some of the other fields are either empty or fragmented. None of these can be deleted!

When I checked the database, the fragmented fields have tabs inbedded in their data.

(in reply to marciohumpris)

Post #: 5

RE: Whitelist bug or DB - 11/29/2008 12:38:12 AM

marciohumpris

Posts: 362
Score: 2
Joined: 5/1/2008
Status: offline

Guys,

This can be deleted directly in DB. If youre using SQLite, I recommend this tool which installs in Firefox and makes it easy to delete them: https://addons.mozilla.org/en-US/firefox/addon/5817

If needed, contact support, surely would be nice to show them the problem so they can find a fix if its not fixed already.

regards,
Marcio

(in reply to bcasson)

Post #: 6

RE: Whitelist bug or DB - 12/4/2008 1:06:37 AM

philou

Posts: 51
Score: 0
Joined: 8/31/2008
Status: offline

you can use the SQLite manager tool from firefox (as suggested by Marcio), or use command line interface or any other native SQL interface available for your antispam database (be it sqlite, mysql, ms sql, access...).

The commands to run are: (make sure to backup the antispam database before running the commands, just in case...)
Update senders set sndsubject=NULL where sndauthorized='0'
Update senders set sndsubject=NULL where sndauthorized='1'

The first one with the filter '0' will do the trick on the blacklist entries
The second one with the filter '1' will do the trick on the whitelist entries.

Actually, there is only one entry in the database, the bug is in the display of the entry in certain cases.
Also, the problem doesn't occur any more in the beta version, so the SQL updates won't be needed in the future.

(in reply to marciohumpris)

Post #: 7