ConfigServer Community Forum

I asked them. I got a statement of "it's required, so if you don't like that, don't use MSFE. They did say they'd possibly look into honoring existing settings, but with my request the only likely one for this, I don't hold much hope. I'll look back to see how long there is between updates to i...

I'm running MSFE on a VPS that doesn't have enough RAM to run CLAMav, and it keeps crashing as a result. The mail passing through this is only for myself, and I have local AV I'm relying on, so can live without a scanner on the server. Problem is, every time MSFE updates, CLAM is put back. I had it ...

Currently running csf: v9.30 and get these messages all the time from mailman.

LOCALHOSTRELAY, IPv6 localhost - ::1
I've tried adding mailman, list-email, list-email-bounces (both of those redacted), to no avail.
Is it possible to get CSF to stop complaining about these mailman sends?

As usual, post about something, and shortly after find the answer. Should anyone else be looking for this: http://www.configserver.com/techfaq/index.php?faqid=6

Tested and confirmed.

Recently had MSFE and Mailscanner installed on a new server, and I've notice that this one does not show a block at the bottom of each message (when you click the "#" to view an individual message) like it does on all the other servers I use it on. It's an extra section at the very bottom ...

Ok, seems to be working with my experimental alternation. authenticator failed for.*|\s+\(ylmf-pc\) The ".*" catches the reverse IP string, and the "\s+" manages the spaces if the first one fails to match; so it caught two, one after the other. Example A: 2014-09-25 09:29:11 cour...

That would match a space, but then we lose the string it has been currently catching. Will this accept alternation? The following *should* see the space *or* space-string-space, no? authenticator failed for.*|\s+\(ylmf-pc\) Maybe that needs to be enclosed? authenticator failed for(.*|\s+)\(ylmf-pc\)

Well, yes and no. The ones with the additional info are being caught, but ones without are being missed. This one was picked up by LFD after the number of attempts specified in the config, but not by this tweak. 2014-09-24 19:06:53 courier_login authenticator failed for (ylmf-pc) [202.53.73.36]:5435...

please let me know if it works for you. Thank you, Sergio. Had one come in after this change with the reverse IP in it and it blocked it perfectly. I have seen a few come in with the reverse missing before this change, but looking at your update that should also be caught now. Thank you for all you...

I had a direct rule just for YLMF-PC attacks and I have just added to the REGEX sticky, please check it at: http://forum.configserver.com/viewtopic.php?f=6&t=7517&start=10#p22150 Any chance you have a version for Courier? Seems that adds content before the ylmc section that's throwing it of...