On Thu, 13 Oct 2011 15:33:48 +0530
Ram r...@netcore.co.in wrote:
On 10/13/2011 02:37 AM, Ralf Hildebrandt wrote:
* Noel Jonesnjo...@megan.vbhcs.org:
You might be able to do something with check_recipient_mx_access.
Mostly, these domains have no MX, but only an A record. But yes, I
I've got working Postfix solutions using hash: and mysql: direct lookups.
I'm now experimenting with using CALLs to MySQL StoredProcedures in
Postfix lookups.
/etc/postfix/main.cf
virtual_mailbox_domains = proxy:mysql:/etc/postfix/virtual_mailbox_domains.cf
virtual_mailbox_maps=
cd /usr/local/src/postfix-2.8.5
grep -rlni CLIENT_MULTI_RESULTS .
... nothing.
Assuming the patch at
http://errorval.livejournal.com/37425.html
works, it looks very similar for current v285 src,
--
--- ./src/global/dict_mysql.c.ORIG 2010-06-18 15:25:13.0 -0700
+++
Rich:
Stored procedures do not work in Postfix without code changes because
the |CLIENT_MULTI_RESULTS connect flag, for MySQL API, is not turned on.
As a general rule, Postfix does not implement a (database) feature
unless the Postfix code is in accordance with the documentation of
the
Conversing with myself ... Reading
http://www.toadworld.com/TWPIPELINEMarch2008/PIPEMarch08MySQL/tabid/308/Default.aspx
Rather than a StoredProcedure which returns a result set, using a
StoredFunction that returns a single value,
DELIMITER //
CREATE FUNCTION
Rich:
Assuming the patch at
http://errorval.livejournal.com/37425.html
works, it looks very similar for current v285 src,
Do not use this patch. It silently ignores database lookup errors.
Postfix will bounce or mis-deliver mail instead of holding off until
the database is fixed.
See
Do not use this patch. It silently ignores database lookup errors.
Postfix will bounce or mis-deliver mail instead of holding off until
the database is fixed.
Thanks for the heads up.
See my other post with the details of what is wrong with this code.
Got it. Reading thru the referenced
Rich:
Do not use this patch. ?It silently ignores database lookup errors.
Postfix will bounce or mis-deliver mail instead of holding off until
the database is fixed.
Thanks for the heads up.
See my other post with the details of what is wrong with this code.
Got it. Reading thru
On Sat, Oct 15, 2011 at 5:31 PM, Wietse Venema wie...@porcupine.org wrote:
Your post suggests that Postfix supports stored procedures that
return a single result (not a set).
That's Stored Functions, not Stored Procedures. But, yes.
That may be a nice workaround.
Atm it looks like the
Atm it looks like the StoredFunc approach is *always* returning a
valid result. Not useful.
Alos, not sure if it's my query, or what Postfix does with the result.
Needs more work.
Making a minor change to the StoredFunctions' DECLARE,
- DECLARE `result` TINYINT(1) DEFAULT anything;
+
Correction, that's:
Testing the Stored*Functions*, and the associated lookups,
postmap -q GOOD_DOMAIN proxy:mysql:/etc/postfix/virtual_mailbox_domains.cf
1
postmap -q GOOD_USER proxy:mysql:/etc/postfix/virtual_mailbox_maps.cf
1
postmap -q BAD_USER
11 matches
Mail list logo
