Internet Mail Gateway queue not passing to sendmail

Discuss the Scalix Server software

Moderators: ScalixSupport, admin

scalar1234
Posts: 11
Joined: Wed Feb 14, 2007 6:09 am

Internet Mail Gateway queue not passing to sendmail

Postby scalar1234 » Tue Feb 20, 2007 5:20 pm

Hello

I installed Scalix CE 11.0.1.22 on Debian running Kernel 2.6.20

My problem seems also to be addressed by the following former post
with the same subject: "Internet Mail Gateway queue not passing to sendmail?"
This thread was closed since it referred to a BETA release.

My problem is, that I cannot send email to an external email account, e.g. GMX.
Sending and receiving internal emails works fine.
All emails to an external email-address are placed in the "Internet Mail Gateway"-queue.

- Sendmail does not seem to get called as all sendmail-logfiles (/var/log/mail*) are empty.
Nothing is written to the sendmail logfiles.

- Sendmail is started on system startup.
- Furthermore omsendin says that all necessary config-entries are existing.

- lsof -i :25 has the following output:
asterisk:/var/opt/scalix/ak/s/sys# lsof -i :25
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
omsmtpd 10919 root 5u IPv4 76826 TCP asterisk.quintec.de:smtp (LISTEN)
sendmail- 11105 root 4u IPv4 77313 TCP localhost.localdomain:smtp (LISTEN)

- /var/opt/scalix/ak/s/sys/unix.mapper has only a single line:
transport-service = inet:localhost:25

- /var/opt/scalix/ak/s/sys/smtpd.cfg has the following entries:
DEBUG_LOG=TRUE

# NB Authenticated RELAYs are always allowed
RELAY accept 127.0.0.1
RELAY accept 192.168.200.8
RELAY accept .quintec.de
RELAY Log_Reject ALL

When sending an email to an external address
the following lines are logged to the end of /var/opt/scalix/ak/s/tmp/smtpd-SMTP.log:

Cli 2989/1 rcvd U: '250 Ok'
Cli 2989/1: Submitted message ': <17376327.131171972276872.JavaMail.root@asterisk>' to unix.in.
response: '250 Ok'
Cli 2989/1 Finished submitting msg : <17376327.131171972276872.JavaMail.root@asterisk>
Cli 2989/1 sent : 250 Ok

Cli 2989/1 rcvd: 'QUIT'
Cli 2989/1 sent : 221 asterisk.quintec.de closing connection

I searched the forum the whole day but I have no further ideas.
But still the original posting referring to the BETA releases seems to fit to my
problem.

Has anybody experienced that problem with Scalix CE 11.0.1.22, too?

Kind regards
Andreas

scalar1234
Posts: 11
Joined: Wed Feb 14, 2007 6:09 am

problem with LDAP-Server not using standard-port 389?

Postby scalar1234 » Wed Feb 21, 2007 6:25 am

Today I received the following hint from another community-member
who had a very similar problem when sending outgoing mails:

Quotation:

Yes - do you have any output in the /var/log/maillog log file?

I ran into two causes of this problem and had to solve both for it to wkr for me:

Problem 1: Fedora's x86_64 build of Sendmail has a serious bug that prevents it talking to the ldapmapper.

Solution: Use the i386 version of the sendmail binary.

Problem 2: I run scalix's ldap server on a non-standard port (i.e. not port 389). The ldapmapper needs to know this so it can communicate with the omslapd process.

solution 2: configure ldapmapper to talk to the right destination port on the ldap server (check the ldapmapper man page for exact syntax).

Once i'd solved those issues, it all worked fine and has been completely stable and reliable for weeks.

scalar1234
Posts: 11
Joined: Wed Feb 14, 2007 6:09 am

error connection LDAP-Server in sendmail-logs

Postby scalar1234 » Wed Feb 21, 2007 6:28 am

My answer:

the first curious thing is, that nothing is written to the sendmail
log-files in /var/log/mail* when a mail is sent e.g. by webmail-client.

I use the i386-version of sendmail.
Due to your LDAP-problems when using another port instead of the standard-port 389,
I remembered that I use port 3890.
According to the manual installation instructions described in the Scalix-Wiki
I changed the config-files to use port 3890.

