MSGIDCache is part of the penaltybox. MSGID's are stored in RAM like any
other cache and will be written to pbdb.msgid.db after PB-maintenance or
if you stop ASSP! There is no chance (and I think no need) to see the
realtime MSGID's! This belongs to all lists and caches - when ever you
click on "show file" in GUI, you'll see the file - never the realtime
cache!
How ever, I recommend setting MSGID tracking at maximum to score (not
block !!!). ASSP will know all MSGID's of outgiong mails, but if the
server, who sends the mail back, does not include the whole header with
the original MSGID, the MSGID check will fail!
Thomas
Katip <katip@...>
Gesendet von: assp-test-bounces@...
28.06.2008 15:08
Bitte antworten an
ASSP development mailing list <assp-test@...>
An
ASSP development mailing list <assp-test@...>
Kopie
Thema
Re: [Assp-test] Antwort: [Fwd: MSGID Cache 2.18]
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?
Katip
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Assp-test mailing list
Assp-test@...
https://lists.sourceforge.net/lists/listinfo/assp-test
DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally
privileged and protected in law and are intended solely for the use of the
individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no
known virus in this email!
|