[SOLVED] Upgrade from v4 to v5: Greylisting database?

What the problem? - this database is build dynamically, so there is no need to backup/restore that.
 
When we started with PMG our employees often asked why incoming mails are delayed. We explained how greylisting works and that it's a "learning system" and that the delays will "go away" after a while. They understood and as expected the delays "went away".
Upgrading to v5 means starting greylisting from zero and bringing all this back. That would disturb our employees again.
So I like to know whether there is a chance to avoid this.

Greets
Stephan
 
Hi Dietmar,

is my point of view comprehensible for you?
And aside from this I would just like to know whether there is a way to take a look into the greylisting database - for example in order to debug a user problem.

Thanks a lot and greets
Stephan
 
sherminator said:
is my point of view comprehensible for you?
Click to expand...

Yes, but I think a short amount of delay is acceptable.

sherminator said:
And aside from this I would just like to know whether there is a way to take a look into the greylisting database - for example in order to debug a user problem.
Click to expand...

Sure, it is just a postgres database table.
 
sherminator said:
I think you're right. Maybe sometimes we are "too" nice to our users. :)
Click to expand...

I think it would even be possible to dump/restore that single database table. But I never done
this, it is a manual task, and deserves some further testing. But If you have some time you can try to go that way.
 
You must log in or register to reply here.
Top Bottom