Zitat von Reindl Harald <h.rei...@thelounge.net>:



Am 07.02.2011 11:51, schrieb lst_ho...@kwsoft.de:
Zitat von Reindl Harald <h.rei...@thelounge.net>:

hi

i have a little problem implementing alias-domains
the backend is dbmail with some additional tables and a inhouse
developed webui for dbmail/postfix/dovecot-proxy

i'm using "recipient_canonical_maps" as follows what works but
RCPT-Verify for "inva...@aliasdomain.tld" gives back that the
address is valid, so the mail will be received and after that
"inva...@targetdomain.tld" is correctly rejected from lmtp and
postfix sends a bounce-mesage wgat results in backscatter

The _canonical_ is *only* for rewriting as far as i know and only useful if you have to rewrite headers too. If you like (and you really should) do recipient verification you should use virtual alias or virtual maibox domains. Have
a look at http://www.postfix.org/ADDRESS_CLASS_README.html for the basics.

For further question please include "postconf -n" output.

Regards

Andreas



Thank you for your reply!

I tried to understand the ADDRESS_CLASS_README.html but until
now i see no esay mysql-based solution for domain-forwards

below the ouput from "postconf -n" and the mysql-config-files
because without the sql-queries it informations are useless

The whole system works really nice since more than a year
and i noticed the domain-alias-problem only because i
got a quarantine-message from the barracuda-appliance
bounced to postmaster :-(

address_verify_sender = postmaster@mydomain
alias_maps = mysql:/etc/postfix/mysql-aliases.cf
anvil_rate_time_unit = 1800s
body_checks_size_limit = 65535
bounce_queue_lifetime = 3d
bounce_template_file = /etc/postfix/bounce.cf
broken_sasl_auth_clients = yes
command_directory = /usr/sbin
config_directory = /etc/postfix
daemon_directory = /usr/libexec/postfix
data_directory = /var/lib/postfix
debug_peer_level = 2
default_destination_concurrency_failed_cohort_limit = 5
default_destination_concurrency_limit = 5
default_destination_rate_delay = 1
default_destination_recipient_limit = 15
double_bounce_sender = double-bounce@mydomain
fast_flush_domains =
html_directory = no
in_flow_delay = ${stress?2}${stress:0}s
inet_interfaces = all
inet_protocols = ipv4
initial_destination_concurrency = 5
lmtp_connection_cache_time_limit = 30
local_recipient_maps = mysql:/etc/postfix/mysql-recipients.cf

This is your source of recipient checking...
So it matters what you get from this by querying with "postmap -q <recipient-address> mysql:/etc/postfix/mysql-recipients.cf



Regards

Andreas


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to