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 Sandy Drobic wrote:

Laurent Renard wrote:

...

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 ?

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

Laurent Renard wrote:

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

Sandy Drobic wrote:

...

Laurent Renard wrote:

...

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

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 wrote:

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

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=<200501182006.57509.riccardo35@gmail.com> Jan 18 21:08:30 katgar postfix/qmgr[11084]: AFE247A72: from=, 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=japantest.homelinux.com@suse.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 ; Tue, 18 Jan 2005 21:08:30 +0100 (CET) Jan 18 21:08:30 katgar amavis[24650]: (24650-02) Checking: -> 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 -> 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=<200501182006.57509.riccardo35@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=, size=3766, nrcpt=1 (queue active) Jan 18 21:08:31 katgar amavis[24645]: (24645-02) Passed, -> , Message-ID: <200501182006.57509.riccardo35@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=, 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

Laurent Renard wrote:

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. (^-^)

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=, 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 Laurent Renard wrote:

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

Sandy Drobic wrote:

...

Laurent Renard wrote:

...

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. (^-^)

it doesn't work from here ... but ... i try to connect to pop server and not smtp Laurent Renard Theo v. Werkhoven wrote:

Wed, 19 Jan 2005, by lrenard@epicuria.be:

...

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=, 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 ?

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

On Wed, 2005-01-19 at 17:25, Theo v. Werkhoven wrote:

Wed, 19 Jan 2005, by lrenard@epicuria.be:

...

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*

The Wednesday 2005-01-19 at 17:33 -0500, Ken Schneider wrote:

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.

You need to run "SuSEconfig --module postfix" to get those changes applied to postfix. Then, reload postfix ("rcpostfix reload") -- Cheers, Carlos Robinson

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 Carlos E. R. wrote:

The Tuesday 2005-01-18 at 23:04 +0100, Laurent Renard wrote:

...

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.

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 Sandy Drobic wrote:

Laurent Renard wrote:

...

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

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

On Wednesday 19 January 2005 4:23 am, Hans du Plooy wrote:

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

Hans du Plooy wrote:

On Wednesday 19 January 2005 22:11, Paul Cartwright wrote:

...

On Wednesday 19 January 2005 4:23 am, Hans du Plooy wrote:

...

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"

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

amavisd-new is now installed. Thanxx Laurent Renard Sandy Drobic wrote:

Laurent Renard wrote:

...

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

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

On Wednesday 19 January 2005 10:46, Sandy Drobic wrote:

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

Carlos E. R. wrote:

The Wednesday 2005-01-19 at 09:46 +0100, Sandy Drobic wrote:

...

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. :-)

everyting is done .. But ... still not works ... -- Laurent Renard

Sandy Drobic wrote:

Laurent Renard wrote:

...

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

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 wrote regarding 'Re: [SLE] Postfix error' on Wed, Jan 19 at 02:46:

Laurent Renard wrote:

...

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

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.