Re: Sudden surge in spam appearing to come from my email address

/outlook.com. > > > So > > > from outlook.com, through some unsecured email server, then to my > > > server. > > > > > > I'm trying to figure out how to block this stuff. Something like > > > "if > > > it appears to come from me, but it's not actually coming from my > > > email server," block it. I don't necessarily think this is a job > > > for > > > SA, but if there's a rule I can tweak or a setting I can change, > > > I'm > > > all ears. > > > > > > Thanks, > > > Thomas > > > > > > > > > -- Robert Senger

Re: Best practice for adding headers?

f patching spamass-milter > > Agreed, it's not a problem from the technical point of view, as it's not a problem to use the -S option to call something else which is not sendmail (that's what I am doing right now). It's more a matter of, well, cosmetics or aesthetics... Regards, Robert -- Robert Senger

Re: Best practice for adding headers?

ms), it should be easy to add such an option to spamass-milter. Regards, Robert -- Robert Senger

Re: Best practice for adding headers?

; > Ciao, > David > Thanks David, never heard of spamassassin-milter before (it's not in the Debian repos), but I'll give it a try as there seem to be more issues with spamass-milter. Robert > ¹ https://crates.io/crates/spamassassin-milter -- Robert Senger

Re: Share bayes database between servers

Am Sonntag, dem 09.07.2023 um 19:21 +0200 schrieb Reindl Harald: > > > Am 09.07.23 um 19:06 schrieb Robert Senger: > > But bayes data may be updated by either the primary mx or the > > backup > > mx, since email may arrive at either server. > > in a smart setup

Best practice for adding headers?

eaders in place if their names match those spamass-milter uses. What do you think? Robert Am Mittwoch, dem 05.07.2023 um 01:38 +0200 schrieb Robert Senger: > Hi all, > > is there a reason why spamassassin adds its "X-Spam ..." headers to > the > bottom of the header

Share bayes database between servers

, with priority in dns set to equal for both mx to get incoming mail distributed evenly to both systems. So far, this seems to work, but this is a low load environment. Any suggestions? Regards, Robert -- Robert Senger

Re: Position of X-Spam headers

use later filtering (e.g. sieve) with multiple "X-Spam-Flag" headers with possibly contradictory results. However, it should be easy to patch spamass-milter to keep existin headers intact. -- Robert Senger

Re: Position of X-Spam headers

Am Mittwoch, dem 05.07.2023 um 10:20 +0200 schrieb Matus UHLAR - fantomas: > On 05.07.23 04:38, Robert Senger wrote: > > Thanks for the hint that the milter is responsible for that. Found > > a > > little patch for spamass-milter that fixed this. > > note that th

Re: Position of X-Spam headers

Thanks for the hint that the milter is responsible for that. Found a little patch for spamass-milter that fixed this. Regards, Robert Am Dienstag, dem 04.07.2023 um 19:45 -0400 schrieb Jared Hall: > On 7/4/2023 7:38 PM, Robert Senger wrote: > > is there a reason why spamassassin ad

Re: Position of X-Spam headers

Hi Jared, I am using spamass-milter. Robert Am Dienstag, dem 04.07.2023 um 19:45 -0400 schrieb Jared Hall: > On 7/4/2023 7:38 PM, Robert Senger wrote: > > is there a reason why spamassassin adds its "X-Spam ..." headers to > > the > > bottom of the header block,

Position of X-Spam headers

Hi all, is there a reason why spamassassin adds its "X-Spam ..." headers to the bottom of the header block, not to the top like every other mail filtering software (e.g. opendkim, opendmarc, clamav ... ) does? Can this behavious be changed? Regards,  Robert -- Robert Senger