Re: [ossec-list] authenticated smtp usage...

2015-06-17 Thread dan (ddp)
On Mon, Jun 15, 2015 at 10:16 AM, Mark Feferman  wrote:
> I know this topic has been discussed many times, but I'm not sure why it
> isn't implemented.
>
> send_from_email_username
> email_password
>
> Granted, there are going to be issues sending to smtp servers that require
> SSL/TLS, etc.., but that's far less of an issue (i.e., finding one that
> doesn't require SSL/TLS) that finding one that doesn't require
> authentication.
>
> I understand the security aspect, but the database credentials are already
> stored there in plain text.
>
> $.02
>

Using a local smtpd to handle that kind of thing makes more sense to
me. That's a common feature in a product designed to deliver email.
Let the experts do it.

> --
>
> ---
> 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.

-- 

--- 
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.


Re: [ossec-list] authenticated smtp usage...

2015-06-15 Thread Eero Volotinen
How about using postix on localhost? Much better solution..
On Jun 15, 2015 6:04 PM, "Mark Feferman"  wrote:

> I know this topic has been discussed many times, but I'm not sure why it
> isn't implemented.
>
> send_from_email_username
> email_password
>
> Granted, there are going to be issues sending to smtp servers that require
> SSL/TLS, etc.., but that's far less of an issue (i.e., finding one that
> doesn't require SSL/TLS) that finding one that doesn't require
> authentication.
>
> I understand the security aspect, but the database credentials are already
> stored there in plain text.
>
> $.02
>
>  --
>
> ---
> 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.
>

-- 

--- 
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] authenticated smtp usage...

2015-06-15 Thread Mark Feferman
I know this topic has been discussed many times, but I'm not sure why it 
isn't implemented.

send_from_email_username
email_password

Granted, there are going to be issues sending to smtp servers that require 
SSL/TLS, etc.., but that's far less of an issue (i.e., finding one that 
doesn't require SSL/TLS) that finding one that doesn't require 
authentication.

I understand the security aspect, but the database credentials are already 
stored there in plain text.

$.02

-- 

--- 
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.