550 Denied due to spam list - please help....

[ericsheats]

I have looked through many posts trying to find an answer to my problem. I have suse 10 OSS and CE working on everything except outbound mail.

I can recieve mail, send to other accounts on the CE server, use the group functions, and send/rec calendar invites, and SSL works perfect....it is great.

but - I cant send mail out; log reports this:

2006-07-20 17:07:27 StandardContext[/webmail]ip: username: ; message: SMTP send: Unable to send message to one or more addresses

javax.mail.SendFailedException: Invalid Addresses;
nested exception is:
class javax.mail.SendFailedException: 550 Denied due to spam list

at com.sun.mail.smtp.SMTPTransport.rcptTo(SMTPTransport.java:926)
at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:389)
at com.oddpost.server.module.SoapMail.sendMessage(SoapMail.java:1926)
at com.oddpost.server.module.SoapMail.send(SoapMail.java:1089)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.oddpost.soap.SoapModule.invokeMethod(SoapModule.java:238)
at com.oddpost.soap.SoapRequestImpl.execute(SoapRequestImpl.java:139)
at com.oddpost.server.HttpRequestHandler.handleRequest(HttpRequestHandler.java:222)
at com.oddpost.server.SoapServlet.doPost(SoapServlet.java:50)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at com.oddpost.server.filter.HttpConfFilter.doFilter(HttpConfFilter.java:182)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186)
... skipping the last 25 lines as irrelevant...

2006-07-20 17:07:27 StandardContext[/webmail]ip: username: message: <SOAP-ENV:Fault><faultcode>SOAP-ENV:SERVER.SomeRecipientsRefused</faultcode><faultstring>Unable to send mail to: outside address

</faultstring><detail><e:SomeRecipientsRefused xmlns:e="http://scalix.com/errors"><message>Unable to send mail to:

outside address </message><debug>[none]</debug></e:SomeRecipientsRefused></detail></SOAP-ENV:Fault>

[ScalixSupport]

Hi,

Denied due to spam list always indicates that the IP address of the SWA server is not listed in the RELAY accept lines in /var/opt/scalix/sys/smtpd.cfg Please make sure you update you smtpd.cfg file

Cheers,
Yuri

[ericsheats]

thanks for the help...

[gregwatson]

Where is this documented? I am trying the evaluation edition and so far I'm not impressed. I had this error as well, which isn't particularly impressive for an out-of-the-box evaluation install.

I'm also amazed at the poor LDAP support. I am trying to install thi on a server which already has an LDAP server running - you would have thought this was a very common scneario. Following instructions in another post I have read how to change the LDAP port for the Scalix LDAP server so they don't clash - but then the SAC doesn't work! It seems also that the address book doesn't work in this configuration - but I will test that again in a moment.

I also don't like the way when you set up the email address format (we're using first letter of forename then surname) it uses capitals (for example for my account, my email address ends up as gWatson@testdomain... - OK it'll still work, but how ugly is that? Why make the first letter small, then the first letter of the surname in capitals??)

[florian]

Hi Greg,

first of all - looking at the overall tone of your message, I'm wondering a little bit if you're looking for help and answers here or if you're just trying to bash a product that is used successfully and happily by thousands of sites. Anyway, I'm assuming you want your problems solved, so let's get on with this!

Where is this documented? I am trying the evaluation edition and so far I'm not impressed. I had this error as well, which isn't particularly impressive for an out-of-the-box evaluation install.

Indeed, the installer normally sets this up correctly by itself; however, it can go wrong if your hostname resolution is not configured correctly. Could you post the contents of your

Code: Select all

/etc/hosts
ifconfig command
/etc/resolv.conf
hostname command
hostname --fqdn command
/var/opt/scalix/smtpd.cfg


I'm also amazed at the poor LDAP support. I am trying to install thi on a server which already has an LDAP server running - you would have thought this was a very common scneario. Following instructions in another post I have read how to change the LDAP port for the Scalix LDAP server so they don't clash - but then the SAC doesn't work! It seems also that the address book doesn't work in this configuration - but I will test that again in a moment.

Well, one of the reasons that Scalix comes with an out-of-the box integrated directory is actually ease of installation. Integration into an existing LDAP, especially if it is a Linux-based OpenLDAP type is something that can never be done automatic.

You have a couple of options here...
- move your existing LDAP to a different port number; under normal circumstances, an email server is a dedicated machine, so it's pretty normal for the email software to own the port numbers.
- change the LDAP port number for Scalix. This needs to be done for the actual LDAP server, the Scalix Admin Console and Scalix Web Access. Please actually look at the Scalix CE Raw installation instructions in the Scalix Wiki at www.scalix.com/wiki - this extensive document documents the places where the port number needs to be changed.

I also don't like the way when you set up the email address format (we're using first letter of forename then surname) it uses capitals (for example for my account, my email address ends up as gWatson@testdomain... - OK it'll still work, but how ugly is that? Why make the first letter small, then the first letter of the surname in capitals??)

So, not all the mapping options for this are documented and exposed through the installer. If you check the "omaddu" man page, you will find the following section:

Code: Select all

G       The full given name in the original case as supplied.

       I       The full initials in the original case as supplied.

       S       The full surname in the original case as supplied.

       C       The full common name in the original case as supplied.

       g       The first character only of the given name in lower case.

       i       The first character only of the initials in lower case.

       s       The first character only of the surname in lower case.

       c       The first character only of the common name in lower case.

       f       The full given name (first name) in lower case.


and I assume this list contains what you're looking for. Not sure if you have all these options when you modify the email address generation rules in the Scalix Admin Console, but they are certainly available if you change them via the command line - please see "man omaddiam" for details.

Hope this helps, greets from Germany,
Florian.

[gregwatson]

Hi Florian and thanks.

Yes the tone was negative, I admit - I was really looking forward to the Scalix evaluation because I had really liked what I saw of it. But straight away I had some issues even when I was following the evaluation guide step by step (which contains a typo, by the way - it tells you to run "ommaddu").

As of now I still can't send mail from SWA (get the 550 error) even though I CAN send mail from an operating system mail command, so to my mind the basic sendmail install (which admittedly I haven't touched since the OS was installed) must be OK. The Scalix smtpd.cfg file contained 127.0.0.1 and the unqualified name of the server followed by a full stop in the relays section.