The CLI-command lsof -i :3890 outputs the lfollowing:

asterisk:/var/log# lsof -i :389
asterisk:/var/log# lsof -i :3890
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
omslapd 1929 root 8u IPv4 3271 TCP *:3890 (LISTEN)


Today I deleted all the Sendmail-logfiles and rebooted the machine.

After reboot the following can be found in /var/log/mail.err:

Feb 21 11:41:39 asterisk sm-mta[1795]: l1LAfaGo001795: SYSERR(root): Error getting LDAP results in map ldaps
x: Can't contact LDAP server
Feb 21 11:43:18 asterisk sm-mta[1977]: l1LAhHF2001977: SYSERR(root): Error getting LDAP results in map ldaps
x: Can't contact LDAP server
Feb 21 11:49:18 asterisk sm-mta[2132]: l1LAnIGl002132: SYSERR(root): Error getting LDAP results in map ldaps
x: Can't contact LDAP server
Feb 21 11:55:18 asterisk sm-mta[2151]: l1LAtIFq002151: SYSERR(root): Error getting LDAP results in map ldaps
x: Can't contact LDAP server


And the following was written to /var/log/mail.log:

Feb 21 11:41:35 asterisk sm-mta[1770]: starting daemon (8.13.4): SMTP+queueing@00:10:00
Feb 21 11:41:35 asterisk sm-mta[1770]: daemon could not open control socket /var/run/sendmail/mta/smcontrol:
Group writable directory
Feb 21 11:41:39 asterisk ldapmapper[1692]: (re)read scalix global config file
Feb 21 11:41:39 asterisk ldapmapper[1692]: found scalix instance asterisk
Feb 21 11:41:39 asterisk ldapmapper[1692]: (re)read relay config file /var/opt/scalix/ak/s/sys/smtpd.cfg
Feb 21 11:41:39 asterisk ldapmapper[1692]: cannot send search request to instance asterisk: Can't contact LD
AP server
Feb 21 11:41:39 asterisk sm-mta[1795]: l1LAfaGo001795: SYSERR(root): Error getting LDAP results in map ldaps
x: Can't contact LDAP server
Feb 21 11:41:39 asterisk sm-msp-queue[1779]: l1LATFPO002267: to=andreas.lueck@gmx.net, ctladdr=root (0/0), d
elay=00:12:24, xdelay=00:00:03, mailer=relay, pri=120046, relay=[127.0.0.1] [127.0.0.1], dsn=4.0.0, stat=Def
erred: 451 4.3.5 Error getting LDAP results in map ldapsx: Can't contact LDAP server
Feb 21 11:43:18 asterisk ldapmapper[1692]: cannot send search request to instance asterisk: Can't contact LD
AP server
Feb 21 11:43:18 asterisk sm-mta[1977]: l1LAhHF2001977: SYSERR(root): Error getting LDAP results in map ldaps
x: Can't contact LDAP server
Feb 21 11:49:18 asterisk ldapmapper[1692]: cannot send search request to instance asterisk: Can't contact LD
AP server
Feb 21 11:49:18 asterisk sm-mta[2132]: l1LAnIGl002132: SYSERR(root): Error getting LDAP results in map ldaps
x: Can't contact LDAP server
Feb 21 11:51:18 asterisk sendmail[2140]: l1LApD0e002140: from=lueck, size=0, class=0, nrcpts=0, relay=root@l
ocalhost
Feb 21 11:51:41 asterisk sm-mta[2145]: l1LApUcd002145: localhost.localdomain [127.0.0.1] did not issue MAIL/
EXPN/VRFY/ETRN during connection to MTA-v4
Feb 21 11:55:18 asterisk ldapmapper[1692]: cannot send search request to instance asterisk: Can't contact LD
AP server


The following is written to mail.warn:

