Discussion:
[SLE] Postfix error
(too old to reply)
Laurent Renard
2005-01-18 15:44:01 UTC
Permalink
I try to use postfix as smtp server but it can't work.
Here is the error log :

Action: failed
Status: 4.0.0
Diagnostic-Code: X-Postfix; delivery temporarily suspended: connect to
mx2.xxxxxx.xx[000.000.000.00]: Connection timed out

In that case xxxxxxx.xx and
000.000.000.00


represents my mail server

Could you help me ?
--
Laurent Renard
Sandy Drobic
2005-01-18 15:55:21 UTC
Permalink
Post by Laurent Renard
I try to use postfix as smtp server but it can't work.
Action: failed
Status: 4.0.0
Diagnostic-Code: X-Postfix; delivery temporarily suspended: connect to
mx2.xxxxxx.xx[000.000.000.00]: Connection timed out
In that case xxxxxxx.xx and 000.000.000.00
represents my mail server
Could you help me ?
No problem. Would you mind telling what version of Suse and Postfix you are
using, what options you already configured and what the desired result
should be?
I seem to have misplaced my crystal ball...

Sandy
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-***@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-***@suse.com
Laurent Renard
2005-01-18 16:12:10 UTC
Permalink
Excuse-me ;)

I use Suse 9.2 and Postfix 2.1.5-3

I just try to use "localhost" as smtp server in Mozilla thunderbird ...
that's all

Thank you
Laurent Renard
Post by Sandy Drobic
Post by Laurent Renard
I try to use postfix as smtp server but it can't work.
Action: failed
Status: 4.0.0
Diagnostic-Code: X-Postfix; delivery temporarily suspended: connect to
mx2.xxxxxx.xx[000.000.000.00]: Connection timed out
In that case xxxxxxx.xx and 000.000.000.00
represents my mail server
Could you help me ?
No problem. Would you mind telling what version of Suse and Postfix
you are using, what options you already configured and what the
desired result should be?
I seem to have misplaced my crystal ball...
Sandy
Patrick Shanahan
2005-01-18 16:27:01 UTC
Permalink
Post by Laurent Renard
I just try to use "localhost" as smtp server in Mozilla thunderbird ...
that's all
Please trim your quotes.

localhost is the address of your 'local' machine, not a smtp server or
an smtp ip client.

You use /usr/sbin/sendmail, or smtp-server.your.ip.com and thunderbird
will provide the sendmail function.
--
Patrick Shanahan Registered Linux User #207535
http://wahoo.no-ip.org @ http://counter.li.org
HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-***@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-***@suse.com
Hamish
2005-01-18 17:05:23 UTC
Permalink
Post by Laurent Renard
Excuse-me ;)
I use Suse 9.2 and Postfix 2.1.5-3
I just try to use "localhost" as smtp server in Mozilla thunderbird ...
that's all
Thank you
Laurent Renard
Post by Laurent Renard
I try to use postfix as smtp server but it can't work.
Action: failed
Status: 4.0.0
Diagnostic-Code: X-Postfix; delivery temporarily suspended: connect to
mx2.xxxxxx.xx[000.000.000.00]: Connection timed out
You might have misspelled "localhost" - tb would not resolve localhost
to MX2.xxx.xxx unless there is a DNS mess up somewhere - if it was
really trying to hit localhost the message would have been
localhost[127.0.0.1]: Connection timed out

Can you post the results of `dig localhost` and `dig localhost MX`,
maybe there is something there that will help.

Also you can try to connect manually, go `telnet localhost 25` - you
should get something like
Trying 127.0.0.1...
Connected to localhost. (this might also be yourdomain.name)
Escape character is '^]'.
"220 your.domain.name ESMTP Postfix"

If you cannot get that, try `telnet 127.0.0.1 25` - if neither work,
postfix is not running on port 25 - try rcpostfix restart and check what
it says

Hope that helps,
H
Laurent Renard
2005-01-18 18:09:39 UTC
Permalink
Dear Hamish,

thanks for your help.
Here's what "dig localhost MX" gives to me :

# dig localhost MX

; <<>> DiG 9.2.4 <<>> localhost MX
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29075
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;localhost. IN MX

;; AUTHORITY SECTION:
localhost. 604800 IN SOA localhost.
root.localhost. 1 604800 86400 2419200 604800

;; Query time: 54 msec
;; SERVER: 195.238.2.21#53(195.238.2.21)
;; WHEN: Tue Jan 18 19:05:26 2005
;; MSG SIZE rcvd: 68

My internet provider DNS is 195.238.2.21

The "dig localhost" telles me that localhost is 127.0.0.1

And finally, here's my "telnet localhost 25" result :

# telnet localhost 25
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
220 suse.local ESMTP Postfix

I don't understand what's the problem

Laurent Renard
Sandy Drobic
2005-01-18 20:19:31 UTC
Permalink
Post by Laurent Renard
# telnet localhost 25
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
220 suse.local ESMTP Postfix
I don't understand what's the problem
The problem is probably how you set up postfix. It seems to accept mail but
then it stumbles while processing the mail.

- How did you install and configure postfix? Yast, rpm install, build from
source?
- Did you configure postfix within yast or directly by editing main.cf,
master.cf etc? If so, which options are set?
- Did you install any other software that might have an impact, like an imap
server, amavisd-new, clam-av etc?

The only hint you gave us were some edited lines from the log. We are flying
blind in heavy fog without radar or map. (^-^)

It would help a lot if you could provide some log lines that would show the
process of the mail from the point where the server accepts the mail to the
point where the delivery fails.

Here are some line that show how the mail wanders through my system
including a scan for spam and virii by amavisd:

