Recent content by kiddx

Thanks for the help everyone, unfortunately the boss came and said to remove it. I tried to explain it must be an issue with the senders email (they are sending https redirects) but since our attorney now went and got a yahoo address and he gets them all he came back and said it must be...

I understand that proxmox doesnt, however in my logs I get an error connecting to 127.0.0.1:10022. this is listed under the postfix/main.cf check_policy option. If I comment it out then everything works okay. if I turn greylisting back on in the proxmox GUI, this config file gets changed and...

Okay, we have isolated the issue but not sure what to do about it... this morning the same problem came back, when we went into /etc/postfix/main.cf there is check_policy_service = inet:127.0.0.1:10022 <--- this is the exact area we get in tracking center. I commented this out again, then when...

heh, I did some digging around about postgrey, and found mention of editing main.cf for postfix with check_policy_service inet:127.0.0.1:10022 This was my error we started getting a few days ago. I forget where the conf file was, it was in /etc , we grepped the whole system for the...

Okay, after a little digging we found an item in the postfix conf file that says to use the postgrey, we commented that line out and hopefully tomorrow we will verify its working okay. Thanks

from the gui all services are running, mail is flowing fine but we now have 3 clients who have sent us mail and that did not fix it. We thought it was just one initially so didnt think too much about it, but now today its 2 more ... i have rebooted prox stopped/started services in the GUI ... i...

Okay, have a few more with the same issue that we didnt know about. In reading this is a postgrey corruption issue, so i was hoping to ssh in and move the postgrey db out, but doesnt look like its where the default is, searching the whole box for *grey* doesn't seem to show me anything ...

Prox is working fine for us except from one client who sends us mail from a large hospital group, we used to get their email no problem. everything else seems to be working okay, mail is flowing fine. timeout on 127.0.0.1:10022 while reading input attribute value Nov 2 08:53:42 smtpd...

Thanks Tom, I turned on email notices and was getting occasional notices, so that was definitley it.

Just as a follow up, we had to enable the anti-spam features of Exchange 2010, they have a filter active directory option like 2003/2007, however the results were still failing from proxmox so we had to disable this feature. We did not have the server LDAP integrated or anything like that ...

I always just assumed this was working for me. I turned on notify admin, and although i have seen about 100 connections from various .ru sites I havent recieved one notice. Maybe I just dont have it set right. this is set to 98 and is the top rule on my list. Mail is still getting to the verify...

this seems to have been working for along time, we have .*@*.ru and many other root level domains blocked. Nothing has changed on config but today we were spewing mail out to aol , hotmail etc, and didnt get blacklisted but our sender score dropped 20 points. I see alot of this coming from .ru...

We upgrade from exchange 2007 to 2010 and started getting unverified address. I notice when i turn off verify recievers then it works. this worked in 2003 and 2007, so probably something on exchange side just not sure how to enable it again.. thanks