Re: bogus HELO name used
Oscar Mauricio Cruz Lazo a écrit : thanks alot my postconf -n here my config postconf -n apac3:~ # mailq Mail queue is empty apac3:~ # postconf -n alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases best_mx_transport = local biff = no command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/lib/postfix debug_peer_level = 2 defer_transports = disable_dns_lookups = no disable_mime_output_conversion = no html_directory = /usr/share/doc/packages/postfix/html inet_interfaces = all inet_protocols = all mail_owner = postfix mailbox_command = mailbox_size_limit = 0 mailbox_transport = cyrus mailq_path = /usr/bin/mailq manpage_directory = /usr/share/man message_size_limit = 10485760 mydestination = mysql:/etc/postfix/mysql-mydestination.cf http://mysql-mydestination.cf myhostname = apac3.apac.org.ni http://apac3.apac.org.ni if apac3.apac.org.ni is what the remote site sees, then it is not bogus and the remote site error is wrong. maybe they block you because of your generic reverse DNS: $ host 165.98.119.11 11.119.98.165.in-addr.arpa domain name pointer pppleon11.ibw.com.ni. but that's not what bogus helo means [snip]
Re: postmulti: inet_interfaces for each instance ?
David Touzeau: Dear I would like to implement multiple instances on my 2.7 postfix. After read the documentation (perhaps my english is very poor) i need to have a confirmation. did i need to disable master_service_disable and specify an IP address for each instance in inet_interfaces token ? The idea is that every Postfix instance listens on the interface address specified with its own inet_interfaces parameter setting. If you have a null client then it usually will not have an SMTP listener. Either comment out smtpd in master.cf or use master_service_disable=inet in main.cf. Wietse
Re: postmulti: inet_interfaces for each instance ?
David Touzeau: Dear I would like to implement multiple instances on my 2.7 postfix. After read the documentation (perhaps my english is very poor) i need to have a confirmation. did i need to disable master_service_disable and specify an IP address for each instance in inet_interfaces token ? The idea is that every Postfix instance listens on the interface address specified with its own inet_interfaces parameter setting. If you have a null client then it usually will not have an SMTP listener. Either comment out smtpd in master.cf or use master_service_disable=inet in main.cf. Wietse Many thanks Wietse for your answer in a week-end :=) so if i want to create 27 instances, i need to create 27 virtual IP addresses and set each in inet_interfaces on each dedicated main.cf. I was thinking that i should create 26 null clients and one instance is in charge of routing connexions to the right instance. (in the same way of an Apache server with vhosts) But i'm wrong. best regards
Re: postmulti: inet_interfaces for each instance ?
David Touzeau: David Touzeau: Dear I would like to implement multiple instances on my 2.7 postfix. After read the documentation (perhaps my english is very poor) i need to have a confirmation. did i need to disable master_service_disable and specify an IP address for each instance in inet_interfaces token ? The idea is that every Postfix instance listens on the interface address specified with its own inet_interfaces parameter setting. If you have a null client then it usually will not have an SMTP listener. Either comment out smtpd in master.cf or use master_service_disable=inet in main.cf. Wietse Many thanks Wietse for your answer in a week-end :=) so if i want to create 27 instances, i need to create 27 virtual IP addresses and set each in inet_interfaces on each dedicated main.cf. Each Postfix instance needs a main.cf file where you configure the myhostname, inet_interfaces, and the domain(s) that the instance will receive mail for (in mydestination, virtual_mailbox_domains, etc.). I was thinking that i should create 26 null clients and one instance is in charge of routing connexions to the right instance. If you put a mail router in front of the 26 instances, that mail router will need to forward mail via an SMTP connection to the instances. Therefore, each Postfix instance still needs a main.cf file where you configure the myhostname, inet_interfaces, and the domain(s) that the instance will receive mail for (in mydestination, virtual_mailbox_domains, etc.). (in the same way of an Apache server with vhosts) Apache does not forward requests for vhosts. Instead, Apache looks at the HTTP client's Host: header in the http request, and then it serves files from the document tree for that host. Wietse
Re: postmulti: inet_interfaces for each instance ?
David Touzeau: David Touzeau: Dear I would like to implement multiple instances on my 2.7 postfix. After read the documentation (perhaps my english is very poor) i need to have a confirmation. did i need to disable master_service_disable and specify an IP address for each instance in inet_interfaces token ? The idea is that every Postfix instance listens on the interface address specified with its own inet_interfaces parameter setting. If you have a null client then it usually will not have an SMTP listener. Either comment out smtpd in master.cf or use master_service_disable=inet in main.cf. Wietse Many thanks Wietse for your answer in a week-end :=) so if i want to create 27 instances, i need to create 27 virtual IP addresses and set each in inet_interfaces on each dedicated main.cf. Each Postfix instance needs a main.cf file where you configure the myhostname, inet_interfaces, and the domain(s) that the instance will receive mail for (in mydestination, virtual_mailbox_domains, etc.). I was thinking that i should create 26 null clients and one instance is in charge of routing connexions to the right instance. If you put a mail router in front of the 26 instances, that mail router will need to forward mail via an SMTP connection to the instances. Therefore, each Postfix instance still needs a main.cf file where you configure the myhostname, inet_interfaces, and the domain(s) that the instance will receive mail for (in mydestination, virtual_mailbox_domains, etc.). (in the same way of an Apache server with vhosts) Apache does not forward requests for vhosts. Instead, Apache looks at the HTTP client's Host: header in the http request, and then it serves files from the document tree for that host. Wietse It is clear Wietse , Topic closed... Many thanks for your time. Have a nice week-end...
