Hi
One of my clients made a setup that all her mails are forwarded to remote
ISP
Unfortunatly i noticed that sometimes i get 450 error from destination ISP
this triggers Delivery Failure Notice wich is naturally sent to this ISP
Is there a way to stop this endless loop ?
Im using postfix 2.5.8
I
On Sun, Feb 19, 2012 at 06:45:14PM -0500, Wietse Venema wrote:
> Peter:
> > On 20/02/12 11:14, Wietse Venema wrote:
> > > Peter:
> > >> Note that if you put the old config in dovecot will give
> > >> a warning on startup and `doveconf -n' will show the new
> > >> config that you should replace it w
Am 20.02.2012 00:45, schrieb Wietse Venema:
> Peter:
>> On 20/02/12 11:14, Wietse Venema wrote:
>>> Peter:
Note that if you put the old config in dovecot will give a warning on
startup and `doveconf -n' will show the new config that you should
replace it with.
>>>
>>> http://www.po
Peter:
> On 20/02/12 11:14, Wietse Venema wrote:
> > Peter:
> >> Note that if you put the old config in dovecot will give a warning on
> >> startup and `doveconf -n' will show the new config that you should
> >> replace it with.
> >
> > http://www.postfix.org/SASL_README.html was updated for Postf
On 20/02/12 11:14, Wietse Venema wrote:
> Peter:
>> Note that if you put the old config in dovecot will give a warning on
>> startup and `doveconf -n' will show the new config that you should
>> replace it with.
>
> http://www.postfix.org/SASL_README.html was updated for Postfix 2.9.
> What are th
Peter:
> Note that if you put the old config in dovecot will give a warning on
> startup and `doveconf -n' will show the new config that you should
> replace it with.
http://www.postfix.org/SASL_README.html was updated for Postfix 2.9.
What are the errors?
Wietse
The dovecot config listed in the SASL_README is obsoleted for dovecot
2.0, it should probably be updated to reflect that. I'm not sure
exactly what should go in the SASL_README file but I'll show the
relevant part of my own dovecot config (which uses an sql db for
authentication, not pam):
auth_m
On Sun, 19 Feb 2012 19:35:56 +0100, Wietse Venema
wrote:
Artemy Tregubenko:
> Instead of enumerating things Postfix that does not do, it would
> be more helpful to say how to achieve a concrete result:
>
>To use ONLY system-supplied default certificate authority
>certificates
Artemy Tregubenko:
> > Instead of enumerating things Postfix that does not do, it would
> > be more helpful to say how to achieve a concrete result:
> >
> > To use ONLY system-supplied default certificate authority
> > certificates, specify those with *_tls_CApath or
> > *_t
There are many mail howtos on the web ... can one more hurt?
http://rob0.nodns4.us/howto/README
http://rob0.nodns4.us/howto/
http://rob0.nodns4.us/howto/latest.tar.gz (all files)
(Sorry, not HTML yet. That is on the agenda.)
This is a multiple address class sample impleme
On Sun, 19 Feb 2012 18:18:12 +0100, Wietse Venema
wrote:
Artemy Tregubenko:
On Sun, 19 Feb 2012 17:10:50 +0100, Wietse Venema
wrote:
> As per the documentation, Postfix APPENDS to certificates in *CApath
> or *CAfile. If you don't specify certificates in *CApath and *CAfile,
> then Postfix
Artemy Tregubenko:
> On Sun, 19 Feb 2012 17:10:50 +0100, Wietse Venema
> wrote:
>
> > As per the documentation, Postfix APPENDS to certificates in *CApath
> > or *CAfile. If you don't specify certificates in *CApath and *CAfile,
> > then Postfix won't append to them.
>
> Could you add to docum
Greetings,
My name is Mike Laris and I am a volunteer with two 501(c)(3) animal
rescue organizations : Texas Great Pyrenees Rescue (txpyrs.org) and
Saint Bernard Rescue Foundation of Texas (saintrescuetx.org). Part of
my volunteer activities for both these groups has been to write and
mainta
On Sun, 19 Feb 2012 17:10:50 +0100, Wietse Venema
wrote:
As per the documentation, Postfix APPENDS to certificates in *CApath
or *CAfile. If you don't specify certificates in *CApath and *CAfile,
then Postfix won't append to them.
Could you add to documentation this sentence "If you don't s
Artemy Tregubenko:
> Is tls_append_default_CA expected to work when none of *CApath and *CAfile
> are set?
As per the documentation, Postfix APPENDS to certificates in *CApath
or *CAfile. If you don't specify certificates in *CApath and *CAfile,
then Postfix won't append to them.
Wietse
On Sun, 19 Feb 2012 16:00:43 +0100, Wietse Venema
wrote:
To investigate, you can strace the SMTP daemon (see DEBUG_README.html)
and see what system calls fail. That will also show whether you
correctly followed instructions to turn of the chroot feature.
Thanks to strace I figured out that
On Sun, 19 Feb 2012 16:00:43 +0100, Wietse Venema
wrote:
Therefore, the Equifax certificate wasn't found with 'smtp_tls_CApath
= /etc/ssl/certs'. For CApath to work, you need to run a program
that sets up the necessary symlinks (named after a certificate hash)
that allow the OpenSSL library t
Artemy Tregubenko:
[ Charset UTF-8 unsupported, converting... ]
> Hello,
>
> I have an Ubuntu server with Postfix 2.8.2 on it. Looks like
> tls_append_default_CA has no effect on it.
>
> When I send emails to Gmail I get message about failed certificate
> verification. There're many articles
Den 2012-02-18 00:14, Reindl Harald skrev:
what i do not understand is how fucking stupid
people are spamming to postmaster/abuse-addresses
+1 hello lease web :-)
On Sun, 19 Feb 2012 15:05:58 +0100, Wietse Venema
wrote:
Artemy Tregubenko:
Hello,
I have an Ubuntu server with Postfix 2.8.2 on it. Looks like
tls_append_default_CA has no effect on it.
See if this fixes the problem:
http://www.postfix.org/DEBUG_README.html#no_chroot
Then, complain
Artemy Tregubenko:
> Hello,
>
> I have an Ubuntu server with Postfix 2.8.2 on it. Looks like
> tls_append_default_CA has no effect on it.
See if this fixes the problem:
http://www.postfix.org/DEBUG_README.html#no_chroot
Then, complain to the DEBIAN maintainer for shipping
as broken Postfi
Hello,
I have an Ubuntu server with Postfix 2.8.2 on it. Looks like
tls_append_default_CA has no effect on it.
When I send emails to Gmail I get message about failed certificate
verification. There're many articles on solving this issue. The ones that
I saw suggest suboptimal approach of
22 matches
Mail list logo