Re: [ossec-list] I want to hack my ossec-agent by metasploit!

2015-12-20 Thread 林威任
Thanks for Dan and Santiage
I will try again.
Thank you!!!

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"ossec-list" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ossec-list+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[ossec-list] ossec-maild Error Sending email to 127.0.0.1

2015-12-20 Thread theresa mic-snare
Hi everyone,

today I've noticed a problem with the ossec-maild process.
The ossec.log keeps saying

ossec-maild(1223): ERROR: Error Sending email to 127.0.0.1 (smtp server)

Of course I started troubleshooting the problem and tried to send several 
test-emails from the ossec master.
I'm using ssmtp through my google-mail account by the way.
All test mails that I sent arrived immediately, so sending mails through my 
MTA seems to work as usual.

Then I checked the mail log /var/log/maillog-20151220
which to my surprise has the latest mail entry from yesterday 19:30
Dec 19 19:30:03 tron sSMTP[3943]: Sent mail for b...@bla.org (221 2.0.0 
closing connection u126sm11888435wme.3 - gsmtp) uid=48 username=apache 
outbytes=1898

changed the email address to b...@bla.org for demonstration purposes...


at least the two test emails that I just send should appear in this log, 
right?

I know that the root cause to this problem is NOT an ossec problembut 
maybe you have an idea what the problem might be?
I've checked the quota settings in my gmail account, (so far only 10% 
used...) 
I've also checked the disk space on my ossec master, still 21GB left on / 
(where also /var is mounted)

so I doubt it's a quota or diskspace problem.
i've also restarted (stopped and started) ossec, to see if any zombie 
processes still allocated the filesystem, and it therefore showed that 
plenty of diskspace was available.
but even after the restart of ossec it still shows that it has plenty of 
diskspace available.

any other ideas how I could troubleshoot this problem?

thanks,
theresa

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"ossec-list" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ossec-list+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[ossec-list] Re: ossec-maild Error Sending email to 127.0.0.1

2015-12-20 Thread theresa mic-snare
oh and I should also mention that ssmtp and ossec-maild worked fine for 
many many months now...
so, yes it has worked in the past just fine.

Am Sonntag, 20. Dezember 2015 13:50:27 UTC+1 schrieb theresa mic-snare:
>
> Hi everyone,
>
> today I've noticed a problem with the ossec-maild process.
> The ossec.log keeps saying
>
> ossec-maild(1223): ERROR: Error Sending email to 127.0.0.1 (smtp server)
>
> Of course I started troubleshooting the problem and tried to send several 
> test-emails from the ossec master.
> I'm using ssmtp through my google-mail account by the way.
> All test mails that I sent arrived immediately, so sending mails through 
> my MTA seems to work as usual.
>
> Then I checked the mail log /var/log/maillog-20151220
> which to my surprise has the latest mail entry from yesterday 19:30
> Dec 19 19:30:03 tron sSMTP[3943]: Sent mail for b...@bla.org (221 2.0.0 
> closing connection u126sm11888435wme.3 - gsmtp) uid=48 username=apache 
> outbytes=1898
>
> changed the email address to b...@bla.org for demonstration purposes...
>
>
> at least the two test emails that I just send should appear in this log, 
> right?
>
> I know that the root cause to this problem is NOT an ossec problembut 
> maybe you have an idea what the problem might be?
> I've checked the quota settings in my gmail account, (so far only 10% 
> used...) 
> I've also checked the disk space on my ossec master, still 21GB left on / 
> (where also /var is mounted)
>
> so I doubt it's a quota or diskspace problem.
> i've also restarted (stopped and started) ossec, to see if any zombie 
> processes still allocated the filesystem, and it therefore showed that 
> plenty of diskspace was available.
> but even after the restart of ossec it still shows that it has plenty of 
> diskspace available.
>
> any other ideas how I could troubleshoot this problem?
>
> thanks,
> theresa
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"ossec-list" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ossec-list+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.