That almost makes sense, even in my ignorant state. Please bear with me.
I'm pretty sure I've overridden local because I use maia mailguard, which
re-injects email into the mail processing queue after running it through
amavisd/spamassassin. Here are the additions I made to the master.cf file when
I installed maia:
smtp-amavis unix - - n - 2 smtp
-o smtp_data_done_timeout=1200
-o smtp_send_xforward_command=yes
-o disable_dns_lookups=yes
-o max_use=20
127.0.0.1:10025 inet n - n - - smtpd
-o content_filter=
-o smtpd_restriction_classes=
-o smtpd_delay_reject=no
-o smtpd_client_restrictions=permit_mynetworks,reject
-o smtpd_helo_restrictions=
-o smtpd_sender_restrictions=
-o smtpd_recipient_restrictions=permit_mynetworks,reject
-o smtpd_data_restrictions=reject_unauth_pipelining
-o smtpd_end_of_data_restrictions=
-o mynetworks=127.0.0.0/8
-o smtpd_error_sleep_time=0
-o smtpd_soft_error_limit=1001
-o smtpd_hard_error_limit=1000
-o smtpd_client_connection_count_limit=0
-o smtpd_client_connection_rate_limit=0
-o smtpd_milters=
-o local_header_rewrite_clients=
-o local_recipient_maps=
-o relay_recipient_maps=
-o
receive_override_options=no_header_body_checks,no_unknown_recipient_checks
If I remember the maia docs correctly, postfix does content filtering on the
mail by sending it to smtp-amavis, and then re-injects the result into
localhost (127.0.0.1) on port 10025 if it's not spam. But I'm not sure of that.
When I add a mailman transport, use a transport map and define the transport
map in main.cf I still get the same "cannot relay" error, which I think means
mail sent to @lists.arcabama.com is still being sent to the Exchange server,
when it should just be delivered to the local unix box.
Any other thoughts?
- Mark
"Too much sanity may be madness! But maddest of all - -to see life as it is and
not as it should be."
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of mouss
Sent: Sunday, December 07, 2008 4:12 PM
To: [email protected]
Subject: Re: Info on Filtering Mail based on subdomain
Mark A. Olbert a écrit :
> I recently installed Exchange as my mail server, with postfix on a linux box
> serving as an anti-spam front end. This works great for all my regular mail.
>
> However, I'm having trouble figuring out how to integrate mailman into the
> setup. Previously, when mail delivery took place on my linux box with postfix
> it "just worked".
>
> I think what I need to do is set postfix to distinguish between mail sent to
> my domain (e.g., [EMAIL PROTECTED]) and mail sent to a subdomain used only
> for mailman lists (e.g., [EMAIL PROTECTED]), and use a different final
> delivery mechanism for each. "Domain" mail (@arcabama.com) would continue to
> be sent to the Exchange server, while "subdomain" mail (@lists.arcabama.com)
> would be routed to mailman on the linux box.
>
> But I'm not sure if that's correct and, even if it is, I'm unclear as to how
> to proceed. I'd appreciate any hints, leads or tips. Thanks!
>
you can put lists.arcabama.com in mydestination. This way it will be
delivered by "local". then use alias_maps to setup mailman aliases. This
assumes that you did not "override" or disable local.
An alternative is to define a "mailman" transport in master.cf.
something like
mailman unix - n n - - pipe
flags=FR user=mailman:mailman
argv=/usr/local/bin/mailman_wrapper.sh
${user} ${extension}
and use transport_maps:
lists.arcabama.com mailman:
__________ Information from ESET NOD32 Antivirus, version of virus signature
database 3669 (20081207) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
__________ Information from ESET NOD32 Antivirus, version of virus signature
database 3669 (20081207) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
