Hello All,
I've a system running 5.2p2 - have some test users with status on HOLD channel and mailHost value changed to a new remote host. I am not getting messages sent to the user's on hold status to hold channel and rather being redirected to a remote system - rewrite envelope shows the channel to which it queues is tcp_intranet.
What is wrong here?
Hi,
> I've a system running 5.2p2 - have some test users
> with status on HOLD channel and mailHost value
> changed to a new remote host. I am not getting
> messages sent to the user's on hold status to hold
> channel and rather being redirected to a remote
> system - rewrite envelope shows the channel to which
> it queues is tcp_intranet.
I tried reproducing what you describe with iMS5.2 hf2.15.. but it appears to work fine:
==> modified account with
dn: uid=test,ou=People, o=aus.sun.com, o=sun
changetype: modify
replace: mailuserstatus
mailuserstatus: hold
./imsimta test -rewrite test@aus.sun.com
<snip>
Submitted address list:
hold
test?aus.sun.com@hold-daemon (orig test@aus.sun.com, inter test@aus.sun.com, host hold-daemon) *NOTIFY-FAILURES* *NOTIFY-DELAYS*
=> Sent a test email, email now 'stuck' in hold channel:
bash-2.05# ./imsimta qm sum
Messages
Channel QueuedSize (Kb)Oldest
-- -- -- --
hold10.8323 Mar, 13:37:35
-- -- -- --
Totals10.83
How does this compare to your experience?
Regards,
Shane.
I changed the status to hold and changed the mailhost attribute to a new remote host, when I tried rewriting the envelope - it is going to tcp_intranet channel on 5.2p2 and the same says 4.2.1 cannot reenqueue on JES 6.2 - I am using the same DS for both 5.2p2 and 6.2 instances.
Any idea what is the problem here?
Perhaps even more to the point,
what is it you're trying to do? Migrate a user?
I would do it this way:
1. Change the mailhost. That'll make all new mail go to the new mailhost for you.
2. use imsbackup to pull the old mail from the old host.
3. Use imsrestore to put the old mail on the new host.
done.
> Perhaps even more to the point,
>
> what is it you're trying to do? Migrate a user?
>
> I would do it this way:
>
> 1. Change the mailhost. That'll make all new mail
> go to the new mailhost for you.
I did it along with mailUserStatus=hold till the time I take back up and restore the mail data on the new mailHost and then change back the mailuserstatus=active and then release the mails in the hold channel - this is not happening as all the mails sent to the user on hold after changing the mailhost are not going to hold channel
>
> 2. use imsbackup to pull the old mail from the old
> host.
>
> 3. Use imsrestore to put the old mail on the new
> host.
>
> done.
> Since 6.0 there is no "hold channel". Messages are
> indeed held.
>
> If you do it my way, there is no need to "hold" the
> user in any case.
Again, I have a system running all components except MMP on one system which is iPlanet Messaging Server 5.2p2 ,
I have the LDAP on the same server in schema I which is acting as both configuration and user/group LDAP.
I want to migrate a few users from 5.2p2 to a new 6.2 (schema I)server keeping the same LDAP
I tried following
1. changed the user's status to HOLD in LDAP and changed the mailHost value to a new 6.2 host
2. messages which are coming in on the 5.2 system are not getting queued in HOLD channel rather being routed to a new host , is this right
