[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Fwd: Re: [suse-security] Postfix connect to localhost connection refused]




--- Begin Message ---
Andreas Winkelmann wrote:

Am Dienstag, 22. Juni 2004 19:13 schrieb Emiliano Sutil:

I have installed posfix-2.0.19 on a Suse 9.1 and I have a problem when I
try to send mails using this server as outgoing smtp server.
If I send the mail from the server it works properly, but If I try to
send the email from another machine I always get this message in
/var/log/mail

Jun 22 19:03:06 adslinux2 postfix/qmgr[8285]: C95573125D:
to=<javier@xxxxxxxxxx>, relay=none, delay=4454, status=deferred (connect to
localhost[127.0.0.1]: Connection refused)

If I do the same from the server I get this log
Jun 22 19:08:22 adslinux2 postfix/pickup[8284]: CF0C231381: uid=0
from=<root>
Jun 22 19:08:22 adslinux2 postfix/cleanup[8355]: CF0C231381:
message-id=<40D86786.mail6G01346CY@xxxxxxxxxxxxxxxx>
Jun 22 19:08:22 adslinux2 postfix/qmgr[8285]: CF0C231381:
from=<root@xxxxxxxxxx>, size=421, nrcpt=1 (queue active)
Jun 22 19:08:22 adslinux2 postfix/local[8357]: CF0C231381:
to=<javier@xxxxxxxxxx>, orig_to=<javier>, relay=local, delay=0, status=sent
(delivered to maildir)
Jun 22 19:08:22 adslinux2 postfix/qmgr[8285]: CF0C231381: removed

I would guess, there is a content_filter defined in master.cf for the smtpd. But there is no content_filter (amavisd-new) installed/started.

Hi,
you guessed it

smtp      inet  n       -       n       -       2       smtpd -o content_filter=smtp:[localhost]:10024

...

localhost:10025 inet    n       -       n       -       -       smtpd -o content_filter=

And I have not started the amavisd-new. I installed because I want to use it right now but I want to run the server first without it, How I can, for the moment, eliminate this relation between postfix and amavis?

thanks

Emi







--- End Message ---
-- 
Check the headers for your unsubscription address
For additional commands, e-mail: suse-security-help@xxxxxxxx
Security-related bug reports go to security@xxxxxxx, not here