Re: Server-to-server TLS

2011-03-19 Thread Victor Duchovni
On Sat, Mar 19, 2011 at 03:37:11PM +0100, Raven wrote: > > As for TLS, the security policy and certficate verification are tied to > > the nexthop destination, not the recipient domain, if the two differ, > > it is the nexthop destination that is used. This is documented, please > > read the docum

Re: Tuning queue life time against some retry errors.

2011-03-19 Thread Reindl Harald
Am 19.03.2011 19:32, schrieb Ralf Hildebrandt: > * David Touzeau : > >> Thanks for this procedure but this is not a bug/error request but an >> howto request. > > What I'm doing is this (just a few examples): > > alo.com error:5.1.2 You probably meant aol.com, > not

Re: Tuning queue life time against some retry errors.

2011-03-19 Thread Ralf Hildebrandt
* David Touzeau : > Thanks for this procedure but this is not a bug/error request but an > howto request. What I'm doing is this (just a few examples): alo.com error:5.1.2 You probably meant aol.com, not alo.com aoll.comerror:5.1.2 You pro

Re: Tuning queue life time against some retry errors.

2011-03-19 Thread David Touzeau
Le samedi 19 mars 2011 à 10:20 -0500, Noel Jones a écrit : > On 3/19/2011 10:14 AM, David Touzeau wrote: > > Le samedi 19 mars 2011 à 11:05 -0400, Wietse Venema a écrit : > >> David Touzeau: > >>> I expected a feature that reduce the queue life time per SMTP error code > >>> but it seems that this

Re: Tuning queue life time against some retry errors.

2011-03-19 Thread Reindl Harald
Am 19.03.2011 16:14, schrieb David Touzeau: > Le samedi 19 mars 2011 à 11:05 -0400, Wietse Venema a écrit : >> David Touzeau: >>> I expected a feature that reduce the queue life time per SMTP error code >>> but it seems that this kind of feature does not exists on postfix >> >> Do you mean, fea

Re: Tuning queue life time against some retry errors.

2011-03-19 Thread Sahil Tandon
On Sat, 2011-03-19 at 16:14:43 +0100, David Touzeau wrote: > Le samedi 19 mars 2011 à 11:05 -0400, Wietse Venema a écrit : > > David Touzeau: > > > I expected a feature that reduce the queue life time per SMTP error code > > > but it seems that this kind of feature does not exists on postfix > >

Re: Tuning queue life time against some retry errors.

2011-03-19 Thread Noel Jones
On 3/19/2011 10:14 AM, David Touzeau wrote: Le samedi 19 mars 2011 à 11:05 -0400, Wietse Venema a écrit : David Touzeau: I expected a feature that reduce the queue life time per SMTP error code but it seems that this kind of feature does not exists on postfix Do you mean, feature to detect th

Re: Tuning queue life time against some retry errors.

2011-03-19 Thread David Touzeau
Le samedi 19 mars 2011 à 11:05 -0400, Wietse Venema a écrit : > David Touzeau: > > I expected a feature that reduce the queue life time per SMTP error code > > but it seems that this kind of feature does not exists on postfix > > Do you mean, feature to detect that hotmiel.com is a typo? > > Do

Re: Tuning queue life time against some retry errors.

2011-03-19 Thread Wietse Venema
David Touzeau: > I expected a feature that reduce the queue life time per SMTP error code > but it seems that this kind of feature does not exists on postfix Do you mean, feature to detect that hotmiel.com is a typo? Do you mean, feature to drop mail immediately when hotmiel.com accepts no SMTP

Re: Tuning queue life time against some retry errors.

2011-03-19 Thread David Touzeau
Le samedi 19 mars 2011 à 10:35 -0400, Sahil Tandon a écrit : > On Sat, 2011-03-19 at 13:00:29 +0100, David Touzeau wrote: > > > Sometimes the bounce queue is filled caused by users that did not type > > the correct domains addresses. > > A common problem. > > > "Connect to hotmiel.com[69.6.2.98

Re: Tuning queue life time against some retry errors.

2011-03-19 Thread Wietse Venema
David Touzeau: > > You wrote: > > > > > But i did not want to postfix growing the bounce queue for 5 days for > > > this kind of errors. Postfix will not keep bounce messages in the queue for five days when the bounced message had a valid sender address. Therefore, if you don't want a queue full

