QMailLDAP and EZMLM, my Adventure
I think that everything we do help us improving our experience. But I know also that documented experiences can help anyone who can read. That's why I'm sharing this experience I had, putting EZMLM to work with QmailLDAP.
To start, I can say that my qmailldap instalation was running great for my regular email, which includes multidomain, and catchall... You know, an out-of-box patch && make && make setup.
Well. Not so fast to say the true... the qmailldap patch was with a small bug... Missing a #define NULL, nothing that a patch to the patch didn't solve in seconds.
Well, but that was before. Let's go back to my EZMLM install... The first list I tried to create was mysql@lists.camelot.co.pt, a list, for portuguese MySQL users. So I created in LDAP an entry mysql@lists.camelot.co.pt, with an alias mysql-catchall@lists.camelot.co.pt. So far so good, isn't it?
My next step was to test if the email was working, and create the Maildir. So, I sent an email to mysql@lists.camelot.co.pt, and everything gone as expected... the Maildir was created and the email was saved in the correct maildir.
The missing part was to test the catchall part. I knew that a catchall@domain was working, since I have one in another domain, were it works terrific, so I thought that mysql-catchall would work too. I was wrong! I few research and some time later, I found out that I did miss to uncomment the "LDAPFLAGS=-DDASH_EXT line in the QMailLDAP Makefile.
outch, make clean && make && make setup again, and lets retry the mysql-cacthall part again... this time with success!
The next step was to create the directory to the mailling list and the dot-files (the .qmail files) with ezmlm-make. This was a small step. Then I subscribed mysql to the list, using the ezmlm-sub, and tested the mailling with an email sent from my normal email client. Far from success, however...
Qmail didn't sent the message, kepted it in the queue, and logged an ezmlm-send:_fatal:_temporary_qmail-queue_error:_/ from ezmlm-send. I looked in the FAQ, the ezmlm.org site, and even in google. The answer I got was not good enought. You know why? The few pages I found about this problem specified that it could be an currupted subscribers file, or an corrupted qmail-queue program. None of them could be the answer to my problem, since every email but to mysql list was working normal (this excludes qmail-queue), and ezmlm-list returned normally, my email, looking fine.
Fast I stoped looking in the internet, since even google could find the answer, so I gone to the next resource, RTFS (Read The Fine Sources).
And the sources give me the answer. The message was written when ezmlm-send tried to execute qmail-queue and failled.
SURPRISE, SURPRISE... This is executing qmail-queue directly? Well... (and this time I got a flash) but my qmail isn't installed in the default directory... Is there any Bernstein conf file to set the qmail directory in the source? YES, it is. The file is called conf-qmail.
Another make && make setup, and everything gone ok. The next one would be easy, but why have the first one so hard?
To start, I can say that my qmailldap instalation was running great for my regular email, which includes multidomain, and catchall... You know, an out-of-box patch && make && make setup.
Well. Not so fast to say the true... the qmailldap patch was with a small bug... Missing a #define NULL, nothing that a patch to the patch didn't solve in seconds.
Well, but that was before. Let's go back to my EZMLM install... The first list I tried to create was mysql@lists.camelot.co.pt, a list, for portuguese MySQL users. So I created in LDAP an entry mysql@lists.camelot.co.pt, with an alias mysql-catchall@lists.camelot.co.pt. So far so good, isn't it?
My next step was to test if the email was working, and create the Maildir. So, I sent an email to mysql@lists.camelot.co.pt, and everything gone as expected... the Maildir was created and the email was saved in the correct maildir.
The missing part was to test the catchall part. I knew that a catchall@domain was working, since I have one in another domain, were it works terrific, so I thought that mysql-catchall would work too. I was wrong! I few research and some time later, I found out that I did miss to uncomment the "LDAPFLAGS=-DDASH_EXT line in the QMailLDAP Makefile.
outch, make clean && make && make setup again, and lets retry the mysql-cacthall part again... this time with success!
The next step was to create the directory to the mailling list and the dot-files (the .qmail files) with ezmlm-make. This was a small step. Then I subscribed mysql to the list, using the ezmlm-sub, and tested the mailling with an email sent from my normal email client. Far from success, however...
Qmail didn't sent the message, kepted it in the queue, and logged an ezmlm-send:_fatal:_temporary_qmail-queue_error:_/ from ezmlm-send. I looked in the FAQ, the ezmlm.org site, and even in google. The answer I got was not good enought. You know why? The few pages I found about this problem specified that it could be an currupted subscribers file, or an corrupted qmail-queue program. None of them could be the answer to my problem, since every email but to mysql list was working normal (this excludes qmail-queue), and ezmlm-list returned normally, my email, looking fine.
Fast I stoped looking in the internet, since even google could find the answer, so I gone to the next resource, RTFS (Read The Fine Sources).
And the sources give me the answer. The message was written when ezmlm-send tried to execute qmail-queue and failled.
SURPRISE, SURPRISE... This is executing qmail-queue directly? Well... (and this time I got a flash) but my qmail isn't installed in the default directory... Is there any Bernstein conf file to set the qmail directory in the source? YES, it is. The file is called conf-qmail.
Another make && make setup, and everything gone ok. The next one would be easy, but why have the first one so hard?
Posted in qmailldap ezmlm information |
Post a Comment