Feb 21 11:41:35 asterisk sm-mta[1770]: daemon could not open control socket /var/run/sendmail/mta/smcontrol:
Group writable directory
Feb 21 11:41:39 asterisk ldapmapper[1692]: cannot send search request to instance asterisk: Can't contact LD
AP server
Feb 21 11:41:39 asterisk sm-mta[1795]: l1LAfaGo001795: SYSERR(root): Error getting LDAP results in map ldaps
x: Can't contact LDAP server
Feb 21 11:43:18 asterisk ldapmapper[1692]: cannot send search request to instance asterisk: Can't contact LD
AP server
Feb 21 11:43:18 asterisk sm-mta[1977]: l1LAhHF2001977: SYSERR(root): Error getting LDAP results in map ldaps
x: Can't contact LDAP server
Feb 21 11:49:18 asterisk ldapmapper[1692]: cannot send search request to instance asterisk: Can't contact LD
AP server
Feb 21 11:49:18 asterisk sm-mta[2132]: l1LAnIGl002132: SYSERR(root): Error getting LDAP results in map ldaps
x: Can't contact LDAP server
Feb 21 11:55:18 asterisk ldapmapper[1692]: cannot send search request to instance asterisk: Can't contact LD
AP server
Feb 21 11:55:18 asterisk sm-mta[2151]: l1LAtIFq002151: SYSERR(root): Error getting LDAP results in map ldaps
x: Can't contact LDAP server


Furthermore I tried to send an email by CLI-command mail to my external GMX-account.
Whe doing so, the following is written to mail.err:

Feb 21 12:13:18 asterisk ldapmapper[1692]: cannot send search request to instance asterisk: Can't contact LDAP server
Feb 21 12:13:18 asterisk sm-mta[2213]: l1LBDIId002213: SYSERR(root): Error getting LDAP results in map ldapsx: Can't contact LDAP server
Feb 21 12:13:51 asterisk sendmail[2214]: l1LBDpsa002214: from=root, size=54, class=0, nrcpts=1, msgid=<200702211113.l1LBDpsa002214@asterisk.quintec.de>, relay=root@localhost
Feb 21 12:13:51 asterisk ldapmapper[1692]: cannot send search request to instance asterisk: Can't contact LDAP server
Feb 21 12:13:51 asterisk sm-mta[2215]: l1LBDpXg002215: SYSERR(root): Error getting LDAP results in map ldapsx: Can't contact LDAP server
Feb 21 12:13:51 asterisk sendmail[2214]: l1LBDpsa002214: to=andreas.lueck@gmx.net, ctladdr=root (0/0), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=30054, relay=[127.0.0.1] [127.0.0.1], dsn=4.0.0, stat=Deferred: 451 4.3.5 Error getting LDAP results in map ldapsx: Can't contact LDAP server


I think I'm a little bit further now and I know where to look for in order to solve the problem.

Thank you very much
Andreas

scalar1234
Posts: 11
Joined: Wed Feb 14, 2007 6:09 am

Problem solved: Reason was missing LDAP-config

Postby scalar1234 » Wed Feb 21, 2007 10:04 am

Hello,

it's me again.
Finally I solved the problem!.

The reason for it all was a missing configuration-entry with regard
to the LDAP-port-configuration.

As I installed according to the instructions in the Wiki for "Manual Installation"
I decided to use port 3890 for LDAP instead of its standard port 389.

I changed all LDAP-port-configurations within the config-files according to the
"Manual Installation"-Wiki to point to port 3890.

But unfortunately nothing was mentioned about the ldapmapper-configuration,
which also has to be told to use port 3890 in order to connect to the Scalix-LDAP-Server-Daemon.

This is done in file /etc/sysconfig/ldapmapper:

#
# Scalix ldapmapper(8) options
#
LDAPMAPPER_OPTIONS="-L ldap://%s:3890"

Upon restart / reboot of all services sendmail was now able to send its mail
to the recipient and the Internet Mail Gateway queue was flushed either.

The necessary TODOs for changing the LDAP-port to a non-standard-port are best described in the following Wiki-article:

http://www.scalix.com/wiki/index.php?ti ... t_from_389

Finally I hope, that this thread will help others experiencing the same problem!

Bye
Andreas


Return to “Scalix Server”



Who is online

Users browsing this forum: No registered users and 11 guests