Sandy Drobic wrote:
Per Qvindesland wrote:
Hello Sandy,
Sorry could you provide a small sample on how to set this up, I got the same problem, Altermime works just fine but it adds the disclaimer in everytime it goes through the server, sucks when it has gone through the server 10 times.
It takes a bit of time to write all the stuff up, so I'll do it when I return home from office. Can't justify the time to do it during work. (^-^)
First step is to set up a second instance of postfix, then bind the first to on ip address, the second to another ip address. Both instances have their own config directory and their own queue directory. As soon as you have that running it it easy to configure transport and content filter according to your needs. I'll give an explicit example this evening.
I assume you are behind a firewall and the firewall forwards post 25 to your server running with a privat address. In this exampe I assume you use the address 192.168.1.10. You will need to bind a secondary address to your network card. You can do this in yast -> Network Devices -> Network Card (select your configured card) -> Advanced -> Add -> Fill in ip address, subnet mask and alias. Verify that you can ping that secondary address. Okay, here are the necessary steps to create a second instance of Postfix. mkdir /etc/postfix-new /var/spool/postfix-in cp /etc/postfix/* /etc/postfix-in/. postconf -e "alternate_config_directories = /etc/postfix-in" postconf -e "inet_interfaces = 192.168.1.10,127.0.0.1" postconf -c /etc/postfix-in -e "inet_interfaces = 192.168.1.11,127.0.0.1" postconf -c /etc/postfix-in -e "syslog_name = postfix-in" postconf -c /etc/postfix-in -e "queue_directory = /var/spool/postfix-in" Change the ports and options of all transports in /etc/postfix-in/master.cf according to your needs. Please check the log to see if any error pop up. Especially take care not to define the same port on localhost twice in both master.cf. There is no problem with the rest of the transports like "smtp" etc. that are bound to the secondary ip. Verify with testmails that mails are being relayed using the new instance on ip 192.168.1.11. Then after testing forward port 25 of your firewall to 192.168.1.11. You should be done. In this example both instances of Postfix listen on localhost, so take care that you do not leave the same port defined in both master.cf. Victor Duchovni posted such an example of a secondary script a few days ago in the postfix-users mailing list. I used it as a template for this example. Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com