spamassassin-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From haman...@t-online.de
Subject Re: SPAM from our own domain
Date Mon, 28 Sep 2015 06:24:40 GMT
>> 
>> Hi Benny,
>> 
>> thanks for your email.
>> 
>> On 28/09/15 13:29, Benny Pedersen wrote:
>> > Tom Robinson skrev den 2015-09-28 05:02:
>> >
>> >> From tenayad@qka.com Thu Sep 24 13:    29:50 2015
>> >
>> > is this the envelope sender domain ?
>> 
>> I believe so. How can I be sure?
>> 
>> >
>> >> From:    "Incoming Fax" <Incoming.Fax@motec.com.au>
>> >
>> > is this unsigned dkim domain ?
>> >
>> Sorry to be a noob. What do you mean here?
>> 
>> >
>> > begin setup spf and dkim signing
>> We have a TXT record in DNS for spf. I'm not sure what to do with DKIM.
>> 
>> >
>> > use pypolicyd-spf in mta stage
>> 
>> Is that package going to work with qmail? If it does work with qmail, will it install
on CentOS 5?
>> 
>> Kind regards,
>> Tom
>> 
>> 
Hi Tom,

I have installed dkim on qmail (not sure about details, it is working since a few years)
Your original post said there was SPF fail on the incoming message, so you could already
score on that.
I have enabled plugin support on qmail (not sure whether that is contained in your package),
and I have worked on qmail-scanner-queue.pl
Both are good places to add extra filtering. The plugin would outright reject mail,
where qmail-scanner would rather tag it as "potential virus"
So if you are very sure that nobody in your organisation would ever send from your domain
through a different mail server (maybe when sending from a mobile), you should probably use
the plugin. A plugin is an executable (script) that reads ENV variables like SMPTMAILFROM
and SMTPRCPTTO and either does nothing or outputs a single line of text like
E550 your mail is not welcome. Go away

Regards
Wolfgang




Mime
View raw message