headers
eL gino | 1 Oct 2004 03:47
Picon

pgsql socket ssl

Hello list,

Is it possible to connect to the PostgreSQL DB with a crypted password and in ssl mode (of course with the
right pg_hba.conf) entry?

currently i have "hide pgsql_servers = (/tmp/.s.PGSQL.5432)/db/usr/passwd" wich connects to the
database in non-ssl mode and the password is currently stored as plaintext.

--Christian.

--

-- 
## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at
http://www.exim.org/ ##
Permalink | Reply | 0 comments |
headers
Tor Slettnes | 1 Oct 2004 08:59

Re: exim+exiscan

On Thu, 2004-09-30 at 06:58, Margrit Lottmann wrote:
> On Thu, 30 Sep 2004, Odhiambo Washington wrote:
> > accept hosts = +webservers
> > 
> > Then begin the scans....
> > 
> I think ...that doesn't work right... ???
> accept in acl_smtp_rcpt is only the "ok" for the recipient check
> I have to exclude special addresses (or hosts) from acl_smtp_data
> ... there hosts option  dosn't work ...

Yes, it does.  

Put the "accept" statement _before_ any statements containing
"malware=", "spam=", etc. conditions.

For instance:

acl_smtp_data:
	...
	
	accept hosts = +webservers

        deny message = Message contains malware ($malware_name)
             malware = *

Also try:
	# exim4 -bhc your.web.server.ip

to issue SMTP commands manually and watch what happens.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Tom Kistner | 1 Oct 2004 09:52
Favicon

Re: and that is not only a disadvantage


--

-- 
## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at
http://www.exim.org/ ##
Permalink | Reply | 0 comments |
headers
Ebruntjen | 1 Oct 2004 02:46
Picon
Favicon

Exim Options Slow

I am setting up a new exim mail server and have an unexpected 
problem. There are two symptoms:

1) Sending mail is slow to initiate from clients.
2) Most surprisingly... exim command line options are slow to 
respond. exim -bp and others take about 25 - 30 seconds to show any 
results. However, exim -bV is quick as can be.

I have set rfc1413_query_timeout=0s to no avail.
I'm not doing any host_lookup at the moment.

Any ideas or pointers to a resolution would be most appreciated.

Thanks

Eric

--

-- 
## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at
http://www.exim.org/ ##
Permalink | Reply | 1 comment |
headers
Philip Hazel | 1 Oct 2004 10:24
Picon
Picon

Re: malformed address: SIZE=[529] problem on "From : " field

On Thu, 30 Sep 2004, Steve Karlsen wrote:

> While I'm getting the square brackets fixed on the content adapter - which
> will take a little time, being as it isn't my box, does anyone know how to get
> the third Exim box (4.30) in the chain, to default to smtp instead of esmtp,
> this will enable me to finish off some testing, with a temporary work around?

It is the *client*, not the server, that decides to use esmtp (by 
sending EHLO instead of HELO). You could perhaps fudge up something by 
defining an ACL for acl_smtp_helo. Unfortunately, you can't discover 
whether the client sent EHLO or HELO, but what you can do is to reject 
the first one it sends (assumed to be EHLO) and accept the second 
(assumed to be HELO). Use one of the acl_cx variables to do this.

It's a hack, but it might work.

-- 
Philip Hazel            University of Cambridge Computing Service,
ph10 <at> cus.cam.ac.uk      Cambridge, England. Phone: +44 1223 334714.
Get the Exim 4 book:    http://www.uit.co.uk/exim-book

--

-- 
## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at
http://www.exim.org/ ##
Permalink | Reply | 2 comments |
headers
Philip Hazel | 1 Oct 2004 10:25
Picon
Picon

Re: Re: Exim 4.42 sleeping "forever"

On Thu, 30 Sep 2004, Alex Kiernan wrote:

> We (think) we understand... setitimer is supposed to return EINVAL for
> non-canonical values
> (http://www.unix.org/onlinepubs/009695399/functions/setitimer.html),
> checking on Solaris 9 and FreeBSD 4.8, that is indeed the case (and
> its *not* on Fedora Core 2), so we end up going to sleep forever,
> having ignored the return from setitimer and end up waiting for an
> event which will never happen.

Thanks for the report and for the further information. I've noted it for 
investigation.

-- 
Philip Hazel            University of Cambridge Computing Service,
ph10 <at> cus.cam.ac.uk      Cambridge, England. Phone: +44 1223 334714.
Get the Exim 4 book:    http://www.uit.co.uk/exim-book

--

-- 
## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at
http://www.exim.org/ ##
Permalink | Reply | 10 comments |
headers
Steve Karlsen | 1 Oct 2004 10:46
Picon
Favicon

Re: malformed address: SIZE=[529] problem on "From : " field

Philip,

Many thanks for yr advice, I'll give it a go...

cheers

Steve

>From: Philip Hazel <ph10 <at> cus.cam.ac.uk>
>Reply-To: exim-users <at> exim.org
>To: Steve Karlsen <eximaccount <at> hotmail.com>
>CC: chris <at> eng.gla.ac.uk, exim-users <at> exim.org
>Subject: Re: [exim] malformed address: SIZE=[529] problem on "From : " 
>field
>Date: Fri, 1 Oct 2004 09:24:03 +0100 (BST)
>
>On Thu, 30 Sep 2004, Steve Karlsen wrote:
>
> > While I'm getting the square brackets fixed on the content adapter - 
>which
> > will take a little time, being as it isn't my box, does anyone know how 
>to get
> > the third Exim box (4.30) in the chain, to default to smtp instead of 
>esmtp,
> > this will enable me to finish off some testing, with a temporary work 
>around?
>
>It is the *client*, not the server, that decides to use esmtp (by
>sending EHLO instead of HELO). You could perhaps fudge up something by
>defining an ACL for acl_smtp_helo. Unfortunately, you can't discover
(Continue reading)

Permalink | Reply | 0 comments |
headers
jori.hamalainen | 1 Oct 2004 11:56
Favicon

RE: router for bounce messages

> > First information, I just fixed my situation by changing
> > senders = :     => condition = ${if 
> eq{$sender_address_domain}{} {yes}{no}}
> 
> Good.

The thing is that after a lot of config tweaking also the "senders = :" seems to work. I needed to go around
errors_to -router option by different way, and that probably that fixed also my bounce routing and this senders-stuff.

So I cannot reproduce my error mentioned earlier, and it might have been a logic-error in my configuration.

--

-- 
## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at
http://www.exim.org/ ##
Permalink | Reply | 0 comments |
headers
eL gino | 1 Oct 2004 13:06
Picon

Re: pgsql socket ssl

On Fri, 1 Oct 2004 08:56:20 +0200
Christian Vogel <chris <at> solarsystems.de> wrote:

> why would you want to run ssl over a unix-domain socket?

why not?, i don't wan't to send my password in plaintext or crypt only (i know it's local).

--Christian.

--

-- 
## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at
http://www.exim.org/ ##
Permalink | Reply | 1 comment |
headers
Wakko Warner | 1 Oct 2004 13:19

Re: pgsql socket ssl

> > why would you want to run ssl over a unix-domain socket?
> 
> why not?, i don't wan't to send my password in plaintext or crypt only (i know it's local).

That's just overhead for nothing really.  What reason would you want to
encrypt a local connection?  Are there admins that like to trace processes? 
If they are that far, they could get the user/pass if they really wanted to
anyway.

I can see doing this for testing, but not in production.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals

--

-- 
## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at
http://www.exim.org/ ##
Permalink | Reply | 0 comments |

Gmane