Exchange Server Forums
Forums |
Register |
Login |
My Profile |
Inbox |
RSS
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Routing incomming email to SQL Server
|
Users viewing this topic:
none
|
Logged in as: Guest
|
Login | |
|
Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM
|
|
TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!
|
Routing incomming email to SQL Server - 21.Feb.2002 8:56:00 PM
|
|
|
rharper
Posts: 1
Joined: 21.Feb.2002
From: Nashville, TN
Status: offline
|
Is there a way to forwared all incoming email to a SQL Server database?
|
|
|
|
RE: Routing incomming email to SQL Server - 27.Feb.2002 7:49:00 PM
|
|
|
ishmell
Posts: 6
Joined: 27.Feb.2002
From: WA
Status: offline
|
I've not found a way for Exchange to do it natively, but I'm working on exactly the same thing... and I've run into a snag. First, I wrote my own SMTP server that will take all inbound messages and insert them into a table. That part was fun and it works great.
But, my problem is, I want to setup exchange server to accept all messages for the domain in question and forward them on to another SMTP server (as outlined by http://support.microsoft.com/default.aspx?scid=kb;EN-US;q260973). So, I've got an SMTP connector that is setup to relay for a specific address space (the domain in question). But, because I run my custom SMTP server on port 26 on the same machine, I had to create a second virtual SMTP server that was configured to send outbound mail to port 26 and use that virtual server as the local bridgehead for my SMTP connector. The problem I have is, exchange server seems to simply say (before checking) "You are sending to the same machine" and gives me an NDR. If exchange would just use the virtual SMTP server and send out on port 26, my custom SMTP server would get the message and the SQL database would be updated. But alas, Exchange server is lame. If I get this working, I'll let you know. I'm also looking to use this technique to try and create a "Catch All" that will allow any unresolved recipients at a given domain to forward on to my custom SMTP server and then back into an existing mailbox on the server. Ahh... the hacks we create to help exchange become a real email server.
Happy times.
|
|
|
|
New Messages |
No New Messages |
Hot Topic w/ New Messages |
Hot Topic w/o New Messages |
Locked w/ New Messages |
Locked w/o New Messages |
|
Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|