But the LDAP thing really annoyed me - it looks like you're saying that there is now a way forward with it - the last post I found regarding changing LDAP ports ended with Scalix support admitting that the SAC would not work, and that it would be requested as a future enhancement. From your reply just now it seems to suggest that things have improved so I will read the Wiki.

I'm not sure about "under normal circumstances" - for small businesses I would imagine that having a single server doing everything is pretty common!

Thank you for the pointer to the omaddu man page. Thing is, I don't have time to read all the man pages on all the commands.. part of the problem is knowing which ones to read up on early on in the evaluation phase of the product...

[florian]

As of now I still can't send mail from SWA (get the 550 error) even though I CAN send mail from an operating system mail command, so to my mind the basic sendmail install (which admittedly I haven't touched since the OS was installed) must be OK.

I also assume that it's not sendmail that's causing the issue, however it's not really the same - SWA sends through SMTP to the server, so from the SMTP MTA's point of view, it's a relaying situation which must be handled differently for spam protection reasons.

The Scalix smtpd.cfg file contained 127.0.0.1 and the unqualified name of the server followed by a full stop in the relays section.

So that's probably wrong - can you replace the unqualified hostname and the "." and replace them with whatever hostname --fqdn returns? Once you've done that, please restart the SMTP relay by issueing

Code: Select all

omoff -d0 -w smtpd; omon -w smtpd

But the LDAP thing really annoyed me - it looks like you're saying that there is now a way forward with it - the last post I found regarding changing LDAP ports ended with Scalix support admitting that the SAC would not work, and that it would be requested as a future enhancement. From your reply just now it seems to suggest that things have improved so I will read the Wiki.

Well, I believe one part of it (port number configurable on the SAC side) was only changed in 10.0.1, but I assume that's what you're running.

HTH,
Florian.

[gregwatson]

Yup, that's done it.

Thanks.

[kanderson]

As a Small Business option, you could also look at Xandros. They package Scalix with their server, and integrate LDAP completely and seamlessly together so that 1 box runs everything and allows a single administration point for everything.

It's a slick package, particularly for small businesses.

Kev.

[gregwatson]

I have changed the Scalix LDAP port to 3890 as per that Wiki. I have also made the changes listed under the SWA and Ubermanager/SAC sections. The SAC loasd up OK, and SWA works - but when I choose Tools->Address Book nothing shows up (System is selected). Also when I search for a name, it just says "searching" and never comes back. Would the address book function also have its own LDAP port setting somewhere? yesterday if I put Scalix LDAP back to 389 and restarted everything then the address book would start working fine...

TIA
Greg

[florian]

Yes, this is in /etc/opt/scalix/webmail/swa.properties - guess you'll just need to look for occurrences of 389. It's in the Wiki, but not clearly marked I believe.

Thx,
Florian.

[gregwatson]

I did look through that file. The wiki mentions that there are two sections which both must be changed (ldap.1 and ldap.2) [Why on earth are there two sections in the same config file for the same thing?? What's the difference between ldap.1 and ldap.2 ?]

In my file the ldap.1 section was commented out but ldap.2 was uncommented. I did try changing it in both sections (and uncommented the ldap.1 line) but will double-check...

[gregwatson]

Unless of course it's just for multiple LDAP servers.. Doh!

[gregwatson]

I must have been drunk yesterday.

The ldap.1 section looks fine today so have changed that one to 3890 as well and the address book is working.

Can't understand why I thought it looked so different yesterday. Maybe searching the file in a hurry.

Thanks again.

[florian]

Actually, both .1 and .2 should be commented in, that's the way the installer leaves this as.

SWA has a generic LDAP access mechanism, so can actually be configured to rely on any LDAP directory - which is what a couple of our customers use heavily - very useful feature.

The LDAP sources are two distinct things from SWA's point of view - one references the SYSTEM directory, which is our Global Address List, the other points to the "MyContacts" LDAP source which provides Address-book type access to the users contacts folder. Usually, those two sources would point to the same server, but it doesn't have to be the case in large deployments.

Florian.