Hi list, I suppose the log below gives a true picture - relaying denied. Jan 22 09:42:22 mand sendmail[11439]: JAA11439: ruleset=check_rcpt, arg1=<PageTeamX@aol.com>, relay=1Cust99.tnt2.richmond.in.da.uu.net [63.26.248.99], reject=550 <PageTeamX@aol.com>... Relaying denied Jan 22 09:42:24 mand sendmail[11439]: JAA11439: ruleset=check_rcpt, arg1=<Webmaster@ztry.fsnet.co.uk>, relay=1Cust99.tnt2.richmond.in.da.uu.net [63.26.248.99], reject=550 <Webmaster@ztry.fsnet.co.uk>... Relaying denied Please, inform, how to secure and check sendmail port 25 agaist such abuses. Antal
At 12:10 PM 22/01/2001 +0100, you wrote:
Hi list, I suppose the log below gives a true picture - relaying denied. Jan 22 09:42:22 mand sendmail[11439]: JAA11439: ruleset=check_rcpt, arg1=<PageTeamX@aol.com>, relay=1Cust99.tnt2.richmond.in.da.uu.net [63.26.248.99], reject=550 <PageTeamX@aol.com>... Relaying denied
Jan 22 09:42:24 mand sendmail[11439]: JAA11439: ruleset=check_rcpt, arg1=<Webmaster@ztry.fsnet.co.uk>, relay=1Cust99.tnt2.richmond.in.da.uu.net [63.26.248.99], reject=550 <Webmaster@ztry.fsnet.co.uk>... Relaying denied
Please, inform, how to secure and check sendmail port 25 agaist such abuses.
It looks to me as is sendmail is doing it's job just fine. This is exactly what is supposed to happen... --- Nix - nix@susesecurity.com SuSE-Security FAQ Maintainer http://www.susesecurity.com
Hi list, I suppose the log below gives a true picture - relaying denied. Jan 22 09:42:22 mand sendmail[11439]: JAA11439: ruleset=check_rcpt, arg1=<PageTeamX@aol.com>, relay=1Cust99.tnt2.richmond.in.da.uu.net [63.26.248.99], reject=550 <PageTeamX@aol.com>... Relaying denied
Jan 22 09:42:24 mand sendmail[11439]: JAA11439: ruleset=check_rcpt, arg1=<Webmaster@ztry.fsnet.co.uk>, relay=1Cust99.tnt2.richmond.in.da.uu.net [63.26.248.99], reject=550 <Webmaster@ztry.fsnet.co.uk>... Relaying denied
Please, inform, how to secure and check sendmail port 25
Had the problem approx 2 weeks ago. Was spammed for one week. Killed 50% of bandwidth. You already have done everything you could. Just too bad that spammers also ruin the bandwidth. I only say DoS. Just wait until the "Hurricane" is gone again. You can't do much more. Btw: send log file extract to abuse@something.uu.net (whatever it is for Hungary) and they will pull the plug of this dial up account. This is possibly the fastest way to regain bandwidth. HTH Philipp
Hello, On Mon, Jan 22, 2001 at 12:10:28PM +0100, webmaster wrote:
Hi list, I suppose the log below gives a true picture - relaying denied. Jan 22 09:42:22 mand sendmail[11439]: JAA11439: ruleset=check_rcpt, arg1=<PageTeamX@aol.com>, relay=1Cust99.tnt2.richmond.in.da.uu.net [63.26.248.99], reject=550 <PageTeamX@aol.com>... Relaying denied
Please, inform, how to secure and check sendmail port 25 agaist such abuses.
if you use sendmail only for local delivery, you can block smtp access by adding some firewall rules allowing access to smtp only for the loopback device. Greetings, Frank -- Hi! I'm the infamous .signature virus! Copy me into your ~/.signature to help me spread!
On Mon, Jan 22, 2001 at 13:05 +0100, Frank Naumann wrote:
if you use sendmail only for local delivery, you can block smtp access by adding some firewall rules allowing access to smtp only for the loopback device.
Or just don't run the daemon. There's no need to have it listening to *any* socket if you don't get mail from the net _into_ the machine. Local delivery usually invokes /usr/sbin/sendmail and should work without any daemon involved. virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you.
participants (5)
-
Frank Naumann -
Gerhard Sittig -
Nix -
Philipp Snizek -
webmaster