From my experience, working on private queues reduces a lot of maintenance and complications both in development and production. It is also faster because each MSMQ call does not hit the AD (you can bypass that by using the GUID though).

All in all, working over an year in MSMQ, I find private queues to be better.

MSMQ is not a tool for sending mail, although you could implement it as that if you wished. It would involve considerable effort compared to a purpose designed mail transfer protocol such as SMTP. A message, in the context of MSMQ, does not mean a mail message.

A reason you have not got a reply so far is that  a Google search or an MSDN search, or even looking at Windows Server or XP documentation for MSMQ would turn up the information you wanted.

http://technet2.microsoft.com/WindowsServer/f/?en/Library/cc01d065-19ff-42fa-a18a-fa13ef01d6251033.mspx

http://technet2.microsoft.com/WindowsServer/f/?en/Library/cc01d065-19ff-42fa-a18a-fa13ef01d6251033.mspx

http://technet2.microsoft.com/WindowsServer/f/?en/Library/cc01d065-19ff-42fa-a18a-fa13ef01d6251033.mspx

http://www.microsoft.com/windowsserver2003/technologies/msmq/default.mspx

A private queue is one whose details are not published in Active Directory. A public queue's details are published in Active Directory.

I hope that is helpful, but next time I suggest doing a little research first.

Yours,

Moray

-------------------------------------
Moray McConnachie
IS Manager        +44 1865 261 600
Oxford Analytica  http://www.oxan.com

From: msmq@yahoogroups.com [mailto:msmq@yahoogroups.com] On Behalf Of Aravinda K
Sent: 10 May 2006 05:35
To: msmq@yahoogroups.com
Subject: [msmq] Query abt sending mail using MSMQ?

Yahoo! India Answers: Share what you know. Learn something new. Click here
Send instant messages to your online friends - NOW

Click here to report this email as spam.