ng used:...
> /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter:
> sender_dependant_default_transport_maps=hash:/etc/postfix/sender_dependant_default_transport_maps
> postfix/postfix-script: refreshing the Postfix mail system
>
> why would postfix not use this directi
tp://www.postfix.org/COMPATIBILITY_README.html for details
postfix: To disable backwards compatibility use "postconf
compatibility_level=2" and "postfix reload"
/usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter:
sender_dependant_default_transport_maps=hash:/etc/postfix
On Fri, 17 Aug 2018 16:25:07 -0400
Viktor Dukhovni wrote:
> > On Aug 17, 2018, at 4:20 PM, Volunteer
> > wrote:
> >
> > I upgraded Postfix with DNF.
>
> What repository is providing this Postfix build? Perhaps
> the upstream maintainer ran into the same issue.
>
I created a fedora bug ab
Did you install postfix-mysql.x86_64?
On 2018-08-17 04:50 PM, volunteer wrote:
Victor,
I am a Fedora user.
Installed Packages
Name : postfix
Epoch: 2
Version : 3.3.1
Release : 1.fc28
Arch : x86_64
Size : 4.2 M
Source : postfix-3.3.1-1.fc28.src.r
Victor,
I am a Fedora user.
Installed Packages
Name : postfix
Epoch: 2
Version : 3.3.1
Release : 1.fc28
Arch : x86_64
Size : 4.2 M
Source : postfix-3.3.1-1.fc28.src.rpm
Repo : @System
>From repo: updates
Summary : Postfix Mail Trans
> On Aug 17, 2018, at 4:20 PM, Volunteer wrote:
>
> I upgraded Postfix with DNF.
What repository is providing this Postfix build? Perhaps
the upstream maintainer ran into the same issue.
--
Viktor.
ow. The error
> messages were:
>
> Aug 12 22:39:28 crash postfix[21125]: /usr/sbin/postconf: warning:
> mysql:/etc/postfix/users.cf: unused parameter: password=xxx
Perhaps you built Postfix from source on a system that does not
have the "m4" preprocessor instal
I used the raw tags and I can't see the error messages now. The error
messages were:
Aug 12 22:39:28 crash postfix[21125]: /usr/sbin/postconf: warning:
mysql:/etc/postfix/users.cf: unused parameter: password=xxx
Aug 12 22:39:28 crash postfix[21125]: /usr/sbin/postconf: warning:
mysql
I upgraded to Postfix 3.3.1 from 2.x.x two days ago. I keep seeing the
following warnings:
This is repeated for the other files: domains.cf and forwardings.cf
I don't see any warnings for the file: alias-maps.cf even though it is
similiar to the above files.
I looked in the documentation (man p
Tuomo Soini:
> On Wed, 1 Aug 2018 09:35:01 -0400 (EDT)
> Wietse Venema wrote:
>
> > Someone messed up and built Postfix on a machine that does not have
> > the m4 preprocessor installed.
>
> Thank you - adding m4 to build system fixed the issue.
> How about failing the build if m4 is not present
On Wed, 1 Aug 2018 09:35:01 -0400 (EDT)
Wietse Venema wrote:
> Someone messed up and built Postfix on a machine that does not have
> the m4 preprocessor installed.
Thank you - adding m4 to build system fixed the issue.
How about failing the build if m4 is not present?
--
Tuomo Soini
Foobar Li
gt; Looks like a ton of parameters were added since I wrote this code.
>
> Also mysql tables suffers from same issue. At lest following config
> options are logged:
>
> /usr/sbin/postconf: warning: mysql:/etc/postfix/virtual.cf: unused
> parameter: password=xxx
Someone messed up and built Postfix on a machine that does not have
the m4 preprocessor installed.
Wietse
ysql tables suffers from same issue. At lest following config
options are logged:
/usr/sbin/postconf: warning: mysql:/etc/postfix/virtual.cf: unused
parameter: password=xxx
/usr/sbin/postconf: warning: mysql:/etc/postfix/virtual.cf: unused
parameter: dbname=sqldbname
/usr/sbin/postconf: wa
Ralf Hildebrandt:
> * Ralf Hildebrandt :
> > postconf complains:
> > /usr/sbin/postconf: warning: ldap:/etc/postfix/laborberlin.com.cf: unused
> > parameter: start_tls=yes
> >
> > according to http://www.postfix.org/ldap_table.5.html
>
> postfix-3.3
* Ralf Hildebrandt :
> postconf complains:
> /usr/sbin/postconf: warning: ldap:/etc/postfix/laborberlin.com.cf: unused
> parameter: start_tls=yes
>
> according to http://www.postfix.org/ldap_table.5.html
postfix-3.3-20170716 is complaining,
postfix-3.3-20170611 is not complain
postconf complains:
/usr/sbin/postconf: warning: ldap:/etc/postfix/laborberlin.com.cf: unused
parameter: start_tls=yes
according to http://www.postfix.org/ldap_table.5.html
STARTTLS can be turned on with the start_tls parameter:
start_tls = yes
Both forms require LDAP protocol version 3
On Thu, Mar 09, 2017 at 11:04:02AM -0500, Robert Moskowitz wrote:
> I found one article:
>
> https://www.howtoforge.com/community/threads/postfix-warning-undefined-parameter-virtual_mailbox_limit_maps.71474/
>
> that says it is not required anymore.
It never was a part of Postfix. This was from
I found one article:
https://www.howtoforge.com/community/threads/postfix-warning-undefined-parameter-virtual_mailbox_limit_maps.71474/
that says it is not required anymore. To remove it. I am *assuming*
that I then also remove:
/etc/postfix/mysql-virtual_mailbox_limit_maps.cf
I looked aro
On Saturday, April 18, 2015 03:48:47 PM Juan Pablo wrote:
> Hello,
>
> I am having a new Ubuntu 14.04 server set up with postfix. When using
> postfix check I am seeing warning about unused parameter
>
>/usr/sbin/postconf: warning: /etc/postfix/main.cf: unused p
Hello,
I am having a new Ubuntu 14.04 server set up with postfix. When using
postfix check I am seeing warning about unused parameter
/usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter:
policy-spf_time_limit=3600s
/usr/sbin/postconf: warning: /etc/postfix/main.cf
1.2015 um 05:49 schrieb Joey J:
>
>> I'm getting the following when I start postfix ( literally that many
>> times)
>>
>> /usr/sbin/postconf: warning: /etc/postfix/main.cf <http://main.cf>:
>> unused parameter: mx_access=hash:/etc/postfix/mx_access
>>
Am 31.01.2015 um 05:49 schrieb Joey J:
I'm getting the following when I start postfix ( literally that many times)
/usr/sbin/postconf: warning: /etc/postfix/main.cf <http://main.cf>:
unused parameter: mx_access=hash:/etc/postfix/mx_access
Here is a section of my configuration, I ca
Hello,
I'm getting the following when I start postfix ( literally that many times)
/usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter:
mx_access=hash:/etc/postfix/mx_access
/usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter:
mx_access=hash:/etc/po
On 11/21/2012 11:45 AM, Sam Jones wrote:
> Thank you so much Noel.
>
> That was exactly it, and to confuse matters even more it had been in my
> old config like that for a year with no warning coming up.
That's exactly why the "unused parameter" feature was invente
ay I don't need
it!
Warm regards
Sam
On Wed, 2012-11-21 at 11:23 -0600, Noel Jones wrote:
> On 11/21/2012 11:12 AM, Sam Jones wrote:
> > Good afternoon,
> >
> > When I start my Postfix up (fresh install I'm trying to commission to
> > take over newsletter dut
On 11/21/2012 11:12 AM, Sam Jones wrote:
> Good afternoon,
>
> When I start my Postfix up (fresh install I'm trying to commission to
> take over newsletter duties) I'm seeing this:
>
> unused parameter: smtpd_client_restrictons=permit_mynetworks
> sleep 1, warn_if_
Good afternoon,
When I start my Postfix up (fresh install I'm trying to commission to
take over newsletter duties) I'm seeing this:
unused parameter: smtpd_client_restrictons=permit_mynetworks
sleep 1, warn_if_reject reject_unauth_pipelining?warn_if_reject
reject_unknown_client?permit
On 7/3/2012 11:02 AM, Marko Weber wrote:
>
> hello,
>
> when i do on console
>
> # postfix reload
>
> i get:
>
> /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter:
> virtual_create_maildirsize=yes
> /usr/sbin/postconf: warning: /e
hello,
when i do on console
# postfix reload
i get:
/usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter:
virtual_create_maildirsize=yes
/usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter:
virtual_mailbox_extended=yes
/usr/sbin/postconf: warning: /etc
Wietse Venema:
> Amazingly, defining a parameter in master.cf then using it in main.cf
> was not covered by the 30 regression tests in the Makefile.
...
> I'll add a regression test and fix.
Wietse:
> The fix for Postfix 2.9 and 2.10 is at:
Wietse:
> Hang on, I need to some some further checking.
Wietse Venema:
> Wietse Venema:
> > Amazingly, defining a parameter in master.cf then using it in main.cf
> > was not covered by the 30 regression tests in the Makefile.
> >
> > > Well. I can set this parameter in main.cf explicitly:
> > >
> > > smtpd_role =
> > >
> > > it will be overwritten
Wietse Venema:
> Amazingly, defining a parameter in master.cf then using it in main.cf
> was not covered by the 30 regression tests in the Makefile.
>
> > Well. I can set this parameter in main.cf explicitly:
> >
> > smtpd_role =
> >
> > it will be overwritten by master.cf setting for a speci
; >>
> >> smtpd_recipient_restrictions = smtpd_${smtpd_role}_recipient_restrictions
> >> smtpd_ext_recipient_restrictions = ...
> >>
> >> postconf: warning: /etc/postfix/master.cf: unused parameter:
> >> smtpd_role=ext
> >
> > This *will* comp
t_restrictions = ...
>>
>> postconf: warning: /etc/postfix/master.cf: unused parameter: smtpd_role=ext
>
> This *will* complain if -o smtpd_role=int is not used in main.cf,
or =ext.
> or if it is not used in the same master.cf line that defines
> smtpd_role.
Yes. But it
estrictions = smtpd_${smtpd_role}_recipient_restrictions
> smtpd_int_recipient_restrictions = ...
> smtpd_ext_recipient_restrictions = ...
>
> and so on.
>
> Now, after upgrading to postfix 2.9, every postfix
> tool issue this warning:
>
> postconf: warning: /etc/postfix/master.cf: unused
ng to postfix 2.9, every postfix
tool issue this warning:
postconf: warning: /etc/postfix/master.cf: unused parameter: smtpd_role=ext
which spams both logs and stderr output.
We've a few more "instances" of this technique,
which has been discussed/suggested in early 2000s
or even lat
On Sun, 2012-03-11 at 03:50 -0700, Ronald F. Guilmette wrote:
>
> I've just updated from 2.8.5 to 2.9.1 and now, when I start postfix,
> I am getting the following set of messages (that I've never seen before):
>
> /usr/local/sbin/postconf: warning: /usr/local/et
sr/local/etc/postfix/main.cf:
> unused parameter: policy_time_limit=600
snip * 16
>
> What gives? I haven't changed anything. The relevant line in my
> main.cf file is unremarkable:
>
> policy_time_limit = 600
Unremarkable, except that nothing in the configuration use
I've just updated from 2.8.5 to 2.9.1 and now, when I start postfix,
I am getting the following set of messages (that I've never seen before):
/usr/local/sbin/postconf: warning: /usr/local/etc/postfix/main.cf: unused
parameter: policy_time_limit=600
/usr/local/sbin/postconf: war
Reindl Harald:
> Am 10.03.2012 02:35, schrieb Wietse Venema:
> > Because they are not used. For example, smtpd_tls_cipherlist
> > does not exist
>
> ok, got an old documentation i assume
Nope, then there would be a backwards compatibility feature.
> 10.0.0.15:10026 inet n - n - - s
Am 10.03.2012 02:35, schrieb Wietse Venema:
> Because they are not used. For example, smtpd_tls_cipherlist
> does not exist
ok, got an old documentation i assume
> and barracuda_smtpd_recipient_restrictions
> also does not exist.
was mentioned by you because "permit_mynetworks, reject"
does n
is intentional, but the former may be an oversight. It
has never been reported before.
Wietse
>
> Mar 10 02:16:45 testserver postfix[1935]: /usr/sbin/postconf: warning:
> /etc/postfix/main.cf: unused parameter:
> barracuda_smtpd_recipient_restrictions=check_policy_service
>
/main.cf: unused parameter:
barracuda_smtpd_recipient_restrictions=check_policy_service
unix:/var/spool/postfix/dbmail-postfix-policyd/socket
permit_mynetworks reject
Mar 10 02:16:45 testserver postfix[1935]: /usr/sbin/postconf: warning:
/etc/postfix/main.cf: unused parameter:
lmtp_max_idle=600
Mar 10
* Joan Moreau :
>
>
> Hi,
>
> I upgraded to 2.9 and I get some few parameters unused
> anymore, but this one troubles me:
>
> usr/sbin/postconf: warning:
> /etc/postfix/main.cf: unused parameter:
> maildrop_destination_recipient_limit=1
>
> WHat
Hi,
I upgraded to 2.9 and I get some few parameters unused
anymore, but this one troubles me:
usr/sbin/postconf: warning:
/etc/postfix/main.cf: unused parameter:
maildrop_destination_recipient_limit=1
WHat is now the default value
for this parameter, if we can not set it up anymore
Wietse Venema:
> Mark Martinec:
> > postfix 2.9.2019 warns me:
> >
> > unused parameter: smtpd_client_connection_limit_exceptions
>
> The problem is that postconf no longer parses parameter values
> that have their default value.
Actually, the "unused
> > -o smtpd_client_connection_limit_exceptions=0.0.0.0/0
Jeroen Geilman wrote:
> This is probably old code, since postconf(5) says:
> http://www.postfix.org/postconf.5.html#smtpd_client_event_limit_exceptions
>
> *smtpd_client_event_limit_exceptions(
> default: $mynetworks )*
>
> Clients
On 2011-11-23 21:05, Mark Martinec wrote:
postfix 2.9.2019 warns me:
unused parameter: smtpd_client_connection_limit_exceptions
Yet if I remove this option from master.cf, I soon reach the connection
limit at the pre-queue content filter's re-entry smtpd service:
421-
Mark Martinec:
> postfix 2.9.2019 warns me:
>
> unused parameter: smtpd_client_connection_limit_exceptions
The problem is that postconf no longer parses parameter values
that have their default value.
You can work around this with an explicit
/etc/postfi
postfix 2.9.2019 warns me:
unused parameter: smtpd_client_connection_limit_exceptions
Yet if I remove this option from master.cf, I soon reach the connection
limit at the pre-queue content filter's re-entry smtpd service:
421-4.7.0 mail.ijs.si Error: too many connections from ::1
50 matches
Mail list logo
