Messages not delivered to real server, but locally

[danvlas]

Hello all,

I have to set up a BlackBerry solution for the company I work for. However, till now we used QMail on a Linux server, which worked very well, and now we need to migrate everything to Exchange, because BlackBerry does not like Linux.
As anyone can imagine, it's a difficult task, with 300+ email accounts and users killing us when the mail is down.

Here is the environment and the idea that I'd like to implement:

QMail set up on a Linux machine, known as mail.domain.com

Exchange 2003 on Win 2003 server with Active Directory, known as mail.testdomain.com

BlackBerry Enterprise server, sitting together with Exchange

user@domain.com is forwarded from QMail to user@testdomain.com on Exchange and subsequently to BlackBerry

Of course, when sending the mail from BlackBerry through Exchange, I want the 'From' address to be user@domain.com
I did this by setting a primary SMTP Address to 'user@domain.com'

It works fine for messages to addresses NOT listed in Exchange.

However, when the SMTP address exists in Exchange, the message is delivered locally instead of being forwarded to the real domain.

This poses a problem, because people using BlackBerry will be able to get their messages on the handheld, but won't get them from the POP3 account and nobody is willing to accept two or more email addresses.

Is there anyone who could point me in the right direction to solve this problem?

Thank you in advance,



Daniel Vlas
Systems Consultant

http://www.geocities.com/danvlas/AutoMail.html

 

[Spirit]

If your implimenting Exchange don't use POP3 it defeats the object of spending all that money!

Now I am not familiar with blackberry but if you have to use POP3 for them, set it to leave the mail on the server and use outlook to manage the emails.

I don't understand what "the message is delivered locally instead of being forwarded to the real domain" means. Do you use need multiple domains for blackberry? I.e. @mydomain.com for normal mail and myBBdomain.com for blackberries?

If thats the case set up a forwarder and deliver to both addresses it means duplication of management on both the BB & Outlook though.

Sorry about note being more specific but if you can say how blackberry works I might be more help

Iain

 

[danvlas]

Actually, I'm positive that not BlackBerry is the problem, but Exchange.

I'll be more specific:

We have an official mail server that has been working properly for a long time, with no problems, but it is not suitable for BlackBerry. Let's call this mail.linux.com, with users like john@linux.com, sam@linux.com, bill@linux.com

I could move all users from QMail to Exchange, but I have not tested long enough and we are not very familiar with Exchange, so I had to think about a temporary solution.

Installed Exchange on a different domain, and set up a limited number of users (people who will work with BlackBerry). Let's call this server mail.exchange.com, with users like john@exchange.com, bill@exchange.com. Let's assume user 'sam' does not have a BlackBerry, therefore is not an Exchange user.

Generally, people who have a BlackBerry also have a notebook, with a mail client set up on the official mail address (john@linux.com). Usually POP3, rarely IMAP4. They have a fast access to the email through BlackBerry, but when not on travel, they download the messages on the laptop or desktop.

I want the Exchange server to send the email address john@exchange.com as john@linux.com

For this, I set the primary SMTP Addresses of users 'john' and 'bill' to john@linux.com and bill@linux.com (in Active Directory).

Now: when john@exchange.com sends an email (via Exchange or BlackBerry) to sam@linux.com, it goes through well and Sam gets the mail fine on his laptop.

But, when john@exchange.com sends the mail to bill@linux.com, Bill gets the email on the BlackBerry but NOT on the laptop.

Looks like Exchange 'knows' the address 'bill@linux.com' exists locally and does not send it to the 'real' server, but stores it locally.

I need to know how to get Exchange to always route emails to the 'outside world', instead of checking if the addresses exist on the local server.


Hope it's clearer now.




Daniel Vlas
Systems Consultant

http://www.geocities.com/danvlas/AutoMail.html

 

[Spirit]

I think the issue here is that as far as exchange is concerned it is the "real" server linux.com because you've set you're AD users up with both addresses.

So when you email Sam who does not have an exchange account its resolved elsewhere, on the Qmail server.

The only way that I know of not to resolve internally is to remove the @linux.com SMTP address. If you connect Bill's laptop to the Exchange server then he will receive it on both? Depending on the POP3 settings about downloading the message and deleting it or leaving it on the server.

Iain

 

[danvlas]

Yes, if connected to Exchange, Bill will receive the message both on BlackBerry and laptop.

If I remove @linux.com address, the address is indeed resolved to Qmail. But the darn 'From' address will be bill@exchange.com when message is sent from BlackBerry (which does not have the option of setting the Reply To field), so when recipient hits Reply, the message is sent to...Exchange.

There is a possibility to setup 2 mail accounts in Outlook - one for Qmail and one for Exchange, but then Bill will receive some messages twice - those that are sent to @linux.com and forwarded to Exchange.

Of course, one may say that I should use aliasing instead of forwarding, but I'm in the test period and can't just relay the messages without storing them on Qmail...


