SMTP Error (451) - Temporary lookup failure

Francois Martin bug.martin96 at yahoo.com
Thu Jul 30 10:41:47 CEST 2015 

Hi,

thanks for the precision !
Apparently the dirsrv is running !

[root at kolab ~]# systemctl status dirsrv at kolab
dirsrv at kolab.service - 389 Directory Server kolab.
   Loaded: loaded (/usr/lib/systemd/system/dirsrv at .service; enabled)
   Active: active (running) since Thu 2015-07-30 03:24:01 EDT; 13min ago
  Process: 82 ExecStart=/usr/sbin/ns-slapd -D /etc/dirsrv/slapd-%i -i /var/run/dirsrv/slapd-%i.pid -w /var/run/dirsrv/slapd-%i.startpid (code=exited, status=0/SUCCESS)
 Main PID: 133 (ns-slapd)
   CGroup: /system.slice/system-dirsrv.slice/dirsrv at kolab.service
           `-133 /usr/sbin/ns-slapd -D /etc/dirsrv/slapd-kolab -i /var/run/dirsrv/slapd-kolab.pid -w /var/run/dirsrv/slapd...

Jul 29 10:21:58 kolab.qi.fr systemd[1]: Stopping 389 Directory Server kolab....
Jul 29 10:22:00 kolab.qi.fr systemd[1]: Stopped 389 Directory Server kolab..
Jul 29 10:44:43 kolab.qi.fr systemd[1]: Starting 389 Directory Server kolab....
Jul 29 10:44:44 kolab.qi.fr systemd[1]: Started 389 Directory Server kolab..
Jul 29 10:50:53 kolab.qi.fr systemd[1]: Stopping 389 Directory Server kolab....
Jul 29 10:50:54 kolab.qi.fr systemd[1]: Stopped 389 Directory Server kolab..
Jul 30 03:24:00 kolab.qi.fr systemd[1]: Starting 389 Directory Server kolab....
Jul 30 03:24:01 kolab.qi.fr systemd[1]: Started 389 Directory Server kolab..
Jul 30 03:28:37 kolab.qi.fr systemd[1]: Started 389 Directory Server kolab..
Jul 08 08:55:29 kolab systemd[1]: Starting 389 Directory Server kolab....
Jul 08 08:55:29 kolab systemd[1]: Started 389 Directory Server kolab..
Jul 08 08:55:31 kolab systemd[1]: Stopping 389 Directory Server kolab....
Jul 08 08:55:32 kolab systemd[1]: Starting 389 Directory Server kolab....
Jul 08 08:55:33 kolab systemd[1]: Started 389 Directory Server kolab..
Jul 08 09:02:50 kolab systemd[1]: Stopping 389 Directory Server kolab....
Jul 08 09:02:52 kolab systemd[1]: Stopped 389 Directory Server kolab..
Jul 09 03:59:35 kolab.qi.fr systemd[1]: Starting 389 Directory Server kolab....
Jul 09 03:59:35 kolab.qi.fr systemd[1]: Started 389 Directory Server kolab..
Jul 09 04:53:33 kolab.qi.fr systemd[1]: Stopping 389 Directory Server kolab....
Jul 09 04:53:34 kolab.qi.fr systemd[1]: Stopped 389 Directory Server kolab..
Jul 09 04:53:38 kolab.qi.fr systemd[1]: Started 389 Directory Server kolab..
[root at kolab ~]#

And for ldapsearch i have try this the last time :
[root at kolab ~]# ldapsearch -b -s base -D 'cn=Directory Manager ,dc=kolab,dc=qi,dc=fr' -h 127.0.0.1 -x -w '*******'
ldap_bind: No such object (32)
        matched DN: dc=qi,dc=fr
[root at kolab ~]#

I add the configurations files to help identify the problem.
I want create several domains (independent) on the same server.

The management domain : qi.fr
The first domain isolate : qualite-info.com

Thank you !
:-)

Best Regards,

Martin Francois

     Le Mercredi 29 juillet 2015 18h13, Geert Janssens <geert at kobaltwit.be> a écrit :
   

 You will probably want to start your kolab dirsrv instance.

Try:
systemctl start dirsrv@<hostname>

You should replace hostname with the name you used when setting up 
kolab. If you're unsure, you can quickly find the name by looking into 
/etc/dirsrv
There should be a directory there called
slapd-<hostname>

Regards,

Geert

On Wednesday 29 July 2015 14:05:34 Francois Martin wrote:
> "Is dirsrv running?"
> I'm doing this to test the operation:
> 
> [root at kolab ~]# service dirsrv status
> Redirecting to /bin/systemctl status  dirsrv.service
> dirsrv.service
>    Loaded: not-found (Reason: No such file or directory)
>    Active: inactive (dead)
> 
> [root at kolab ~]# service dirsrv start
> Redirecting to /bin/systemctl start  dirsrv.service
> Failed to issue method call: Unit dirsrv.service failed to load: No
> such file or directory. [root at kolab ~]#
> 
> 
> [root at kolab ~]# systemctl status dirsrv@*
> dirsrv@\x2a.service - 389 Directory Server \x2a.
>    Loaded: loaded (/usr/lib/systemd/system/dirsrv at .service; enabled)
>    Active: inactive (dead)
> [root at kolab ~]#
> 
> 
> [root at kolab ~]# ps | grep dirsrv
> [root at kolab ~]#
> 
> 
> "Can you do a manual lookup of items in your LDAP server with
> ldapsearch?" Here is the command I executed (I do not know if it is
> correct): [root at kolab ~]# ldapsearch -b -s base -D 'cn=Directory
> Manager ,dc=kolab,dc=qi,dc=fr' -h 127.0.0.1 -x -w '*******'
> ldap_bind: No such object (32)
>        matched DN: dc=qi,dc=fr
> [root at kolab ~]#
> 
> Regards,
> 
> Martin
> 
> 
>      Le Mercredi 29 juillet 2015 14h04, "bshaw at vsvinc.com"
> <bshaw at vsvinc.com> a écrit :
> 
> 
>  <!--#yiv1498902834 #yiv1498902834 p {font-family:Century Gothic,
> CenturyGothic, AppleGothic,
> sans-serif;font-size:10.0pt;color:#1F497D;}-->Is dirsrv running?  Can
> you do a manual lookup of items in your LDAP server with
> ldapsearch?Brian
> 
> From: Francois Martin <bug.martin96 at yahoo.com>
> Sent: Jul 29, 2015 5:39 AM
> To: users at lists.kolab.org
> Subject: Re: SMTP Error (451) - Temporary lookup failure
> 
> Hello everyone,
>  i give you more details about the problem of "SMTP Error (451)
> Temporary lookup failure". Here are the error messages from email
> logs :
> Jul 29 03:41:31 kolab postfix/cleanup[12225]: 9C4B918888B6:
> message-id=<20150729074131.9C4B918888B6 at kolab.qi.fr> Jul 29 03:41:31
> kolab postfix/cleanup[12225]: warning: dict_ldap_connect: Unable to
> bind to server ldap://localhost:389 with dn
> uid=kolab-service,ou=Special Users,dc=qualite-info,dc=com: 32 (No
> such object) Jul 29 03:41:31 kolab postfix/cleanup[12225]: warning:
> ldap:/etc/postfix/ldap/qualite-info.com/mydestination.cf: table
> lookup problem Jul 29 03:41:31 kolab postfix/cleanup[12225]: warning:
> ldap:/etc/postfix/ldap/qualite-info.com/local_recipient_maps.cf
> lookup error for "root at kolab.qi.fr" Jul 29 03:41:31 kolab
> postfix/cleanup[12225]: warning: 9C4B918888B6: virtual_alias_maps map
> lookup problem for root at kolab.qi.fr -- deferring delivery Jul 29
> 03:42:31 kolab postfix/pickup[12251]: AC34E18888B6: uid=0 from=<root>
> I join you main.cf file
> 
>  Regards,
> 
>  Martin
> 
>      Le Mardi 28 juillet 2015 18h41, Francois Martin
> <bug.martin96 at yahoo.com> a écrit :
> 
> 
>  Hello,
> 
> I just follow the procedure to make the Kolab multi-domain server with
> the following pages:
> https://docs.kolab.org/howtos/multi-domain.html#amavisd-changes
> http://kolab.org/blog/cornelius-hald/2015/01/05/kolab-3.3-multi-domai
> n-setup-centos-7
> 
> I can connect with users in new domains and send mail locally.
> 
> When I try to send mail to the outside, the following error message
> appears in the webmail: SMTP Error (451): failed when adding the
> recipient "admin at mail.zimbra.com" (4.3.0 <admin at mail.zimbra.com>:
> Temporary lookup failure)
> 
> What should I do to correct this?
> 
> thank you in advance ! :-)
> Martin
> 
> 
> 
> _______________________________________________
> users mailing list
> users at lists.kolab.org
> https://lists.kolab.org/mailman/listinfo/users

_______________________________________________
users mailing list
users at lists.kolab.org
https://lists.kolab.org/mailman/listinfo/users

  
-------------- section suivante --------------
Une pi�ce jointe HTML a �t� nettoy�e...
URL: <http://lists.kolab.org/pipermail/users/attachments/20150730/894a6cef/attachment-0001.html>
-------------- section suivante --------------
Une pi�ce jointe autre que texte a �t� nettoy�e...
Nom: Configurations server.zip
Type: application/octet-stream
Taille: 51308 octets
Desc: non disponible
URL: <http://lists.kolab.org/pipermail/users/attachments/20150730/894a6cef/attachment-0001.obj>

More information about the users mailing list