

lisali
Members-
Content Count
23 -
Joined
-
Last visited
Community Reputation
0 NeutralAbout lisali
-
Rank
Member
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
"Mailhost configuration problem, identified internal IP as source" - can't submit ANY spam!
lisali replied to lisali's topic in SpamCop Reporting Help
You may be right. It's unfortunate. We're providing valuable data to Cisco (owners of SpamCop), and they don't seem to want to invest any resources to get this sorted. Sad. -
"Mailhost configuration problem, identified internal IP as source" - can't submit ANY spam!
lisali replied to lisali's topic in SpamCop Reporting Help
Done! Let's hope they fix this. Thank you! -
"Mailhost configuration problem, identified internal IP as source" - can't submit ANY spam!
lisali replied to lisali's topic in SpamCop Reporting Help
Is there anything that we can do? Is there a way to send feedback to Google? -
"Mailhost configuration problem, identified internal IP as source" - can't submit ANY spam!
lisali replied to lisali's topic in SpamCop Reporting Help
Yes! This seems to be a Gmail issue. spam not sent to Gmail seems to be parsed fine. I can't be manually editing lines for SpamCop to accept this. Why can't everyone just work together nicely? ? Is there a way for SpamCop to work around this in the meantime? -
"Mailhost configuration problem, identified internal IP as source" - can't submit ANY spam!
lisali replied to lisali's topic in SpamCop Reporting Help
Any fix or an update? -
"Mailhost configuration problem, identified internal IP as source" - can't submit ANY spam!
lisali replied to lisali's topic in SpamCop Reporting Help
Hi! Any update on this? -
"Mailhost configuration problem, identified internal IP as source" - can't submit ANY spam!
lisali replied to lisali's topic in SpamCop Reporting Help
Hi! No worries. Yes, I have configured all my mailhosts. From what I understand, this issue relates to how Gmail shows the sender/relaying IP, which confuses SpamCop. Other online tools, however, seem to parse these headers just fine. -
"Mailhost configuration problem, identified internal IP as source" - can't submit ANY spam!
lisali replied to lisali's topic in SpamCop Reporting Help
Sorry - what do you mean? In my case, I can see the original email in my reports. -
"Mailhost configuration problem, identified internal IP as source" - can't submit ANY spam!
lisali replied to lisali's topic in SpamCop Reporting Help
Hi! That seems to be the case ONLY if the email is NOT forwarded. In my case, all emails are forwarded to a catch-all address, let's call it EMAIL B. If spam was sent to EMAIL A, then forwarded to EMAIL B, only EMAIL B will be redacted in the report. I can still see the full EMAIL A in SpamCop reports, even when not logged in. -
"Mailhost configuration problem, identified internal IP as source" - can't submit ANY spam!
lisali replied to lisali's topic in SpamCop Reporting Help
Hi! If you click "view full message", it shows more details. In my case, it shows the full email that the spam was sent to, even if not logged in. As mentioned, only the final destination that the offending email is forwarded to is redacted by SpamCop. -
"Mailhost configuration problem, identified internal IP as source" - can't submit ANY spam!
lisali replied to lisali's topic in SpamCop Reporting Help
Hi! I was going to add an example, but they all seem to reveal a bit too much data, including the email the spam was sent to (only the final catch-all email seems to be redacted). Is there a way around this? -
Hi, Since about a month ago, I can't submit ANY spam. All I get, every time, is: "Mailhost configuration problem, identified internal IP as source" It seems to be a SpamCop parsing issue, as other online tools parse the same email headers correctly: https://mxtoolbox.com/EmailHeaders.aspx https://www.iptrackeronline.com/email-header-analysis.php What do I do? Thanks!
-
Thank you! I will give that a go!
-
That sucks. However, we assign every sender a unique email on our domain, to track any email leaks/spam. If an email is compromised, we change it at the source, and then set the compromised email to forward any incoming spam to SpamCop. Those emails will only ever receive spam so we don't need to check those reports. But there does not seem to be a way to do that?
-
Hi, Is there a way to avoid getting and acting on individual emails that say "SpamCop is now ready to process your spam. Use links to finish spam reporting (members use cookie-login please!)" and process all submitted spam automatically? Thanks!