Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
On 26.06.2008 09:17, Thomas Eckardt/eck wrote:
> Set MSGIDCacheInterval to a low value to check if the Message-ID's will
> be kicked out from Cache. I just saw, that I've forgot to save the
> MSGIDCache in PB-maintenance, this will be fixed!
after PB-maintenance (or rebuildspamdb?), yes there are some msg-id's
saved in pbdb.msgid.db
but a real time saving as seen on verbose log is not done.
as a result, a number of
"[MSGID-tracking] 2xx.1xx.2xx.1xx to: user@... [monitoring]
MSGID tracking failed for bounce sender"
appear, which are legit bounces indeed due to some failure on receiving end.
where are msg-id's saved in real time of sending? in pbdb.msgid.db
(obviously not) or in RAM or somewhere else on disk?