Hi list,
Do anybody here have successfully implemented fail2ban for vpopmail. I tried
by following this way:
http://www.mail-archive.com/qmailtoaster-list@qmailtoaster.com/msg23954.html
but not working. Can anybody help me out to resolve the same.
Regards,
Vidyadhar
Hello,
Works like a dream here.
What is your OS, version
Error messages?
B/R
Ole J
_
From: Vidyadhar [mailto:vidyadha...@gmail.com]
Sent: 30. oktober 2009 11:41
To: qmailtoaster-list@qmailtoaster.com
Subject: [qmailtoaster] fail2ban query
Hi list,
Do anybody here
Hi
OS : CentOS:5.3
Enabled log of fail2ban.
2009-10-18 04:02:07,988 fail2ban.filter : INFO Log rotation detected for
/var/log/maillog
2009-10-18 04:02:07,990 fail2ban.filter : INFO Log rotation detected for
/var/log/maillog
2009-10-18 04:04:09,985 fail2ban.filter : INFO Log rotation
I think i need to see your conf files for fail2ban.
You may send it directly to my email address.
_
From: Vidyadhar [mailto:vidyadha...@gmail.com]
Sent: 30. oktober 2009 12:28
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] fail2ban query
Hi
OS : CentOS:5.3
Dear All,
I have setup DKIM as per instution in the DKIM video. Everything is setup
correctly but still when i see mail hearders on yahoo or gmail i see
Authentication-Results: mta164.mail.in.yahoo.com from=gnvfc.net;
domainkeys=pass (ok); from=mail.gnvfc.net; dkim=permerror (no key)
I too am getting similar errors and it has never worked for my qmail
installation. It works for Proftpd and ssh just fine. Although in this
snippet it shows a ProFTPD error too. Little or no info out there to
resolve this.
2009-10-30 09:01:02,004 fail2ban.actions.action: ERROR iptables
W dniu 06.10.2009 15:28, Aleksander Podsiadly pisze:
On my office servers I have Dovecot one year but I didn't know how it
is fast.
[...]
A little change to previous dovecot.conf patch. I modified some lines
for imap/vpopmail quota support. Now it works like with original QMT and
Eric Broch wrote:
Hello list,
I had a client ask me if there was any way to create a shared email
folder that all IMAP clients could access and store project email.
My first thought was to create a symbolic link in each email clients
folder.
Has anyone ever heard of such a
Thanks, Aleksander.
I wonder if there isn't some way to specify a variable of some sort in
the dovecot.conf file that will pick up the difference between 32 and 64
bit environments. How are other packages handling this? We typically
don't/shouldn't need to change a configuration file for
Eric Shubert wrote:
I'd like to know if this works, but I don't expect it will.
I believe that chkuser is not finding an MX record for the
backup.mydomain.com domain, and this cannot be specified in the hosts
file. An MX record for backup.mydomain.dom would need to be added to
the
Anil Aliyan wrote:
Dear All,
I have setup DKIM as per instution in the DKIM video. Everything is
setup correctly but still when i see mail hearders on yahoo or gmail i see
Authentication-Results: mta164.mail.in.yahoo.com from=gnvfc.net;
domainkeys=pass (ok); from=mail.gnvfc.net;
Eric Shubert wrote:
Thanks, Aleksander.
I wonder if there isn't some way to specify a variable of some sort in
the dovecot.conf file that will pick up the difference between 32 and
64 bit environments. How are other packages handling this? We
typically don't/shouldn't need to change a
Noel Rivera (Border Less) wrote:
Jake, when we install this update?
Whenever you wish. When I put a new version online, I usually do not put
it in the current.txt file for 24 hours (qtp-newmodel knows a new
package is released by looking at this file). This way it gives me (and
a couple
Maxwell Smart wrote:
Like this?
ip.of.server.dotted:allow,RELAYCLIENT=,DKSIGN=/var/qmail/control/domainkeys/%/private,RBLSMTPD=,NOP0FCHECK=1
ip.of.server.dotted:allow
If you want to apply a line to multiple consecutive hosts, you can do this:
192.168.1.:allow,[whatever-else]
This
Jake Vickers wrote:
Eric Shubert wrote:
Thanks, Aleksander.
I wonder if there isn't some way to specify a variable of some sort in
the dovecot.conf file that will pick up the difference between 32 and
64 bit environments. How are other packages handling this? We
typically don't/shouldn't
W dniu 30.10.2009 17:42, Eric Shubert pisze:
Thanks, Aleksander.
I wonder if there isn't some way to specify a variable of some sort in
the dovecot.conf file that will pick up the difference between 32 and
64 bit environments. How are other packages handling this? We
typically
You may send me the conf files directly to me.
I need to know your OS and version.
Currently running it for ssh, pop3, proftp on Centos 5
But will be away for the weekend so you wont get any answers from before
monday.
I too am getting similar errors and it has never worked for my qmail
Jake Vickers wrote:
Eric Shubert wrote:
I'd like to know if this works, but I don't expect it will.
I believe that chkuser is not finding an MX record for the
backup.mydomain.com domain, and this cannot be specified in the hosts
file. An MX record for backup.mydomain.dom would need to be
Jakes,
Please find the config file attached with this mail.
I have not changed anything in the conf file and i copied it as it is in the
/var/qmail/control/dkim folder persmission are:
-rw-r--r-- 1 qmailr qmail 891 Oct 29 17:06 global.key
-rw-r--r-- 1 qmailr qmail 241 Oct 29 17:07 public.txt
Aleksander Podsiadly wrote:
W dniu 30.10.2009 17:42, Eric Shubert pisze:
Thanks, Aleksander.
I wonder if there isn't some way to specify a variable of some sort in
the dovecot.conf file that will pick up the difference between 32 and
64 bit environments. How are other packages handling this?
W dniu 30.10.2009 18:32, Eric Shubert pisze:
While I agree with your position and hypothetical scenario, I don't
believe that adding an MX record for each host is the correct nor best
solution.
I don't see any purpose in adding an MX record for each host that
sends email. [...]
That's
Thanks Jake.
-Original Message-
From: Jake Vickers [mailto:j...@qmailtoaster.com]
Sent: Friday, October 30, 2009 9:51 AM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] clamav-toaster-0.95.2-1.3.31 released
Noel Rivera (Border Less) wrote:
Jake, when we install this
Eric Shubert wrote:
Jake Vickers wrote:
Eric Shubert wrote:
Thanks, Aleksander.
I wonder if there isn't some way to specify a variable of some sort
in the dovecot.conf file that will pick up the difference between 32
and 64 bit environments. How are other packages handling this? We
Aleksander Podsiadly wrote:
W dniu 30.10.2009 18:32, Eric Shubert pisze:
While I agree with your position and hypothetical scenario, I don't
believe that adding an MX record for each host is the correct nor best
solution.
I don't see any purpose in adding an MX record for each host that
Jake Vickers wrote:
Eric Shubert wrote:
Jake Vickers wrote:
Eric Shubert wrote:
Thanks, Aleksander.
I wonder if there isn't some way to specify a variable of some sort
in the dovecot.conf file that will pick up the difference between 32
and 64 bit environments. How are other packages
W dniu 30.10.2009 20:43, Eric Shubert pisze:
I'm not (necessarily) disputing that. I believe that the sending
server should probably not have the host name included in the address
after the @. IE @host.domain.com should simply be @domain.com, and
this is configured on the sending server.
Eric Shubert wrote:
While I agree with your position and hypothetical scenario, I don't
believe that adding an MX record for each host is the correct nor best
solution.
I don't see any purpose in adding an MX record for each host that
sends email. An MX record is intended as an indication
OK, here's my setup, slightly different, but seems to be same issue. I
have a production mail server it's working perfectly fine. I have a
test server on the LAN 192.168.0.195 I want it to be able to send the
logwatch e mails to my address on my production server, but I get this
error.
Jake Vickers wrote:
Eric Shubert wrote:
While I agree with your position and hypothetical scenario, I don't
believe that adding an MX record for each host is the correct nor best
solution.
I don't see any purpose in adding an MX record for each host that
sends email. An MX record is
I believe that the correct way is to configure the test server to use a
valid domain in the sender address.
It's also a good idea to configure the test server to authenticate
itself as well.
How you do this depends on which mail software the server uses.
Maxwell Smart wrote:
OK, here's my
Don't know if this is what you are looking for, but I have a server
with an private ip of 192.168.5.15 (pluto) running sendmail. I have a
qmt server with private ip address 192.168.5.2 (mercury). I want to
send all email (both local and remote) from pluto through mercury. I
do the
Jakes,
Please find the config file attached with this mail.
I have not changed anything in the conf file and i copied it as it is in the
/var/qmail/control/dkim folder persmission are:
-rw-r--r-- 1 qmailr qmail 891 Oct 29 17:06 global.key
-rw-r--r-- 1 qmailr qmail 241 Oct 29 17:07 public.txt
Ole,
I have attached the fail2ban.conf and the jail.conf file. I am running
the following:
* uname -a*
Linux laetitia.area510.net 2.6.18-128.7.1.el5 #1 SMP Mon Aug 24 08:20:55
EDT 2009 i686 athlon i386 GNU/Linux
* rpm -qa|grep release*
remi-release-5-4.el5.remi
centos-release-notes-5.4-4
Sorry fellas, You can ignore that.
Maxwell Smart wrote:
Ole,
I have attached the fail2ban.conf and the jail.conf file. I am running
the following:
* uname -a*
Linux laetitia.area510.net 2.6.18-128.7.1.el5 #1 SMP Mon Aug 24 08:20:55
EDT 2009 i686 athlon i386 GNU/Linux
* rpm -qa|grep
I have a qmailToaster acting as a filter in front of an Exchange
server. No mail is kept locally, everything is forwarded to the
Exchange server.
Since the toaster doesn't know about the accounts on the Exchange server
it can't block inbound messages for unknown addresses during
Brent,
With my limited knowledge, I think Spamdyke on the toaster will weed out
a considerable amount of unwanted e mails. It will likely require some
modified config settings, but should work. Several others on the list
know much more about this than me.
Brent Gardner wrote:
I have a
36 matches
Mail list logo
