Jérôme Blion writes:
Sam Varshavchik a écrit :
Jérôme Blion writes:
Sam Varshavchik a écrit :
Jérôme Blion writes:
« HTML content follows »
Gordon Messmer a écrit :
If you need to stop delivery, just use "courier stop" to stop the
courierd process while you do the upgrade.
Delivery is stopped whereas IMAP is working...
But but but... in my case, the queue is not filling... i don't see
anything in mailq output :(
You'll see it when you start courier again. While it's stopped new
messages will be collected, but will be inserted in the queue only
after Courier starts.
Hello, Sam.
I saw that. Do you know how I could "block" the queue in order to
test the patch I was talking about yesterday?
What about different ways that have been written? .mailfilter...
MAXDELS... ? What are your feelings about that?
courier stop is the least disruptive approach.
Hello,
I'm OK with you on that point.
But how to fill my queue in order to test my patch? (the server is not
loaded at all, so mails are sent quickly)
What part of "if you don't want mail delivery to take place, run courier
stop" do you not understand?
"courier stop" **DOES NOT** stop Courier from accepting new mail. New
mail will continue to be received via SMTP, or even via the local sendmail
command. It just won't appear in the output of "mailq" until you run
"courier start". All new mail gets saved in a temporary holding directory.
When you later run "courier start", all mail that has been received, will be
added to the mail queue, and delivered normally.
If you're doing something that affects mail delivery, "courier stop" is
sufficient to suspend mail delivery from taking place, while you do whatever
you need to do. Then, run "courier start", to begin working on the backlog.
My goal is to see something in mailq whereas delivery is stopped.
Any suggestion?
Yes. That something appearing or not appearing in the mail queue is
completely irrelevant.
14 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Dynamic delivery
