Re: [Vserver] Localhost definition problem with Postfix/Amavisd-new
Hi Alejandro! Today I write to Herbert because I lost my mail account password, but now I retrieve itso I have a question to ask you. I have Debian Etch with a vserver, having a base host and two vservers. One of these vservers has a LDAP server with localhost mapped to a private non-routable IP and it runs OK, and the other vserver has a mail server using Postfix/Courier/Amavisd-new/Spamassassin/Clamav, where I map localhost to 192.168.0.1 (another private non-routable IP). But I can't put the mail server to work because the Postfix can't establish a connection to the amavisd. Because of the variety of components I suspect that amavisd-new, spamassassin or clamav are hardcoded to 127.0.0.1, so I can't use a private non-routable IP as localhost. I'm running the same setup as you within vservers, without the need for a localhost address. Postfix instances can be bound to a specific address (see man 5 master), the same goes for amavisd-new ($inet_socket_bind). Calamav uses a unix-socket and spamassassin gets called via the Perl bindings (Mail::SpamAssassin). However if your using the spamd, you should be able to bind it to a specific address too (-i address iirc). My question is: do you recommend to me to map localhost to 127.0.0.1 as usual in my mail server (vserver) because some mail packages could be hardcoded ??? Or is it OK to continue using localhost mapped to 192.168.0.1 defined as the localhost interface of my vserver It's up to you, however I prefer to use a dedicated RFC 1918 address for each internal service and bind each daemon explicit to the dedicated address. regards, Chris ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Localhost definition problem with Postfix/Amavisd-new
HI Alejandro, But I can't put the mail server to work because the Postfix can't establish a connection to the amavisd. Because of the variety of components I suspect that amavisd-new, spamassassin or clamav are hardcoded to 127.0.0.1, so I can't use a private non-routable IP as localhost. I use exactly that setup in an vserver. Clamd can use sockets to communicate, in amavisd-new you can set all the IP-Adresses. The setup does not use spamd, as amavisd-new has native support for SpamAssassin. Try modifying your amavisd and clamd settings to reflect that, it should definitively work. In amavisd.conf the following variables should do ## # M T A I N T E R F A C E A N D D O M A I N S ## # where to forward checked mail $forward_method = 'smtp:1.2.3.4:fromamavis'; # where to submit notifications $notify_method = 'smtp:1.2.3.4:fromamavis'; # where to listen for incoming mail $inet_socket_port = 2005; $inet_socket_bind = '1.2.3.4'; # allow connections from these hosts only @inet_acl = qw( 127.0.0.1 ::1 1.2.3.4 ); Hope that helps, Baltasar ((( Baltasar Cevc ) World wide web: # http://www.openairkino.net/ (a project for the local youth; German only) # http://technik.juz-kirchheim.de/ (programming and admin projects) # http://baltasar.cevc-topp.de/ (private homepage) ) Phone: +49 176 23 22 08 22 ) PGP.sig Description: This is a digitally signed message part ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] unsubsribe
Christian Affolter wrote: Hi Alejandro! Today I write to Herbert because I lost my mail account password, but now I retrieve itso I have a question to ask you. I have Debian Etch with a vserver, having a base host and two vservers. One of these vservers has a LDAP server with localhost mapped to a private non-routable IP and it runs OK, and the other vserver has a mail server using Postfix/Courier/Amavisd-new/Spamassassin/Clamav, where I map localhost to 192.168.0.1 (another private non-routable IP). But I can't put the mail server to work because the Postfix can't establish a connection to the amavisd. Because of the variety of components I suspect that amavisd-new, spamassassin or clamav are hardcoded to 127.0.0.1, so I can't use a private non-routable IP as localhost. I'm running the same setup as you within vservers, without the need for a localhost address. Postfix instances can be bound to a specific address (see man 5 master), the same goes for amavisd-new ($inet_socket_bind). Calamav uses a unix-socket and spamassassin gets called via the Perl bindings (Mail::SpamAssassin). However if your using the spamd, you should be able to bind it to a specific address too (-i address iirc). My question is: do you recommend to me to map localhost to 127.0.0.1 as usual in my mail server (vserver) because some mail packages could be hardcoded ??? Or is it OK to continue using localhost mapped to 192.168.0.1 defined as the localhost interface of my vserver It's up to you, however I prefer to use a dedicated RFC 1918 address for each internal service and bind each daemon explicit to the dedicated address. regards, Chris ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] unsubsribe
Hi there, to unsubscribe headers show: List-Unsubscribe: http://list.linux-vserver.org/mailman/listinfo/vserver, mailto:[EMAIL PROTECTED] So unsubscription has a different mail adress which should be used. -- regards 'n greez, Guenther Fuchs (aka muh and powerfox) ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
