[Lowfer] QTH.NET mail problem

[DTX]

Good job, Ralph.

A similar situation occurred a few months ago.  It was decided (by the
infamous THEY ;-) that since many Spammers were using IP addresses from the
"residential dynamic pool" it would be a good idea to refuse all email
coming from those addresses.  Perhaps I am the only person in the world
running a personal mail server on his 24/7 connection who is not a spammer?
But rather than fight a losing battle with all the administrators sending me
similar messages, I just routed my server's smtp out to my ISP's server.
Now we are all happy again.

Gary WA6DTX
----- Original Message -----
From: "W5JGV" <w5jgv@spectrotek.com>
To: <lowfer@mailman.qth.net>
Sent: Friday, December 26, 2003 2:44 PM
Subject: RE: [Lowfer] QTH.NET mail problem


> > Kurt and Ralph
> > >has discovered their messages are blocked.  Kurt also
>
> > Are these guys getting informed by the qth net (as an
> > automatic return) why
> > this rejection is occurring?
>
> <snip>
>
> I emailed the sysadmin about my rejection, and he whitelisted my email
> address.  Here's the message I received from him about this problem...
>
> >>>message begins<<<
>
> At 09:28 PM 12/25/2003, W5JGV wrote:
> >Hello,
> >
> >Congrats on your new spam filters.  Hopefully they'll work out OK.
>
> Thanks.  They're working fine.
>
> > But - for the past several days, I get all my posts rejected with a
> >return message subject of "Undeliverable Message"  Here's one of the
> >latest rejections; maybe you can spot the problem.  I can't.  It seems
> >that the server feels the LOWFER list is not there any more...
>
>
> Dec 22 20:06:27 mailman postfix/smtpd[1453]: reject: RCPT from
> unknown[12.168.32.55]: 554 <unknown[12.168.32.55]>: Client host
> rejected: Need FQDN for Client. See http://mailman.qth.net/spamfaq.htm;
> from=<w5jgv@spectrotek.com> to=<lowfer@mailman.qth.net>
>
> This problem is caused by a misconfigured mail server on your end.
>
> When a server connects to us to send mail it's suppose to identify
> itself by sending us a FQDN (fully qualified domain name) and IP #.  The
> IP # should not fail a lookup and the lookup should match the FQDN given
> by the server.  The server used to send this message does not send a
> FQDN, just an IP# (see our mail transaction log entry above).  This
> could be compared to transmitting without giving your call sign.
>
> Leaving out the FQDN of the server is typical of spam servers where 99%
> of our spam comes from so we are now refusing connections from un-named
> servers.
>
> I'm going to white list you so you can post but if I were you I would
> contact your ISP because this problem may pop up again somewhere else.
>
> Tim
> System Admin
> QTH.NET
>
> >>>Message ends<<<
>
> 73,
>
> Ralph   W5JGV - WC2XSR/13
>
> http://www.emachine.com
>
>
>
>
> _______________________________________________
> From the Lowfer mailing list
> Send messages to: Lowfer@mailman.qth.net
> To sub/unsub visit: http://mailman.qth.net/mailman/listinfo/lowfer