TDC 0 Posted April 22, 2017 (edited) In recent, any email i submit to spamcop and get the same reply, anyone have an idea what maybe wrong?: Possible forgery. Supposed receiving system not associated with any of your mailhosts Will not trust this Received line. Mailhost configuration problem, identified internal IP as source Mailhost: Please correct this situation - register every email address where you receive spam No source IP address found, cannot proceed. http://www.spamcop.net/sc?id=z6372751063zd6d08a231c9afe6ed095c7b2f46332a4z http://www.spamcop.net/sc?id=z6372751064z7f8fb4a192cf4b8ecdeeb72fcc56b208z http://www.spamcop.net/sc?id=z6372751065zf8f67fac38bd584ebc8a91428704829fz http://www.spamcop.net/sc?id=z6372751066z0e5503e2514ebbe0587bb787c415c3dez http://www.spamcop.net/sc?id=z6372751067zd5a05bda370d7b5ddc1d32ea309699b5z http://www.spamcop.net/sc?id=z6372751068z2ab0d1215ccb95de27d94086839af130z I have gone back and re-register email address to no avail Edited April 22, 2017 by TDC Share this post Link to post Share on other sites
cooper02 0 Posted April 24, 2017 Experienced this issue as well. Subscribing for possible solutions. Share this post Link to post Share on other sites
AJR 0 Posted April 25, 2017 I notice that in the top Received header, your mail server is identifying itself with a private-use IP address (172.20.20.12 in the first tracking link, or 172.20.20.13 in the others.) I don't know if this will cause a problem, but I wouldn't be entirely surprised if this is throwing off Spamcop's logic, e.g. because it can't use that IP address to uniquely identify a particular server. Share this post Link to post Share on other sites
TDC 0 Posted April 28, 2017 It seem that all emails inbound is being received by 172.20.20.xx. No sure what the ISP is doing. Share this post Link to post Share on other sites
TDC 0 Posted April 28, 2017 (edited) This is what i found for a map of my email servers. I do not understand all of it. I believe my servers are 64.135.130.5 & 64.135.130.6 I started at sacoriver.net, then was purchased by pinetreenetworks.com, who was purchased by OTT. Edited April 28, 2017 by TDC Share this post Link to post Share on other sites
TDC 0 Posted May 14, 2017 Is there any solution for this issue? Share this post Link to post Share on other sites