 | Start a set with this search |
 | Include this search in one of my sets |
 | Exclude this search from one of my sets |
 | Permalink to these results Paste this link in email or IM: |
 | Atom feed for tracking future search results Paste this URL into your reader: |
5 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Temporary failures - ...| From | Sent On | Attachments |
|---|---|---|
| ml | Jul 17, 2006 6:53 am | |
| Tony Earnshaw | Jul 17, 2006 10:46 pm | |
| ml | Jul 18, 2006 2:34 am | |
| Tony Earnshaw | Jul 18, 2006 5:31 am | |
| mouss | Jul 30, 2006 4:02 pm |
| Permalink for this message Paste this link in email or IM: |
| Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | Re: [maildropl] Temporary failures - maildrop+LDAP+postfix | Actions... |
|---|---|---|
| From: | Tony Earnshaw (teri...@barlaeus.nl) | |
| Date: | Jul 18, 2006 5:31:16 am | |
| List: | net.sourceforge.lists.courier-maildrop | |
ml skrev:
What OS and version is this? I used to get a lot of this on RHEL3 with OpenLDAP 2.2.17 installed from source. It's virtually all gone with RHAS4 and OpenLDAP 2.3.24 built from adapted Buchan Milne (Mandriva cooker) rpms.
my OS is SuSE-9.3 ... ;/ openldap 2.2.23, installed via SuSE-rpm
Ok - I haven't done much with SuSE, but 9 isn't the latest, is it? That would be 10. Did you build maildrop on the server, or is it also a SuSE rpm?
OL 2.2 uses an OK BDB/HDB backend, but you *must* have a properly configured DB_CONFIG in /var/lib/ldap (or wherever it is). Also, 2.2.23 is known as buggy (RHAS4 also has it as standard) and you should try to update to 2.2.29.
- postfix 2.2.1, virtual_transport = maildrop
I have Postfix 2.3.0 with a local transport table (pipe) to maildrop.
Do You mean such an entry in master.cf ? maildrop unix - n n - - pipe flags=DRhu user=vmail argv=/usr/local/bin/maildrop -d ${recipient} -w 80
if yes, same here !
More or less, though I have a local transport table, not virtual. But that wouldn't affect your trouble, Postfix is handing off to maildrop ok.
Nobody has his own login, the mail structure is owned by vmail.
Same here.
- maildrop-2.0.2
Same here
- courier-imap-3.0.8-3
4.1.1 here, but that won't have anything to do with it
- cyrus-saslauthd
I don't use Cyrus saslauthd. This would be for Postfix or pam, since maildrop doesn't use any SASL code. Would you be authenticating with pam? maildrop can use pam, but I use authldaprc which lets me use quotas and a specified Maildir (neither possible with pam) and more (a compound attribute filter)
I'm using authldap too, no pam... cyrus-saslauthd is just for smtp-auth, so it should not be relevant when receiving mail.
Nope, it's not. I use auxprop for Postfix with ldapdb (I built my own SASL 2.1.22 spec and rpms) with libldapdb support for Postfix cram- and digest-md5 support.
- openldap2 as backend for all
What OpenLDAP 2? If this is 2.0, you could be letting yourself in for much trouble.
openldap 2.2.23, installed via SuSE-rpm.
I might consider to upgrade my openldap and compile it from source !?
You could try and see if it helps, especially if you have a test server. OpenLDAP 2.3.24 is way further than 2.2 with the advanced layered components it supports, its replication (delta syncrepl) and utter stability (including automatic DB repair on restart of slapd).
Red Hat people are lucky with the rpm spec-writer support they have - Sam drilled "think rpm" in to me a long time ago. There's just about nothing on our 4 servers that isn't built as rpms - it wasn't always so.
My guess might be that you should be looking at your LDAP support - it's always so, that if thousands of people are using a product with no problems, the best thing to do is to look at one's own individual components.
Good luck,
--Tonni
-- tonni at barlaeus.nl Tony Earnshaw