Change message routing

[Rafael Ortega]

Hello, All

Is it possible to change a message routing after it has been enqueued?

I currently have several message to a specific destination that our
CommuniGate server is having trouble reaching. This is a network
problem, but I can reach it from another of my servers in another
network, so I set up a route to work around the issue while the
network people fix the problem.

If I specify the route in the router (like so: N:domain.com =
domain.com@[smart.host.ip.here] ) it will correctly route new
messages, but it won't affect the messages already in the queue, they
will keep trying to reach the troubled destination directly instead of
using the smartroute server.

Is it possible to do this? I'm currently on version 5.2.12.

Regards

#############################################################
This message is sent to you because you are subscribed to
the mailing list <CGat...@mail.stalker.com>.
To unsubscribe, E-mail to: <CGateP...@mail.stalker.com>
To switch to the DIGEST mode, E-mail to <CGatePr...@mail.stalker.com>
To switch to the INDEX mode, E-mail to <CGatePr...@mail.stalker.com>
Send administrative queries to <CGatePro...@mail.stalker.com>

[Technical Support]

Hello,

Rafael Ortega wrote:
> Hello, All
>
> Is it possible to change a message routing after it has been enqueued?
>
> I currently have several message to a specific destination that our
> CommuniGate server is having trouble reaching. This is a network
> problem, but I can reach it from another of my servers in another
> network, so I set up a route to work around the issue while the
> network people fix the problem.
>
> If I specify the route in the router (like so: N:domain.com =
> domain.com@[smart.host.ip.here] ) it will correctly route new
> messages, but it won't affect the messages already in the queue, they
> will keep trying to reach the troubled destination directly instead of
> using the smartroute server.
>
> Is it possible to do this? I'm currently on version 5.2.12.

The simplest way to re-enqueue the messages is to restart the server
(after the necessary router records have been added.)

If you need to re-enqueue the files without restarting the server, then
you need to copy the queue files (on the server side) into some
temporary directory inside the CGpro Base directory. Once the files are
copied you can remove the files from the queue using WebAdmin ->
Monitors -> Mail -> SMTP -> Waiting (suppressing any bounce messages) or
through the CLI (the REJECTQUEUEMESSAGE command with NONDN as the error
text parameter).

After that rename the temporary directory with the saved queue files
into ForeignQueue, and all the files in it will be re-enqueued by the
server.

<http://www.communigate.com/CommuniGatePro/PIPE.html#ForeignQueue>

> Regards
>

--
Best regards,
Dmitry Akindinov

=======================================================================
When answering to letters sent to you by the tech.support staff, make
sure the original message you have received is included into your reply.