On Fri, 22 Apr 2005, Sam Varshavchik wrote:
Joe Laffey writes:
Here is what I see in the log:
Apr 22 00:01:23 raw courierd:
started,id=002DCE56.4261BA37.00004CD1,from=<>,module=dsn,host=,addr=<s_trap@laffeyco
mputer.com>
Apr 22 00:01:23 raw courierd: Waiting. shutdown time=none, wakeup time=Fri
Apr 22 00:01:32 2005, queuedelivering=
37, inprogress=1
Apr 22 00:01:23 raw courierdsn: Problems injecting bounce - submit failed.
Apr 22 00:01:23 raw courierd: completed,id=002DCE56.4261BA37.00004CD1
Apr 22 00:01:23 raw courierd: Waiting. shutdown time=Fri Apr 22 00:06:23
2005, wakeup time=Fri Apr 22 00:01:32 20
05, queuedelivering=37, inprogress=0
s_trap is a spamtrap setup via an alias map pointing it to spamtrap and a
bofh entry pointing that address to be a spamtrap.
I think that might be a problem.
You should still be able to cancelmsg this message, and the doublebounce
would go to postmaster, which should not be spamtrapped.
Well, I ran cancelmsg on it. The first time it said is was scheduled for
cancelling. But repeated calls to malq show it is still there (even a day
later). BUT, If I try cancelmsg again I get "Message not found".
Any thoughts on that?
When you sa above that the spamtrap setup might be a problem am I better
off putting the individual spamtrap addresses into bofh ? If so, will this
work for domains other than the mail server's domain (virtual addresses)?
I can certainly move them into bofh if that will solve the problem and/or
is the correct way to do it.
--------------------------------------------------------------------------
Mail here will be rejected --> "Real Trap" <r_t...@laffeycomputer.com>
6 messages in net.sourceforge.lists.courier-usersRe: [courier-users] interesting loop