Jan 18 21:08:30 katgar postfix/smtpd[24657]: connect from
lists.suse.de[195.135.221.131]
Jan 18 21:08:30 katgar postfix/smtpd[24657]: AFE247A72:
client=lists.suse.de[195.135.221.131]
Jan 18 21:08:30 katgar postfix/cleanup[24658]: AFE247A72:
message-id=<***@gmail.com>
Jan 18 21:08:30 katgar postfix/qmgr[11084]: AFE247A72:
from=<suse-linux-e-return-223034-suse-linux-e=***@s
use.com>, size=3377, nrcpt=1 (queue active)
Jan 18 21:08:30 katgar postfix/smtp[24662]: starting TLS engine
Jan 18 21:08:30 katgar postfix/smtpd[24657]: disconnect from
lists.suse.de[195.135.221.131]
Jan 18 21:08:30 katgar postfix/smtp[24662]: connect to localhost[::1]:
Connection refused (port 10024)
Jan 18 21:08:30 katgar amavis[24650]: (24650-02) ESMTP::10024
/var/spool/amavis/amavis-20050118T210513-24650: <suse-linux-e-re
turn-223034-suse-linux-e=***@suse.com> ->
<suse-linux-***@japantest.homelinux.com> Received: SIZE=3377 from
japantest.homelinux.com ([127.0.0.1]) by localhost (japantest.homelinux.com
[127.0.0.1]) (amavisd-new, port 10024) with ESMTP
id 24650-02 for <suse-linux-***@japantest.homelinux.com>; Tue, 18 Jan 2005
21:08:30 +0100 (CET)
Jan 18 21:08:30 katgar amavis[24650]: (24650-02) Checking:
<suse-linux-e-return-223034-suse-linux-e=***@su
se.com> -> <suse-linux-***@japantest.homelinux.com>
Jan 18 21:08:31 katgar amavis[24645]: (24645-02) spam_scan: hits=0.999
tests=FROM_ENDS_IN_NUMS
Jan 18 21:08:31 katgar amavis[24645]: (24645-02) FWD via SMTP:
[127.0.0.1]:10025 <suse-linux-e-return-223034-suse-security=jap
***@suse.com> -> <suse-***@japantest.homelinux.com>
Jan 18 21:08:31 katgar postfix/smtpd[24665]: connect from localhost[127.0.0.1]
Jan 18 21:08:31 katgar postfix/smtpd[24665]: 9F3E07A74:
client=localhost[127.0.0.1]
Jan 18 21:08:31 katgar postfix/cleanup[24658]: 9F3E07A74:
message-id=<***@gmail.com>
Jan 18 21:08:31 katgar postfix/smtpd[24665]: disconnect from
localhost[127.0.0.1]
Jan 18 21:08:31 katgar postfix/qmgr[11084]: 9F3E07A74:
from=<suse-linux-e-return-223034-suse-security=japantest.homelinux.com@
suse.com>, size=3766, nrcpt=1 (queue active)
Jan 18 21:08:31 katgar amavis[24645]: (24645-02) Passed,
<suse-linux-e-return-223034-suse-security=***@sus
e.com> -> <suse-***@japantest.homelinux.com>, Message-ID:
<***@gmail.com>, Hits: 0.999
Jan 18 21:08:31 katgar amavis[24645]: (24645-02) TIMING [total 1431 ms] -
SMTP EHLO: 4 (0%), SMTP pre-MAIL: 1 (0%), SMTP pre-D
ATA-flush: 7 (0%), SMTP DATA: 38 (3%), body hash: 1 (0%), mime_decode: 45
(3%), get-file-type: 24 (2%), decompose_part: 5 (0%)
, parts: 0 (0%), AV-scan-1: 799 (56%), SA msg read: 5 (0%), SA parse: 7
(1%), SA check: 238 (17%), fwd-connect: 79 (6%), fwd-m
ail-from: 4 (0%), fwd-rcpt-to: 10 (1%), write-header: 16 (1%), fwd-data: 1
(0%), fwd-data-end: 126 (9%), fwd-rundown: 4 (0%),
unlink-1-files: 16 (1%), rundown: 1 (0%)
Jan 18 21:08:31 katgar postfix/smtp[24659]: 18EE87A60:
to=<suse-***@japantest.homelinux.com>, relay=localhost[127.0.0.1],
delay=2, status=sent (250 2.6.0 Ok, id=24645-02, from MTA: 250 Ok: queued
as 9F3E07A74)
Jan 18 21:08:31 katgar postfix/qmgr[11084]: 18EE87A60: removed

Sandy
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-***@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-***@suse.com
Laurent Renard
2005-01-18 22:04:57 UTC
Permalink
Dear Sandy,

i installed postfix with yast and configured it with yast
Postfix is running with clamav

I first would like to use it as smtp server
but it could be interesting to use it too to intercept my email accounts
too.

Best regards

