Hi'ya

I've just been trying to get my server to send an email with Mail Enable but it wasn't working so I went into mail enable to look at the settings,

and when I looked at the SMTP logs LOADS of emails have tried to have been sent!!!!????

I have no users on the server yet as I've only got it last week.

luckly no emails were sent (I think) as the SMTP isn't working.


Any ideas so what happent and how to sort it?

Cheers.

Check out your relay settings on your SMTP Connector... Allow relay for authenticated senders...

That might be the problem.. then check your DNS settings within MailEnable.. I know when I first installed it, it was having a horrible time sending out mail cause I put my own DNS servers in (like I would for hosting a domain) .. idiot move... put in 207.218.192.38 and 207.218.192.39 with a space in between and that might help too!

Jake

As a sidenote, MS DNS does reply to non-authoritative entries. This means that you *can* use your DNS IPs for normal forward-lookup queries. Of course, DNS must be opperational to facilitate this.

HI.
Okay I've made it so the mail relay is not open to eveyone now!

Also SMTP via an email client now works, but not via an ASP script?

HELP... PLEASE!

Cheers.

how are you sending e-mail via ASP? If you disable relay for non-auth users, then you must use a script that logs into the SMTP server.

Also, Windows 2003 does not support CDONTs natively.

From ASP you can use Persits ASPEMAIL which is free for the basic version (pretty much all you should need) www.aspemail.com which will allow asp scripts to send the required authentication.

Of course if you have Mailenable Pro it also has its own built in COM object to do that I believe.

PressCMS

SO I can't use the standard mail component that comes with ASP?

?

Cheers.

why would you want to? The standard mail component requires an open relay -- and that's a HUGE security risk. If you have MailEnable Pro, use their method, or if you have MailEnable Standard, then you can use Persits ASPEmail, as pointed out earlier.

I disagree -- you can have your cake and eat it too

You can:
- Set MS SMTP server to a different port
- Close incoming TCP on that port (TCP/IP filtering or firewall)
- Set the Relay Access restrictions to 127.0.0.1 and your server's IPs
- Make sure you have the correct NTFS on your Drop (or is it Pickup??) directory

Watch MailEnable and CDO.sys play nicely together.

Keith

...then watch as someone signs up for an account on your box and merrily spams 2,000,000 emails out from it on a web script and you have no idea who it was that did it... oh my!

Until recently I would have agreed with you, but I have seen the light.

PressCMS

yes, but then you're open to a spammer on your box. I like the authenticated method because it promotes accountability. If my clients try to spam, I know exactly who it is.

_//_ Edit _//_ Wow, PressCMS, twice we've posted at the same time, in as many days.

doh! -- ok.. In that case... I like the authenticated method

I suppose my method works if I'm the only developer on the box

Ironic really as it was you that changed my mind about using CDONTS, MS SMTP etc

PressCMS

Hi.


Yup okay I agree the MS SMTP is not the best solution, but for now it will have to do as I need to get this site uploaded.

What port would you recomend for now?

Cheers.

Anything that's not being used...

8080, 8088, 8888 seem to be common, however.

If you mean the port for MS SMTP it doesnt matter, so set it to 666 or something Its only the port that it listens on you are changing. That way mailenable will listen on 25 and SMTP will listen on 666 so they wont clash.

CDONTS etc sends to the actual pickup queue, so MS SMTP doesnt actually need to listen at all.

PressCMS

- Damn, LighthousePoint beat me this time

SOB SOB, CRY CRY!


Changed to port 666 (WHAHAHAH), and it says...

'Service Didn't respond in a timley manner??!!?!?!'

Any ideas?



PS. Thanks guys for taking the time to help me!

hmmm... which port did you change and where are you getting this service error?

PressCMS

Hi.

I went into IIS and right clicked on the SMTP server, then clicked advanced, changed the port to 666.

Okayed everything.

Then right clicked on the 'Default SMTP virtual server' -> Start.

Then hungs for about 1min then says the error.

??
GULP

Jase.

How many places does your site send e-mail? I assume only a few -- maybe less... You'll spend less time, and have a more secure setup if you simply modify your code to work with an authenticated SMTP server.

My $0.02.

Hi.
I can't really as some clients sites use the standard mail object.

I'm getting there though,
the service is now starting and test's via the HELM config.exe can send emails over the MS SMTP.

But if I try and send mail via an ASP script I get an error saying it can't create the Object?

Any thoughts?

Cheers

I havent got a lot of information to go on but is the script running in a site you have created with Helm? If so I imagine Helm creates its own users for each IIS site, and these users will need write permissions to the intetpub/mailroot/pickup directory otherwise they cant drop mail.

On the other hand, it could be your script!

PressCMS

Hi'ya

Okay I couldn't get MS SMTP working on port 666, but I got it all working if I changed mail enables SMTP port to 666 and left MS SMTP on 25, that way they will play nicely together.

But...

Does anyone know if I can get the microsoft CDO mail object in ASP to use a diffrent SMTP other than the very doddgy MS SMTP?

Cheers.

I dont think so. The CDO component doesnt actually send anything anywhere iirc, it just creates the mail and places it in the pickup folder of the SMTP server.

If you have put MS SMTP on port 25, I hope you remembered to stop everything but local relaying from it. And if Mailenable is on 666 I assume you arent expecting any incoming mail?

I would suggest that you use another mail script like ASPEmail or similiar if you want to send to mailenable. At least that way you can provide authentication with it.

Yes, whatever mail server runs on port 25 is the one that will handle incoming mail. For this reason, you want MailEnable on port 25. MS SMTP is a very *bad* mail server for handling incomming messages.