I haven't tracked this down yet, but attached are the gory details. This may not be a bug in the code so much as new usage issues.
The config looks like:
<processor name="spam">
<mailet match="All" class="Forward">
<forwardto>[EMAIL PROTECTED]</forwardto>
<passThrough>true</passThrough>
</mailet>
<mailet match="All" class="ToRepository">
<repositoryPath>file://var/mail/spam/</repositoryPath>
</mailet>
</processor>
That is in the spam processor. The result is going back to root, and is
being sent back to spam, thus creating the loop. That did not happen
before, so there is something different about how the new Forward does
things. I'm guessing off-hand that the difference is the source IP. I
haven't looked at the code, yet, but my guess would be that the forwarded
message has the same source IP as the original, thus getting picked up again
by the DNS RBL matchers.
Anyhow, this is just a HEADS up for folks.
--- Noel
spoolmanager-2003-06-05-22-58.log
Description: Binary data
mailet-2003-06-05-22-58.log
Description: Binary data
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
