On Tue, May 13, 2014 at 01:31:09PM +, Viktor Dukhovni wrote:
>
> The logging is misleading, it should say "Anonymous" rather than
> "untrusted". This is fixed in 2.11.1 and 2.12 snapshots.
>
> If you want authentication of this destination, you need to use a
> security level that demands aut
On Tue, May 13, 2014 at 02:11:34PM +0200, li...@rhsoft.net wrote:
> > And like I said.. it looks well from the openssl command and from
> > Chromium if I use the certificate inside an Apache2.. but postfix is
> > complaining and it is not telling me anything special what the issue is.
>
> the CA o
On Tue, May 13, 2014 at 01:12:07PM +0200, li...@rhsoft.net wrote:
> > I know that untrusted means that the identity has not been verified. But
> > it _should_ (that's why I'm confused). So DANE may be implemented in the
> > future but for now it should work already. So any other ideas?
>
> *who* i
On Tue, May 13, 2014 at 10:50:32AM +0200, Patrick Ben Koetter wrote:
> * Simon Effenberg :
> > Hi @list,
> >
> > I have an issue with my SSL certificate. When I send a mail from another
> > postfix to the one with the installed certificate it is complaining
> >
Hi @list,
I have an issue with my SSL certificate. When I send a mail from another
postfix to the one with the installed certificate it is complaining
about an Untrusted TLS connection. The certificate uses SAN and is
signed. OpenSSL tells me that everything is fine. When I test it through
ssl-too
On Sat, 9 Nov 2013 15:30:10 -0500 (EST)
wie...@porcupine.org (Wietse Venema) wrote:
> > transport:
> >
> > @domain1.tld smtp:[internal.relay]
> > @domain2.tld smtp:[external.relay]
>
> If you want to send domain1.tld and domain2.tld to the internal
> relay, then the correct syntax for a hash
So has anybody an idea if I can get the functionallity I want? I know that I
could put all the logic from the hash table into the tcp table but that sounds
ugly..
Simon Effenberg schrieb:
>Sorry the mistake was only in my example.. pardon me. The transport
>file has no @ prefix
Sorry the mistake was only in my example.. pardon me. The transport file has no
@ prefix in my configuration. (And if I disable the tcp table the transport
file works like expected).
Jeroen Geilman schrieb:
>On 11/09/2013 02:33 PM, Simon Effenberg wrote:
>> On Sat, 09 Nov 2013 14:21
On Sat, 09 Nov 2013 14:21:51 +0100
Jeroen Geilman wrote:
> On 11/9/2013 2:13 PM, Simon Effenberg wrote:
> > On Sat, 9 Nov 2013 07:54:30 -0500 (EST)
> > wie...@porcupine.org (Wietse Venema) wrote:
> >
> >> transport_maps can use hash tables AND tcp tables. transpor
On Sat, 9 Nov 2013 07:54:30 -0500 (EST)
wie...@porcupine.org (Wietse Venema) wrote:
> transport_maps can use hash tables AND tcp tables. transport_maps
> queries each table in the specified order, and stops when a result
> is found. When no result is found, Postfix uses default_transport.
>
>
d_
table has a domain hit.
Correct me if I'm wrong.
Simon
> On Nov 9, 2013 7:49 AM, "Simon Effenberg" wrote:
> >
> >
> >
> >
> > wie...@porcupine.org schrieb:
> > >transport_maps are searched in the order as specified in main
wie...@porcupine.org schrieb:
>transport_maps are searched in the order as specified in main.cf.
>If it's not found in regexp:/etc/postfix/transport.exp, then
>the tcp map is queried.
>
> Wietse
So this means that I cannot distinguish between x...@yyy.com and yyy.com
lookups in the tcp
Hi,
my transport_maps is:
transport_maps = hash:/etc/postfix/transport,
regexp:/etc/postfix/transport.exp,
tcp:[127.0.0.1]:2527
I want to use the "tcp" as "last resort" lookup but I don't know in
which order postfix is checking everything.
It looks like it is doing:
first round:
che
Hi,
we have problems that Postfix is crying about "warning: Illegal address
syntax" for mails like:
-b...@blub.org
and i'm not sure if this is correct.. in the source code (it's quite
old but also a newer postfix (2.7) shows this) there is a strict_rfc821
but i'm not sure if this one is what i'm
14 matches
Mail list logo
