Scalix Forums

Hi,

i had search the forum about that but nothing helped completly. My Problem is, that EMails from outside sometimes appear with that kind of warning message, so it could not be delivered. I dont want that smtp is checking the correct syntax of a domain he should only deliver the mail.
Here is the entry in my submit.mc:


divert(0)dnl
VERSIONID(`$Id: submit.mc,v 8.6.2.7 2003/09/10 22:11:56 ca Exp $')
define(`confCF_VERSION', `Submit')dnl
define(`__OSTYPE__',`')dnl dirty hack to keep proto.m4 from complaining
define(`_USE_DECNET_SYNTAX_', `1')dnl support DECnet
define(`confTIME_ZONE', `USE_TZ')dnl
define(`confDONT_INIT_GROUPS', `True')dnl
define(`confDOMAIN_NAME',`$my-domain.de')dnl
dnl
dnl If you use IPv6 only, change [127.0.0.1] to [IPv6:::1]dnl
FEATURE(`msp', `[127.0.0.1]')dnl
FEATURE(`accept_unresolvable_domains')dnl
dnl Enable access.db for allowed relaying dnl
FEATURE(`acces_db',`hash -T<TMPF> /etc/mail/access.db')dnl
dnl FEATURE(relay_mail_from)dnl
dnl Enable for fetchmail dnl
FEATURE(`masquerade_envelope')dnl
FEATURE(`accept_unqualified_senders')dnl
FEATURE(`relay_local_from')dnl

Thats the entry in my /etc/mail/access

# Default for loop back is RELAY
127.0.0.1 OK
localhost OK
hsp-gbr.de OK
unresolvable_domain OK


Need HELP please....

Hello again,

no one who can help me with this error?

Please my Chief is making me one head shorter....

MfG

Looking at http://www.sendmail.org/m4/anti_spam.html it says the following:



You need to make the change to your sendmail.mc, not the submit.mc (you shouldn't have to touch this file). Then regenerate your sendmail.cf from the sendmail.mc and run omsendin.

Also, according to the above your access file needs to read
From:unresolvable.domain OK

so an example would be
From:example.com OK

Remember to regenerate the access.db file after you've changed the access file, as only the hashed versions gets used.

Hi,

first thx for the reply....but the Problem now ist i doesn`t have a file named sendmail.mc????!!!
Can i generate the sendmail.mc? And how?

Thx

What distribution are you running on? Can you list the files in /etc/mail for me, please?

Im running SLES 9 and here the content of the /etc/mail:
ls -la

drwxr-xr-x 4 root root 4096 Dec 20 17:10 .
drwxr-xr-x 60 root root 8192 Dec 21 09:37 ..
-rw-r--r-- 1 root root 1143 Jul 1 2004 Makefile
-rw-r--r-- 1 root root 12306 Jul 1 2004 README
-rw-r--r-- 1 root root 117 Dec 20 17:10 access
-rw-r--r-- 1 root root 12288 Dec 20 17:10 access.db
lrwxrwxrwx 1 root root 10 Oct 24 15:13 aliases -> ../aliases
drwxr-x--- 2 root root 4096 Oct 24 18:00 auth
drwxr-x--- 2 root root 4096 Jul 1 2004 certs
-rw-r--r-- 1 root root 723 Jul 1 2004 genericstable
-rw-r--r-- 1 root root 12288 Oct 24 15:22 genericstable.db
-rw-r--r-- 1 root root 12545 Jul 1 2004 linux.mc
-rw-r--r-- 1 root root 921 Jul 1 2004 linux.nullclient.mc
-rw-r--r-- 1 root root 2704 Jul 1 2004 linux.submit.mc
-rw-r--r-- 1 root root 365 Jul 1 2004 local-host-names
-rw-r--r-- 1 root root 1446 Jul 1 2004 mailertable
-rw-r--r-- 1 root root 12288 Oct 24 15:22 mailertable.db
-rw-r--r-- 1 root root 363 Dec 18 11:59 relay-domains
-rw-r--r-- 1 root root 330 Jul 1 2004 service-nodns.switch
-rw-r--r-- 1 root root 815 Jul 1 2004 service.switch
-rw-r--r-- 1 root root 39934 Oct 24 18:06 submit.cf
-rw-r--r-- 1 root root 374 Oct 24 18:10 trusted-users
-rw-r--r-- 1 root root 257 Jul 1 2004 userdb
-rw-r--r-- 1 root root 8192 Oct 24 15:22 userdb.db
-rw-r--r-- 1 root root 441 Jul 1 2004 virtusertable
-rw-r--r-- 1 root root 12288 Oct 24 15:22 virtusertable.db

Ah, I believe you are looking for linux.mc

....sometimes i hate SUSE. I try to edit this file now and hope that it will have the right effect.

ThX

I just found my own problem with this... and it was all working before!

So I thought I'd share my solution in the hopes that others will do the same with other topics.



MX RECORDS. Yes, they are important, we all know that. But I did a little change in my DNS and I started my own DNS servers for the 6 domains that we manage. For the main domain... not a problem. It was all done through the miracle of Microsoft Server 2003 DNS wizards. The others I did by hand. (No, I don't use that server for my external DNS. I have full separation from my internal DNS and our external DNS... which is a linux server). The linux side is easy... copy a file, make a few changes, and restart the server. But Windows was more difficult. So for a month now I didn't test the mail features of the domain... just name resolution. The problem is my scalix box queries the internal DNS first and because those domains are there.... and I was missing my MX records, the Scalix server was saying the domain didn't exist!

SO, before you go any further and mess with configuration, make sure you do some "host example.com" on your scalix server to make sure you have all MX records, SPF records (I'd advise setting those up too... but not required by all mail) in your DNS server so that your domains are being shown as existent on the scalix box. (Below is an example from my troubleshooting today.)


(Before I fixed the MX record in the DNS - I'm using dumbolddomain.net as the name of my fake domain name.)



(After I fixed the MX record)


NOTE: I did NOT do a:



because that was already there! Scalix needs the MAILER EXCHANGE RECORD... thus the MX record!

Three clicks and a quick type on the DNS server fixed HOURS of troubleshooting![/code]