Mercury32 - how can I send / recv separately? - Thread - go-pugleaf

Thread View: comp.mail.pegasus-mail.ms-windows

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Alfredo Mon, 26 Mar 2007 01:42

Mercury32 - how can I send / recv separately?

#16

Author: Alfredo
Date: Mon, 26 Mar 2007 01:42

19 lines
2218 bytes

Can I shut down the the "receive" or the "send" part independently of
each other?

I would like to intercept incoming emails from the receive queue fodler,
do some grep on them, and then place them in the sender's queue without
the sender grabbing them up first.  I hope I can do this because (in my
ideal world) the two queues use two separate directories.

Yes, I have heard that you can write plug-ins for M32, but I already
have a big complicated program that does the text replacements.

Second request, I also want to clear a queue before I start receiving on
that server, so I do want to shut them down independently, to put it in
"send only" mode until the queue clears, if I can. I know I could block
the port but that would cause me other problems.

So - two separate daemons?  Two separate queue directories?

Thanks in advance!

Re: Mercury32 - how can I send / recv separately?

#17

Author: Rob
Date: Mon, 26 Mar 2007 17:28

48 lines
3288 bytes

alfredo@KILL_SPAM_megapath.net (Alfredo) wrote in news:4607215f.167880734
@news.megapath.net:

> Can I shut down the the "receive" or the "send" part independently of
> each other?

If all you want to do is stop the reception or sending of messages, just 
Pause the respective module through the Mercury/32 interface. Check the 
Pause box on the module's console window.

> I would like to intercept incoming emails from the receive queue 
fodler,
> do some grep on them, and then place them in the sender's queue without
> the sender grabbing them up first.  I hope I can do this because (in my
> ideal world) the two queues use two separate directories.

The queues use a common directory.

> Yes, I have heard that you can write plug-ins for M32, but I already
> have a big complicated program that does the text replacements.

Try and work it out as a policy. Have Mercury/32 trigger the program 
using the policy interface. Or try and wrap your program inside a daemon. 
I have no personal experience programming a daemon, but you should be 
able to program one that just acts as an interface between Mercury/32 and 
your program.

> Second request, I also want to clear a queue before I start receiving 
on
> that server, so I do want to shut them down independently, to put it in
> "send only" mode until the queue clears, if I can. I know I could block
> the port but that would cause me other problems.

If you want to stop receiving messages, then Pause MercuryS. This will 
cause it to issue a temporary failure to all incoming connections:

421 Service temporarily unavailable - please try again later.

> So - two separate daemons?  Two separate queue directories?
> 
> Thanks in advance!

-- 
Rob Croson (robert@arcm.com)
Member of the Pegasus Mail and Mercury/32 Beta Test Teams
Pegasus Mail and Mercury/32 Portal: http://email.arcm.com
Visit the MailWiki: http://email.arcm.com/wiki
Support Pegasus Mail: http://www.cafeshops.com/pegasusmail

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads