I really was very happy with your help and my criticism of course is not against you. But a delisting page should have clear instructions how to contact someone, if the delisting does not work, or it should give directly the reason why it does not work. All other DNSBLs do this - well I do not know about all, just a handfull I checked in the past.
My system may have problems, that I do not see, but to solve these, I need some input about the reason of beeing listed.
For example a few months ago I had a problem with mails sent to gmx.de (www.gmx.com). In their check-site there was directly noted a contact mail address. I could write a mail and got an anwser within one day and everything was solved.
I understand that a compony does not want to give to much info about the spam detection, but basic infos should be given to people like me.
Still now after 5 days and your help here I do not know why I was listed and I am sure, also you cannot check this (without doing more than you should). I assume to have found the reason, but maybe my assumption is wrong.
So, still I think Symantec as company and provider for this reputation list surely could do a better job ;-)
Original Message:
Sent: Jan 31, 2022 07:31 AM
From: alexander sanita
Subject: IP removal not working
Good man. See I helped u.
Original Message:
Sent: 1/31/2022 7:28:00 AM
From: Juergen Weiss
Subject: RE: IP removal not working
Maybe I found the problem in the Symantec check routin.
Proxmox mailgateway accepts connections on Port 26 without authentication. But it accepts only predefined IPs. Because these IPs work on the MTA level, you can connect, and send a mail, but you will get an error AFTER the data command (not allowed due to policy restrictions).
If the open proxy check does not go up to this level and expects to get an error already after the rcpt to Command, then these mailgateways always look like open proxies but they aren't.
From my point of view the check routine - if it is working as expected - is error prone, which should not happen on such a large company!!!!!
Original Message:
Sent: Jan 27, 2022 10:30 AM
From: alexander sanita
Subject: IP removal not working
What ip / domains can u NOT send to?
Original Message:
Sent: 1/27/2022 10:16:00 AM
From: Juergen Weiss
Subject: RE: IP removal not working
My IP still shows up to have a bad reputation, with the notes "snow shoe" and "unauthorized". Seems that the team who checks the delisting requests still does not like my system. I have about 20 mails in my queues that cannot be delivered, due to this bad reputation.
Is there any chance to get detailed infos about the reason, why my IP gets listed.
I am concerned about the open relay policy. This proxmox mailgateway has the concept that predifined IPs are allowed to send without further authentication (but only on Port 26). So I have defined about 30 IPs from my customers that are allowed to send. No other IP can send. From my point of view this concept is very safe. Is it possible that the check routine detects this as an open relay (though I cannot imagine how this could be checked).
I am a little bit at a loss what to do
Original Message:
Sent: Jan 26, 2022 11:47 AM
From: Juergen Weiss
Subject: IP removal not working
Ok, will do that. Again I appreciate your great help here!!!!
Original Message:
Sent: Jan 26, 2022 11:24 AM
From: alexander sanita
Subject: IP removal not working
Once off the bad list, keep watching for 24 hours. And monitor your queues.
Original Message:
Sent: 1/26/2022 11:23:00 AM
From: Juergen Weiss
Subject: RE: IP removal not working
Ok, this makes sense to me. I set this values now, restarted postfix and again I made a delisting request. How long will it take until the delisting is investigated and the IP removed?
Original Message:
Sent: Jan 26, 2022 10:51 AM
From: alexander sanita
Subject: IP removal not working
Your values are too high. Use these and try please
This are the settings in postfix config:
default_destination_concurrency_limit = 10
lmtp_destination_concurrency_limit = 10
relay_destination_concurrency_limit = 20
smtp_destination_concurrency_limit = 10
virtual_destination_concurrency_limit = 10
Original Message:
Sent: 1/26/2022 10:39:00 AM
From: Juergen Weiss
Subject: RE: IP removal not working
This are the settings in postfix config:
default_destination_concurrency_limit = 40
lmtp_destination_concurrency_limit = 20
relay_destination_concurrency_limit = 20
smtp_destination_concurrency_limit = 20
virtual_destination_concurrency_limit = 20
Original Message:
Sent: Jan 26, 2022 10:00 AM
From: alexander sanita
Subject: IP removal not working
What is the sending rate limits of your mta's???
Original Message:
Sent: 1/26/2022 9:48:00 AM
From: Juergen Weiss
Subject: RE: IP removal not working
I'm not sure what you are meaning. I do not use any symantec product. My system is this one https://www.proxmox.com/en/proxmox-mail-gateway
It is used by several customers form me, you can say I am a very small hosting-provider.
The system uses the hostname mailgateway.wwweiss.de, setup for IP4 and IP6. Reverse-DNS is set correctly and the helo is the same as the hostname. From the technical part the system is an debian system running postfix, spamassassin and clamav. The system is running for more than 2 years without problems. End of last year I only switched the server and thereby got a new IP address. After that I thought the problem may be caused by the previous usage of the IP. But now it is clear that mails going out from my system caused this bad reputation.
Which details do you want to see?
Original Message:
Sent: Jan 26, 2022 06:33 AM
From: alexander sanita
Subject: IP removal not working
Show us what your delivery settings are under smtp, advanced.
Original Message:
Sent: 1/26/2022 6:29:00 AM
From: Juergen Weiss
Subject: RE: IP removal not working
I come back to this discussion because the same thing happens again. Our server again is listed with bad reputation. Seems that our server is doing something that Symantec does not like. I am sure that our server does not send Spam, but we have customers sending out mass mails (the customers are chambers of engineers sending infomails to there members - typically about 10.000 mails).
Is it possible that this might cause these problems?
Anyway, it would be very helpful to get the reason for this bad reputation. And of course it would be helpful if we would get any response when using the delisting site.
I am not using any symantec products, so I can't find a way to get in contact with any supporter. Last time you were very helpful, maybe you can give me some tipps how to solve my problem? Don't want to make this discussion to an endless loop ;-)
Original Message:
Sent: Dec 24, 2021 06:25 AM
From: alexander sanita
Subject: IP removal not working
Woohoo
Original Message:
Sent: 12/24/2021 6:25:00 AM
From: Juergen Weiss
Subject: RE: IP removal not working
Sorry, due to a very limitd time, I really was not aware of your "doing" - so I really thank you very, very much for that! It made my day much better :-)
Original Message:
Sent: Dec 24, 2021 05:29 AM
From: alexander sanita
Subject: IP removal not working
U can thank me for that.
Original Message:
Sent: 12/24/2021 1:25:00 AM
From: Juergen Weiss
Subject: RE: IP removal not working
Ok, I thought I cannot do that, because I am not using any Brodcom products. But the problem has gone, after serveral days our IP now has been removed from the bad reputation list - it's christmas time :-)
Original Message:
Sent: Dec 23, 2021 07:39 PM
From: alexander sanita
Subject: IP removal not working
Open a support case.
Original Message:
Sent: 12/23/2021 11:21:00 AM
From: Juergen Weiss
Subject: IP removal not working
We are running a mailserver for a few customers. The server is properly configured and not listed on any DNSBL. It is not sending out spam and I spend a lot of time so that it will never do this.
But if I check on the reputation of our IP (116.202.14.71) your system tells me it has a negative reputation. Therefore I used the form to get removed. But nothing happens. I tried this removal 5 Times within the last 3 days, but nothing happens.
Can anybody help - maybe I am doing something wrong. But there are not really much options on the form, so I really have no idea what to do.