[SGVLUG] E-mail "stamps" -- someone finally did it, it seems...

[Michael Proctor-Smith]

On 10/24/05, John Riehl <jcriehl at mail.jpl.nasa.gov> wrote:
> Emerson, Tom wrote:
> >> -----Original Message-----
> >> Behalf Of John Riehl
> >>
> >> By the way, I got the irritating gimme a stamp message from
> >> spindel56 at comcast.net, in response to my email on friday.  It
> >> only came
> >> this morning (10:04), which would indicate that it is not tied to his
> >> mail server, but more likely the client.
> >
> > Ahh -- good to know it wasn't an isolated event.  Did you also get some failed-to-deliver from postmaster and/or a "spamsleuth" message?
>
> Yes, besides the e-stamp message, I got a whitelist message, and a
> delivery failure message from postmast at comcast.com.   This last message
> involves mail.realtybrokeroffice.com. at first glance it looks like
> sgvlug.net sent to there, but that did something odd.

Ok just so everybody knows dslextreme will not let us use outbound
port 25. So I send sgvlug.net's email over a vpn to our server that
can use outbound port 25. All mail from sgvlug will come out throght
mail.realtybrokeroffice.com.

> In the case of spindel56, he apparently generates two messages back for
> each one in.  If you whitelisted him, and sent back each message, .....
> Because he seems to be doing this on his client system, any potential
> systemic problem should be limited by the size of his mailbox.  (any
> other messages get dinged by the system, and the error message is not
> from him....).

Well I looked at these messages and there is something weird going on
as while messages from spindel56 at comcast.net claim to me coming from
smtp.comcast.net there ip address is a dhcp address at caltech. The
reason we are getting 550 when we send to spindel56 at comcast.net is
that it probably does not exist.