Laurent Renard
Post by Sandy Drobic
Post by Laurent Renard
# telnet localhost 25
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
220 suse.local ESMTP Postfix
I don't understand what's the problem
The problem is probably how you set up postfix. It seems to accept
mail but then it stumbles while processing the mail.
- How did you install and configure postfix? Yast, rpm install, build
from source?
- Did you configure postfix within yast or directly by editing
main.cf, master.cf etc? If so, which options are set?
- Did you install any other software that might have an impact, like
an imap server, amavisd-new, clam-av etc?
The only hint you gave us were some edited lines from the log. We are
flying blind in heavy fog without radar or map. (^-^)
It would help a lot if you could provide some log lines that would
show the process of the mail from the point where the server accepts
the mail to the point where the delivery fails.
Here are some line that show how the mail wanders through my system
Jan 18 21:08:30 katgar postfix/smtpd[24657]: connect from
lists.suse.de[195.135.221.131]
client=lists.suse.de[195.135.221.131]
use.com>, size=3377, nrcpt=1 (queue active)
Jan 18 21:08:30 katgar postfix/smtp[24662]: starting TLS engine
Jan 18 21:08:30 katgar postfix/smtpd[24657]: disconnect from
lists.suse.de[195.135.221.131]
Connection refused (port 10024)
Jan 18 21:08:30 katgar amavis[24650]: (24650-02) ESMTP::10024
/var/spool/amavis/amavis-20050118T210513-24650: <suse-linux-e-re
japantest.homelinux.com ([127.0.0.1]) by localhost
(japantest.homelinux.com [127.0.0.1]) (amavisd-new, port 10024) with
ESMTP
2005 21:08:30 +0100 (CET)
Jan 18 21:08:31 katgar amavis[24645]: (24645-02) spam_scan: hits=0.999
tests=FROM_ENDS_IN_NUMS
[127.0.0.1]:10025 <suse-linux-e-return-223034-suse-security=jap
Jan 18 21:08:31 katgar postfix/smtpd[24665]: connect from
localhost[127.0.0.1]
client=localhost[127.0.0.1]
Jan 18 21:08:31 katgar postfix/smtpd[24665]: disconnect from
localhost[127.0.0.1]
suse.com>, size=3766, nrcpt=1 (queue active)
Jan 18 21:08:31 katgar amavis[24645]: (24645-02) Passed,
Jan 18 21:08:31 katgar amavis[24645]: (24645-02) TIMING [total 1431
ms] - SMTP EHLO: 4 (0%), SMTP pre-MAIL: 1 (0%), SMTP pre-D
45 (3%), get-file-type: 24 (2%), decompose_part: 5 (0%)
7 (1%), SA check: 238 (17%), fwd-connect: 79 (6%), fwd-m
ail-from: 4 (0%), fwd-rcpt-to: 10 (1%), write-header: 16 (1%),
fwd-data: 1 (0%), fwd-data-end: 126 (9%), fwd-rundown: 4 (0%),
unlink-1-files: 16 (1%), rundown: 1 (0%)
queued as 9F3E07A74)
Jan 18 21:08:31 katgar postfix/qmgr[11084]: 18EE87A60: removed
Sandy
Sandy Drobic
2005-01-18 22:13:49 UTC
Permalink
Post by Laurent Renard
Dear Sandy,
i installed postfix with yast and configured it with yast
Postfix is running with clamav
That might be a problem. Normally clam-av is called from within amavisd-new.
Probably you didn't configure postfix correctly to pass mails to clam-av and
then take them back after inspection.
What steps did you take to configure postfix within yast?

Sandy

PS: Please address your mails only to the mailing-list. I don't really need
a personal copy. (^-^)
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-***@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-***@suse.com
Laurent Renard
2005-01-19 06:33:50 UTC
Permalink
In fact, i didn't configure manually postfix
Everything was done by yast

DO i have to edit manually main.cf in /etc/postfix ?

Laurent Renard
Post by Sandy Drobic
Post by Laurent Renard
Dear Sandy,
i installed postfix with yast and configured it with yast
Postfix is running with clamav
That might be a problem. Normally clam-av is called from within
amavisd-new. Probably you didn't configure postfix correctly to pass
mails to clam-av and then take them back after inspection.
What steps did you take to configure postfix within yast?
Sandy
PS: Please address your mails only to the mailing-list. I don't really
need a personal copy. (^-^)
Laurent Renard
2005-01-19 06:52:58 UTC
Permalink
Here is my last attempt log :

Jan 19 07:49:59 mail postfix/smtp[16331]: connect to
mx2.epicuria.be[204.200.196.67]: Connection timed out (port 25)
Jan 19 07:49:59 mail postfix/smtp[16331]: B4DB711E44:
to=<***@epicuria.be>, relay=none, delay=12543, status=deferred (connect
to mx2.epicuria.be[204.200.196.67]: Connection timed out)

Is it possible that i cannot get out on port 25 ?

Laurent Renard
Post by Laurent Renard
In fact, i didn't configure manually postfix
Everything was done by yast
DO i have to edit manually main.cf in /etc/postfix ?
Laurent Renard
Post by Sandy Drobic
Post by Laurent Renard
Dear Sandy,
i installed postfix with yast and configured it with yast
Postfix is running with clamav
That might be a problem. Normally clam-av is called from within
amavisd-new. Probably you didn't configure postfix correctly to pass
mails to clam-av and then take them back after inspection.
What steps did you take to configure postfix within yast?
Sandy
PS: Please address your mails only to the mailing-list. I don't
really need a personal copy. (^-^)
Theo v. Werkhoven
2005-01-19 21:09:36 UTC
Permalink
Post by Laurent Renard
Jan 19 07:49:59 mail postfix/smtp[16331]: connect to
mx2.epicuria.be[204.200.196.67]: Connection timed out (port 25)
to mx2.epicuria.be[204.200.196.67]: Connection timed out)
Is it possible that i cannot get out on port 25 ?
Stranger things have happened.
Have you tried 'telnet 204.200.196.67 smtp' directly?

$ telnet 204.200.196.67 smtp
Trying 204.200.196.67...
Connected to 204.200.196.67.
Escape character is '^]'.
220 leolargo.tempdomainname.com ESMTP Sendmail 8.13.1/8.12.6; Wed,
19 Jan 2005 22:08:05 +0100 (CET)

Works here.

Theo
--
Theo v. Werkhoven Registered Linux user# 99872 http://counter.li.org
ICBM 52 13 26N , 4 29 47E. + ICQ: 277217131
SUSE 9.2 + Jabber: ***@jabber.xs4all.nl
Kernel 2.6.8 + MSN: twe-***@ferrets4me.xs4all.nl
See headers for PGP/GPG info. +
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-***@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-***@suse.com
Laurent Renard
2005-01-19 21:36:35 UTC
Permalink
it doesn't work from here ... but ... i try to connect to pop server and
not smtp
Laurent Renard
Post by Theo v. Werkhoven
Post by Laurent Renard
Jan 19 07:49:59 mail postfix/smtp[16331]: connect to
mx2.epicuria.be[204.200.196.67]: Connection timed out (port 25)
to mx2.epicuria.be[204.200.196.67]: Connection timed out)
Is it possible that i cannot get out on port 25 ?
Stranger things have happened.
Have you tried 'telnet 204.200.196.67 smtp' directly?
$ telnet 204.200.196.67 smtp
Trying 204.200.196.67...
Connected to 204.200.196.67.
Escape character is '^]'.
220 leolargo.tempdomainname.com ESMTP Sendmail 8.13.1/8.12.6; Wed,
19 Jan 2005 22:08:05 +0100 (CET)
Works here.
Theo
Theo v. Werkhoven
2005-01-19 22:25:59 UTC
Permalink
Post by Laurent Renard
it doesn't work from here ... but ... i try to connect to pop server and
not smtp
Then I'd say the probability that port 25 is blocked for you has
definitely increased.
And what does this POP server have to do with Postfix?

