Message
From: Anthony Peacock [mailto:a.peacock (AT) chime (DOT) ucl.ac.uk]
Sent: Tuesday, July 04, 2006 5:06 AM
To: SpamAssassin Users
Subject: Myway.com and RFC-ignorant.org
balance these scores out? I understand that SPF is not a sign of
hammy/spammyness, but would I be openening up my system too much by
But maybe ignoring emails to postmaster@ and abuse@ and having no valid
whois contacts IS a sign of spammyness, and that they don't care if
their users spam, have viruses or pass along phishing emails.
Since you use SPF, you could use whitelist from spf to make sure that
you aren't allowing in forged myway.com spam.
Put this in local.cf in /etc/spamassassin directory where local config
files are.
Something like:
whitelist_from_spf *@myway.com
(which would allow SPAM from myway.com users, but not FRGED SPAM)
or
whitelist_from_spf remoteuser (AT) myway (DOT) com
(which would be the safest)
However, $$$ is the best way to get myway.com to act.
Tell your user to get another ISP.
If myway.com doesn't care about spam, viruses, network abuse then they
don't care about the internet.
Vote with your feet.

Hi,

Michael Scheidell wrote:
>Message
>From: Anthony Peacock [mailto:a.peacock (AT) chime (DOT) ucl.ac.uk]
>Sent: Tuesday, July 04, 2006 5:06 AM
>To: SpamAssassin Users
>Subject: Myway.com and RFC-ignorant.org

>balance these scores out? I understand that SPF is not a sign of
>hammy/spammyness, but would I be openening up my system too much by

But maybe ignoring emails to postmaster@ and abuse@ and having no valid
whois contacts IS a sign of spammyness, and that they don't care if
their users spam, have viruses or pass along phishing emails.

Absolutely agreed! I wasn't questioning their listing in the
rfc-ignorant.org RBLs. I was just wondering out loud if anyone had
tried to convince Myway to fix their ways.

Personally I have no qualms about dropping these emails, but you know
users

Since you use SPF, you could use whitelist from spf to make sure that
you aren't allowing in forged myway.com spam.
Put this in local.cf in /etc/spamassassin directory where local config
files are.

This is now what I have done on an individual user basis. There is no
way I would whitelist the whole of myway.

I generally try to avoid whitelisting if at all possible as I think it
is a very blunt instrument and without SPF easy to fool, and adds an
administrative overhead. top of this I use SA via MailScanner so at
the moment any whitelisting was done through the MailScanner rules,
which provided me with consistent log analysis, adding a
whitelist_from_spf into the SA config messes up the reporting and
creates another file that needs maintaining.

I could whitelist these addresses in the standard MailScanner method,
but I like the idea of the extra protection against fraud that SPF provides.

or
whitelist_from_spf remoteuser (AT) myway (DOT) com
(which would be the safest)

This is what I am doing now.

However, $$$ is the best way to get myway.com to act.

Tell your user to get another ISP.

If myway.com doesn't care about spam, viruses, network abuse then they
don't care about the internet.

Vote with your feet.

Hmm! I would love to do this. I doubt whether my user would be happy
to move him and his family.