Re: Manually manipulating serialmail queues
On Thu, Jul 19, 2001 at 05:22:17PM +0200, Paulo Jan wrote: [snip] > So, with that in mind, what are the features that you mention above? > :-) (I'm afraid that they will turn out to be "write a shell script to > grep the mails in the queue and touch those who come from $BIG_BOSS", > but oh well...) That's the way to go! /bin/sh is your friend :) Jörgen
Re: Manually manipulating serialmail queues
> > There is a perfectly good list for serialmail. Subscribe by sending a > mail to <[EMAIL PROTECTED]>. > I did just a few hours ago. I received my confirmation request, replied to it... and I'm still waiting. I'll give it a few more hours. BTW, is there any place where the serialmail list is archived? Just so that I can, uh, search it looking for my question before posting... > Serialmail isn't a daemon, something else starts it -- usually a script > that pppd activates. You can solve those problems by adding some > features to whatever starts serialmail. > I know it isn't a daemon. In my customer's case, it's started by a cron job that calls it every 30 minutes using setlock. The complete line is something like: /usr/local/bin/setlock -nx ~alias/outmail/seriallock /usr/local/bin/maildirsmtp ~alias/outmail alias-outmail- [UPSTREAM MAIL SERVER'S IP] `hostname` So, with that in mind, what are the features that you mention above? :-) (I'm afraid that they will turn out to be "write a shell script to grep the mails in the queue and touch those who come from $BIG_BOSS", but oh well...) Paulo Jan. DDnet.
Re: Manually manipulating serialmail queues
On Wed, Jul 18, 2001 at 03:38:15PM +0200, Paulo Jan wrote: > Hi all: > > I have a customer who is using serialmail to upload their mail through > their dial-up connection to our mail server. They have two problems: > > 1) Sometimes the dialup line isn't fast enough, and mail piles up. They > would like to manually move some messages so that serialmail sends them > before others. How could I do this? I guess that "touch"-ing the files > so that they have an earlier date would work, but it would be better if > it was automated (messages from this and that user always get more > priority). Also, there's the problem of what happens if serialmail is > already running while they are doing this; would serialmail "catch" that > change right away? (That is, after sending the current message, it would > scan again the queue, find the message that has been "touch"-ed, and > start with it inmediately). Would it do that, or does serialmail scan > the queue only once (when it starts)? > > 2) Related to the above: sometimes there are messages that don't get > sent; instead, they just sit in the queue while serialmail is happily > processing other mails that arrived after them. I suppose that the cause > might be that serialmail timed out while trying to send them and just > skipped them... but those mails aren't usually *that* big, just regular > 3K, 10K, etc., messages. Is there any other cause for this? How could I > force serialmail to send them? There is a perfectly good list for serialmail. Subscribe by sending a mail to <[EMAIL PROTECTED]>. Serialmail isn't a daemon, something else starts it -- usually a script that pppd activates. You can solve those problems by adding some features to whatever starts serialmail. Jörgen
Manually manipulating serialmail queues
Hi all: I have a customer who is using serialmail to upload their mail through their dial-up connection to our mail server. They have two problems: 1) Sometimes the dialup line isn't fast enough, and mail piles up. They would like to manually move some messages so that serialmail sends them before others. How could I do this? I guess that "touch"-ing the files so that they have an earlier date would work, but it would be better if it was automated (messages from this and that user always get more priority). Also, there's the problem of what happens if serialmail is already running while they are doing this; would serialmail "catch" that change right away? (That is, after sending the current message, it would scan again the queue, find the message that has been "touch"-ed, and start with it inmediately). Would it do that, or does serialmail scan the queue only once (when it starts)? 2) Related to the above: sometimes there are messages that don't get sent; instead, they just sit in the queue while serialmail is happily processing other mails that arrived after them. I suppose that the cause might be that serialmail timed out while trying to send them and just skipped them... but those mails aren't usually *that* big, just regular 3K, 10K, etc., messages. Is there any other cause for this? How could I force serialmail to send them? Paulo Jan. DDnet.