Oh, and please, *do not toppost anymore*.

Theo
--
Theo v. Werkhoven Registered Linux user# 99872 http://counter.li.org
ICBM 52 13 26N , 4 29 47E. + ICQ: 277217131
SUSE 9.2 + Jabber: ***@jabber.xs4all.nl
Kernel 2.6.8 + MSN: twe-***@ferrets4me.xs4all.nl
See headers for PGP/GPG info. +
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-***@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-***@suse.com
Ken Schneider
2005-01-19 22:33:31 UTC
Permalink
Post by Theo v. Werkhoven
Post by Laurent Renard
it doesn't work from here ... but ... i try to connect to pop server and
not smtp
Then I'd say the probability that port 25 is blocked for you has
definitely increased.
And what does this POP server have to do with Postfix?
Oh, and please, *do not toppost anymore*.
Check /etc/sysconfig/mail for a line like:

SMTPD_LISTEN_REMOTE="yes"

If it does not exist create the line and restart your mail server. If it
is "no" then that is what is blocking you from sending mail from this
machine.
--
Ken Schneider
UNIX since 1989
linux since 1994
SuSE since 1998
* Only reply to the list please*
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-***@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-***@suse.com
Laurent Renard
2005-01-19 22:57:38 UTC
Permalink
Post by Ken Schneider
Post by Theo v. Werkhoven
Post by Laurent Renard
it doesn't work from here ... but ... i try to connect to pop server and
not smtp
Then I'd say the probability that port 25 is blocked for you has
definitely increased.
And what does this POP server have to do with Postfix?
Oh, and please, *do not toppost anymore*.
SMTPD_LISTEN_REMOTE="yes"
If it does not exist create the line and restart your mail server. If it
is "no" then that is what is blocking you from sending mail from this
machine.
Always the same error ... a little bit far away :

