Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 27 subscribers
  • Views 2321 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Identify cause of Backscatterer-Listing

oxident

Hello!

I'm getting listed on backscatterer.org every few days (!) but I can't find any cause for this. The only mailserver running behind the XG shows absolutely no activity around the time (+/- 10min), backscatterer.org tells me. I've already blocked outgoing SMTP traffic for every other host and even created a single rule, just for outgoing SMTP traffic in order to study the XG log afterwards ... but still, no evidence of any abusive usage.

I suspect that the XG's SMTP-Proxy (I'm not running MTA mode) is somehow sending bounces (that don't even reach my actual mailserver) to forged addresses or something like that. But I haven't configured any rule which may return undeliverable mail to the sender.

Is there anything I can do to test this or any other logs where I could "spot" these bounces?

I guess backscatterer.org won't tell me any more details.

Thanks for any help!



This thread was automatically locked due to age.
Parents
  • 0

    First of all, would suggest to run a Dump Port 25 to get a clue, if you XG or some client is connecting via Port 25. 

    If you find some information about Port 25, you should try to find the reason (client behind XG or XG itself). 

    Do you use Notification of XG? Maybe you have a wrong configuration of notifications. 

Reply
  • 0

    First of all, would suggest to run a Dump Port 25 to get a clue, if you XG or some client is connecting via Port 25. 

    If you find some information about Port 25, you should try to find the reason (client behind XG or XG itself). 

    Do you use Notification of XG? Maybe you have a wrong configuration of notifications. 

Children
No Data