Hello,
since some days we use postfix 3.1.0
We have some failoversystems and use a main.cf which is symlinked into a
drbd-area.
When using postconf to change a main.cf parameter, symlink is replaced
by regular file.
This behaviour is documented here: http://www.postfix.org/postconf.1.html
Wha
Hajo Locke:
> Hello,
>
> since some days we use postfix 3.1.0
> We have some failoversystems and use a main.cf which is symlinked into a
> drbd-area.
> When using postconf to change a main.cf parameter, symlink is replaced
> by regular file.
Sorry, symlinked configuration files are NOT SUPPORTE
> On Dec 8, 2016, at 08:39, Dominic Raferd wrote:
>
> If nothing was specified as smtp_fallback_relay would it wait and try again
> on a transient error or would it just give up immediately? If the former,
> this would give me the behaviour I want but I really need to have the
> fallback opti
On 08/12/2016 13:28, Dusan Obradovic wrote:
On Dec 8, 2016, at 08:39, Dominic Raferd wrote:
If nothing was specified as smtp_fallback_relay would it wait and try again on
a transient error or would it just give up immediately? If the former, this
would give me the behaviour I want but I reall
On Thu, Dec 08, 2016 at 07:39:00AM +, Dominic Raferd wrote:
> Is there a way to get it instead to try again, after a delay, to the
> primary onward server(s) (whether the one specified as relayhost or,
> if no relayhost is specified, the MXs per the recipient address),
> and only if these fail
> On Dec 8, 2016, at 14:57, Dominic Raferd wrote:
>
> Thanks for your swift reply Dusan. What you write is logical but my postfix
> doesn't seem to behave that way. I have no special setting for
> maximal_queue_lifetime but I give below a recent extract from my log
> (obfuscated). After tryin
On 08/12/2016 14:15, Dusan Obradovic wrote:
On Dec 8, 2016, at 14:57, Dominic Raferd wrote:
Thanks for your swift reply Dusan. What you write is logical but my postfix
doesn't seem to behave that way. I have no special setting for
maximal_queue_lifetime but I give below a recent extract from
Dominic Raferd:
> I'm using Postfix 3.1.0. If a message is rejected by an onward server
> with a transient error message (e.g. 421-4.7.0 'temporarily rate
> limited') then my postfix immediately tries any other specified MXs per
> the recipient address and if these give the same response (as the
On 08/12/2016 14:11, Bastian Blank wrote:
On Thu, Dec 08, 2016 at 07:39:00AM +, Dominic Raferd wrote:
Is there a way to get it instead to try again, after a delay, to the
primary onward server(s) (whether the one specified as relayhost or,
if no relayhost is specified, the MXs per the recipi
On 08/12/2016 14:28, Wietse Venema wrote:
Dominic Raferd:
I'm using Postfix 3.1.0. If a message is rejected by an onward server
with a transient error message (e.g. 421-4.7.0 'temporarily rate
limited') then my postfix immediately tries any other specified MXs per
the recipient address and if th
Hi,
We have a server running Postfix, with mailing lists run by Mailman,
for a local domain. This server receives mail from an upstream
cloud-based server for all recipients not on the cloud-based server
(the idea being that any user not on the cloud server is a mailing
list). The mail is relayed
Dominic Raferd:
> I already have:
> smtp_destination_concurrency_limit = 1
> smtp_destination_concurrency_failed_cohort_limit = 10
> smtp_destination_rate_delay = 3s
> smtp_destination_recipient_limit = 1
Well there you messed up. Don't set smtp_destination_recipient_limit=1
that makes the rate li
On 08/12/2016 15:46, Wietse Venema wrote:
Dominic Raferd:
I already have:
smtp_destination_concurrency_limit = 1
smtp_destination_concurrency_failed_cohort_limit = 10
smtp_destination_rate_delay = 3s
smtp_destination_recipient_limit = 1
Well there you messed up. Don't set smtp_destination_recip
On Thu, Dec 08, 2016 at 02:58:24PM +, cmc wrote:
> We have a server running Postfix, with mailing lists run by
> Mailman, for a local domain. This server receives mail from an
> upstream cloud-based server for all recipients not on the
> cloud-based server (the idea being that any user not o
Thanks for the reply
> On Thu, Dec 08, 2016 at 02:58:24PM +, cmc wrote:
>> We have a server running Postfix, with mailing lists run by
>> Mailman, for a local domain. This server receives mail from an
>> upstream cloud-based server for all recipients not on the
>> cloud-based server (the idea
Hi,
On Tue, Dec 6, 2016 at 9:24 AM, /dev/rob0 wrote:
> On Tue, Dec 06, 2016 at 08:59:56AM +0100, Julian Kippels wrote:
>> Am Mon, 5 Dec 2016 20:52:21 -0500
>> schrieb Alex :
>>
>> > I have a postfix-3.0.5 system with a few hundred users. They
>> > have access to submission, webmail, and dovecot t
On 09/12/16 15:02, Alex wrote:
> It looks like this is what's enabling it on port 25:
> smtps inet n - n - - smtpd
> -o syslog_name=postfix/smtps
> -o smtpd_tls_wrappermode=yes
> -o smtpd_sasl_auth_enable=yes
> -o smtpd_client_restrictions=permit_sasl_auth
17 matches
Mail list logo
