Jump to content

jase

Members
  • Content Count

    9
  • Joined

  • Last visited

Community Reputation

0 Neutral

About jase

  • Rank
    Newbie
  1. jase

    mailtrap?

    Telstra are highly unlikely to fix this easily either as at some stage during the process they may have to admit fault to someone.
  2. jase

    mailtrap?

    Thanks JeffG, A good idea. I did a search in the logs of the firewall and compared them to the outbound logs of the smtp service, and they were congruent. I believed (yet to prove) that the ip was soiled prior to me getting it. I'm seeing ALOT of bigpond/telstra IP's in that range showing up.
  3. Thousands of people on the network ARE being effected. None of those ip's are static either. I think its a flaw in reporting system.
  4. jase

    mailtrap?

    Don't get too confused Wazoo........block is gone now. I'd just like to see some concrete of what caused it in the first place.
  5. jase

    mailtrap?

    Jeff g --> Yep, I agree! (afaik - wazoo ) I have the external interface of the mailserver in the same subnet as the router, and the clients on a seperate subnet (and a second net adapter in the mailserver for the client subnet). The firewall only allows that subnet. Sorry Wazoo (and Ellen) I'm not that familiar with spamtraps. I didn't realise they were not (but can now see why) public knowledge. I have looked through the outbound logs and can't see anything I wouldn't expect. I really just have to wait this out I spose.
  6. jase

    mailtrap?

    Google just came back with over 35,900 hits. First page included people that use them, people that want to declare war on them, and people that explain them. That you're playing from a non-static IP has you screwed from the viewpoint that you'ne no idea who had it last. So the issue may not be you at all (but of course, "we" have no idea of the timing involved .... No accusations, but you won't believe the people that have barged in and said "ain't no way my system/network is screwed up" only to find that yep, there was a Trojanized computer in the sales office, yep, the super-secure e-mail app was actually 17 revisions away from current due to hacking issues, yep, some idiot had re-installed some major package and left all thje default passwords in place .... it just would have been nicer to see the words "to the best of my knowledge" in your last .... Yep, Wazoo, reading it, I can see how it sounds. I'm too used to being the one getting asked the dumb questions.....I'm sure you know how that is. I forgot the count in the left column has me at less than 5 posts. I did do a search on google before I asked the question....What I meant was can I see the logs etc of my supposed breach in relation to a mailtrap?
  7. jase

    mailtrap?

    Merlyn -> I'm using dynamic while I'm waiting for a static to be allocated. I have no open proxy on that machine. (as I have no proxy on that machine). There is no malware on the PC's connect to that mailserver. Only the internal side has access to the mailserver, and they have whitelisted internet access only. I can see why you believe no-one should accept mail from that server. But I don't agree. Sorry. Cheers for the RFC wakeup Spambo, I'll probably leave that till the static is done though. I greatly appreciate your comments. There's still very little info on this actual block. I get concerned when blacklist blocks get made with grey. Where can I find out more about the "spamtraps"?
  8. jase

    mailtrap?

    Help & Feedback Site Map Statistics Query bl.spamcop.net - 144.139.33.146 DNS error: 144.139.33.146 has no reverse dns Just as additional info: (Help) (Trace IP) (Senderbase lookup) 144.139.33.146 listed in bl.spamcop.net (127.0.0.2) Since SpamCop started counting, this system has been reported less than 10 times by less than 10 users. It has been listed for 34 hours. In the past week, this system has: Been detected sending mail to spam traps Other hosts in this "neighborhood" with spam reports: 144.139.33.3 144.139.33.31 144.139.33.52 144.139.34.31 144.139.34.101
  9. jase

    mailtrap?

    Hi, I have an mailserver blocked on 144.139.33.146 for sending mail to mailtraps. The ip address that is blocked is not a static ip. There's nothing in ordb etc about the ip being blocked. (It can't be relay, it has no externally reachable smtp service) I fixed open relays before, but maybe I don't understand this....it seems pretty silly right now. Jase
×