> Sorry, but IMHO this is weird, storing mails in a mysql-database is just > .... don't know how to tell you, it's SICK.
I know, I am not a big fan of it either, but I do like their frontend
interface! Until, I have time to fix the backend I am going to have to deal
with the database system...
OK, sounds like the director is the way to go.
What format would this file have to be? Just a long list of users, with one
user on every line? Are there any examples of directors I could use to do
this?
Also, if I place this director at the bottom, will other mail to this domain
first be placed in my "real" accounts before this director checks a user
list?
Thanks
Michael
On 5/2/03 00.08, "Nico Erfurth" <masta@???> wrote:
> Michael Roterman wrote:
>> Yes this is sort of correct. I am using a mail system called hivemail.com
>> Basically, the program receives mail through a catch-all address that pipes
>> the mail to a PHP script that either adds the message to the db or sends
>> back a bounced error message via the php mail() function. So, exim thinks
>> that I am the sender of the mails and when they fail it sends all bounced
>> messages to my admin account.
>
> Sorry, but IMHO this is weird, storing mails in a mysql-database is just
> .... don't know how to tell you, it's SICK.
>
>> Third is to create as you said a director that checks if the user exists.
>> This is why I needed the mysql connection as my user list is in a mysql
>> database. Not really sure how to do this as I am afraid that re-compiling
>> exim will break my cpanel installation.
>
> The easy wait is to use a small scriopt, which just dumps the list of
> available accounts/aliases/whatever into a file, which is searchable via
> exim (lsearch/dbm/cdb)
>
> Nico
>
>
>
