Sendmail problem in Suse 10.1 - relaying denied

[Clemens]

Hello,

I've got a sendmail problem on a my Scalix test server running Suse 10.1. I've searched the web for days now without luck, so I thought I'd try it here. I hope you don't mind, considering that this is not directly a Scalix-Issue...?

Problem:
I've set sendmail to use a relay from my provider by editing sendmail.cf aswell as the access and auth-info file. The .db files were created by running SuSEconfig. The type of authentication used is PLAIN.

When I try to send a message, I get the following error (I've tried both regfish and 1and1).

Now, the interesting bit is that everything works under Suse 10.0, using exactly the same logins. I'm beginning to think that it has to do the a new sendmail version (8.13.6) or sasl (2.1.21)?

Connecting to mailserv.regfish.com. via relay...
220 mailserv.regfish.com ESMTP
>>> EHLO my.servername
250-mailserv.regfish.com
250-PIPELINING
250-SIZE 104857600
250-AUTH LOGIN PLAIN
250 8BITMIME
>>> MAIL From:<root@my.servername> SIZE=599 AUTH=<>
250 ok
>>> RCPT To:<another@address>
>>> DATA
553 sorry, relaying denied from your location [my IP is here] (#5.7.1)

One thing on the side: I believe that I had it working until I installed Scalix for the first time (Not sure though, haven't got a good memory!). But even after uninstalling it, reinstalling sendmail, sasl etc it still does not work...

This problem kind of follows on the other one I had where I could not even send when Scalix was installed due to Suse's AppArmor. But I have it all disabled, so this should not have anything to do with it...

Thanks for your support guys!

Clemens

[ScalixSupport]

Hi,

we would need to see a complete SMTP transaction from the relay to see if it does authenticate OK. To do so, edit /var/opt/scalix/sys/smtpd.cfg and add the line DEBUG_LOG=TRUE at the top. Then, stop smtpd using omoff -d0 smtpd and then restart it using omon smtpd.

Then, send a test messages and post the contents of /var/opt/scalix/temp/smtpd.log here.

Have I mentioned Suse 10.1 is not supported yet?

Thanks,

Sascha.

[Clemens]

Hi Sascha,

first of all thanks for trying to help out even though it is not supported! I've read that it will be supported from the end of this year... Unfortunately, on my "playground-server" I was forced to run 10.1 as Suse 10.0 had some problems with my hardware... :-( Wouldn't dream of using it as a production system though, but I can't stop myself from trying things out! :-)

Also, I thought it could not hurt to ask, the worst thing that can happen is getting told off for using it! ;-) But I appreciate it very much that you are considering to help. Top man!

Right, regarding your help: I've added DEBUG_LOG=TRUE and restarted Scalix. But even after sending a couple of messages (+rebooting the server) the /var/opt/scalix/temp/smtpd.log doesn't exist... :-(

(AppArmor is off!!!)

Thanks!

Clemens

[ScalixSupport]

I think Sascha meant /var/opt/scalix/tmp/smtpd.log. Please have a look there.

Regards,
Don

[Clemens]

This one works better! :D

The output is:

SMTP Relay 10.0.1.3 started (8306): Mon, 12 Jun 2006 20:34:24 +0200 (CEST)
Accepted client 1 from (Test.server.eu)
Cli 8306/1 sent : 220 Test.server.eu ESMTP Scalix SMTP Relay 10.0.1.3; Mon, 12 Jun 2006 20:35:30 +0200 (CEST)

Cli 8306/1 rcvd: 'EHLO Test.server.eu'
Cli 8306/1 sent : 250-Test.server.eu Hello Test.server.eu [192.168.125.100], pleased to meet you
250-AUTH LOGIN GSSAPI
250-AUTH=LOGIN
250-DSN
250 8BITMIME

Cli 8306/1 rcvd: 'MAIL FROM:<Test-admin@mail.server.eu>'
Cli 8306/1 sent : 250 Test-admin@mail.server.eu... Sender ok

Cli 8306/1 rcvd: 'RCPT TO:<test@mydomain.com> NOTIFY=FAILURE,DELAY'
... new process 8487
8306: Allocate new unix.in process 8487
Cli 8306/1 rcvd U: '220 Scalix ESMTP Ready.'
Cli 8306/1 rcvd U: '250 Ok'
Cli 8306/1 sent U: rcpt to: <test@mydomain.com> NOTIFY=FAILURE,DELAY

Cli 8306/1 rcvd U: '250 Ok'
Cli 8306/1 sent : 250 Ok

Cli 8306/1 rcvd: 'DATA'
Cli 8306/1 sent : 354 Enter mail, end with "." on a line by itself (relay)

Cli 8306/1 sent U: data

Cli 8306/1 rcvd U: '354 Enter mail, end with "." on a line by itself.'
Cli 8306/1 got .
Cli 8306/1 sent U: Received: from Test.server.eu (Test.server.eu 192.168.125.100)
by Test.server.eu (Scalix SMTP Relay 10.0.1.3)
via ESMTP; Mon, 12 Jun 2006 20:35:30 +0200 (CEST)
Message-ID: <1088940267.1150137330173.JavaMail.root@Test.server.eu>
Date: Mon, 12 Jun 2006 20:35:30 +0200 (CEST)
From: Scalix Administrator <Test-admin@mail.server.eu>
To: test@mydomain.com
Subject: test
Mime-Version: 1.0

[ScalixSupport]

Hi Clemens,

If I understand your original message correctly, you're having problems sending outbound to your ISP via SMTPAuth. If that's the case, please post your access file (be sure to hide the password info) and verify that you've made the changes to your sendmail.cf file to use the access file info for SMTPAuth.

Thanks,
Rachel

[Clemens]

Hi,

this is my access file (with the top/info bit cut off)

Code: Select all

# ...info section above...
# Default for loop back is RELAY
127             RELAY

AuthInfo:smtp.1und1.com "U:ptXXXXXX-auth" "I:ptXXXXXX-auth" "P:XXXXX" "M:PLAIN"


The access.db file was created by running /sbin/SuSEconfig

And the corresponding section from the sendmail.cf:

Code: Select all

# "Smart" relay host (may be null)
DSsmtp.1und1.com


The interesting thing is that I have this setup working on another Suse 10.0 server!
:?

Thanks!

[ScalixSupport]

Hi Clemens,

Have you compared the sendmail.cf files on both machines, line by line to ensure they're the same? Also if you enable extended logging with sendmail and then try to send, what shows up in the maillog file?

Thanks,
Rachel

[Clemens]

The sendmail.cf files look identical to me...

This is the output from the sendmail log with high logging:

Code: Select all

sendmail[10854]: k5CMMjLU010854: from=root, size=233, class=0, nrcpts=1, msgid=<200606122222.k5CMMjLU010$
sendmail[10855]: k5CMMjDt010855: assigned id
sendmail[10855]: NOQUEUE: connect from localhost [127.0.0.1]
sendmail[10855]: AUTH: available mech=GSSAPI ANONYMOUS CRAM-MD5 DIGEST-MD5 LOGIN PLAIN, allowed mech=EXT$
sendmail[10855]: k5CMMjDt010855: Milter: no active filter
sendmail[10855]: k5CMMjDt010855: --- 220 .server.eu ESMTP Sendmail 8.13.6/8.13.6/SuSE Linux 0.8; Tu$
sendmail[10855]: k5CMMjDt010855: <-- EHLO .server.eu
sendmail[10855]: k5CMMjDt010855: --- 250-.server.eu Hello localhost [127.0.0.1], pleased to meet you
sendmail[10855]: k5CMMjDt010855: --- 250-ENHANCEDSTATUSCODES
sendmail[10855]: k5CMMjDt010855: --- 250-PIPELINING
sendmail[10855]: k5CMMjDt010855: --- 250-8BITMIME
sendmail[10855]: k5CMMjDt010855: --- 250-SIZE
sendmail[10855]: k5CMMjDt010855: --- 250-DSN
sendmail[10855]: k5CMMjDt010855: --- 250-ETRN
sendmail[10855]: k5CMMjDt010855: --- 250-AUTH GSSAPI DIGEST-MD5 CRAM-MD5
sendmail[10855]: k5CMMjDt010855: --- 250-DELIVERBY
sendmail[10855]: k5CMMjDt010855: --- 250 HELP
sendmail[10855]: k5CMMjDt010855: <-- MAIL From:<root@.server.eu> SIZE=233 AUTH=root@.server.eu
sendmail[10855]: ruleset=trust_auth, arg1=root@.server.eu, relay=localhost [127.0.0.1], reject=550 $
sendmail[10855]: k5CMMjDt010855: --- 250 2.1.0 <root@.server.eu>... Sender ok
sendmail[10855]: k5CMMjDt010855: <-- RCPT To:<address@server.com>
sendmail[10855]: k5CMMjDt010855: --- 250 2.1.5 <address@server.com>... Recipient ok
sendmail[10855]: k5CMMjDt010855: <-- DATA
sendmail[10855]: k5CMMjDt010855: --- 354 Enter mail, end with "." on a line by itself
sendmail[10855]: k5CMMjDt010855: from=<root@.server.eu>, size=480, class=0, nrcpts=1, msgid=<200606$
sendmail[10855]: k5CMMjDt010855: queueup ./qfk5CMMjDt010855
sendmail[10855]: k5CMMjDt010855: dropenvelope, e_flags=0x4604042, OpMode=d, pid=10855
sendmail[10855]: k5CMMjDt010855: queueup ./qfk5CMMjDt010855
sendmail[10855]: k5CMMjDt010855: unlock
sendmail[10855]: k5CMMjDt010855: unlink ./xfk5CMMjDt010855
sendmail[10855]: k5CMMjDt010855: ./xfk5CMMjDt010855: unlink-fail 2
sendmail[10859]: k5CMMjDt010855: disconnect level 2
sendmail[10859]: k5CMMjDt010855: in background, pid=10859
sendmail[10859]: k5CMMjDt010855: dowork, pid=10859
sendmail[10855]: k5CMMjDt010855: --- 250 2.0.0 k5CMMjDt010855 Message accepted for delivery
sendmail[10855]: k5CMMjDu010855: assigned id
sendmail[10854]: k5CMMjLU010854: to=address@server.com, ctladdr=root (0/0), delay=00:00:01, xdelay=$
sendmail[10855]: k5CMMjDu010855: <-- QUIT
sendmail[10855]: k5CMMjDu010855: --- 221 2.0.0 .server.eu closing connection
sendmail[10855]: k5CMMjDu010855: disconnect level 1


Thanks for all the time you guys+girls are spending on this!!!

[ScalixSupport]

Hi Clemens,

Without knowing what your server name is and who you're sending to, the log snippet you posted is rather confusing. However, it appears you posted the section where the message is handed off from Scalix to sendmail via localhost. If that's the case, there should be more to that entry that shows your server connecting to your ISP, that's the section we'll need to see. BTW, have you spoken to your ISP about how others connect to them via AuthSMTP via sendmail?

Thanks,
Rachel

[Clemens]

Hello again, I've done a bit of playing around and figured out the following:
1. I can copy paste the sendmail.cf, access and auth-info files from another system and get the same error, however it works on the other system in the same network.
--> not a simple auth configuration problem

2. It works all nicely on a fresh system, but following a Scalix install, it reverts to the above error... So I guess I'll have to look a bit deeper into how Scalix integrates itself with sendmail...

Now, would it be possible for you to tell me which files related to sendmail or sasl/authentication are changed during the scalix install?

Thanks,

Clemens

[ScalixSupport]

Hi Clemens,

Scalix adds some Scalix specific stuff into the sendmail.cf file, but if you're copying over a different sendmail.cf file, those items are being removed. In your previous posts you said you had this working with Scalix then it stopped working after (I believe) and upgrade. There's really nothing in the upgrade from 9.4 to 10.x that would have change this. We've provided a sasldb.so file since 9.1 but only Scalix should be using that. Are you saying that if you uninstall Scalix from your system then it starts working again, but if you re-install Scalix it stops working?

Thanks,
Rachel

[Clemens]

Ok, i've tried a couple of things...
I've set up another Suse box and set it to relay via my provider, works fine.
Then I've removed scalix, sasl and sendmail from the dodgy system, reinstalled them and copied all the entire folder /etc/mail as well as sendmail.cf over from the working system to the dodgy one.

Still the same problem! Maybe I got word blind if you know what I mean...
I will let it rest for a bit and start again in a couple of days with a clear mind... :-)

Thanks guys!
Clemens

[netphantom]

Hi,
i am interested in this topic ... ;)
Did someone got a solution for this case?

Best regards ...

[Clemens]

Hi,

I haven't had time to do any further testing, so the problem still remains... was thinking running VMwares at some point anyway, so I did not put any further effort on this problem either... sorry... :(

But please let me know if you come across a solution... !

Clemens