Problem sending mail

[jjc]

Hi,

I am very new to Scalix and recently finished the inital eval install. I created 2 userids. When attempting to send mail from one to the other, I receive a
Java Script Application warning window displaying "methodName = send".
I click on the OK button, the window dispears but no mail is sent.

What have I missed and/or how do I track the error down?

We are evaluating Scalix 9.2.0.211.

Thanks.

[ScalixSupport]

For any SWA-related issues, the first place to always look is the tomcat logs at $TOMCAT_HOME/logs.

The file catalina.out is the tomcat server log file but there may also be files beginning with scalix-swa for client-related problems.

Cheers

Dave

[aschomme]

First of all: i do not know if i have the same issue nor if the sendmail-log-entry i found is really related. But if so, it may help to fix the problem.

I have the same problem (on a server just being set up); in the sendmail-log, i see an error like

Code: Select all

Jun 13 19:24:38 scalix92 sendmail[8944]: ruleset=check_relay, arg1=scalix92.fs-edv.de, arg2=213.203.205.202, relay=scalix92.fs-edv.de [213.203.205.202], reject=550 5.7.1 Access denied

I have installed spamassassin as described in the knowledge-base (which also is not yet working); maye it is related. 213.203.205.202 is the primary ip (i.e. that of sendmail).

[jreeder]

I was having the exact same problem. After installing spamassassin and clamav per the knowledgebase instructions I can no longer send mail through swa.

I was getting the "methodname=send" popup.

The fix was to let swa know that it should be using the second port (as defined by the knowledgebase spamassassin instructions). By default scalix will configure swa during install to use the FQDN as smtp port. I think you have to override that value with the secondary address used in the spamassassin setup. Maybe I missed this part but I didn't see it in the instructions.

/etc/opt/scalix/webmail/partner.xml

edit "smtpServer=" and input the second ip address

But it still didn't work. The tomcat swa log indicated that webmail originated mail wasn't authenticated (methodname=send.....530 authentication required).

So I also had to loosen the rules in smtpd.cfg so that anonymous was allowed.

/var/opt/scalix/sys/smtpd.cfg

remove "ANONYMOUS reject ALL"
enable "RELAY accept .domain.com"

We're behind a firewall and the public internet can't access the second ip address that routes through scalix. Any mail to the FQDN from the internet is routed to the first ip address which should be handled by sendmail (per the scalix/spamassasin install instructions).


Is this going to open us up to relay spammers that forge the address as from .domain.com?

What am I missing? After logging into swa, shouldn't any mail that you send be properly authenticated?

[jreeder]

Following is the smtpd.log created when sending from webmail.

Is the webmail authenticating?

----------------------------------------------------------------------------
SMTP Relay 9.4.0.8 started (9622): Sun, 21 Aug 2005 09:27:48 -0400 (EDT)
Accepted client 1 from ()
Cli 9622/1 sent : 220 mail.domain.com ESMTP Scalix SMTP Relay 9.4.0.8; Sun, 21 Aug 2005 09:29:44 -0400 (EDT)

Cli 9622/1 rcvd: 'EHLO mail.domain.com'
Cli 9622/1 sent : 250-mail.domain.com Hello [192.168.2.241], pleased to meet you
250-AUTH GSSAPI CRAM-MD5 PLAIN DIGEST-MD5 LOGIN
250-AUTH=LOGIN
250-DSN
250 8BITMIME

Cli 9622/1 rcvd: 'MAIL FROM:<userid@domain.com>'
Cli 9622/1 sent : 250 userid@domain.com... Sender ok

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

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

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

Cli 9622/1 sent U: data

Cli 9622/1 rcvd U: '354 Enter mail, end with "." on a line by itself.'
Cli 9622/1 sent U: Received: from mail.domain.com ( 192.168.2.241)
by mail.domain.com (Scalix SMTP Relay 9.4.0.8)
via ESMTP; Sun, 21 Aug 2005 09:29:45 -0400 (EDT)
Message-ID: <23149395.1124630984941.JavaMail.root@mail.domain.com>
Date: Sun, 21 Aug 2005 09:29:44 -0400 (EDT)
From: Jay Reeder <userid@domain.com>
Reply-To: Jay Reeder <userid@domain.com>
To: euserid@gmail.com
Subject: test from scalix
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_Part_1_31361704.1124630984938"
X-Scalix-Id: userid@domain.com@domain.com
X-Client-IP: 68.158.xx.yy
X-Mailer: Scalix 9.4.0.52
X-MSMail-Priority:


Cli 9622/1 got .
Cli 9622/1 sent U: ------=_Part_1_31361704.1124630984938
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

test
------=_Part_1_31361704.1124630984938
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<html><head><style type="text/css"><!-- DIV {margin:0px;} P {margin:0px;} --></style></head><body><font face="times new roman,new york,times,serif" size=3>test
</font></body></html>
------=_Part_1_31361704.1124630984938--

.

Cli 9622/1 rcvd U: '250 Ok'
Cli 9622/1: Submitted message ': <23149395.1124630984941.JavaMail.root@mail.domain.com>' to unix.in.
response: '250 Ok'
Cli 9622/1 Finished submitting msg : <23149395.1124630984941.JavaMail.root@mail.domain.com>
Cli 9622/1 sent : 250 Ok

Cli 9622/1 rcvd: 'QUIT'
Cli 9622/1 sent : 221 mail.domain.com closing connection

[jreeder]

Not urgent at this point - but can anyone tell me if this looks like the webmail is authenticating or not? If not then is there something I need to do to get it working?

Thanks,

Jay

[ScalixSupport]

SWA doesn't authenticate. Because the mail submission from SWA can only happen through a tomcat session, the authentication (effectively) happens at login time.

Rather than specifying the domain in the RELAY accept line, you can specify a subnet or IP address.

For example,

RELAY accept 192.168.0.1

Be careful about the order that you add the lines, they are processed in order and the first match is the one that is used. So, if you put a RELAY reject ALL before and RELAY accept lines, the accept lines will *not* be used.

Cheers

Dave

[jreeder]

Ahh thanks.

The spamassassin howto in the knowledgebase instructs you to insert the line:

ANONYMOUS reject ALL

It seems this instruction would break swa smtp functions.