From owner-freebsd-questions Tue Jun 11 4: 5:44 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by hub.freebsd.org (Postfix) with ESMTP id 59A3337B405 for ; Tue, 11 Jun 2002 04:05:27 -0700 (PDT) Received: from hades.hell.gr (patr530-a175.otenet.gr [212.205.215.175]) by mailsrv.otenet.gr (8.12.3/8.12.3) with ESMTP id g5BB5LZN001897 for ; Tue, 11 Jun 2002 14:05:23 +0300 (EEST) Received: from hades.hell.gr (hades [127.0.0.1]) by hades.hell.gr (8.12.3/8.12.3) with ESMTP id g5BB5FeP042156 for ; Tue, 11 Jun 2002 14:05:15 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from charon@localhost) by hades.hell.gr (8.12.3/8.12.3/Submit) id g5BB3TiX042105; Tue, 11 Jun 2002 14:03:29 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Tue, 11 Jun 2002 14:03:29 +0300 From: Giorgos Keramidas To: Alexander V Zubchenko Cc: FreeBSD Questions Subject: Re: SysAdm docs Message-ID: <20020611110329.GB41922@hades.hell.gr> References: <20020610140957.GA15454@hades.hell.gr> <20020611080552.P87143-100000@server.hermes-comp.zp.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020611080552.P87143-100000@server.hermes-comp.zp.ua> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 2002-06-11 08:30 +0300, Alexander V Zubchenko wrote: > On Mon, 10 Jun 2002, Giorgos Keramidas wrote: > > On 2002-06-10 13:32 +0300, Alexander V Zubchenko wrote: > > > > > > Second (not so global) question: After installing fbsd instead of linux on > > > my server some url's became unavaiable, some - avaiable from time to time. > > > > This question is too vague. What URLs? What do these URLs have to do > > with your server? > > E.g. http://rambler.ru (i can't connect), http://ya.ru (from time to time > it's also unreachable). But my friends simultaneously successfully connect > to them. I mean that some sites became unreachable as from server itself, > so and from LAN. That's still a bit of lacking in information. + Are you running a web server? + What software are you using for that web server? + Are those domains that you listed above configured as 'virtual domains'? + What are the relevant parts of your configuration files for them? + Are you using a log file with your web server? + When the problem pops up, is there anything interesting in your logs? > > > Some mail cannot b delivered due to 'Premature EOM' or 'timeout waiting > > > input during message collect' errors > > > > Can you post the relevant log lines? My guess is, .. but no, it's > > only a guess. Without knowing the exact messages, nobody can answer > > to you in detail, and correctly. > > O.K. But, imho, the only important info was show above. Here they r: > > *timeout* > _sendmail_ > Jun 5 00:10:48 server sendmail[36649]: g54KAmq36649: \ > to=, delay=01:00:00, pri=30000, \ > stat=timeout waiting for input during message collect Hmmm. This looks like your Sendmail stops getting any data after a while. Could it be that you have some firewall that blocks packets after a while? (After, for instance, a dynamic rule expires.) > Sorry for my english. I mean that Postfix does not resolve above > problem, but fully meet my requirements. And I don't need > customizability of sendmail for my tasks. Not advertising, but > satisfied user. Sorry again. Cool :) Yet another happy Postfix user. I know a lot of people who have found Postfix easier to configure and having no need for those extra bits of Sendmail, use it happily for a long time, and then forget all about mail servers. Glad you got it working so quickly ;) > I add there above log lines. And i log all smtp traffic. From my side > this looks like client send DATA, server (mine) reply with 354 and > after that.. nothing. Silence from client side before timeout. That is > for timeout which looks like timeout in both sendmail and postfix. > After timeout my server send to client '421 Error: timeout exceeded' > After that connection is closed w/o QUIT command. This doesn't look right. After the 354 responce, the client should immediatelly start writing the message to you. Unless of course, something is blocking the client. If you are using some sort of firewall, what is its configuration? What rules does it use to pass or block packets? > In case, when sendmail reported premature EOM, all is similar, but > after '421...' client reply with QUIT and connection is closed. - Giorgos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message