![](https://seccdn.libravatar.org/avatar/dacaa21e4ebb17afe4d251a650d33615.jpg?s=120&d=mm&r=g)
Hi,
so now fetchmail has fetched about 900 mails from my imap, but fails to deliver it to my local inbox. During the yast configuration i tried several things with postfix and procmail, but without luck. in the logs (mail.info e.g.) i see the messages passing like this:
Mar 5 13:26:24 nfspdt2 postfix/qmgr[9450]: 0E1AB138AB2: to=
, orig_to= , relay=none, delay=10247, status=deferred (connect to loopback.mydomain[127.0.0.1]: Connection refused)
And... does loopback.mydomain exist? Is postfix really listening on that interface (check with postconf)? Firewall? Did you try to enable/disable spamassassin and/or amavis? More info would be seen in the previous or next line in the logs. i can connect from the commandline to loopback.mydomain 25 and postfix answers my connection. There is no firewall running either spamassin has never been turned on, amavis is, but now is turned back off and uninstalled. The log continues with similar lines from all the mails in the queue. in the warn logfile there appear (only sometimes) messages like this: 5 15:13:43 nfspdt2 postfix/smtp[11038]: warning: host loopback.mydomain[127.0.0.1] greeted me with my own hostname nfspdt2.mydomain Mar 5 15:13:43 nfspdt2 postfix/smtp[11038]: warning: host loopback.mydomain[127.0.0.1] replied to HELO/EHLO with my own hostname nfspdt2.mydomain It should work out of the box configuring it with Yast. Yep, i have had good experiences with yast, that's why i risked to take the shot :-) Pieter _________________________________________________________________
![](https://seccdn.libravatar.org/avatar/861b5545c111d2257fa12e533e723110.jpg?s=120&d=mm&r=g)
The 2004-03-05 at 17:24 +0100, luksedj luksedj wrote:
i can connect from the commandline to loopback.mydomain 25 and postfix answers my connection. There is no firewall running either spamassin has never been turned on, amavis is, but now is turned back off and uninstalled. The log continues with similar lines from all the mails in the queue.
Hold on: loopback.mydomain is another machine, isn't it? Then it needs to have an MX entry in the DNS server. I think you might be able to trick postfix to send to it without that requirement, but you need to write the IP number on the postfix configuration file somewhere - not sure about this. [...] Ah, read this, it applies to you: # On an intranet, specify the organizational domain name. If your # internal DNS uses no MX records, specify the name of the intranet # gateway host instead. # # In the case of SMTP, specify a domain, host, host:port, [host]:port, # [address] or [address]:port; the form [host] turns off MX lookups. # If you specify multiple SMTP destinations, Postfix will try them # in the specified order. # # relayhost = [an.ip.add.ress]
in the warn logfile there appear (only sometimes) messages like this:
5 15:13:43 nfspdt2 postfix/smtp[11038]: warning: host loopback.mydomain[127.0.0.1] greeted me with my own hostname nfspdt2.mydomain Mar 5 15:13:43 nfspdt2 postfix/smtp[11038]: warning: host loopback.mydomain[127.0.0.1] replied to HELO/EHLO with my own hostname nfspdt2.mydomain
Weird. Perhaps you have copied the configuration from one computer to the other: if so, change its domain name (/etc/postfix/main.cf): myhostname = telperion.valinor Make sure you set the computer name in yast, network configuration, different for both. -- Cheers, Carlos Robinson
participants (2)
-
Carlos E. R.
-
luksedj luksedj