How to know if I'm blacklisted (SOLVED)

[Glenn Steen]

On 18/01/2008, Matt Kettler <mkettler at evi-inc.com> wrote:
> Juan Pablo Lorier wrote:
> > Hi everybody,
> >
> > Thanks for your help, especially to Matt Kettler who really took some
> > time to research things for me.
> > Matt, I know the header is wrong, but in fact is a testing server that
> > made it's way to production when we had our mail server to crash, so
> > configs are not what should be. As I use Scalix as mail server, it's not
> > that easy to change hostname and settings so what we are doing is
> > building a real server to change the emergency one.
> > Thanks again for the great info you gave me, I'm also quite new in this
> > mail stuff and I've been realizing for some time that is a world in it's
> > own, so the best of your answer is that I learnt a lot from it.
> > Thanks and regards.
>
>
> You're welcome, and thank you.
>
> It's also given me an opportunity to explore some of the actual requirements
> with Glenn. Which is good.
>
> I've now learned it is legal to refuse them if they're syntactically invalid,
> because such a HELO would cause your server to violate format requirements for
> Received: headers.
>
> The rest, we're still exploring. It will be interesting to see where we end up.
>
Unfortunately, that is likely as far as we'll get... But that in and
of itself isn't bad... That one can use a cheap syntactical check to
refuse crud is ... very good indeed.
I'll give you some numbers, come Monday... There used to be quite a
few valid senders falling afoul of stuff like this, but ... a friendly
reminder to be RFC-compliant to the admin usually sorted that, so
now... It's (almost) only spammers falling afoul of this.

We'll see, perhaps there is more to be found in the treasure trove of
RFCs:-):-).
Cheers
-- 
-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se