Thanks for that clarification.
On 30/06/19 10:48 AM, Kurt Hackenberg wrote:
On 2019-06-28 23:24, Frank Watt wrote:
I'm looking at the getmail documentation...
BTW, Is "mbox" the standard abbreviation of Mboxrd or is it something
else?
Mbox is not a single file format; i
On 29/06/19 4:22 PM, Ian Zimmerman wrote:
On 2019-06-29 15:24, Frank Watt wrote:
My question is: how do I know what type of file locking that has been
in use all these years of using fetchmail?
AFAIK the default mode for fetchmail is not to touch the mailbox file
itself at all, but either
I'm looking at the getmail documentation at
http://pyropus.ca/software/getmail/configuration.html#conf-retriever
In the Mboxrd destination description it states in red letters:
You must ensure that all other programs accessing any the mbox file
expect mboxrd-format mbox files and the same type
On 9/06/19 6:36 AM, Kurt Hackenberg wrote:
On 2019-06-07 05:08, Frank Watt wrote:
| However, fetchmail has a -m option, which can probably deliver directly
| to procmail, bypassing the local mail system entirely.
Looks like that's not as simple as I'd hoped.
I'm sort of j
First of all, apologies for munging the thread: Gmail didn't deliver
Cameron's response. I had to get the text from the archives.
Cameron Simpson wrote:
[...]
| Procmail generally relies on being installed in the user's ~/.forward
| file to cause sendmail (the mail system) to deliver email
Thanks, Nathan,
On 5/06/19 10:37 PM, Nathan Stratton Treadway wrote:
On Wed, Jun 05, 2019 at 21:30:51 +1200, Frank Watt wrote:
[...]
Would that really work? It's an attractive idea, avoiding the
complications of compiling new code with ancient functionality and
getting rid of sendm
Christian Brabant wrote:
| On Di, 04 Jun 2019, Frank Watt wrote:
|
[.]
|
| > Were I to install nullmailer, it would remove sendmail, but is
| > that any use with a 9 year old mutt? I find everything I need in
| > it. Would it work to reinstall the old mutt deb after
On 4/06/19 1:24 AM, Dan Ritter wrote:
Frank Watt wrote:
|You seem to be on x86_64 (or amd64 as debian calls it), so unless
|you are building as 32-bit you don't need any of these.
|
|The -dev versions include headers, so you need those to compile, the
|more-basic versions are onl
Ken Moffat wrote:
|Hi Frank,
|
| I assume you probably won't get this mail (gmail dislikes my mails
|from this address), but just in case ...
|
At least it got to the archives.
|[...]
|> p lib32ncurses5 - shared libraries for
|> terminal handling (32-bit)
|>
On 3/06/19 2:00 AM, Kevin J. McCarthy wrote:
[...]
Lastly, the latest mutt releases have started to bump up system
requirements:
* If your gpgme library is too old and you don't use gpgme,
you can just leave '--enable-gpgme' out.
* If your OpenSSL version is too old, you could try '
On 2/06/19 9:07 PM, Jens John wrote:> On Sun, 2 Jun 2019, at 05:36,
Frank Watt wrote:
>> Am I to assume that I would have had sendmail in my environment at the
>> time the deb was installed? So I'd need to remove it so that I can
>> compile mutt with built-in SMT
I've used mutt for nearly 20 years, but since I install it from a deb
package, the latest version I have is 1.5.21 -- almost 9 years old.
I figured out enough of sendmail to use as an MTA, but it recently got
the better pf me. I've been informed that newer versions of mutt have
a built in SMTP
12 matches
Mail list logo
