Eliot Sabath-Levitt <eslevitt(_at_)mindspring(_dot_)com> writes:
This is technically no longer a "procmail" question, since the answer I
received on my last question pointed me to using "fetchmail"... However,
it is related (since I have the feeling that a procmail command may be the
solution to the sendmail queueing problem I will describe below--a
solution I tried for 2 hours to implement properly but was unable to)...
Actually, I think this is a sendmail question.
...
I have a problem with the mail queueing, because sendmail is set to
automatically queue all messages. Normally this does not affect
locally-addressed messages, but I guess these messages in particular are
not considered "local" because they came from somewhere else. So they sit
in the queue after they are fetched.
Now my ip-up entry is now:
sendmail -q
fetchmail
I think the correct thing for your setup is to have fetchmail deliver
to your local SMTP port (the default I believe), with sendmail running
in daemon mode (-bd) with delivery attempted in the background (should
be the default, but -odb if not), *not* running the queue periodically
(the sendmail -q at ip-up will do that), don't invoke "expensive" mailers
except on queue runs (-oc), and then in the config file, mark the smtp
mailers (all 4 if you're running sendmail V8) as expensive.
In summary:
Invoke sendmail at boot time as
sendmail -bd -odb -oc
Make sure the config file shows the smtp mailers as expensive
(F=....e... in each)
Run the queue right on connection
Have fetchmail deliver to the local smtp port
Make sense?
Philip Guenther