Cloudmark Lookup During List Import Referencing Removed IP

liquidfuse

New Member
Hello,

I'm trying to track down where MailWizz may still be caching or referencing an old sending IP address that is no longer configured anywhere in my current setup.

The issue specifically happens during list imports.

When importing a new list, MailWizz appears to still perform Cloudmark-related checks against an old IP address that is no longer active or assigned to any current delivery server.

Example message/log reference:
"Cloudmark Sender Intelligence lookup/check for IP 159.183.67.23"

That IP is no longer being used anywhere in my active configuration. Also, when I check cloudmark, it's noit listed anymore.
1778699004245.png

Background:

  • The IP was previously used in an older sending configuration.
  • It has since been completely removed from active use.
  • The IP is no longer attached to any delivery server, bounce server, or sending domain.
  • Despite this, Cloudmark-related checks during imports still seem tied to that old IP.
What I've already checked:

  • Delivery servers
  • Bounce servers
  • Sending domains
  • Tracking domains
  • Cron jobs
  • General MailWizz settings
I also searched portions of the database manually and still found some historical references tied to old records/logs.

My questions are:

  1. Does MailWizz cache Cloudmark or blacklist-related IP data internally?
  2. During list imports, where does MailWizz determine which IP to use for Cloudmark/reputation checks?
  3. Are there specific database tables, cache directories, queue tables, or import-related logs that could continue referencing a removed IP?
  4. Is there a recommended cleanup process for fully removing legacy IP references from MailWizz?
I'm mainly trying to determine where this old IP could still be stored or referenced during the import validation/import process.

Any guidance would be appreciated.
 
Back
Top