Re: proxymap error with mysql access table

Hello thank you Viktor for your advice, it was very helpful. I do hold temporarily incoming mails for migrating users with a transport table with retry: transport. As you said it's better clean than with smtpd_restrictions avec hold queue - no need to release manually hold mails - no trouble

proxymap error with mysql access table

Hello, I have a problem with a proxymap mysql access table. I'im using postfix 2.9.6 (Debian Wheezy package with mysql, ldap support). let me explain what i want to do : I migrate mailserver for my company from courier-imap to zimbra ZCS 8.x. During the migration process of an user account/ma

Postfix+SASL double backend (LDAP+MySQL)

Hello, first, happy new year ! I have a SMTPS server with SASL user authentication based on LDAP access/search. I have some troubles with the ldap server, so smtps service is sometimes down because LDAP service is unreachable. i would like to add a rescue/secondary backend with a MySQL table

autoresponder mail sent twice

Hello, I have installed an autoresponder using a perl script and special transport (autoreply) in master.cf my problem is that postfix send the email to the perl script twice so the perl script sends two mails to the recipient instead of one as i wish. when an user has set up its responder,

Limit mail submission

Hello i have set up a smtp test server for nomad clients outside my network at work (postfix + TLS + SASL + LDAP) to prevent suspicious / infected client with spam (or usurpated login and password) i would like to limit mail submission (rate, count, max connexion) ideally, i would to limit

Avoid recursive table lookup

Hello, i'm trying to set up a Vacation Mail Responder using postfix and special transport + PERL script. i want to let users choose between : case 1 : automatic vacation responding and not delivrering the original message (message is lost) case 2 : automatic vacation responding and delivrerin

Mixing Postfix lookup table types (mysql+ db)

Hello, I have a question about "mixing" Postfix lookup table types : For a transport lookup table i wish to set up an MySQL lookup table (as primary lookup) and a standard .db lookup table (the text and .db file are periodically generated by a shell script querying the database) as a rescue tabl

trouble using SQL like command in mysql query for map access

Hello, i set up a transport map with mysql backend but when i try use the SQL like command in the WHERE clause i've got an db_common_parse error : postmap -q '[EMAIL PROTECTED]' mysql:/etc/postfix/mysql_transport.cf postmap: fatal: db_common_parse: /etc/postfix/mysql_transpor.cf: Invalid que