>>default spamassassin DO scan rfc1918, but there is no rbl that lists ips
this is not true. SpamAssassin contains code to avoid querying DNS lists
against RFC1919 ranges. >>internal_networks 192.168.0.0/16
don't do this. Only your mail relays (mx backups and submission servers),
should be in internal_networks.
End users should not be there. >>trusted_networks 192.168.0.0/16
this is fine.
On 24.04.21 17:01, firstname.lastname@example.org wrote: >Yes this are done with my own ranges but still the same issue. Sending mail
>from own domain
you should understand that neither "trusted_networks" nor "internal_networks"
mean "Don't scan this mail".
They have use when SpamAssassin DOES scan the mail. >Please I have two problems that I want friendly ask for help
we are trying to help you but you seem to ignore some of our e-mail. >I need to send any mails from internal Privat Network to Public Network
>without that me email will send as Spam
well, how can your outgoing mail be evaluated as spam?
That should now happen.
However, the best way to avoid that is not to scan such e-mail. >the second point are, if receiving email from users at spamassassin this
>will and only this, will received with two
>spam flags Yes
>spam flags No
>possible are here that this email wiss send from gmx and after recifing any
>answer this will forward to mailserver
sorry, but it's hard to understand you now.
if SpamAssassin filters e-mail, it removes/replaces X-Spam headers.
therefore I can't explain how a mail with multiple x-spam headers can get to
Matus UHLAR - fantomas, email@example.com ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Atheism is a non-prophet organization.