Bounce messages

I have a user that reports people not getting his e-mail and
I find them
in Maia, but he never got a response. I cannot find any
response in our
mail logs either, how can I verify if Maia is bouncing
messages? All I
see in the logs are is Discarded message and I thought that
I read to
have all $final_* settings in amavisd.conf set to D_DISCARD
and Maia
would handle the bounce itself, is this correct? Or should I
set my
$final_spam_destiny to D_BOUNCE?

-- 
Robert

_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users

On 12/31/07, Robert Fitzpatrick wrote:

> I have a user that reports people not getting his
e-mail and I find them
> in Maia, but he never got a response. I cannot find any
response in our
> mail logs either, how can I verify if Maia is bouncing
messages? All I
> see in the logs are is Discarded message and I thought
that I read to
> have all $final_* settings in amavisd.conf set to
D_DISCARD and Maia
> would handle the bounce itself, is this correct? Or
should I set my
> $final_spam_destiny to D_BOUNCE?
>
> --
> Robert
>

Please clarify. Is this is one of your users that is sending
mail
through the Maia machine to a remote domain? If the mail is
in the
logs, does it show the mail was sent to the remote domain,
or was it
blocked by Maia?

If the mail was accepted by the remote server, then the
problem lies
in that server.

D_DISCARD does not send bounces. Using D_BOUNCE will, but
consider the
fact that nearly all spam has a forged sender address. Most
bounces
will either get stuck in your deferred queue (because the
address is
invalid), or worse, will get sent to innocent victims (real
address,
but not the sender's actual address). Bouncing spam (and
viruses) will
make you a source of backscatter (which may get you
blacklisted) and
will make you an unwitting contributor to  'joe jobs'. Not
the best
option. You might consider using D_BOUNCE for banned files
however.

If the sender is internal, you can usually use a policy bank
(MYNETS
for example) that you can use to set spam to D_BOUNCE.
Example (you
clients are on the 192.168.0.0/16 network):

mynetworks = qw(127.0.0.0/8 192.168.0.0/16);

$policy_bank{'MYNETS'} = {  # mail originating from mynetworks
  final_spam_destiny => D_BOUNCE, # so our sender knows
they are a spammer
  spam_kill_level_maps => [7.0],
  spam_dsn_cutoff_level_maps => [9999],
};

Note that your . domain (if you have one) may override
kill_level and
dsn_cutoff_level.

-- 
Gary V
_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users

On Mon, 2007-12-31 at 08:28 -0700, Gary V wrote:
> Please clarify. Is this is one of your users that is
sending mail
> through the Maia machine to a remote domain? If the
mail is in the
> logs, does it show the mail was sent to the remote
domain, or was it
> blocked by Maia?

Yes, blocked by Maia from a mail server on our network to a
transport
domain in Postfix. The recipient domain being in Postfix
transport using
Maia for content filtering is where the block occurred and
found in the
recipients spam cache. We don't bypass rules for servers on
our network
since we don't want users spamming.

> 
> If the mail was accepted by the remote server, then the
problem lies
> in that server.
> 
> D_DISCARD does not send bounces. Using D_BOUNCE will,
but consider the
> fact that nearly all spam has a forged sender address.
Most bounces
> will either get stuck in your deferred queue (because
the address is
> invalid), or worse, will get sent to innocent victims
(real address,
> but not the sender's actual address). Bouncing spam
(and viruses) will
> make you a source of backscatter (which may get you
blacklisted) and
> will make you an unwitting contributor to  'joe jobs'.
Not the best
> option. You might consider using D_BOUNCE for banned
files however.
> 

Thanks, now that you said this, I believe this is why we do
the
D_DISCARD... 

> If the sender is internal, you can usually use a policy
bank (MYNETS
> for example) that you can use to set spam to D_BOUNCE.
Example (you
> clients are on the 192.168.0.0/16 network):
> 
> mynetworks = qw(127.0.0.0/8 192.168.0.0/16);
> 
> $policy_bank{'MYNETS'} = {  # mail originating from
mynetworks
>   final_spam_destiny => D_BOUNCE, # so our sender
knows they are a spammer
>   spam_kill_level_maps => [7.0],
>   spam_dsn_cutoff_level_maps => [9999],
> };

Sweet! Thanks. They are not private addresses, but I have
set this up to
include public trusted IP's like people we smarthost for and
other mail
servers on our local and remote networks.

-- 
Robert

_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users