hello friends
how to achieve the following using empf
i want to prevent misuse of my mail servers by means of masquerading -- ie
user authenticates as user @ domain_on_my_server.com plus password but
changes the mail from to user @ yahoo.com etc ... i had several incidences
of such a kind of
Rajesh,
I don't think empf can help with your issue. empf defines who an authenticated
user can send and receive emails to and from. Since the user is
authenticating, empf will not help.
Are you sure the email is being sent from your server? Can you actually
see the email going out through
hello
for all who have blackberry issues with chkuser
go to /etc/tcprules.d
open tcprules.smtp
copy paste the ips below into your tcp.smtp file and compile
# tcprules tcp.smtp.cdb tcp.smtp.tmp tcp.smtp
restart qmail
the ips below are from
http://www.blackberry.com/btsc/KB11036
Rajesh M wrote:
hello
for all who have blackberry issues with chkuser
go to /etc/tcprules.d
open tcprules.smtp
copy paste the ips below into your tcp.smtp file and compile
# tcprules tcp.smtp.cdb tcp.smtp.tmp tcp.smtp
restart qmail
the ips below are from
Thanks Jake.
Ok I added the NOP0FCHECK to each line in my tcp.smtp file and compiled
tcp.smtp cdb.
127.:allow,RELAYCLIENT=,DKSIGN=/var/qmail/control/domainkeys/%/private,RBLSMTPD=,NOP0FCHECK=1
192.168.105.:allow,SENDER_NOCHECK=1,RELAYCLIENT=,RBLSMTPD=,NOP0FCHECK=1
spamdyke's detailed logging facility is sweet. It logs the full session
much like recordio, but puts each session in its own file so it's a lot
easier to find what you're interested in. Also easier to turn on and
off. FWIW
d...@acbsco.com wrote:
Thanks Jake.
Ok I added the NOP0FCHECK to each
Have you changed the password for the compromised user?
d...@acbsco.com wrote:
Rajesh,
I don't think empf can help with your issue. empf defines who an
/authenticated/ user can send and receive emails to and from. Since the
user is authenticating, empf will not help.
Are you sure the email
Eric, I think this is the person you were referring to on the
development list regarding the 127. hole. Rajesh, you may want to
review Eric's post on the development list with subject squirrelmail,
tcp configuration tweaks. If you use spamdyke, this may help.
Dave
Eric Shubert wrote:
Have you
Everything about it is simple and easy (only not gui). Setting up
differing configurations for different domains is a little tricky, but
that's about the toughest thing you'd do with it, and it's rarely needed.
qtp-install-spamdyke does all of the work for you. Read the wiki page
hi
yes i am positive that all the spam was sent thru my server.
this company has a office server with fetchmail, around 300 users aliased
to a catchall account.
some spammer hacked into their server, put a script which shot of spam
email and landed my server blacklisted by barracudanetworks and
That sounds pretty nasty. Changing the password and using iptables to
block are the only mechanisms I'm aware of in the toaster.
Making the 'from' address adhere to certain rules seems reasonable to
me. I would think that eMPF would have such a thing, but on first glance
I don't see that it
11 matches
Mail list logo
