MailEnable and PHP

[Dale]

i've been using a custom lib that works with just about every setup i've
come across. it creates a raw, rfc compliant email and saves it to file.
usually i'll exec sendmail (*nix and windows) or put it in iis' pickup
directory and life is good. i've got a client now that is using MailEnable.
the problem is, it seems, that though i programmatically place the file in
the correct directory and have ME setup to poll the outgoing folder, it must
kind of 'register' emails and that, through recieving it literally via
smtp...even though those files are put in the same directory as the one i'm
writing to. the second problem is that the command-line tool doesn't support
taking a file name as an argument - if it did, the file could be
'registered' and processed correctly. it takes pretty much the same
arguments as php's mail function.

is there something i'm missing or is it not possible to configure ME to
process any files it finds in the outgoing directory?

tia,

me

[Dale]

"Dale" <th*****@example.comwrote in message
news:5V*******************@newsfe07.iad...

i've been using a custom lib that works with just about every setup i've
come across. it creates a raw, rfc compliant email and saves it to file.
usually i'll exec sendmail (*nix and windows) or put it in iis' pickup
directory and life is good. i've got a client now that is using
MailEnable. the problem is, it seems, that though i programmatically place
the file in the correct directory and have ME setup to poll the outgoing
folder, it must kind of 'register' emails and that, through recieving it
literally via smtp...even though those files are put in the same directory
as the one i'm writing to. the second problem is that the command-line
tool doesn't support taking a file name as an argument - if it did, the
file could be 'registered' and processed correctly. it takes pretty much
the same arguments as php's mail function.

is there something i'm missing or is it not possible to configure ME to
process any files it finds in the outgoing directory?

same goes for the 'incoming' directory.

thanks.

[Dale]

"Dale" <th*****@example.comwrote in message
news:5V*******************@newsfe07.iad...

i've been using a custom lib that works with just about every setup i've
come across. it creates a raw, rfc compliant email and saves it to file.
usually i'll exec sendmail (*nix and windows) or put it in iis' pickup
directory and life is good. i've got a client now that is using
MailEnable. the problem is, it seems, that though i programmatically place
the file in the correct directory and have ME setup to poll the outgoing
folder, it must kind of 'register' emails and that, through recieving it
literally via smtp...even though those files are put in the same directory
as the one i'm writing to. the second problem is that the command-line
tool doesn't support taking a file name as an argument - if it did, the
file could be 'registered' and processed correctly. it takes pretty much
the same arguments as php's mail function.

is there something i'm missing or is it not possible to configure ME to
process any files it finds in the outgoing directory?

tia,

me

here's a freaking v8 moment! just write the file directly to the recipient's
postoffice inbox...duh!

:^)