> Am 02.11.2016 um 21:45 schrieb Christian Rößner
> :
>
>> Am 01.11.2016 um 13:48 schrieb Wietse Venema :
>>
>> Christian Ro??ner:
>>>
Am 25.10.2016 um 08:22 schrieb Wietse Venema :
Wietse Venema:
> Wietse Venema:
>> Looks like either 1) an exclusion mechanism or 2) a s
> Am 01.11.2016 um 13:48 schrieb Wietse Venema :
>
> Christian Ro??ner:
>>
>>> Am 25.10.2016 um 08:22 schrieb Wietse Venema :
>>>
>>> Wietse Venema:
Wietse Venema:
> Looks like either 1) an exclusion mechanism or 2) a selection
> mechanism would do the job.
>
> 1) Nullifies
Christian Ro??ner:
>
> > Am 25.10.2016 um 08:22 schrieb Wietse Venema :
> >
> > Wietse Venema:
> >> Wietse Venema:
> >>> Looks like either 1) an exclusion mechanism or 2) a selection
> >>> mechanism would do the job.
> >>>
> >>> 1) Nullifies the smtpd_milters setting depending on the client.
> >
> Am 25.10.2016 um 08:22 schrieb Wietse Venema :
>
> Wietse Venema:
>> Wietse Venema:
>>> Looks like either 1) an exclusion mechanism or 2) a selection
>>> mechanism would do the job.
>>>
>>> 1) Nullifies the smtpd_milters setting depending on the client.
>>>
>>> 2) Chooses the smtpd_milters se
John @ KLaM:
> Do you have any suggestions/recommendations for a maintenance system.
Wietse:
> Not specifically. In the past years I have main.cf and master.cf
> configurable with "postconf" commands, to make the job easier for
> configuration tool writers. I'll leave writing such tools to the
> p
Am 25.10.2016 um 13:31 schrieb Wietse Venema:
> Wietse Venema:
>> I've implemented the second variant. If you maintain configurations
>> by hand, then excluding mynetworks will be a bit of extra work. I
>> recommend that configurations aren't maintained by hand.
> John @ KLaM:
>> Do you have any
Wietse Venema:
> I've implemented the second variant. If you maintain configurations
> by hand, then excluding mynetworks will be a bit of extra work. I
> recommend that configurations aren't maintained by hand.
John @ KLaM:
> Do you have any suggestions/recommendations for a maintenance system.
Do you have any suggestions/recommendations for a maintenance system.
On October 25, 2016 7:23:22 PM wie...@porcupine.org (Wietse Venema) wrote:
Wietse Venema:
Wietse Venema:
> Looks like either 1) an exclusion mechanism or 2) a selection
> mechanism would do the job.
>
> 1) Nullifies the sm
Wietse Venema:
> Wietse Venema:
> > Looks like either 1) an exclusion mechanism or 2) a selection
> > mechanism would do the job.
> >
> > 1) Nullifies the smtpd_milters setting depending on the client.
> >
> > 2) Chooses the smtpd_milters setting depending on the client.
> >
> > I'll think about
Wietse Venema:
> Looks like either 1) an exclusion mechanism or 2) a selection
> mechanism would do the job.
>
> 1) Nullifies the smtpd_milters setting depending on the client.
>
> 2) Chooses the smtpd_milters setting depending on the client.
>
> I'll think about it.
I've implemented the second
Looks like either 1) an exclusion mechanism or 2) a selection
mechanism would do the job.
1) Nullifies the smtpd_milters setting depending on the client.
2) Chooses the smtpd_milters setting depending on the client.
I'll think about it.
Wietse
> Am 20.10.2016 um 14:11 schrieb Patrick Ben Koetter :
>
> * Wietse Venema :
>> Christian Ro??ner:
>>> Possible situation: Central SMTP-hub that gets connections from
>>> MX-ins and internal servers, ...
>>
>> I have a simpler solution: separate those mail streams with separate
>> MTA instances.
* Wietse Venema :
> Christian Ro??ner:
> > Possible situation: Central SMTP-hub that gets connections from
> > MX-ins and internal servers, ...
>
> I have a simpler solution: separate those mail streams with separate
> MTA instances. That avoids the complexity of adding exceptions to
> main.cf, mi
Christian Ro??ner:
> Possible situation: Central SMTP-hub that gets connections from
> MX-ins and internal servers, ...
I have a simpler solution: separate those mail streams with separate
MTA instances. That avoids the complexity of adding exceptions to
main.cf, milters, ...
Different streams ca
14 matches
Mail list logo
