Adding footer to outgoing messages with postfix
Hi all! Recently in my office I've been "suggested" to automatically add a footer to all outgoing emails, as General Management has accorded. As Postfix doesn't have this feature I've been "googling" a little bit and I've found AlterMime to add the disclaimer. I've installed it and everything works fine but with a little not wanted feature: it adds the disclaimer to *every* mail postfix treats, it doesn't matter if it's outgoing or incoming mails. I've seen in AlterMime documentation that it could be easily solved with a new network device but I need another solution as installing a new network card is simply not possible. So, my 2 questions for you all are: -) has anybody succeed in marking all outgoing messages but not incoming, with only one network card? How have you done it? ;-) -) does anybody know another way to add footers in outgoing messages? Thanks in advance :-) David
David wrote:
Hi all!
Recently in my office I've been "suggested" to automatically add a footer to all outgoing emails, as General Management has accorded.
As Postfix doesn't have this feature I've been "googling" a little bit and I've found AlterMime to add the disclaimer. I've installed it and everything works fine but with a little not wanted feature: it adds the disclaimer to *every* mail postfix treats, it doesn't matter if it's outgoing or incoming mails. I've seen in AlterMime documentation that it could be easily solved with a new network device but I need another solution as installing a new network card is simply not possible.
It is not necessary to add another network card, you can achieve this by adding another instance of postfix. Then you can separate incoming and outgoing mails. Incoming -> Instance 1 (IP1) -> content_filter=amavis (antispam/antivirus) -> internal server Outgoing -> instance 2 (IP2) -> content_filter=altermime -> Internet Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com
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. Regards Per Qvindesland On Tuesday 13 December 2005 10:46, Sandy Drobic wrote:
David wrote:
Hi all!
Recently in my office I've been "suggested" to automatically add a footer to all outgoing emails, as General Management has accorded.
As Postfix doesn't have this feature I've been "googling" a little bit and I've found AlterMime to add the disclaimer. I've installed it and everything works fine but with a little not wanted feature: it adds the disclaimer to *every* mail postfix treats, it doesn't matter if it's outgoing or incoming mails. I've seen in AlterMime documentation that it could be easily solved with a new network device but I need another solution as installing a new network card is simply not possible.
It is not necessary to add another network card, you can achieve this by adding another instance of postfix. Then you can separate incoming and outgoing mails.
Incoming -> Instance 1 (IP1) -> content_filter=amavis (antispam/antivirus) -> internal server Outgoing -> instance 2 (IP2) -> content_filter=altermime -> Internet
Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com
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. Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com
Can anyone help with setting up fetchmail for Gmail's smtp protocol? I have tried using the YaST tool that configures the /etc/fetchmailrc file. However its unable to retrieve mails from my GMail account.
On Tue December 13 2005 8:28 am, Biyi Akinpelu wrote:
Can anyone help with setting up fetchmail for Gmail's smtp protocol? I have tried using the YaST tool that configures the /etc/fetchmailrc file. However its unable to retrieve mails from my GMail account. I used kmail setup, configured it for pop.gmail.com port 995 and it worked fine.
I forget if there is a pop section you have to turn on in the gmail web interface... -- Paul Cartwright Registered Linux user # 367800
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2005-12-13 at 15:28 +0200, Biyi Akinpelu wrote:
Can anyone help with setting up fetchmail for Gmail's smtp protocol? I have tried using the YaST tool that configures the /etc/fetchmailrc file. However its unable to retrieve mails from my GMail account.
What does that have to do with "Adding footer to outgoing messages with postfix"? Please, if you want answers, be polite and don't hijack threads. To answer your question this once, fetchmail doesn't do "smtp protocol", but it does pop3. If that's what you want, add the ssl option to the config.. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDn3vPtTMYHG2NR9URAh4bAJ0WF9Mu3Aa9e4YI7Fd6JD7IIzcG9ACfXkym opT4WB9ydVOny6VaINrR8kU= =aaxn -----END PGP SIGNATURE-----
On Tuesday 13 December 2005 8:56 pm, Carlos E. R. wrote:
To answer your question this once, fetchmail doesn't do "smtp protocol", but it does pop3. If that's what you want, add the ssl option to the config.. It also does imap. -- Jerry Feldman
Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
How can this ms transplant be removed or disabled in suse 10? Any help will be appreciated.
On Wednesday 14 December 2005 12:28 pm, kanenas@hawaii.rr.com wrote:
How can this ms transplant be removed or disabled in suse 10? Any help will be appreciated.
That thing has bothered me too.... I think if you go into control center --> security --> kde wallet --> access --> Prompt on wallet open You'll find it checked. Uncheck it. Seems to work here.
On Wednesday 14 December 2005 07:56, Bruce Marshall wrote:
On Wednesday 14 December 2005 12:28 pm, kanenas@hawaii.rr.com wrote:
How can this ms transplant be removed or disabled in suse 10? Any help will be appreciated.
That thing has bothered me too....
I think if you go into control center --> security --> kde wallet --> access --> Prompt on wallet open
You'll find it checked. Uncheck it.
Seems to work here.
Thanks, that did it! btw, i also went to the general tab and disabled kwallet completely:) no ill effects yet!
On Thursday 15 December 2005 1:36 pm, kanenas@hawaii.rr.com wrote: <snip>
Thanks, that did it! btw, i also went to the general tab and disabled kwallet completely:) no ill effects yet! What Kwallet is supposed to do, if I understand correctly is encrypt the file or otherwise make it not human readable w/o the password for the wallet. Very handy for any sort of portable device w/ your information on it . Especially anything you would prefer not get into the hands of strangers. IF you look at the wallet files, when it's enabled you see nothing.. until you do it via password and gui then suddenly passwords for email and anything else you save in the wallet are readable...
-- j Don't try to change my attitude or rearrange my latitude; Don't tell me what I think, I got to get me some boat drinks
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2005-12-14 at 08:54 -0500, Jerry Feldman wrote:
To answer your question this once, fetchmail doesn't do "smtp protocol", but it does pop3. If that's what you want, add the ssl option to the config.. It also does imap.
Of course, and not only those two; but gmail does not offer imap, so it is useless for the OP. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDofl6tTMYHG2NR9URAg6tAJ4tY1Uq4GK2TSykbjnyDUxwgOPXVQCfZj3g m0RqPFHq11USfbYDSv6MmuA= =eF8l -----END PGP SIGNATURE-----
On Thursday 15 December 2005 6:17 pm, Carlos E. R. wrote:
The Wednesday 2005-12-14 at 08:54 -0500, Jerry Feldman wrote:
To answer your question this once, fetchmail doesn't do "smtp protocol", but it does pop3. If that's what you want, add the ssl option to the config..
It also does imap.
Of course, and not only those two; but gmail does not offer imap, so it is useless for the OP. I would agree here, but when I answer a question on a listserv, I prefer to generalize the answer for others. I really don't care what gmail does or does not do, I was speaking in terms of what fetchmail can do.
--
Jerry Feldman
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
David wrote:
documentation that it could be easily solved with a new network device but I need another solution as installing a new network card is simply not possible.
It seems to those footers make people seem foolish, there is some doubt as to their efficacy, and they irritate people (think big sigs, and the longstanding guidelines on those). IMV if you send me something, it's just like real mail: it's mine to do with as I wish. Unless we have a prearranged agreement to the contrary. But, IANAL. Besides, no doubt law variies from country to country and with intercourse between countries. For creating multiple interfaces: ifconfig dummy0 ... ifconfig eth0:1 .... create a VPN (the interfaces are a side effect, but routing is exactlyt as if you have real wire between the endpoints).
participants (11)
-
Biyi Akinpelu
-
Bruce Marshall
-
Carlos E. R.
-
David
-
Jerry Feldman
-
jfweber@bellsouth.net
-
John Summerfield
-
kanenas@hawaii.rr.com
-
Paul Cartwright
-
Per Qvindesland
-
Sandy Drobic