On 19.06.2015 16:24, Reindl Harald wrote:
Am 19.06.2015 um 16:19 schrieb Axb:
On 19.06.2015 16:01, Reindl Harald wrote:
Am 19.06.2015 um 15:56 schrieb Reindl Harald:
envelope=_SENDERDOMAIN_, from=_AUTHORDOMAIN_
syslog to SQL and you can xref all the info you need
that's a workaround and not a solution, there's a reason why
the spamfirewall is the *only* machine not logging to mysql
because you really don't want a dozen millions of sql-inserts
each month
*YOU* don't want them. If you have a cluster of more than the one
"spamfirewall" it can be very practical to have central SQL
logging.
*if* you have a cluster and central logging don't imply SQL logging
at all
and for messages without a MID you have currently no way at all
to xfer anything since you only see the rules and the result with
*nothing* to grep for
Postfix/MTA/Glue Session IDs, etc... having the data in a DB also
allows all kinds of stats.
nonsense, there is *nothing* to xfer the other log entries and the
timestamp is for sure nothing you can rely on in case of multiple
mails arrive at the same time
Jun 19 11:10:55 mail-gw spamd[25089]: spamd: result: . 4 -
BAYES_50,HTML_MESSAGE,MISSING_MID,RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,RP_MATCHES_RCVD,SPF_NONE
scantime=1.9,size=5966,user=sa-milt,uid=189,required_score=5.5,rhost=localhost,raddr=127.0.0.1,rport=/run/spamassassin/spamassassin.sock,mid=(unknown),bayes=0.599086,autolearn=disabled,shortcircuit=no
if you only have one user=sa-milter then you're screwed
Your system design limits you. Maybe you should reconsider your spamd
options so it logs the recipient using -q
