On Sun, Jul 09, 2023 at 07:06:10PM +0200, Robert Senger wrote:
> I've set up a testing environment that also uses master-master
> replication of the mysql bayes database, with priority in dns set to
> equal for both mx to get incoming mail distributed evenly to both
> systems. So far, this seems
Am Sonntag, dem 09.07.2023 um 13:55 -0700 schrieb Loren Wilton:
> > I've patched spamass milter to let any previously added "X-Spam"
> > headers untouched
>
> Its generally considered bad practice to pass thru X-Spam headers
> from an
> unkonwn source.
> Like most anything else in an email
Am Sonntag, dem 09.07.2023 um 19:23 +0200 schrieb David Bürgin:
> Hello Robert,
>
> > Now, I am a bit uncertain about what would be the best practice for
> > a
> > milter to place its headers.
> >
> > I've patched spamass milter to let any previously added "X-Spam"
> > headers untouched, and
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 your bayes-database is read-only
On 2023-07-07 at 12:08:22 UTC-0400 (Fri, 7 Jul 2023 09:08:22 -0700
(PDT))
Richard Troy
is rumored to have said:
Hi All,
I changed the subject line to hopefully get some insight from a wider
audience regarding this situation that Reindl uncovered:
It should be noted that Harald Reindl is
I've patched spamass milter to let any previously added "X-Spam"
headers untouched
Its generally considered bad practice to pass thru X-Spam headers from an
unkonwn source.
Like most anything else in an email header, a spammer could inject his own
headers, probably populated with items
Hello Robert,
> Now, I am a bit uncertain about what would be the best practice for a
> milter to place its headers.
>
> I've patched spamass milter to let any previously added "X-Spam"
> headers untouched, and just add its own headers on top of the header
> list as required by spamassassin's
First of all, thanks for your help!
Now, I am a bit uncertain about what would be the best practice for a
milter to place its headers.
I've patched spamass milter to let any previously added "X-Spam"
headers untouched, and just add its own headers on top of the header
list as required by
Hi there,
I am running two mailservers, first one serving two domains, other one
serving one domain.
Both serve as backup mx for each other. Both know about users and
aliases of the other domain(s).
On both systems, spamassassin is configured to read/store userprefs and
bayes data (per user) in
