I have to fix my mistake, I inform wrong version of my maildrop in my last mail. The exactly version is 1.7.0. I didn´t mention, I´m using Debian with Postfix. I don´t know where is the configuration files from Maildrop. I swept all over files into the machine and couldn´t find it. Maybe it is my problem. I don´t know why this files weren´t created, and if I will create it now, how can I put this things to work toghether. Perhaps it is a particularity configuration of debian?

From: Tony Earnshaw <tonye@bi...> <http://sourceforge.net/mailarchive/message.php?msg_id=12061880> Re: Maildrop 2005-06-14 10:04

tir, 14.06.2005 kl. 14.13 skrev Sérgio A P Ferreira:

My experience is with Postfix 2.0 through to Postfix 2.2.3. I use LDAP, not MySQL for all network authentication (especially useful if one has to log in at shell or GUI level), but that shouldn"t make any difference at all to your own setup. maildrop works well with virtual-style domains, where a static user (say vmail) has all read and write access to the users" mail directories and the users authenticate using Courier"s authlib or authdaemon.

I intend to use LDAP in one step further. Now I need It with MYSQL. I´m learning about LDAP for do it.

There is no configuration difference for delivery to maildrop from Postfix 2.0 to 2.2.3.

OK!

Your problem is delivering from Postfix to maildrop? What have you done to now? Either master.cf or postconf -n.

Below is my postconf –n. I belive there is a problem with the config files. The maildrop don´t know where is the config files and I don´t know where to put them...

alias_maps = mysql:/etc/postfix/mysql-aliases.cf broken_sasl_auth_clients = yes config_directory = /etc/postfix disable_vrfy_command = yes home_mailbox = Maildir/ local_recipient_maps = $alias_maps $virtual_mailbox_maps unix:passwd.byname mailbox_command = /usr/bin/maildrop mydomain = cultura.gov.br myhostname = gaia.cultura.gov.br relocated_maps = mysql:/etc/postfix/mysql-relocated.cf smtpd_data_restrictions = reject_unauth_pipelining smtpd_etrn_restrictions = reject smtpd_helo_required = yes smtpd_helo_restrictions = permit_mynetworks, reject_unknown_client, reject_invalid_hostname, reject_unauth_pipelining, reject_unknown_hostname, reject_non_fqdn_hostname, permit smtpd_recipient_restrictions = reject_unauth_pipelining, reject_non_fqdn_recipient, reject_unknown_recipient_domain, permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination, check_sender_access mysql:/etc/postfix/mysql-sender.cf, check_recipient_access mysql:/etc/postfix/mysql-recipient.cf, reject_rbl_client relays.ordb.org, reject_rbl_client list.dsbl.org, reject_rbl_client sbl-xbl.spamhaus.org, check_policy_service unix:private/sbfpolicy, check_policy_service inet:127.0.0.1:10023, permit smtpd_sasl_auth_enable = yes smtpd_sasl_security_options = noanonymous smtpd_sender_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_invalid_hostname, reject_non_fqdn_sender, reject_unauth_pipelining, reject_unknown_client, reject_unknown_hostname, reject_unknown_sender_domain, permit smtpd_tls_cert_file = /etc/postfix/smtpd.cert smtpd_tls_key_file = /etc/postfix/smtpd.key smtpd_use_tls = yes transport_maps = mysql:/etc/postfix/mysql-transport.cf unknown_local_recipient_reject_code = 550 virtual_alias_maps = mysql:/etc/postfix/mysql-virtual.cf virtual_gid_maps = mysql:/etc/postfix/mysql-virtual-gid.cf virtual_mailbox_base = /home/mailsystem virtual_mailbox_domains = mysql:/etc/postfix/mysql-virtual-domains.cf virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual-maps.cf virtual_transport = maildrop virtual_uid_maps = mysql:/etc/postfix/mysql-virtual-uid.cf

If this is a pure Postfix problem, you"d be better off posting on the Postfix ML.

I think there is a problem with Maildrop, as I said the virtual and local transport is OK...

--Tonni

Sérgio Ferreira

CGINF - Ministério da Cultura

Tel.: (61) 316 2233