Re: Best method to post master.conf
Victor Duchovni: On Tue, Jul 12, 2011 at 05:56:42PM -0400, Jerry wrote: On Tue, 12 Jul 2011 17:35:56 -0400 Victor Duchovni articulated: Indeed. Returning to the original topic though, I have a postmast(1) patch that adds a new utility that does with master.cf what postconf(1) does with main.cf. In particular it supports: postmast - show all entries in a machine-parseable normal form postmast -n - show non-default entries postmast -d - show default entries postmast -e - edit or add master.cf entries via CLI. I don't whether this is of sufficiently broad utility to warrant inclusion in the official release. It gets a Thumbs Up from me. Perhaps a link similar to the postfinger tool might a adequate, although I favor the inclusion concept. The utility uses various Postfix library functions, and builds properly only within the Postfix source distribution, so if not adopted by Wietse, it would be an unofficial patch, and I don't think that releasing it as a patch makes much sense. If the community feels it's useful, perhaps Wietse will adopt it, otherwise it can quitely disappear... I think this is an example of 0.1% benefit. It makes the learning curve steeper, because it inserts an unfamiliar program between the user and an unfamiliar file format. It does not help the people who make the mistakes. Like other mistakes, this user's mistake could be addressed by adding an extra helpful error message to the master daemon (if the line starts with '-letter then it's pretty surely a bad line continuation). Wietse
Re: Best method to post master.conf
On Wed, Jul 13, 2011 at 07:07:25AM -0400, Wietse Venema wrote: The utility uses various Postfix library functions, and builds properly only within the Postfix source distribution, so if not adopted by Wietse, it would be an unofficial patch, and I don't think that releasing it as a patch makes much sense. If the community feels it's useful, perhaps Wietse will adopt it, otherwise it can quitely disappear... I think this is an example of 0.1% benefit. It makes the learning curve steeper, because it inserts an unfamiliar program between the user and an unfamiliar file format. It does not help the people who make the mistakes. Like other mistakes, this user's mistake could be addressed by adding an extra helpful error message to the master daemon (if the line starts with '-letter then it's pretty surely a bad line continuation). Not claiming that postconf(1) will protect users from themselves, it is just a CLI for querying and modifying master.cf. Indeed for most users vi(1) is just fine. POSTMAST(1) POSTMAST(1) NAME postmast - Postfix master.cf command-line editor SYNOPSIS postmast [-c config_dir] [-dn] [-s service] [-t type] postmast [-c config_dir] -e definition -s service -t type postmast [-c config_dir] -# [-s service] -t type So one can list the definition (or the default definition, or a non-default definition) of all services or a specific service or service type. Or edit the definition of a service, or comment-out a service. I agree it is not essential. I'll just keep it in-house... -- Viktor.
Re: Best method to post master.conf
On 7/12/2011 12:16 AM, jeffrey starin wrote: I am trying to use the smtp_bind_address command so that three seperate ips can be used for 3 separate clients who are using email campaign software as explained in this howto: http://www.kutukupret.com/2010/01/02/postfix-bind-sender-domain-to-dedicated-outgoing-ip-address/ The error logs show the entry: Jul 11 23:46:31 who postfix/master[5309]: fatal: /etc/postfix/master.cf http://master.cf: line 6: bad transport type: smtp_bind_address=174.121.222.21 which refers to the the entries in the master.cf http://master.cf using that command, smtp_bind_address command. The second problem is even if I comment out those lines that refer to smtp_bind_address in the master.cf http://master.cf, I still receive that error in the logs which is very strange indeed. It's almost as if after commenting them out, postfix has a cached copy or something of the master.cf http://master.cf which it is using. I even restart postfix and postfix reload but to no avail. If someone sees something in the syntax (although I've double checked it so many times) let me know. I even upgraded to postfix 2.8.4 from 2.3.3 because I thought it may have had something to do with the version. master.cf http://master.cf: customer1 unix - - n - - smtp -o smtp_bind_address=174.121.222.21 -o smtp_helo_name=domain1.com http://domain1.com -o syslog_name=postfix-domain1.com http://postfix-domain1.com customer2 unix - - n - - smtp -o smtp_bind_address=174.121.222.22 -o smtp_helo_name=domain2.org http://domain2.org -o syslog_name=postfix-domain2.org http://postfix-domain2.org customer3 unix - - n - - smtp -o smtp_bind_address=174.121.222.23 -o smtp_helo_name=domain3.com http://domain3.com -o syslog_name=postfix-domain3.com http://postfix-domain3.com maillog: Jul 11 23:46:31 who postfix/postfix-script[5308]: starting the Postfix mail system Jul 11 23:46:31 who postfix/master[5309]: fatal: /etc/postfix/master.cf http://master.cf: line 6: bad transport type: smtp_bind_address=174.121.222.21 Jul 11 23:46:31 who postfix/master[5309]: fatal: /etc/postfix/master.cf http://master.cf: line 6: bad transport type: smtp_bind_address=174.121.222.22 This appears to be a case of no whitespace before -o. If there is a non-whitespace character first on the line, then Postfix will treat it as a new entry. customer1 unix - - n - - smtp -o smtp_bind_address=174.121.222.21 -o smtp_helo_name=domain1.com http://domain1.com -o syslog_name=postfix-domain1.com http://postfix-domain1.com
Re: Best method to post master.conf
On Tue, Jul 12, 2011 at 1:03 AM, Stan Hoeppner s...@hardwarefreak.comwrote: On 7/11/2011 11:16 PM, jeffrey starin wrote: I am trying to use the smtp_bind_address command so that three seperate ips can be used for 3 separate clients who are using email campaign software as explained in this howto: http://www.kutukupret.com/2010/01/02/postfix-bind-sender-domain-to-dedicated-outgoing-ip-address/ The error logs show the entry: Jul 11 23:46:31 who postfix/master[5309]: fatal: /etc/postfix/master.cf: line 6: bad transport type: smtp_bind_address=174.121.222.21 I even upgraded to postfix 2.8.4 from 2.3.3 because I thought it may have had something to do with the version. smtp_bind_address is a new feature as of 2.7, clearly stated at the top of the article you linked. The fact that you receive the error with 2.3.3 and after you upgraded to 2.8.4 suggests that you didn't successfully replace 2.3.3 with 2.8.4. Posting the output of the following shell command will confirm this. ~$ postconf -d|grep 'mail_version =' If it says 2.3.3 you need to thoroughly remove all traces of that package (specifically /etc/init.d entries) and re-install 2.8.4 following these instructions: http://www.postfix.org/INSTALL.html -- Stan running the command at the server prompt: postconf -d|grep 'mail_version' produces: mail_version = 2.8.4 milter_macro_v = $mail_name $mail_version I don't know where you saw 2.3.3 but will nevertheless take your suggestions and re-install.
Re: Best method to post master.conf
On 7/12/2011 4:34 PM, jeffrey starin wrote: I don't know where you saw 2.3.3 but will nevertheless take your suggestions and re-install. I hope you read my comments made 8 hours ago before you do this. It is probably not necessary. (Archive: http://marc.info/?l=postfix-usersm=131047442028765)
Re: Best method to post master.conf
smtp_bind_address is a new feature as of 2.7, clearly stated at the top No, smtp_bind_address is available in all Postfix versions since 2001. If Postfix complains like this: postfix/master[5309]: /etc/postfix/master.cf: line 6: bad transport type: smtp_bind_address=174.121.222.21 then line 6 in master.cf starts with -o smtp_bind_address=174.121.222.21 without the leading whitespace. No amount of Postfix reinstalling will fix that problem. Wietse
Re: Best method to post master.conf
Le 12/07/2011 06:16, jeffrey starin a écrit : I am trying to use the smtp_bind_address command so that three seperate ips can be used for 3 separate clients who are using email campaign software as explained in this howto: http://www.kutukupret.com/2010/01/02/postfix-bind-sender-domain-to-dedicated-outgoing-ip-address/ The error logs show the entry: Jul 11 23:46:31 who postfix/master[5309]: fatal: /etc/postfix/master.cf: line 6: bad transport type: smtp_bind_address=174.121.222.21 which refers to the the entries in the master.cf using that command, smtp_bind_address command. The second problem is even if I comment out those lines that refer to smtp_bind_address in the master.cf, I still receive that error in the logs which is very strange indeed. It's almost as if after commenting them out, postfix has a cached copy or something of the master.cf which it is using. I even restart postfix and postfix reload but to no avail. If someone sees something in the syntax (although I've double checked it so many times) let me know. I even upgraded to postfix 2.8.4 from 2.3.3 because I thought it may have had something to do with the version. master.cf: customer1 unix - - n - - smtp -o smtp_bind_address=174.121.222.21 This is wrong. you need spaces at the beginning of the continuation line. you really need to understand postfix syntax. it goes like this: servicename op1 opt2 opt3 program -o option=value -o option2=value2 ... with spaces in the continuation lines (all but the line the starts the definition of the service). [snip]
Re: Best method to post master.conf
On Tue, Jul 12, 2011 at 05:22:03PM -0400, Wietse Venema wrote: smtp_bind_address is a new feature as of 2.7, clearly stated at the top No, smtp_bind_address is available in all Postfix versions since 2001. If Postfix complains like this: postfix/master[5309]: /etc/postfix/master.cf: line 6: bad transport type: smtp_bind_address=174.121.222.21 then line 6 in master.cf starts with -o smtp_bind_address=174.121.222.21 without the leading whitespace. Indeed. Returning to the original topic though, I have a postmast(1) patch that adds a new utility that does with master.cf what postconf(1) does with main.cf. In particular it supports: postmast- show all entries in a machine-parseable normal form postmast -n - show non-default entries postmast -d - show default entries postmast -e - edit or add master.cf entries via CLI. I don't whether this is of sufficiently broad utility to warrant inclusion in the official release. -- Viktor.
Re: Best method to post master.conf
On 7/12/2011 4:22 PM, Wietse Venema wrote: smtp_bind_address is a new feature as of 2.7, clearly stated at the top No, smtp_bind_address is available in all Postfix versions since 2001. Correct. I got in hurry. Apologies. The 2.7 feature in the 'how-to' article he linked was: sender_dependent_default_transport_maps If Postfix complains like this: postfix/master[5309]: /etc/postfix/master.cf: line 6: bad transport type: smtp_bind_address=174.121.222.21 then line 6 in master.cf starts with -o smtp_bind_address=174.121.222.21 without the leading whitespace. No amount of Postfix reinstalling will fix that problem. My troubleshooting mistake was skimming the article, thinking it was relevant to the problem. Seeing that the OP upgraded from 2.3.3 to 2.8.4, my skimming of said article led me to believe it might be an upgrade issue. Note that I did say to upgrade only if mail_version=2.3.3, which it did not. Apologies for the noise as the problem lie elsewhere. -- Stan
Re: Best method to post master.conf
On Tue, 12 Jul 2011 17:35:56 -0400 Victor Duchovni articulated: Indeed. Returning to the original topic though, I have a postmast(1) patch that adds a new utility that does with master.cf what postconf(1) does with main.cf. In particular it supports: postmast - show all entries in a machine-parseable normal form postmast -n - show non-default entries postmast -d - show default entries postmast -e - edit or add master.cf entries via CLI. I don't whether this is of sufficiently broad utility to warrant inclusion in the official release. It gets a Thumbs Up from me. Perhaps a link similar to the postfinger tool might a adequate, although I favor the inclusion concept. Just my 2¢. -- Jerry ✌ postfix-u...@seibercom.net _ TO REPORT A PROBLEM see http://www.postfix.org/DEBUG_README.html#mail TO (UN)SUBSCRIBE see http://www.postfix.org/lists.html
Re: Best method to post master.conf
On Tue, Jul 12, 2011 at 05:56:42PM -0400, Jerry wrote: On Tue, 12 Jul 2011 17:35:56 -0400 Victor Duchovni articulated: Indeed. Returning to the original topic though, I have a postmast(1) patch that adds a new utility that does with master.cf what postconf(1) does with main.cf. In particular it supports: postmast- show all entries in a machine-parseable normal form postmast -n- show non-default entries postmast -d - show default entries postmast -e - edit or add master.cf entries via CLI. I don't whether this is of sufficiently broad utility to warrant inclusion in the official release. It gets a Thumbs Up from me. Perhaps a link similar to the postfinger tool might a adequate, although I favor the inclusion concept. The utility uses various Postfix library functions, and builds properly only within the Postfix source distribution, so if not adopted by Wietse, it would be an unofficial patch, and I don't think that releasing it as a patch makes much sense. If the community feels it's useful, perhaps Wietse will adopt it, otherwise it can quitely disappear... -- Viktor.
Re: Best method to post master.conf
I am trying to use the smtp_bind_address command so that three seperate ips
can be used for 3 separate clients who are using email campaign software as
explained in this howto:
http://www.kutukupret.com/2010/01/02/postfix-bind-sender-domain-to-dedicated-outgoing-ip-address/
The error logs show the entry:
Jul 11 23:46:31 who postfix/master[5309]: fatal: /etc/postfix/master.cf:
line 6: bad transport type: smtp_bind_address=174.121.222.21
which refers to the the entries in the master.cf using that command,
smtp_bind_address command.
The second problem is even if I comment out those lines that refer to
smtp_bind_address in the master.cf, I still receive that error in the logs
which is very strange indeed. It's almost as if after commenting them out,
postfix has a cached copy or something of the master.cf which it is using.
I even restart postfix and postfix reload but to no avail.
If someone sees something in the syntax (although I've double checked it so
many times) let me know. I even upgraded to postfix 2.8.4 from 2.3.3
because I thought it may have had something to do with the version.
master.cf:
customer1 unix - - n - - smtp
-o smtp_bind_address=174.121.222.21
-o smtp_helo_name=domain1.com
-o syslog_name=postfix-domain1.com
customer2 unix - - n - - smtp
-o smtp_bind_address=174.121.222.22
-o smtp_helo_name=domain2.org
-o syslog_name=postfix-domain2.org
customer3 unix - - n - - smtp
-o smtp_bind_address=174.121.222.23
-o smtp_helo_name=domain3.com
-o syslog_name=postfix-domain3.com
pickup fifo n - n 60 1 pickup -o content_filter=smtp:127.0.0.1:10027
cleanup unix n - n - 0 cleanup
qmgr fifo n - n 1 1 qmgr
tlsmgrunix - - n 1000? 1 tlsmgr
rewrite unix - - n - - trivial-rewrite
bounceunix - - n - 0 bounce
defer unix - - n - 0 bounce
trace unix - - n - 0 bounce
verifyunix - - n - 1 verify
flush unix n - n 1000? 0 flush
proxymap unix - - n - - proxymap
smtp unix - - n - - smtp
relay unix - - n - - smtp
-o fallback_relay=
showq unix n - n - - showq
error unix - - n - - error
discard unix - - n - - discard
local unix - n n - - local
virtual unix - n n - - virtual
lmtp unix - - n - - lmtp
anvil unix - - n - 1 anvil
scache unix--n-1scache
maildrop unix - n n - - pipe
flags=DRhu user=vmail argv=/usr/local/bin/maildrop -d ${recipient}
old-cyrus unix - n n - - pipe
flags=R user=cyrus argv=/usr/lib/cyrus-imapd/deliver -e -m ${extension}
${user}
cyrus unix - n n - - pipe
user=cyrus argv=/usr/lib/cyrus-imapd/deliver -e -r ${sender} -m
${extension} ${user}
uucp unix - n n - - pipe
flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail
($recipient)
ifmailunix - n n - - pipe
flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient)
bsmtp unix - n n - - pipe
flags=Fq. user=foo argv=/usr/local/sbin/bsmtp -f $sender $nexthop
$recipient
plesk_virtual unix - n n - - pipe flags=DORhu user=popuser:popuser
argv=/usr/lib64/plesk-9.0/postfix-local -f ${sender} -d ${recipient} -p
/var/qmail/mailnames
mailman unix - n n - - pipe flags=R user=mailman:mailman
argv=/usr/lib64/plesk-9.0/postfix-mailman ${nexthop} ${user} ${recipient}
127.0.0.1:10025 inet n n n - - spawn user=mhandlers-user
argv=/usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10027 before-queue
127.0.0.1:10026 inet n - n - - smtpd -o smtpd_client_restrictions= -o
smtpd_helo_restrictions= -o smtpd_sender_restrictions= -o
smtpd_recipient_restrictions=permit_mynetworks,reject -o
smtpd_data_restrictions= -o
receive_override_options=no_unknown_recipient_checks
127.0.0.1:10027 inet n n n - - spawn user=mhandlers-user
argv=/usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10026 before-remote
plesk_saslauthd unix y y n - 1 plesk_saslauthd status=5 listen=6
dbpath=/var/spool/postfix/plesk/passwd.db
pipeDomainA unix - n n - - pipe user=dukey argv=/usr/bin/php -q
/var/www/vhosts/domain1/httpdocs/admin/pipe_bounce.php
smtp inet n - n - - smtpd -o smtpd_proxy_filter=127.0.0.1:10025
smtps inet n - n - - smtpd -o smtpd_proxy_filter=127.0.0.1:10025 -o
smtpd_tls_wrappermode=yesretry unix - - n -
-
Re: Best method to post master.conf
On 7/11/2011 11:16 PM, jeffrey starin wrote: I am trying to use the smtp_bind_address command so that three seperate ips can be used for 3 separate clients who are using email campaign software as explained in this howto: http://www.kutukupret.com/2010/01/02/postfix-bind-sender-domain-to-dedicated-outgoing-ip-address/ The error logs show the entry: Jul 11 23:46:31 who postfix/master[5309]: fatal: /etc/postfix/master.cf: line 6: bad transport type: smtp_bind_address=174.121.222.21 I even upgraded to postfix 2.8.4 from 2.3.3 because I thought it may have had something to do with the version. smtp_bind_address is a new feature as of 2.7, clearly stated at the top of the article you linked. The fact that you receive the error with 2.3.3 and after you upgraded to 2.8.4 suggests that you didn't successfully replace 2.3.3 with 2.8.4. Posting the output of the following shell command will confirm this. ~$ postconf -d|grep 'mail_version =' If it says 2.3.3 you need to thoroughly remove all traces of that package (specifically /etc/init.d entries) and re-install 2.8.4 following these instructions: http://www.postfix.org/INSTALL.html -- Stan
Best method to post master.conf
Rather than post my master.conf in the wrong format here, what is the suggested way to post that information that in this forum. I will have a follow up question regarding it, but know it will be needed to help troubleshoot. I know people are rightfully finicky about how those things are posted so I am asking first. Thanks.
Re: Best method to post master.conf
On 7/10/2011 10:19 PM, jeffrey starin wrote: Rather than post my master.conf in the wrong format here, what is the suggested way to post that information that in this forum. I will have a follow up question regarding it, but know it will be needed to help troubleshoot. I know people are rightfully finicky about how those things are posted so I am asking first. Thanks. Either output of the postfinger tool (google for it), or something like grep -v '^#' master.cf to strip the comments. Please also include postconf -n output and logging demonstrating the problem. In your problem report, please be sure to tell us what you expected, and why you think there's a problem. http://www.postfix.org/DEBUG_README.html#mail
