On Thu, 2005-07-14 at 10:07 +0200, jdd sur free wrote:

I can send mails from the client to the web from the client and from the gateway (kmail ou mail), but

* I can't send mail from a account of the gateway to an other account of the same gateway. gives me no error but mail vanishes (with "mail") or gives me an "domain not found" error with kmail (set from the gateway to the same acciunt. dns resolution by /etc/hosts)

* I can neither send a mail from the client to the gateway

* I can't receive mails on the gateway from the net try jdd@dodin.org if you wan't. Mails vanishes... no error, no return, I get cc's (to my ISP server).

I first tried with main.cf (postfix) raw from suse install, didn't work (all mails refused). I comment out all the suse stuff at the end of the file and it worked as said. I added this: myorigin = mecum perso dodin.org localhost

#le 12 juillet #mydestination = mecum.perso localhost.perso dodin.org mydomain = dodin.org myhostname = mecum.dodin.org mynetworks = 127.0.0.0/8 10.0.0.0/8

From the sample postfix docs., the parameters (in a list) are comma separated. Yours are separated by a space - try comma separated list in mynetworks, mydestination etc.

relay_domains = dodin.org

I suggest remove this, even though it does not do any harm. By default postfix picks this up from mydomain and will accept messages only for this domain from the 'Net.

#13 07 05 mydestination = perso dodin.org localhost.perso mecum.perso mecum.dodin.org relay_domains = dodin.org localhost perso ... any idea? may be the master.cf local host config?

Typically, the "stock" master.cf is sufficient to do what you are trying to do. I suggest keep tweaking the params in main.cf. Is .perso a valid TLD? I tried "whois mecum.perso" and it complained it did not know of a whois server for .perso object. Perhaps this is what postfix is complaining about as well. I suggest you go in the following manner to setup postfix. 1) Get your Intranet clients (10.0.0.0/8) to send outbound emails (relay) thru postfix. 2) For local Intranet accounts send mail in the form <user>@mecum.dodin.org (this makes the host fully qualified) 3) Ensure MX for dodin.org is pointing to the correct IP address of the server where postfix is running. 4) Get postfix to accept messages from the 'Net. Once this is working, mail to <user>@dodin.org will work as well i.s.o <user>@mecum.dodin.org. HTH, -- Arun Khan Linux is a wigwam: No Windows, No Gates, Apache inside.

jdd sur free wrote:

my config is:

client<--->gateway (mecum, domain dodin.org)<--->web

I wan to store all my mails on the gateway (in fact server, gateway, firewall).

If all that functionality is combined into one server you should be aware that you have to be careful not to expose your internal net unvoluntarily to the internet.

right now I have postfix and gpopper installed.

gpopper? Do you mean qpopper?

I can send mails from the client to the web from the client and from the gateway (kmail ou mail), but

So you can give the mail to postfix, and postfix sends the mail correctly to the internet.

* I can't send mail from a account of the gateway to an other account of the same gateway. gives me no error but mail vanishes (with "mail") or gives me an "domain not found" error with kmail (set from the gateway to the same acciunt. dns resolution by /etc/hosts)

The DNS error needs to be solved before any other experiments. (^-^)

* I can neither send a mail from the client to the gateway

Okay, no I am confused. Didn't you say that you could send a mail to postfix from the client?

* I can't receive mails on the gateway from the net try jdd@dodin.org if you wan't. Mails vanishes... no error, no return, I get cc's (to my ISP server).

Mails don't vanish, at least not with postfix. (^-^) What does the command "mailq" tell about mails in the queue?

I first tried with main.cf (postfix) raw from suse install, didn't work (all mails refused). I comment out all the suse stuff at the end of the file and it worked as said. I added this: myorigin = mecum perso dodin.org localhost

Sorry, that information is not sufficient to solve your problems. Please post the output of: postconf -n grep -v '^#' /etc/postfix/master.cf cat /etc/postfix/transport cat /etc/xinetd/qpopper cat /etc/xinetd chkconfig --list| grep ":on" netstat -tulpen

/var/log/mail gives this for my last try:

Jul 14 10:02:46 mecum postfix/qmgr[1762]: 3083C3FB6D: from=, size=943, nrcpt=1 (queue active)

message to my isp, receuved

Jul 14 10:02:47 mecum postfix/qmgr[1762]: 3083C3FB6D: to=, relay=none, delay=3099, status=deferred (transport is unavailable)

this leads to the problem, probably

Jul 14 10:03:07 mecum postfix/qmgr[1762]: warning: connect to transport local: Connection refused

The local transport is responsible for delivering mails to your local mail storage. Either the transport postfix uses for that purpuse is not defined or not working. I suspect that either your pop server is not running or the configuration of your pop server does not match the configuration of postfix.

any idea? may be the master.cf local host config?

pin is giving me the following information on qpopper: ./CD2/suse/src/qpopper-4.0.5-171.src.rpm: You have to agree to the license in ./CD2/suse/src/qpopper-4.0.5-171.src.rpm: /usr/share/doc/packages/qpopper/License.txt before being allowed to use ./CD2/suse/src/qpopper-4.0.5-171.src.rpm: qpopper. ./CD2/suse/src/qpopper-4.0.5-171.src.rpm: ./CD2/suse/src/qpopper-4.0.5-171.src.rpm: After installation you have to activate the server in the file ./CD2/suse/src/qpopper-4.0.5-171.src.rpm: /etc/inetd.conf or /etc/xinetd.d/qpopper. Sandy -- List replies only please! Please address PMs to: news-reply (@) japantest (.) homelinux (.) com