On Wed, 2005-04-13 at 09:47 -0500, David Gomillion wrote:
> [EMAIL PROTECTED] wrote:
> > Hi,
> >
> > I'm currently running a courier-mta (courier.example.com)
> > with authmysq, maildrop and spamassassin as a xfilter. I'm
> > hosting multiple domains at this server. A client (which for
> > strange reasons) uses an MS Exchange-server
> > (exch.example.com). All other domains than this clients
> > domain must be delivered locally. Now, I want to spamfilter
> > all his mail. I'm thinking subdomains here:
> >
> > client.com IN MX 10 courier.example.com
> > exch.client.com IN MX 10 exch.example.com
> >
> > And at the end of /etc/courier/maildroprc, resend mail to
> > [EMAIL PROTECTED] to [EMAIL PROTECTED] This need to be
> > dynamic, as I don't know the usernames active at his server.
> > I also need to trap [EMAIL PROTECTED] and forward it to myself.
> >
> > Another possibility would be to write a xfilter that invokes
> > sendmail to resend the messages.
>
> Courier supports sending all emails destined for a domain ("Virtual
> Domain") into a single mailbox. For details look at
> http://www.courier-mta.org/?makealiases.html.
>
> Next, consider that local deliveries are already covered by the
> /etc/courier/maildroprc, so the spam filtering and virus scanning have
> already been taken care of. As to the authmysql as an xfilter, I'm not
> completely sure what you mean.
I was thinking of writing a quick perlscript that rewrites
[EMAIL PROTECTED] to [EMAIL PROTECTED], and send it directly to the
exchange-server and return a blank mail. If the To-address is anything
else, it would return the mail. It's a hack. A damn dirty one.
> Now set up a .courier-webmaster to point to your box, and a
> .courier-default to remail the email to the Exchange server, and I think
> you should be good to go. For information, see
> http://www.courier-mta.org/?dot-courier.html. You will notice that the
> .courier-default can see what the actual email address delivered to was,
> which means that you should be able to harvest the intended recipient
> from that.
>
> A word of caution: this means all email will be accepted. If there is a
> problem (like emailing an employee no longer with the company) then the
> Exchange server will only notify Courier, not the original recipient.
> That is why it is dangerous to relay messages between MTAs without the
> MTA receiving the mail from the world knowing what users are valid.
>
> My recommendation would be to either:
> 1. Host the mailboxes on Courier
> - or -
> 2. Implement spam checking and antivirus on Exchange
>
> That having been said, good luck, and let us know how it works out.
Considering the problem of bounces, I'll tell the client to just pop the
damn mailboxes himself. ;)
On the other hand; how about this:
===ALL CODE UNTESTED===
dns:
client.com IN MX 10 courier.example.com
; no exch.client.com
exchange:
Let the damn box believe that it hosts client.com directly.
I don't know if exchange is capable of looking up MX, but
let us hope not.
courier:
/etc/courier/aliases/client:
@client.com: |/usr/local/bin/redirect.pl
/usr/local/bin/redirect.pl:
#!/usr/bin/perl
use Email::Send qw[sendmail];
use strict;
my $host = 'exch.example.com';
my $mail;
while (<>) {$mail.=$_;}
send SMTP => $mail, $host;
--
Carl-Christian Salvesen <[EMAIL PROTECTED]>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
