This IP address has been reported a total of 68
times from 59 distinct
sources.
134.122.88.217 was first reported on ,
and the most recent report was .
Old Reports:
The most recent abuse report for this IP address is from .
It is possible that this IP is no longer involved in abusive activities.
2024-09-14T13:14:13.037409+02:00 mail01 postfix/submission/smtpd[950331]: improper command pipelinin ... show more2024-09-14T13:14:13.037409+02:00 mail01 postfix/submission/smtpd[950331]: improper command pipelining after CONNECT from unknown[134.122.88.217]: \026\003\003\001\247\001\000\001\243\003\003\361p\264\260-!5\270iD\307\307\376t\0014\003\367Ap\f\265\307}"H0\246\244c\026\263 \207\b\366\310\242vn\343(\357\253\233"\245jjX\215\034\242\343\247~\026\342xS\301\255\347\224\000\212\000\026\0003\000g\300\236\300\242\000\236\0009\000k\300\237\300\243\000\237 show less
2024-09-13T23:15:49.352926+02:00 pingusmc postfix/submission/smtpd[921727]: improper command pipelin ... show more2024-09-13T23:15:49.352926+02:00 pingusmc postfix/submission/smtpd[921727]: improper command pipelining after CONNECT from unknown[134.122.88.217]: \026\003\003\001\246\001\000\001\242\003\003\a\022\003\212\310pI(\016\253SD\3045}\3000\244\266\212|\000\210\207\210\364*'F2T\017 \023\bk>.\304\315\003\314\351w\371\232{u\246{\317\261\251x@\202\243\n\315\347W\303\237\335\324\000\212\000\026\0003\000g\300\236\300\242\000\236\0009\000k\300\237\300\243\000\237
2024-09-13T23:15:49.365884+02:00 pingusmc postfix/submission/smtpd[921734]: improper command pipelining after CONNECT from unknown[134.122.88.217]: \026\003\003\001\246\001\000\001\242\003\003\310\002L\276\255\307\202\345Ml\3743\r=e\2565\362J@\365_\261x\347\263\317\000\234\326bk \237*Ul4\363\321\341\351j\333\202\037\250'\2333\325\204\277\027$!\342(\325\266\v\343SkW\000\212\000\005\000\004\000\a\000\300\000\204\000\272\000A\000\235\300\241\300\235\000=
2024-09-13T23:15:49.378023+02:00 pingusmc postfix/submission/smtpd[921727]: improper com
... show less