Spam from same email ID.

[Glenn Steen]

On 9 September 2010 10:18, Steve Freegard <steve.freegard at fsl.com> wrote:
> On 08/09/10 23:11, Dhaval Soni wrote:
>>
>>
>> On Thu, Sep 9, 2010 at 3:15 AM, Alex Neuman <alex at rtpty.com
>> <mailto:alex at rtpty.com>> wrote:
>>
>>    The other message involving dkim and spf works well, too.
>>
>>
>> I already have DKIM and spf with spamassassin. But is it preferable to
>> use smf-spf at MTA level?
>>
>
> You might have DKIM and SPF in SpamAssassin; but these are totally useless
> unless the domain you are having this problem with (e.g. 123l.com) actually
> publishes or uses them...
>
> smf at smf-laptop:~$ host -t TXT 123l.com
> 123l.com has no TXT record
>
> Same with smf-spf or milter-spiff; they'll only fix this problem if a policy
> is published for the domain in question (ideally a '-all' hard fail).
>
> Regards,
> Steve.
I'm a bit rusty on the rendmaul...Oops, sendmail ... side of things,
but couldn't one do pretty much the same as I do in PF? That is, use
an access-like map to disallow ones own (or customers) domain(s) as
(envelope) senders? The loss for any typical smaller business would be
greeting card stes etc, so shouldn't matter much.
Sure, SPF with correct DNS record(s) would perhaps be easier, but ...
sometimes it is easier to futz with ones MTA than with a (possibly
externally managed) DNS:-).

Cheers
-- 
-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se