Re: Tuning queue life time against some retry errors.

2011-03-19 Thread Larry Stone
On 3/19/11 9:22 AM, David Touzeau at da...@touzeau.eu wrote: > Le samedi 19 mars 2011 à 08:46 -0500, Larry Stone a écrit : >> On 3/19/11 8:29 AM, David Touzeau at da...@touzeau.eu wrote: >> >>> The problem is not really inbound mails but growing the queue by >>> outbound mails. >>> >>> What is t

Re: Server-to-server TLS

2011-03-19 Thread Raven
On Wed, 2011-03-09 at 12:23 -0500, Victor Duchovni wrote: > On Wed, Mar 09, 2011 at 01:36:46PM +0100, Raven wrote: > > > How can I apply this to $relayhost without having to list all local > > domains in the transport map (as they are already listed in > > $virtual_mailbox_domains)? > > Why are

Re: Tuning queue life time against some retry errors.

2011-03-19 Thread Sahil Tandon
On Sat, 2011-03-19 at 13:00:29 +0100, David Touzeau wrote: > Sometimes the bounce queue is filled caused by users that did not type > the correct domains addresses. A common problem. > "Connect to hotmiel.com[69.6.2.98]:25: Connection refused" This particular problem occurs because hotmiel.com

Re: Tuning queue life time against some retry errors.

2011-03-19 Thread David Touzeau
Le samedi 19 mars 2011 à 09:56 -0400, Wietse Venema a écrit : > David Touzeau: > > Le samedi 19 mars 2011 ? 09:11 -0400, Wietse Venema a ?crit : > > > reject_unlisted_sender > > > > Dear weitse. > > > > i have read (and understand) ,that reject_unlisted_sender can only > > available when senders

Re: Tuning queue life time against some retry errors.

2011-03-19 Thread David Touzeau
Le samedi 19 mars 2011 à 08:46 -0500, Larry Stone a écrit : > On 3/19/11 8:29 AM, David Touzeau at da...@touzeau.eu wrote: > > > The problem is not really inbound mails but growing the queue by > > outbound mails. > > > > What is the best strategy to filter these user's mistakes ? > > Perhaps yo

Re: Tuning queue life time against some retry errors.

2011-03-19 Thread Wietse Venema
David Touzeau: > Le samedi 19 mars 2011 ? 09:11 -0400, Wietse Venema a ?crit : > > reject_unlisted_sender > > Dear weitse. > > i have read (and understand) ,that reject_unlisted_sender can only > available when senders are known and internals. > But when users send outbound mails to internet we c

Re: Tuning queue life time against some retry errors.

2011-03-19 Thread Larry Stone
On 3/19/11 8:29 AM, David Touzeau at da...@touzeau.eu wrote: > The problem is not really inbound mails but growing the queue by > outbound mails. > > What is the best strategy to filter these user's mistakes ? Perhaps you should follow the list's directions from your initial subscription confirm

Re: Tuning queue life time against some retry errors.

2011-03-19 Thread David Touzeau
Le samedi 19 mars 2011 à 09:11 -0400, Wietse Venema a écrit : > reject_unlisted_sender Dear weitse. i have read (and understand) ,that reject_unlisted_sender can only available when senders are known and internals. But when users send outbound mails to internet we cannot list internet domains. T

Re: Tuning queue life time against some retry errors.

2011-03-19 Thread Wietse Venema
David Touzeau: > But i did not want to postfix growing the bounce queue for 5 days for > this kind of errors. Why are your NDRs queued for 5 days? Perhaps you need to turn on reject_unlisted_sender/smtpd_reject_unlisted_sender and not accept from bogus sender addresses. Wietse

Tuning queue life time against some retry errors.

2011-03-19 Thread David Touzeau
Dear Sometimes the bounce queue is filled caused by users that did not type the correct domains addresses. For example type hotmil.com against hotmail.com mistake Results are sometimes "MX: Host not found, try again" For postfix, this is normal. But i did not want to postfix growing the boun

Re: Verify Outgoing From Address

2011-03-19 Thread Benny Pedersen
On Tue, 15 Mar 2011 10:30:44 -0700, Neil wrote: # you have smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination, reject_invalid_helo_hostname, reject_non_fqdn_helo_hostname, reject_non_fqdn_sender, reject_unlisted_sender, reject_unlisted_recipient