Jan 19 23:55:20 mail postfix/qmgr[23245]: EC9FC12859:
to=<***@epicuria.be>, relay=none, delay=24, status=deferred (delivery
temporarily suspended: connect to mx2.epicuria.be[204.200.196.67]:
Connection timed out)
Jan 19 23:55:24 mail postfix/smtp[23261]: connect to
mx1.veriomail.com[129.250.36.52]: Connection timed out (port 25)
--
Laurent Renard
Carlos E. R.
2005-01-19 23:07:35 UTC
Permalink
Post by Ken Schneider
SMTPD_LISTEN_REMOTE="yes"
If it does not exist create the line and restart your mail server. If it
is "no" then that is what is blocking you from sending mail from this
machine.
You need to run "SuSEconfig --module postfix" to get those changes applied
to postfix. Then, reload postfix ("rcpostfix reload")
--
Cheers,
Carlos Robinson
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-***@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-***@suse.com
Carlos E. R.
2005-01-18 23:14:07 UTC
Permalink
Post by Laurent Renard
Dear Sandy,
i installed postfix with yast and configured it with yast
Postfix is running with clamav
I first would like to use it as smtp server
but it could be interesting to use it too to intercept my email accounts too.
We still need to see the log - part of it, of course, not whole.
--
Cheers,
Carlos Robinson
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-***@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-***@suse.com
Laurent Renard
2005-01-19 06:36:26 UTC
Permalink
Here is a part off my mail.err :
Jan 13 10:21:20 mail spamc[24768]: connect(AF_INET) to spamd at
127.0.0.1 failed, retrying (#1 of 3): Connection refused
Jan 13 10:21:21 mail spamc[24768]: connect(AF_INET) to spamd at
127.0.0.1 failed, retrying (#2 of 3): Connection refused
Jan 13 10:21:22 mail spamc[24768]: connect(AF_INET) to spamd at
127.0.0.1 failed, retrying (#3 of 3): Connection refused
Jan 13 10:21:23 mail spamc[24768]: connection attempt to spamd aborted
after 3 retries
Jan 13 10:30:50 mail spamc[24865]: connect(AF_INET) to spamd at
127.0.0.1 failed, retrying (#1 of 3): Connection refused
Jan 13 10:30:51 mail spamc[24865]: connect(AF_INET) to spamd at
127.0.0.1 failed, retrying (#2 of 3): Connection refused
Jan 13 10:30:52 mail spamc[24865]: connect(AF_INET) to spamd at
127.0.0.1 failed, retrying (#3 of 3): Connection refused
Jan 13 10:30:53 mail spamc[24865]: connection attempt to spamd aborted
after 3 retries
Jan 13 10:40:33 mail spamc[24951]: connect(AF_INET) to spamd at
127.0.0.1 failed, retrying (#1 of 3): Connection refused
Jan 13 10:40:34 mail spamc[24951]: connect(AF_INET) to spamd at
127.0.0.1 failed, retrying (#2 of 3): Connection refused
Jan 13 10:40:35 mail spamc[24951]: connect(AF_INET) to spamd at
127.0.0.1 failed, retrying (#3 of 3): Connection refused
Jan 13 10:40:36 mail spamc[24951]: connection attempt to spamd aborted
after 3 retries
Jan 14 10:22:31 mail postfix/qmgr[23230]: fatal: watchdog timeout
Jan 15 00:32:47 mail postfix/qmgr[30436]: fatal: watchdog timeout

Spamassassin seems not to work ;{

Laurent Renard
Post by Carlos E. R.
Post by Laurent Renard
Dear Sandy,
i installed postfix with yast and configured it with yast
Postfix is running with clamav
I first would like to use it as smtp server
but it could be interesting to use it too to intercept my email accounts too.
We still need to see the log - part of it, of course, not whole.
Sandy Drobic
2005-01-19 08:46:00 UTC
Permalink
Post by Laurent Renard
Jan 13 10:21:20 mail spamc[24768]: connect(AF_INET) to spamd at
127.0.0.1 failed, retrying (#1 of 3): Connection refused
Excellent! That is an error message we can work with. postfix is trying to
pass the mail to spamassassin and doesn't get a connect. Probably because
the service isn't running.

katgar:~ # netstat -tulpen | grep spam
tcp 0 0 127.0.0.1:783 0.0.0.0:* LISTEN
0 4095 1878/spamd -d -c -a

Here you can see that spamd is started and listening on port 783. If you
don't see such a line you need to start the service first.
Try to start spamassassin and give the deferred queue a kick to see if that
already solves the problem.

/etc/init.d/spamd start
postsuper -r ALL

Then check your maillog again to see if that solved the problem. If you you
need to tell your system to start the service spamd at boot time.

I definitely recommend to install and start the package amavisd-new. It is a
set of scripts that can be easily configured to run the virus scanner and
spamassassin.

Sandy
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-***@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-***@suse.com
Laurent Renard
2005-01-19 08:59:55 UTC
Permalink
Thanx for your great help sandy ;)

But it seems that spamd cannot start.
i tryied :
# /etc/init.d/spamd start
The error given is :

The -a option has been removed. Please look at the use_auto_whitelist
config option instead.

Laurent Renard
Epicuri@ Websolutions
www.epicuria.be <http://epicuria.be>
114, Rue Vandervelde
7033 MONS ( BELGIUM )
TEL/FAX : +32 65 31 77 81
SKYPE : leolargo2004
------------------------------------------------
Scanned with Clamav Antivirus on Procmail Server


This e-mail and any attachment thereto is confidential and are intended
for the sole use of the recipient(s) named above. Any use of the
information contenaid herein is prohibited.
If you have received this e-mail in error, please notify the sender
either by telephone or by e-mail and delete the material from any
computer. Thank you for your cooperation

Ce message electronique, y compris tout document joint, est
confidentiel. Si vous n'etes pas le destinataire de ce message, toute
divulgation, copie ou utilisation en est interdite.
Si vous avez recu ce message par erreur, veuillez le detruire et en
informer immediatement l'expediteur. Merci de votre collaboration
Post by Sandy Drobic
Post by Laurent Renard
Jan 13 10:21:20 mail spamc[24768]: connect(AF_INET) to spamd at
127.0.0.1 failed, retrying (#1 of 3): Connection refused
Excellent! That is an error message we can work with. postfix is
trying to pass the mail to spamassassin and doesn't get a connect.
Probably because the service isn't running.
katgar:~ # netstat -tulpen | grep spam
tcp 0 0 127.0.0.1:783 0.0.0.0:*
LISTEN 0 4095 1878/spamd -d -c -a
Here you can see that spamd is started and listening on port 783. If
you don't see such a line you need to start the service first.
Try to start spamassassin and give the deferred queue a kick to see if
that already solves the problem.
/etc/init.d/spamd start
postsuper -r ALL
Then check your maillog again to see if that solved the problem. If
you you need to tell your system to start the service spamd at boot time.
I definitely recommend to install and start the package amavisd-new.
It is a set of scripts that can be easily configured to run the virus
scanner and spamassassin.
Sandy
Hans du Plooy
2005-01-19 09:23:57 UTC
Permalink
Post by Laurent Renard
Thanx for your great help sandy ;)
But it seems that spamd cannot start.
# /etc/init.d/spamd start
The -a option has been removed. Please look at the use_auto_whitelist
config option instead.
edit /etc/sysconfig/spamd and remove the -a in the startup options.
--
Kind regards
Hans du Plooy
Newington Consulting Services
hansdp at newingtoncs dot co dot za
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-***@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-***@suse.com
Paul Cartwright
2005-01-19 20:11:04 UTC
Permalink
Post by Hans du Plooy
edit /etc/sysconfig/spamd and remove the -a in the startup options.
when I tried to start it I got this error:
:/etc/sysconfig # ERROR! spamassassin script is v3.000000, but using
modules v3.000001!


/etc/init.d/spamd looks like this:
( minus commented lines:)
SPAMD_ARGS="-d -c -a -L"
--
Paul Cartwright
Registered Linux user # 367800
X-Request-PGP: http://home.comcast.net/~p.cartwright/wsb/key.asc
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-***@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-***@suse.com
Hans du Plooy
2005-01-20 07:29:31 UTC
Permalink
Post by Paul Cartwright
Post by Hans du Plooy
edit /etc/sysconfig/spamd and remove the -a in the startup options.
:/etc/sysconfig # ERROR! spamassassin script is v3.000000, but using
modules v3.000001!
( minus commented lines:)
SPAMD_ARGS="-d -c -a -L"
Have you done the YOU updates? I'm sure there was an update for either
Spamassassin or some perl module that it requires.

Otherwise, did you by any chance upgrade spamassassin? How?
--
Kind regards
Hans du Plooy
Newington Consulting Services
hansdp at newingtoncs dot co dot za
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-***@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-***@suse.com
Laurent Renard
2005-01-20 07:42:00 UTC
Permalink
Post by Hans du Plooy
Post by Paul Cartwright
Post by Hans du Plooy
edit /etc/sysconfig/spamd and remove the -a in the startup options.
:/etc/sysconfig # ERROR! spamassassin script is v3.000000, but using
modules v3.000001!
( minus commented lines:)
SPAMD_ARGS="-d -c -a -L"
Have you done the YOU updates? I'm sure there was an update for either
Spamassassin or some perl module that it requires.
Otherwise, did you by any chance upgrade spamassassin? How?
I don't think that there's a problem with spamd
the real problem is that postfix cannot contact pop servers
;{
--
Laurent Renard
Hans du Plooy
2005-01-20 07:49:35 UTC
Permalink
Post by Laurent Renard
Post by Paul Cartwright
:/etc/sysconfig # ERROR! spamassassin script is v3.000000, but using
modules v3.000001!
( minus commented lines:)
SPAMD_ARGS="-d -c -a -L"
[snip]
Post by Laurent Renard
I don't think that there's a problem with spamd
the real problem is that postfix cannot contact pop servers
;{
Sorry, I missed the thread, just saw the spamd startup problem.

Yes, Postfix cannot contact a pop server.
--
Kind regards
Hans du Plooy
Newington Consulting Services
hansdp at newingtoncs dot co dot za
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-***@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-***@suse.com
Laurent Renard
2005-01-19 09:01:44 UTC
Permalink
amavisd-new is now installed.
Thanxx

Laurent Renard
Post by Sandy Drobic
Post by Laurent Renard
Jan 13 10:21:20 mail spamc[24768]: connect(AF_INET) to spamd at
127.0.0.1 failed, retrying (#1 of 3): Connection refused
Excellent! That is an error message we can work with. postfix is
trying to pass the mail to spamassassin and doesn't get a connect.
Probably because the service isn't running.
katgar:~ # netstat -tulpen | grep spam
tcp 0 0 127.0.0.1:783 0.0.0.0:*
LISTEN 0 4095 1878/spamd -d -c -a
Here you can see that spamd is started and listening on port 783. If
you don't see such a line you need to start the service first.
Try to start spamassassin and give the deferred queue a kick to see if
that already solves the problem.
/etc/init.d/spamd start
postsuper -r ALL
Then check your maillog again to see if that solved the problem. If
you you need to tell your system to start the service spamd at boot time.
I definitely recommend to install and start the package amavisd-new.
It is a set of scripts that can be easily configured to run the virus
scanner and spamassassin.
Sandy
Sandy Drobic
2005-01-19 09:22:55 UTC
Permalink
Post by Laurent Renard
amavisd-new is now installed.
Thanxx
So, is everything running or are there still some bugs lurking around?
Please check if the system is still running correcty after a reboot.

Sandy
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-***@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-***@suse.com
Hans du Plooy
2005-01-19 09:29:41 UTC
Permalink
Post by Sandy Drobic
I definitely recommend to install and start the package amavisd-new. It is
a set of scripts that can be easily configured to run the virus scanner and
spamassassin.
I have to side with Sandy here. amavisd-new is excellent glue for your
antivirus scanners, spamassassin and dspam. It took us about a month of
doing sa-learn daily, and we've had a 100% accuracy since.

Also, if you build virus-scanning mailservers for clients, adding amavis-stats
- http://rekudos.net/amavis-stats/ - is a nice touch. It uses rrdtool to
make graphs - http://rekudos.net/amavis-stats/node/view/7 - which will blow
your client's hair back, defnitely.

To have it work properly, you have to set your loglevel in /etc/amavisd.conf
to 5. I also separate the logfile, ad it to logrotate, and remove the
compress option (otherwise it throws out your graphs
accuracy.
--
Kind regards
Hans du Plooy
Newington Consulting Services
hansdp at newingtoncs dot co dot za
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-***@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-***@suse.com
Carlos E. R.
2005-01-19 23:10:02 UTC
Permalink
Here you can see that spamd is started and listening on port 783. If you don't
see such a line you need to start the service first.
Try to start spamassassin and give the deferred queue a kick to see if that
already solves the problem.
/etc/init.d/spamd start
try:

rcspamd start

it is shorther. Also "rc[tab][tab]" will give you a list of all available
services. :-)
--
Cheers,
Carlos Robinson
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-***@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-***@suse.com
Laurent Renard
2005-01-20 06:32:42 UTC
Permalink
Post by Carlos E. R.
Here you can see that spamd is started and listening on port 783. If you don't
see such a line you need to start the service first.
Try to start spamassassin and give the deferred queue a kick to see if that
already solves the problem.
/etc/init.d/spamd start
rcspamd start
it is shorther. Also "rc[tab][tab]" will give you a list of all available
services. :-)
everyting is done .. But ... still not works ...
--
Laurent Renard
Sandy Drobic
2005-01-20 09:36:26 UTC
Permalink
Post by Laurent Renard
everyting is done .. But ... still not works ...
So... What error messages came up while you executed these commands?

So far it seems as if postfix is trying to deliver the message to the mail
servers that are supposed to accept the messages according to the mx entries.
The time-out indicates that a connection to port 25 of those servers is not
accepted.

Try: telnet mx2.epicuria.be 25

The answer should be something like:
220 japantest.homelinux.com ESMTP Postfix

If you don't get such a message you have a problem on the server side.
Either mx2.epicuria.be does not listen on port 25 or a firewall is denying
you access to the port.

Sandy
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-***@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-***@suse.com
Laurent Renard
2005-01-20 16:10:10 UTC
Permalink
Post by Sandy Drobic
Post by Laurent Renard
everyting is done .. But ... still not works ...
So... What error messages came up while you executed these commands?
So far it seems as if postfix is trying to deliver the message to the
mail servers that are supposed to accept the messages according to the
mx entries.
The time-out indicates that a connection to port 25 of those servers
is not accepted.
Try: telnet mx2.epicuria.be 25
220 japantest.homelinux.com ESMTP Postfix
If you don't get such a message you have a problem on the server side.
Either mx2.epicuria.be does not listen on port 25 or a firewall is
denying you access to the port.
Sandy
No errors came from the commands.

Effectively, Sandy, i cannot access it using such a command. But I can
access it usin Thunderbird ... ?!
--
Laurent Renard
Sandy Drobic
2005-01-20 19:07:43 UTC
Permalink
Post by Laurent Renard
Post by Sandy Drobic
Try: telnet mx2.epicuria.be 25
220 japantest.homelinux.com ESMTP Postfix
No errors came from the commands.
Okay, I've said it before, but here it goes...
We are flying blind without a map and need your eyes to see what is happening.

So, let's try again.

remoteMailserver: mx2.epicuria.be
yourserver: ?
your-server-ip: ?
your-workstation-ip: ?

Do I assume correctly that you have a workstation that is sending a mail to
your local mailserver (or is it one and the same pc?!?) and this mailserver
tries to deliver a mail to mx2.epicuria.be and fails?
Or are you trying to set up a mailserver for an official domain on a host
that is connected permanently to the internet with a fixed official ip?
Post by Laurent Renard
Effectively, Sandy, i cannot access it using such a command. But I can
access it usin Thunderbird ... ?!
Not enough data to compute an intelligent suggestion. How did you configure
thunderbird and which server did you enter as smtp server?
Is thunderbird a client on your workstation or directly on the server
(localhost)?

Sandy
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-***@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-***@suse.com
Laurent Renard
2005-01-21 09:49:39 UTC
Permalink
Ah, now I see. Thunderbird has no problem delivering mails to your
local mailserver but the local mailserver itself can't send these
mails outside your system.
have you tried to send mails to any other system? You could try to
I guess you have a problem not related to postfix but rather a general
system setup problem.
- Is your Firewall turned on? Check yast -> security.
- Can you ping the server?
- Can you confirm that mx2.epicuria.be receives mails?
Sandy
PS: Please send Mails only to the list.
You're right sandy ;)

Yes i tried to send emails to other syustems and it fails too.
My firewall is turned off ( i got a router with firewall buit-in )
I can ping mx2.epicuria.be without any problems
And yes, it receives emails

Thanx for your great help ;)
--
Laurent Renard
Sandy Drobic
2005-01-21 12:21:46 UTC
Permalink
Post by Laurent Renard
I guess you have a problem not related to postfix but rather a general
system setup problem.
- Is your Firewall turned on? Check yast -> security.
- Can you ping the server?
- Can you confirm that mx2.epicuria.be receives mails?
Yes i tried to send emails to other syustems and it fails too.
My firewall is turned off ( i got a router with firewall buit-in )
I can ping mx2.epicuria.be without any problems
And yes, it receives emails
I just tried to contact mx2.epicuria.be and had no problems.
The command "telnet mx2.epicuria.be 25" returns:

220 leolargo.tempdomainname.com ESMTP Sendmail 8.13.1/8.12.6; Fri, 21 Jan
2005 13:15:17 +0100 (CET)
quit
221 2.0.0 leolargo.tempdomainname.com closing connection

If a telnet to port 25 of the remote system is not possible from your
system, then postfix won't be able to send an email either.

So, our next step to solving the mailproblem is to get the basic connection
to work. After you can contact the remote mailserver we can check to see if
postfix is working as it is supposed to.

Sandy
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-***@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-***@suse.com
Laurent Renard
2005-01-21 14:22:04 UTC
Permalink
Post by Sandy Drobic
Post by Laurent Renard
I guess you have a problem not related to postfix but rather a
general system setup problem.
- Is your Firewall turned on? Check yast -> security.
- Can you ping the server?
- Can you confirm that mx2.epicuria.be receives mails?
Yes i tried to send emails to other syustems and it fails too.
My firewall is turned off ( i got a router with firewall buit-in )
I can ping mx2.epicuria.be without any problems
And yes, it receives emails
I just tried to contact mx2.epicuria.be and had no problems.
220 leolargo.tempdomainname.com ESMTP Sendmail 8.13.1/8.12.6; Fri, 21
Jan 2005 13:15:17 +0100 (CET)
quit
221 2.0.0 leolargo.tempdomainname.com closing connection
If a telnet to port 25 of the remote system is not possible from your
system, then postfix won't be able to send an email either.
So, our next step to solving the mailproblem is to get the basic
connection to work. After you can contact the remote mailserver we can
check to see if postfix is working as it is supposed to.
Sandy
Yes Sandy,

my command :

telnet mx2.epicuria.be 25

returns :

Trying 204.200.196.67...

and nothing else ...

what kind of problem could it be ?
I can access mx2.epicuria.be 25 with all my email clients but postfix
cannot access it ?!
--
Laurent Renard
Sandy Drobic
2005-01-21 17:05:36 UTC
Permalink
Post by Sandy Drobic
telnet mx2.epicuria.be 25
Trying 204.200.196.67...
The next line should show the connection:

katgar:~ # telnet mx2.epicuria.be 25
Trying 204.200.196.67...
Connected to mx2.epicuria.be.
Escape character is '^]'.
220 leolargo.tempdomainname.com ESMTP Sendmail 8.13.1/8.12.6; Fri, 21 Jan
2005 17:46:40 +0100 (CET)
Post by Sandy Drobic
and nothing else ...
That is strange indeed. Your DNS seems to resolve the host to the correct ip
address but is unable to receive the connection?

What about pop3?

katgar:~ # telnet mx2.epicuria.be 110
Trying 204.200.196.67...
Connected to mx2.epicuria.be.
Escape character is '^]'.
+OK POP3 leolargo.tempdomainname.com 2004.87 server ready
quit
+OK Sayonara
Connection closed by foreign host.


katgar:~ # ping mx2.epicuria.be
PING mx2.epicuria.be (204.200.196.67) 56(84) bytes of data.
64 bytes from leolargo.tempdomainname.com (204.200.196.67): icmp_seq=1
ttl=53 time=111 ms

Is an icmp echo request with 'ping' really working?
Post by Sandy Drobic
what kind of problem could it be ?
I can access mx2.epicuria.be 25 with all my email clients but postfix
cannot access it ?!
Do you configure your email client on your mail server with mx2.epicuria.be
as your smtp server and it works? This shouldn't be possible since the
client is using the very same mechanism as we do with telnet on port 25.

Sandy
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-***@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-***@suse.com
Laurent Renard
2005-01-21 17:03:23 UTC
Permalink
I'd rather like to know what happens if you enter the command
telnet mx2.epicuria.be 25
in your console. As I wrote you should be able to see the lines I
mentioned.
Sandy
Here's what i get :
telnet mx2.epicuria.be 25
Trying 204.200.196.67...
telnet: connect to address 204.200.196.67: Connection timed out
--
Laurent Renard
Danny Sauer
2005-01-21 17:59:21 UTC
Permalink
Post by Sandy Drobic
I'd rather like to know what happens if you enter the command
telnet mx2.epicuria.be 25
in your console. As I wrote you should be able to see the lines I
mentioned.
Sandy
telnet mx2.epicuria.be 25
Trying 204.200.196.67...
telnet: connect to address 204.200.196.67: Connection timed out
There's your problem - DNS works, but the connection's dropped. Blame
your ISP.

You probably just need to set your smart_relay to point at your ISP's
smtp host, rather than letting your machine directly deliver itself.

--Danny
Sandy Drobic
2005-01-21 19:35:11 UTC
Permalink
Post by Danny Sauer
Post by Sandy Drobic
telnet mx2.epicuria.be 25
Trying 204.200.196.67...
telnet: connect to address 204.200.196.67: Connection timed out
There's your problem - DNS works, but the connection's dropped. Blame
your ISP.
You probably just need to set your smart_relay to point at your ISP's
smtp host, rather than letting your machine directly deliver itself.
It is indeed possible that the ISP has enforced a policy to allow smtp
client connections only to his own mail server.
That is the reason I asked you to connect via telnet to port 110 (pop3) as
well. That should work in any case because you have to be able to get your
mail via pop from any server you might need.

In that case you need to set the parameter
relayhost = [mail server of isp]
in /etc/postfix/main.cf. Alternatively you could use another ISP to connect
to the internet. (^-^)

Sandy
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-***@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-***@suse.com
Theo v. Werkhoven
2005-01-21 22:23:41 UTC
Permalink
Post by Danny Sauer
Post by Sandy Drobic
I'd rather like to know what happens if you enter the command
telnet mx2.epicuria.be 25
in your console. As I wrote you should be able to see the lines I
mentioned.
Sandy
telnet mx2.epicuria.be 25
Trying 204.200.196.67...
telnet: connect to address 204.200.196.67: Connection timed out
There's your problem - DNS works, but the connection's dropped. Blame
your ISP.
I came to that conclusion two days ago in
X-Message-Number-for-archive: 223195
:-P

Theo
--
Theo v. Werkhoven Registered Linux user# 99872 http://counter.li.org
ICBM 52 13 26N , 4 29 47E. + ICQ: 277217131
SUSE 9.2 + Jabber: ***@jabber.xs4all.nl
Kernel 2.6.8 + MSN: twe-***@ferrets4me.xs4all.nl
See headers for PGP/GPG info. +
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-***@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-***@suse.com
Danny Sauer
2005-01-24 16:16:31 UTC
Permalink
Post by Theo v. Werkhoven
Post by Danny Sauer
Post by Sandy Drobic
I'd rather like to know what happens if you enter the command
telnet mx2.epicuria.be 25
in your console. As I wrote you should be able to see the lines I
mentioned.
Sandy
telnet mx2.epicuria.be 25
Trying 204.200.196.67...
telnet: connect to address 204.200.196.67: Connection timed out
There's your problem - DNS works, but the connection's dropped. Blame
your ISP.
I came to that conclusion two days ago in
X-Message-Number-for-archive: 223195
:-P
I typed X-Message-Number-for-archive: 223273 before I had received any
other responses in that thread, but the machine I typed the response
on masqueraded my address, and the message didn't get posted until I
fixed the problem and resent. Unfortunately, that particular message
must've been missed even after it was finally posted, as neither the
postconf -n results or the telnet test were run until much later in
the thread. :)

So there. :)

--Danny, in second grade again

Danny Sauer
2005-01-20 15:14:58 UTC
Permalink
Post by Sandy Drobic
Post by Laurent Renard
Jan 13 10:21:20 mail spamc[24768]: connect(AF_INET) to spamd at
127.0.0.1 failed, retrying (#1 of 3): Connection refused
Excellent! That is an error message we can work with. postfix is trying to
pass the mail to spamassassin and doesn't get a connect. Probably because
the service isn't running.
Actually, if spamc can't connect spamd, it will just pass the mail
through without checking it for spam - so that wouldn't prevent
delivery of mail. It's a handy little safety feature, IMHO.

--Danny, who just discovered that his postfix has been stripping part
of his domain name, stopping plenty useful posts from arriving at the
list. Argh.
Danny Sauer
2005-01-20 15:17:53 UTC
Permalink
Post by Laurent Renard
i installed postfix with yast and configured it with yast
Postfix is running with clamav
I first would like to use it as smtp server
but it could be interesting to use it too to intercept my email accounts
too.
To get postfix to deliver your mail, it has to either have access
to a working DNS server, or access to a mail server that will relay on
its behalf. It then has to know what's local, and what's not local.

The defaults generally work very well. To let us know exactly how
things are configured, it would probably help to send the output of
"postconf -n" and the output of "postconf mydomain myhostname". It
would also be helpful to know what kind of connection you're on -
dial-up or broadband - and whether your ISP will allow outgoing
connections on port 25. To test that last thing, just telnet to some
arbitrary mail server on port 25, like "telnet mail.suse.com 25" (then
type QUIT, followed by a return).

BTW, postconf -n will display non-default settings, so we know what's
changed.

--Danny, pretty sure we can get your needs met
Continue reading on narkive:
Loading...