Haven't had such a headache for a long time...


Daniel Vlas
Systems Consultant

http://www.geocities.com/danvlas/AutoMail.html

 

[ilceres]

What a strange and complicated situation!!

Ok, it's only an idea, I'm not sure that it can work:

Set up a machine with a SMTP daemon, and configure it in a Perimeter Network. We call it MAILRELAY .

Now set Exchange server to send all mails trough MAILRELAY with a new SMTP connector.
Then MAILRELAY will relay the mails with domains.

MAILRELAY not have AD, then for solve domain @linux.com it takes "internet way".

Teorically it work.... Pratically I don't know

Italian are WORLD CHAMPION

 

[danvlas]

Yes, theoretically it should work, but - as always - it became so urgent that there was no more time for testing, so I just changed the SMTP/POP3 account properties for people using BlackBerry to point to Exchange instead of QMail.

And now it's time to move all other accounts from Qmail to Exchange...

Thank you anyway, I'll try the solution in a development environment.




Daniel Vlas
Systems Consultant

http://www.geocities.com/danvlas/AutoMail.html

 

[ilceres]

Can I ask you a thing now?

How is move Linux accounts to Exchange?

I probabilly have to do this work soon, from a Courier IMAP server, and at the moment I haven't start studing the work...
but I have to do.

It's an hard work?

Italian are WORLD CHAMPION

 

[Fatboy0341]

Research, plan, test, revise and implement.



"He who laughs last probably made a backup. He who laughs loudest probably hasn't checked his backups in a while."

 

[ilceres]

Thak you Fatboy, but it's obvious.

I only asked for a personal opinion from danvlas, about migrating a mail server from Linux to Microsoft world.

Italian are WORLD CHAMPION

 

[Fatboy0341]

Understood...I wasn't trying to be a wiseguy.

Let us know how your migration goes.

JB

PS - Viva Italia!!!



"He who laughs last probably made a backup. He who laughs loudest probably hasn't checked his backups in a while."

 

[danvlas]

To be honest, I wouldn't make this move unless other solution was impossible. Linux server just sat there on a Pentium III machine 500 Mhz for some 6 years, never needed a restart, excellent security, no monitor, no mouse, no keyboard.

But this BlackBerry server only runs with Exchange which in turn runs on a Win 2003 Server which needs updates which require restarting the server...
But that's life.

Now, about migration, it won't be very difficult, but tedious. Here is my plan:

1. Create a corresponding Exchange email account for each Qmail user, with a generic password
2. Create an alias on Qmail to forward the incoming email to that user on both servers/domains.
3. Inform the user about the OWA (link, user name and password) - in order to be able to check the mail by himself before I have the time to go and configure his client mail account
4. Urge user (in writing) to change his password via OWA
5. Actually go and configure his client mail account
6. Keep Qmail as a mail backup server for as long as it takes me to get some grip on Exchange. And...if something happens to Exchange,

I believe it will take me some time to move almost 300+ mail accounts from 2 domains, I really hope I won't have to roll it back...

To Fatboy0341: what you recommend is excellent, but it's only theory. Lately I found out the time is much shorter than expected. I was just given the time to implement...we'll revise, test, plan and research after that



Daniel Vlas
Systems Consultant

http://www.geocities.com/danvlas/AutoMail.html

 

[Fatboy0341]

To Fatboy0341: what you recommend is excellent, but it's only theory. Lately I found out the time is much shorter than expected. I was just given the time to implement...we'll revise, test, plan and research after that.

I agree again 100% - that's usually the way it goes. "Get it done and test it later".

Your plan sounds good...how much time do you actually have to start and complete this project?

JB




"He who laughs last probably made a backup. He who laughs loudest probably hasn't checked his backups in a while."

 

[ilceres]

Thank you danvlas.. the plans sounds good.

About Linux Mail Server... with our Debian based linux mail server (the administration it's by outsourcing) we have a lot of problem.

It's right... low HW requirements, no restart but...
- A lot of problem with imap syncrhonize (please don't ask me how heavy that server is loading my network..)
-Spam a lot
-Slow delivery: the mailbox (about 150) start to become very big (up to 30 gb), and the disk access is a neck bottle
-Sometimes client stop working and I have to reconfigurate the account

I'm not saying that all Linux server has problem, but this is my experience

For the Exchange: don't worry, I implemented and managed a EXCH server with about 200 mailbox for 2 years without problem, except SPAM, solved with a relay server with GFI software.
About updates restart, I think is a good thing: I planned updates and restarting nightime after backup - never had a problem - and with a restart you free your RAM charge of Information Store service.

I haven't understand if you have or not expirience with exchange.. but this is a good tech source:

http://www.msexchange.org

Finally... good luck!!

Fatboy... it's all ok, advice are wellcome

Italian are WORLD CHAMPION