Mailhosts doesn't know a host name?

[silentlarry 0]

spam submitted:

http://www.spamcop.net/sc?id=z466507945z5b...a6cac66a2ea5eez

End result:

You have failed to configure your own mail host, from which you pop mail

Mailhost: mta1pub.gte.net ( 206.46.170.10 )

Please correct this situation - register every email address where you receive spam

No source IP address found, cannot proceed  .

The IP address of mailhost identified above DOES show up on my mailhost config as a Verizon address. While the host mta1pub.gte.net does NOT.

Have been submitting lots of spam POPed from verizon (x-gte) account (the email address is a [at]gte.net, BTW). First time I've seen this.

What's up?

Thanks

Edited May 7, 2004 by silentlarry

[Wazoo 0]

Have you followed instructions found in Ellen's Pinned post http://forum.spamcop.net/forums/index.php?showtopic=1081 or are you considering your specific issue a "general" case?

This might fall back on the global naming issue that also runs into the "internal" name changes, but ... no one "here" has access to that data, and Ellen only happens by here when she's got time (after handling all the e-mail that she's asked for) ...

[silentlarry 0]

Have you followed instructions found in Ellen's Pinned post http://forum.spamcop.net/forums/index.php?showtopic=1081 or are you considering your specific issue a "general" case?

Read it, was maybe still a bit confused on where to direct this.

I may forward this issue, not sure if it's worth bothering deputies with. There's been only the one instance.

Thanks

[Ellen 0]

Have you followed instructions found in Ellen's Pinned post http://forum.spamcop.net/forums/index.php?showtopic=1081 or are you considering your specific issue a "general" case?

Read it, was maybe still a bit confused on where to direct this.

I may forward this issue, not sure if it's worth bothering deputies with. There's been only the one instance.

Thanks

hrmmmm -- not quite sure what to do about this one other than passing it along to Julian. While you say you have only seen it a couple of times, it may become a more prevalent issue depending on how verizon passes mail around their servers.