Hi,
My previous ISP had this recipe for forwarding
virtual email aliases to real email accounts.
However, lately I've been reading in the manuals
and on this mailing list that it's a "losing battle"....
Here is their recipe:
The only problem I had with it was with mailing lists,
when the recipient email is somehwere in a "for
alias(_at_)thisdomain(_dot_)com".
Of course it didn't catch those because the recipes don't
use the built in ^TO_ or ^TO (would those catch a 'for' ?).
Anyway, here is their recipe... with the ISP annotations.
I would appreciate if someone could evaluate this 'solution'
and point out what could be wrong.
# Okay, this is the last example. It is somewhat involved, and is only
# necessary if you wish to have a bullet-proof configuration that will
# handle both Carbon-Copy (Cc:) and multiple receipients on the "To:" line
# within the very same email. This is what virtual domain users
# might want to use.
#:0 c
#* ^To(_dot_)*support(_at_)virtual(_dot_)com
#! tgjohnj(_at_)aloha(_dot_)com
#:0 c
#* ^Cc(_dot_)*support(_at_)virtual(_dot_)com
#! tgjohnj(_at_)aloha(_dot_)com
# These first 2 recipies send A COPY of mail addressed to
# "support(_at_)virtual(_dot_)com", over to tgjohn(_at_)aloha(_dot_)com(_dot_)
We'll see why in a
# minute. The first one covers the TO: line, the second covers
# the CC: line.
#:0 c
#* ^To(_dot_)*manager(_at_)virtual(_dot_)com
#! billy(_at_)aol(_dot_)com
#:0 c
#* ^Cc(_dot_)*manager(_at_)virtual(_dot_)com
#! billy(_at_)aol(_dot_)com
# These next 2 recipies send A COPY of mail addressed to
# "manager(_at_)virtual(_dot_)com", over to billy(_at_)aol(_dot_)com(_dot_) The
reason we
# mail copies instead of the original is this: what happens if
# the TO: line says "To:support(_at_)virtual(_dot_)com,
manager(_at_)virtual(_dot_)com"?
# you guessed it, it only goes to support. why? because procmail
# processes this file IN THE ORDER THEY APPEAR. It never gets to
# the manager(_at_)virtual(_dot_)com recipies because it already quit after
# the first recipie. So, by sending a copy to each person, we
# guarantee that every recipient has a chance to get the mail.
#:0:
#* ^To(_dot_)*(_at_)virtual(_dot_)com
#/dev/null
#:0:
#* ^Cc(_dot_)*(_at_)virtual(_dot_)com
#/dev/null
On 16 January 2000, Rick Conn <rac170(_at_)psu(_dot_)edu> wrote:
Hello,
I have searched the procmail FAQs, the archived replies to this
mailing list, and the web, and I have failed to find an answer to this
question. I'd be much appreciative if you could help me out.
I administer a small web site for a non-profit organization.
We would like to be able to allow our volunteers to have
yourname(_at_)OurOrganization(_dot_)org email addresses that forward to
their
existing private email accounts.
[...]
This has been discussed many times in the past, and the conclusion
has always been that doing it in Procmail is a losing battle. The right
way to handle this is to add aliases for your users in your MTA. This
would be far more efficient than having Postfix figure out where to send
messages, and it would take care of all problems you describe.
Regards,
Liviu Daia
--
Dr. Liviu Daia e-mail: Liviu(_dot_)Daia(_at_)imar(_dot_)ro
Institute of Mathematics web page: http://www.imar.ro/~daia
of the Romanian Academy PGP key: http://www.imar.ro/~daia/daia.asc