scalix and thunderbird

[DDavid]

Since moving to Scalix Ver 10, my thunderbird users cant send mail other than internal network, they are been rejected by spam list, I've included AUTH_SUCCESS accept ALL in my smtpd.cfg file and restarted smtp relay...still been rejected...was not happening with previous version of scalix.
any ideas why ?

Thanks

[ScalixSupport]

If they are authenticating, they will be able to send messages outside of the network.

If not, it sounds like the IP address range for your clients may have changed or reverse DNS lookup is not working correctly.

Cheers

Dave

[DDavid]

These clients are outside of the office, so their IP address range has changed

[ScalixSupport]

In that case, they must authenticate to be allowed to send outside of your domain.

Adding IP address ranges to smtpd.cfg for addresss outside of your network is a dangerous thing and I strongly advise against it.

Cheers

Dave

[DDavid]

i have now two cases where they authenticate and still can send..but all outlook users are fine.hmmmm

[ScalixSupport]

I took that to read that they "can't" send.

One thing to check is if they are genuinely authenticating. To check this, you need to enable debug logging in the SMTP Relay. Edit /var/opt/scalix/sys/smtpd.cfg and add the line

Code: Select all

DEBUG_LOG=TRUE

You will need to restart the SMTP Relay service

Code: Select all

omoff -d 0 smtpd
omon smtpd

for this change to be picked up. The file /var/opt/scalix/tmp/smtpd.log will contain all of the SMTP conversations from sending clients/MTAs. The caveat to this is that if the file gets above 2Gb in size, it will cause problems so, enable the logging, get one of the problem users to send a message and then disable logging again.

You should be able to see if any successful authentication takes place. One thing to point out about Thunderbird is that it will attempt a couple of authentication methods to see which one succeeds before it returns any kind of error back to the client.

Cheers

Dave