No local users

I would like messaging to treat all mail as non-local. In other words no local users all mail must travel to an outside SMTP server that I specifiy. I have a pretty much out of the box imta.cnf file and tried to add a domain rule / rewrite so that all mail from my domain goes to a specific SMTP host. But it still wants to deliver internal mail to the messaging server and not push it out. Any ideas or help on this would be appriciated.

Erik

[456 byte] By [ekkong] at [2007-11-26 9:22:54]
# 1
Messaging Server cannot deliver mail to users that are not defined in ldap.You'll need to be a little more descriptive of what you have going.....please do:imsimta test -rewrite -debug valid_address@your_domainso we can see what it's trtying to do.
jay_plesset at 2007-7-6 23:56:42 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...
# 2

Ya, sorry, that was probably a little vague. I want all my internal users / mail to go to an out bound SMTP server - not be treated as internal mail - even though it is.

Here is a test rewrite:

forward channel= l

channel description=

channel user filter=

dest channel filter=

source channel filter =

channel flags #0= BIDIRECTIONAL MULTIPLE IMMNONURGENT NOSERVICEALL

channel flags #1= NOSMTP DEFAULT

channel flags #2= COPYSENDPOST COPYWARNPOST POSTHEADONLY HEADERINC NOEXPROUTE

channel flags #3= LOGGING NOGREY NORESTRICTED RETAINSECURITYMULTIPARTS

channel flags #4= EIGHTBIT NOHEADERTRIM NOHEADERREAD RULES

channel flags #5=

channel flags #6= LOCALUSER REPORTNOTARY

channel flags #7= NOSWITCHCHANNEL NOREMOTEHOST DATEFOUR DAYOFWEEK

channel flags #8= NODEFRAGMENT EXQUOTA REVERSE NOCONVERT_OCTET_STREAM

channel flags #9= NOTHURMAN INTERPRETENCODING USEINTERMEDIATE RECEIVEDFROM VALIDATELOCALSYSTEM NOTURN

defaulthost= vcsu.edu vcsu.edu

linelength = 1023

channel env addr type = SOURCEROUTE

channel hdr addr type = SOURCEROUTE

channel official host = hostname1.vcsu.edu

channel queue 0 name= LOCAL_POOL

channel queue 1 name= LOCAL_POOL

channel queue 2 name= LOCAL_POOL

channel queue 3 name= LOCAL_POOL

channel after params=

channel user name=

urgentnotices = 1 2 4 7

normalnotices = 1 2 4 7

nonurgentnotices= 1 2 4 7

channel rightslist ids =

local behavior flags= %x7

expandchannel =

notificationchannel=

dispositionchannel=

saslswitchchannel=

tlsswitchchannel=

backward channel= l

header To: address= user.name@vcsu.edu

header From: address= user.name@vcsu.edu

envelope To: address= user.name@vcsu.edu (route (hostname1.vcsu.edu,hostname1.vcsu.edu)) (host vcsu.edu)

envelope From: address = user.name@vcsu.edu

name=

mbox= user.name

Extracted address action list:

user.name@vcsu.edu

Extracted 733 address action list:

user.name@vcsu.edu

Address list expansion:

user.name@ims-ms-daemon

1 expansion total.

Expanded address:

user.name@vcsu.edu

Submitted address list:

ims-ms

user.name@ims-ms-daemon (orig user.name@vcsu.edu, inter user.name@vcsu.edu, host ims-ms-daemon) *NOTIFY-FAILURES* *NOTIFY-DELAYS*

Submitted notifications list:

I want this internal user not be treated interanl and go to a different host like user.name@server2.vcsu.edu

Hopefully that is a little clearer?

Thanks,

Erik

ekkong at 2007-7-6 23:56:42 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...
# 3

Ok, so the user exists in LDAP. And the value of "mailhost" is the system we're talking about.

Messaging Server will ALWAYS attempt to deliver such users' messages to the "mailhost" specified in the user's ldap record.

If you want the messages delivered elsewhere, simply specify "mailhost" as the system you want the mail sent to.

jay_plesset at 2007-7-6 23:56:42 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...
# 4
okay - yup - but then they can't access messaging express, since the mailhost is different than the messaging server, does that make sense?Erik
ekkong at 2007-7-6 23:56:42 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...
# 5

Um, not really.

Messaging Express can be easily configured to be Messaging Express Multiplexor. MEM is a http proxy specifically for webmail.

If you need to use a second system for store, then ME is useless anyway, as a local package. It interacts directly with the mail store, so if the mail isn't there, it can't find it.

Check the capter for configuring MEM. Configutil setting, restart, and you're there.

jay_plesset at 2007-7-6 23:56:42 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...
# 6

Okay - maybe I should explain a little more what I am trying to do.

We just migrated to Exchange - not my choice, ask our administration - anyway, we have both systems up and going so users and get into both and move / backup information on the Sun JES side for a few months. But, they will continue to send from Messaging Express and Thunderbird so I until we shut the messaging system down. So I would like any message they send in the Sun JES system to get auto re-directed to our Exchange SMTP server.

I don't want to use the forwarding piece since they could change that or shut it off.

I was hoping a simple domain rewrite would do the trick:

vcsu.edu becomes exchange.vcsu.edu

I have have played with this for a week now and it still want to keep all internal users internal.

Thanks for your patiences with me....

Erik

ekkong at 2007-7-6 23:56:42 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...
# 7

Well, your desires seem to be somewhat incompatible.

ME won't work with Exhange. Period.

If you want to keep a copy of mail on your Messaging Server, you could use a global sieve filter, to fwd all messages. This wouldn't be available to the users to mess with, but . . .

If they connect to your exchange server and delete messages, and then use ME, those messages will still be there.

You will need to migrate, or not migrate.......

I understand wanting to keep a working server as backup for Exchange. I've heard many stories of how much maintaince these take...

jay_plesset at 2007-7-6 23:56:42 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...
# 8
Thanks - I understand not wanting to work with Exchange - it has been - well a pain in the #$!%.And my administrator was determine to keep same domain but keep both systems up for at least 3 months - ick.I will keep working with it.Thanks,Erik
ekkong at 2007-7-6 23:56:42 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...
# 9

Hi Erik,

You could use the mailroutingaddress: attribute on each users account. This attribute overrides any mailforwarding/vacation message etc. and sends the email to the address that you specify (in this case <blah>@exchange.vcsu.edu)

The other advantage of this is you can do it user-by-user so if there are any users who for some political issue want to remain on the 'old' system that is easy to accomplish (just don't add the attribute).

Cheers,

Shane.

shane_hjorth at 2007-7-6 23:56:42 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...
# 10
that is a good idea - thanks! I will try it and see.Thanks AGAIN,Erik
ekkong at 2007-7-6 23:56:42 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...