Exch2003, use connector if email is from @alternative.com (internal)
- Hi,Company have several domains. All emails are relayed using DNS and send directly to internet. I have a need, if email is written from one specific internal domain (which is not default one), send it to smarthost (connector), and not relay directly to internet. I need this because of DNS MX records. I can create multiple MX records, but I use greylisting, and I end up not getting emails for hours because boucing emails n+k+2 times.If it was exchange 2007, I would use transport rules, how to do same with 2003?--Muson
All Replies
- Thats the limitation on SMTP connector. It always works based on the recipient domain name and not the sender one. so if you set a SMTP connon hotmail.com, any mail for hotmail.com originating from your organization , will take thaat connector.
Raj - Not sure what how your use of greylisting affects your ability to send messages.
Can you explain further what exactly you are trying to accomplish and why? - I have a company A (a.com), and B company (b.com), They are merging, but not IT, separate AD forests. A company is also using email domain abc.com, and i created shared namespace of abc.com in both companies.At the moment, abc.com have two MX DNS records, pointing to A and B exchange servers;. I want to leave only one MX record for A exchange (because of greylisting). So if B is sending email from B exchange server to internet with source email as abc.com, Reverse DNS test will fail, and message will be filtered by antispam (at client side).Hope it will make clearer--Muson
Hi Muson,
From your first post, I understand you have one Exchange organization. But in you second post, you said they're separate AD forest and separte Exchange organization. I'm a little bit confused. Could you please explain it?
If you have two seprate Exchange organization, you could forward all mails of Exchange server B to server A, and let A send the mails out.
Regarding the greylist, as it's a anti-spam feature, it should not have relationship with sending email.
Thanks,
Elvis
- Hi Elvis,There are two exchange organizations. Link between them are very slow (B company is in another country), so I don't want to relay all emails from one server.About Greylisting. For example external user send email to admin@abc.com. It send to first MX record pointing Exchange server A, A server refuses message. Then message is send to second MX record to Exchange server B, B server also refuses, because it does not have triplet jet (source email, destination email, time). Then message should retry to server A, but depending on senders SMTP configuration it could take 10min, 30min, 4hours, or 24hours before trying to send again to server A.This greylisting problem can be resolved by removing second MX record (for server B), and all messages will be send only to server A. But if server B tries to send email from B to Internet with source email abc.com, it will be market as spam at receiver, because "reverse DNS test" (sender SMTP IP is not the same as in MX record) will fail.--Muson
Hi Muson,
If the SMTP IP is not the same with MX record, the mail server should NOT reject the mail and it can't be a criteria for judging junk email. For instance, sometimes, the send server and receive server is not the same. Given the current situation, if the remove server use an uncommon method for junk mail identification, we need to contact their admin for further negotiation.
Thanks,
Elvis
- Hi Elvis,most of emails servers especially in eastern europe, use reverse DNS lookup test, and stamp messages as spam, this is against dynamic IP spammers. And you can't send email to @mail.ru if your seding SMTP IP is not the same as MX record. I know that. As I can see no one got even close to answering my question, so i guess is not possible with E2003 (unless IIS event sinks...)--Muson
Hi Muson,
Even you use other server rather than Exchange to send email, given the current situation, the MX record doesn't match with the sender IP, it will fail if the recipient side consider this is a criteria for judging junk mail. As I explained before, the root caused is they don't use standard way for email identification. If you would like to make MX record match with the sender IP, the only way is forward the mails from B company to A company.
Thanks,
Elvis
