Install urlview
Paul M Foster (12024-01-01):
> Of course, it doesn't fix the retarded way Mutt handles links.
To the better of my knowledge, Mutt does not handle links at all. Please
refrain from calling it retarded.
> For those
> familiar
hich had been wrapped.
>
> This is "quoted-printable" encoding. You need to use a properly decoded
> version of the file, rather than the raw text.[1]
>
> > As a solution, I took that email from my mutt mail file and stripped out
> > all the headers and non-HTML content. Then I f
On Mon, 1 Jan 2024, Nicolas George wrote:
> This was not a reply to the original mail. You might consider using a
> MUA with proper threading to better understand what is going on.
from the negative nature of your communications
every one understands what's going on
fxkl4...@protonmail.com (12024-01-01):
> actually the question was
> " what is wrapping the lines on my incoming emails, and how do I fix it "
> please try to keep up
This was not a reply to the original mail. You might consider using a
MUA with proper threading to better understand what is going
On Mon, 1 Jan 2024, Nicolas George wrote:
> gene heskett (12024-01-01):
>> Most browsers to well with such as long as the link is surrounded by
>> the left-right arrows delineate the links contents even if it is wrapped to
>> several lines on your screen.
>
> Please try to keep up with the
gene heskett (12024-01-01):
> Most browsers to well with such as long as the link is surrounded by
> the left-right arrows delineate the links contents even if it is wrapped to
> several lines on your screen.
Please try to keep up with the context of the discussion, we were
talking about links
On 1/1/24 11:52, Nicolas George wrote:
Greg Wooledge (12024-01-01):
It's been my experience that the hyperlinks I'm meant to click are so
long that they wrap around the terminal width multiple times. This
makes copy/pasting them tedious at best, and even then it still
sometimes fails for me.
Greg Wooledge:
> It's been my experience that the hyperlinks I'm meant to click are so
> long that they wrap around the terminal width multiple times. This
> makes copy/pasting them tedious at best, and even then it still
> sometimes fails for me.
My wife has the same problem.
--
John Hasler
Greg Wooledge (12024-01-01):
> It's been my experience that the hyperlinks I'm meant to click are so
> long that they wrap around the terminal width multiple times. This
> makes copy/pasting them tedious at best, and even then it still
> sometimes fails for me.
Surprising. The graphical web
Hello,
On Mon, Jan 01, 2024 at 09:23:03AM -0500, Greg Wooledge wrote:
> Passing the entire text/html part to an actual web browser has been
> what works best for me.
Me too. I'll do the mailcap thing to visually skim the text/html
part with w3m, but there are so many broken HTML messes that I'm
On Mon, Jan 01, 2024 at 11:42:59AM +0100, Nicolas George wrote:
> Greg Wooledge (12023-12-31):
> > Have your browser load THAT file.
>
> Or just have this:
>
> text/html; lynx -force_html -dump %s; copiousoutput
>
> in your .mailcap file. Possibly along with:
>
> auto_view text/html
>
> in
Greg Wooledge (12023-12-31):
> Have your browser load THAT file.
Or just have this:
text/html; lynx -force_html -dump %s; copiousoutput
in your .mailcap file. Possibly along with:
auto_view text/html
in the .muttrc.
Regards,
--
Nicolas George
On 31 Dec 2023 22:51 -0500, from pa...@quillandmouse.com (Paul M Foster):
> As a solution, I took that email from my mutt mail file and stripped out
> all the headers and non-HTML content. Then I fed that to my browser. Sorta
> worked. However, the button I was supposed to click di
> Like everyone else, I get emails with links in them which need to be
> clicked to change passwords, verify identity and such. I was a loyal mutt
> user for years, but problems with URLs caused me to eventually change to
> claws-mail. Recently, I tweaked my mutt config, and URLs se
rly decoded
version of the file, rather than the raw text.[1]
> As a solution, I took that email from my mutt mail file and stripped out
> all the headers and non-HTML content. Then I fed that to my browser.
If you received a correctly formatted email, it should contain one or more
parts, ea
Folks:
Like everyone else, I get emails with links in them which need to be
clicked to change passwords, verify identity and such. I was a loyal mutt
user for years, but problems with URLs caused me to eventually change to
claws-mail. Recently, I tweaked my mutt config, and URLs seemed to work
On Tue, Dec 12, 2023 at 06:04:04AM +0800, jeremy ardley wrote:
[...]
> If you look at the NTFS file system [...]
> Underneath the hood of a NTFS file is alternate data streams (ADS). That is
> a single file can contain main different 'sub files' of completely different
> content type. Each ADS
On 12/12/23 01:49, Jeremy Nicoll wrote:
There's no concept of filetype in file systems used for the MVS side
of z/OS systems. (These days there's also Unix/Linux environments
& of course they do have more familiar file naming structures.)
If you look at the NTFS file system - supported by
debian-u...@howorth.org.uk wrote:
> songbird wrote:
>> wrote:
>> > On Sun, Dec 10, 2023 at 01:28:20PM -0500, songbird wrote:
>> >> wrote:
>>
>> there is rarely a need to e-mail me directly.
>>
>> >> ...
>> >> > That's why I cringe when people name executables "foo.sh". What
>> >> > do
On Mon, 11 Dec 2023, at 13:16, Greg Wooledge wrote:
> 4) File extensions are used by programs on every operating system.
Certainly on many OSes, but not all.
They're not present on native RISC OS systems (as in ex-Acorn micros).
Filetype data IS stored, but it is in files' metadata.
There's
there is
> > > > > > > an image to
> > > > > > > view, viewing it in neomutt calls up one of the ImageMagick
> > > > > > > programs. I've set
> > > > > > > the mailcap_path variable in my neomutt config to point to
> >
On Mon, Dec 11, 2023 at 10:10:31AM -0500, Stefan Monnier wrote:
[...]
> I think what you're saying is that it would make sense to use
> a dedicated extension for executables, like, say, `.exe`,
> since "all users rely on it being" executable.
I'd prefer ".com", but hey ;-)
> FWIW, I agree, but
On Mon 11 Dec 2023 at 10:07:28 (+1100), Zenaan Harkness wrote:
> > Second, how do I fix this so that mutt uses feh to display images?
>
> Here is my mailcap entry, which works for me - had to deal with
> annoying filename munging by mutt, and getting the "close the v
songbird wrote:
> wrote:
> > On Sun, Dec 10, 2023 at 01:28:20PM -0500, songbird wrote:
> >> wrote:
>
> there is rarely a need to e-mail me directly.
>
> >> ...
> >> > That's why I cringe when people name executables "foo.sh". What
> >> > do you do when you decide to rewrite the thing
On 2023-12-11 09:34:09 -0500, Pocket wrote:
> On 12/11/23 09:04, Vincent Lefevre wrote:
> > On 2023-12-11 08:16:30 -0500, Greg Wooledge wrote:
> > > 2) When *receiving* email, mutt will use the sender's MIME type label
> > > to decide how to deal with the att
> (Note that I'd even make a difference: where the implementation matters,
> e.g. some shell code to be sourced in, I'd be more lenient in calling
> the thing ".sh": after all, its users rely on it being shell code. When
> you can change the implementation without changing the function, e.g.
> a
/mutt/mailcap-mutt, which is
a specially crafted subset of /etc/mailcap with a few additions
(like converting webp to a jpeg rather than opening in gimp,
and playing midi files the way I want).
and
set an entry in there for image/jpg to point to /usr/bin/feh. I've even set
On Mon, Dec 11, 2023 at 08:52:37AM -0600, David Wright wrote:
> On Sun 10 Dec 2023 at 15:51:02 (-0500), Pocket wrote:
[...]
> > File names in Linux are a character string of 255 chars. Again there are
> > not file extensions in a Linux file name.
> >
> > People are conflating the issue.
> >
;> I've set
> >>>> the mailcap_path variable in my neomutt config to point to ~/.mailcap,
> >
> > Similarly, I point it to ~/.config/mutt/mailcap-mutt, which is
> > a specially crafted subset of /etc/mailcap with a few additions
> > (like converting webp
On 12/11/23 09:34, Vincent Lefevre wrote:
On 2023-12-11 15:16:57 +0100, to...@tuxteam.de wrote:
On Mon, Dec 11, 2023 at 02:58:01PM +0100, Vincent Lefevre wrote:
I do not care about the "microsoft world", and I doubt that this is
required there at the low level (what would be the equivalent
On Mon, Dec 11, 2023 at 03:34:28PM +0100, Vincent Lefevre wrote:
> On 2023-12-11 15:16:57 +0100, to...@tuxteam.de wrote:
> > On Mon, Dec 11, 2023 at 02:58:01PM +0100, Vincent Lefevre wrote:
> > > I do not care about the "microsoft world", and I doubt that this is
> > > required there at the low
On 2023-12-11 15:16:57 +0100, to...@tuxteam.de wrote:
> On Mon, Dec 11, 2023 at 02:58:01PM +0100, Vincent Lefevre wrote:
> > I do not care about the "microsoft world", and I doubt that this is
> > required there at the low level (what would be the equivalent of the
> > Linux kernel) [...]
>
>
On 12/11/23 09:04, Vincent Lefevre wrote:
On 2023-12-11 08:16:30 -0500, Greg Wooledge wrote:
2) When *receiving* email, mutt will use the sender's MIME type label
to decide how to deal with the attachment.
But the notion of filename extension is even used in this context too.
Quoting
On Mon, Dec 11, 2023 at 02:58:01PM +0100, Vincent Lefevre wrote:
[...]
> I do not care about the "microsoft world", and I doubt that this is
> required there at the low level (what would be the equivalent of the
> Linux kernel) [...]
This depends: the FAT file system (which still is the lowest
On 2023-12-11 08:16:30 -0500, Greg Wooledge wrote:
> 2) When *receiving* email, mutt will use the sender's MIME type label
>to decide how to deal with the attachment.
But the notion of filename extension is even used in this context too.
Quoting the Mutt
On 2023-12-11 07:32:30 -0500, Pocket wrote:
>
> On 12/11/23 07:12, Vincent Lefevre wrote:
> > On 2023-12-10 15:51:02 -0500, Pocket wrote:
> > > On Dec 10, 2023, at 3:05 PM, David Wright
> > > wrote:
> > > > ¹ Re the argument raging in this thread about "extension", the
> > > > term is clearly
> no goal with this thread.
>
>
> I would ask you to continue this discussion elsewhere.
It's on topic, so there's no call to ask for the discussion to be
discontinued here.
The facts are pretty simple:
1) When *sending* email, mutt uses the file's extension to decide which
MI
David writes:
> Hi, the filename extension is usually irrelevant on Linux, because
> Linux tools typically
> use the standard 'file' command to inspect the content of the
> fileinstead of relying on
> the filename to indicate content.
It is very often not irrelevant for files that you might
On Monday, 11 Dec 2023 at 07:32, Pocket wrote:
> No it is microsoft non sense
I'm not an MS fanboi but please stop blaming MS for something they did
not invent!
--
Eric S Fraga via gnus (Emacs 30.0.50 2023-09-14) on Debian 12.2
All,
I do not see the relevance of the discussion about file name extensions,
types, suffixes for Debian. Even more so as you are at the stage of
repeating statements without bringing new value. In fact, there seems to
be no goal with this thread.
I would ask you to continue this
On 12/11/23 07:12, Vincent Lefevre wrote:
On 2023-12-10 15:51:02 -0500, Pocket wrote:
On Dec 10, 2023, at 3:05 PM, David Wright wrote:
¹ Re the argument raging in this thread about "extension", the
term is clearly appropriate, as a glance at /etc/mime.types
demonstrates. The literature
On 12/11/23 06:39, Vincent Lefevre wrote:
On 2023-12-08 17:06:15 -0500, Pocket wrote:
On 12/8/23 16:53, David wrote:
Hi, the filename extension is usually irrelevant on Linux, because
Linux tools typically
use the standard 'file' command to inspect the content of the
fileinstead of relying
On 2023-12-10 15:51:02 -0500, Pocket wrote:
> On Dec 10, 2023, at 3:05 PM, David Wright wrote:
> > ¹ Re the argument raging in this thread about "extension", the
> > term is clearly appropriate, as a glance at /etc/mime.types
> > demonstrates. The literature is full of the term.
> >
> > I
On 2023-12-08 17:06:15 -0500, Pocket wrote:
> On 12/8/23 16:53, David wrote:
> > Hi, the filename extension is usually irrelevant on Linux, because
> > Linux tools typically
> > use the standard 'file' command to inspect the content of the
> > fileinstead of relying on
> > the filename to indicate
wrote:
> On Sun, Dec 10, 2023 at 01:28:20PM -0500, songbird wrote:
>> wrote:
there is rarely a need to e-mail me directly.
>> ...
>> > That's why I cringe when people name executables "foo.sh". What do you
>> > do when you decide to rewrite the thing in C (or Rust, or whatever)?
>> >
>> > Do
> Finally, occasionally I need to cleanly dump html, this one seems a bit
> simpler:
>
> text/html; lynx -stdin -dump -width=$COLS; copiousoutput; compose=vim %s
I meant "cleanly _view_ html ..."
> Second, how do I fix this so that mutt uses feh to display images?
Here is my mailcap entry, which works for me - had to deal with
annoying filename munging by mutt, and getting the "close the viewer"
bit working - this is quite a few years ago and now I can't even
remember why th
e:
>>>>
>>>> I'm on Debian bookworm, using neomutt for email. Where there is an image to
>>>> view, viewing it in neomutt calls up one of the ImageMagick programs. I've
>>>> set
>>>> the mailcap_path variable in my neomutt config t
On Sun 10 Dec 2023 at 19:48:29 (+0100), to...@tuxteam.de wrote:
> On Sun, Dec 10, 2023 at 01:28:20PM -0500, songbird wrote:
> > wrote:
> > ...
> > > That's why I cringe when people name executables "foo.sh". What do you
> > > do when you decide to rewrite the thing in C (or Rust, or whatever)?
>
image
> > > to
> > > view, viewing it in neomutt calls up one of the ImageMagick programs.
> > > I've set
> > > the mailcap_path variable in my neomutt config to point to ~/.mailcap,
Similarly, I point it to ~/.config/mutt/mailcap-mutt, which is
a spec
On Sun, Dec 10, 2023 at 01:28:20PM -0500, songbird wrote:
> wrote:
> ...
> > That's why I cringe when people name executables "foo.sh". What do you
> > do when you decide to rewrite the thing in C (or Rust, or whatever)?
> >
> > Do you go over all calling sites and change the caller's code?
>
>
wrote:
...
> That's why I cringe when people name executables "foo.sh". What do you
> do when you decide to rewrite the thing in C (or Rust, or whatever)?
>
> Do you go over all calling sites and change the caller's code?
no, i would just consider it a transition or a change
in versions. :)
On Sun, Dec 10, 2023 at 04:15:22PM -, Curt wrote:
> On 2023-12-09, Eric S Fraga wrote:
> > On Friday, 8 Dec 2023 at 17:06, Pocket wrote:
> >> In Unix and Linux there isn't a file extension, that is a microsoft
> >> invention.
> >
> > Predates MS by years. Systems like RSTS/E on PDP-11s,
On 2023-12-09, Eric S Fraga wrote:
> On Friday, 8 Dec 2023 at 17:06, Pocket wrote:
>> In Unix and Linux there isn't a file extension, that is a microsoft
>> invention.
>
> Predates MS by years. Systems like RSTS/E on PDP-11s, just to name one.
They certainly are convenient.
I must be stupid
On Friday, 8 Dec 2023 at 17:06, Pocket wrote:
> In Unix and Linux there isn't a file extension, that is a microsoft
> invention.
Predates MS by years. Systems like RSTS/E on PDP-11s, just to name one.
--
Eric S Fraga via gnus (Emacs 30.0.50 2023-09-14) on Debian 12.2
On 12/8/23 17:55, Greg Wooledge wrote:
On Fri, Dec 08, 2023 at 04:50:04PM -0600, John Hasler wrote:
Greg writes:
cc(1) and make(1) would like to have a talk with you.
Those are applications and can do whatever they want. The OS does not
care about extensions.
What do you consider "the OS"
On 12/8/23 18:17, Greg Wooledge wrote:
On Fri, Dec 08, 2023 at 05:59:58PM -0500, Pocket wrote:
On 12/8/23 17:54, Greg Wooledge wrote:
cc(1) looks at the file extension to decide what kind of content each
named argument file is expected to contain.
No it looks for a suffix
So Debian files
On Fri, Dec 08, 2023 at 05:59:58PM -0500, Pocket wrote:
> On 12/8/23 17:54, Greg Wooledge wrote:
> > cc(1) looks at the file extension to decide what kind of content each
> > named argument file is expected to contain.
> No it looks for a suffix
So Debian files have "suffixes" and Windows files
On 2023-12-08 22:55, Greg Wooledge wrote:
On Fri, Dec 08, 2023 at 04:50:04PM -0600, John Hasler wrote:
Greg writes:
> cc(1) and make(1) would like to have a talk with you.
Those are applications and can do whatever they want. The OS does not
care about extensions.
What do you consider "the
Content-type header to generate for a given static file based on its
extension. I would imagine other web servers do the same thing.
Apache is an application that looks for a file suffix
And hey, I'm using mutt to compose and send this email. If I were to
attach a file to this message, mu
On Fri, Dec 08, 2023 at 04:50:04PM -0600, John Hasler wrote:
> Greg writes:
> > cc(1) and make(1) would like to have a talk with you.
>
> Those are applications and can do whatever they want. The OS does not
> care about extensions.
What do you consider "the OS" to be, then?
ch decides what
Content-type header to generate for a given static file based on its
extension. I would imagine other web servers do the same thing.
And hey, I'm using mutt to compose and send this email. If I were to
attach a file to this message, mutt would look at its extension to
decide what M
On 12/8/23 17:41, Pocket wrote:
On 12/8/23 17:31, Greg Wooledge wrote:
On Fri, Dec 08, 2023 at 05:06:15PM -0500, Pocket wrote:
In Unix and Linux there isn't a file extension, that is a microsoft
invention.
cc(1) and make(1) would like to have a talk with you.
Linux/Unix filenaming specs
Greg writes:
> cc(1) and make(1) would like to have a talk with you.
Those are applications and can do whatever they want. The OS does not
care about extensions.
--
John Hasler
j...@sugarbit.com
Elmwood, WI USA
On 12/8/23 17:31, Greg Wooledge wrote:
On Fri, Dec 08, 2023 at 05:06:15PM -0500, Pocket wrote:
In Unix and Linux there isn't a file extension, that is a microsoft
invention.
cc(1) and make(1) would like to have a talk with you.
Linux/Unix filenaming specs would like to inform you.
file
On Fri, Dec 08, 2023 at 05:06:15PM -0500, Pocket wrote:
> In Unix and Linux there isn't a file extension, that is a microsoft
> invention.
cc(1) and make(1) would like to have a talk with you.
lternative to feh with update-alternatives. Still, mutt is
calling an imagemagick program to display jpgs.
First, if alternatives doesn't point to the imagemagick program, and the
mailcap file doesn't point to it, and there's nothing in the neomutt config
pointing to the imagemagick program, then wher
n
> > > set
> > ↑↑↑ try jpeg
> >
> > > the "display" alternative to feh with update-alternatives. Still, mutt is
> > > calling an imagemagick program to display jpgs.
> > >
> > > First, if alternatives doesn't
ograms. I've
> > set
> > the mailcap_path variable in my neomutt config to point to ~/.mailcap, and
> > set an entry in there for image/jpg to point to /usr/bin/feh. I've even set
> ↑↑↑ try jpeg
>
> > the "display&q
o ~/.mailcap, and
> set an entry in there for image/jpg to point to /usr/bin/feh. I've even set
↑↑↑ try jpeg
> the "display" alternative to feh with update-alternatives. Still, mutt is
> calling an imagemagick program to display jpgs.
>
>
. I've even set
the "display" alternative to feh with update-alternatives. Still, mutt is
calling an imagemagick program to display jpgs.
First, if alternatives doesn't point to the imagemagick program, and the
mailcap file doesn't point to it, and there's nothing in the neomutt confi
gt; > autentificación avanzados (OAuth2).
> >
> > parece que desde mayo del 2022 no funciona.
> >
>
> Yo actualmente conecto a gmail dede Mutt usando OAuth, y me funciona
> sin problemas.
>
> http://www.mutt.org/doc/manual/#oauth
>
bueno pude resolverl configurando una clave para aplicacion
no funciona.
>
Yo actualmente conecto a gmail dede Mutt usando OAuth, y me funciona
sin problemas.
http://www.mutt.org/doc/manual/#oauth
El 28/9/23 a las 20:20, Camaleón escribió:
> Desde hace ¿años¹? Gmail ya no permite usar la contraseña que usas
> cuando accedes desde el webmail o aplicaciones que admitan sistemas de
> autentificación avanzados (OAuth2).
parece que desde mayo del 2022 no funciona.
>
> Para usar una
gt; > El 28/9/23 a las 5:18, Guido Ignacio escribió:
> > > Antes recuerdo era configurar imap y smtp en .muttrc y salia andando.
> >
> > Hola:
> > Hace tiempo que no consulto ninguna cuenta de gmail con mutt y la
> > configuración que tenía en .muttrc ya no me sirv
ninguna cuenta de gmail con mutt y la
> configuración que tenía en .muttrc ya no me sirve:
>
> set imap_user = "USUARIO"; set imap_pass = "CLAVE"; set folder =
> "imaps://imap.gmail.com:993";set smtp_url =
> "smtp://USUARIO:CLAVE?@smtp.gmai
urar imap y smtp en .muttrc y salia andando.
>
> Hola:
> Hace tiempo que no consulto ninguna cuenta de gmail con mutt y la
> configuración que tenía en .muttrc ya no me sirve:
>
> set imap_user = "USUARIO"; set imap_pass = "CLAVE"; set folder =
> "ima
El 28/9/23 a las 5:18, Guido Ignacio escribió:
> Antes recuerdo era configurar imap y smtp en .muttrc y salia andando.
Hola:
Hace tiempo que no consulto ninguna cuenta de gmail con mutt y la
configuración que tenía en .muttrc ya no me sirve:
set imap_user = "USUARIO"; set imap_
Hola! les consulto, alguien está usando totalmente funcional mutt con gmail?
He querido volver a usar mutt pero no doy con la configuración
correcta de todas las que encuentro por ahi.
Antes recuerdo era configurar imap y smtp en .muttrc y salia andando.
Si alguien me da una mano,genial
ho
permet.
Per exemple, si el meu correu està a Gandi i m'hi connecto amb
Mutt normalment via SMTP, podria configurar el meu MTA local per
enviar el correu sortint via Gandi utilitzant les mateixes
credencials d'usuari. Jo no tinc configurat el meu MTA local així
perquè no tinc processos que env
Hola, Eloi:
> Ho dic perquè hi ha una opció més potent fent servir sieve
Jo només he vist Sieve en servidors IMAP (cyrus, dovecot, etc.) i
no sabia que també es podia utilitzar en local (gràcies!).
Altres eines per a filtrar que he conec són procmail i mailfilter.
Salut,
Alex
--
⢀⣴⠾⠻⢶⣦⠀
2023-07- 8, 07:20 (+0200); Xavier Drudis Ferran escriu:
> El Fri, Jul 07, 2023 at 01:39:30PM +, Ernest Adrogué deia:
> > 2023-07- 7, 09:59 (+0200); Narcis Garcia escriu:
> > > Em sembla que l'Alex es referia a aquest recorregut per a «smarthost»:
> > > MUA (Mutt)
El Fri, Jul 07, 2023 at 01:39:30PM +, Ernest Adrogué deia:
> 2023-07- 7, 09:59 (+0200); Narcis Garcia escriu:
> > Em sembla que l'Alex es referia a aquest recorregut per a «smarthost»:
> > MUA (Mutt) -> MTA local -> MTA públic
> >
> > Amb això, el servido
2023-07- 7, 09:59 (+0200); Narcis Garcia escriu:
> Em sembla que l'Alex es referia a aquest recorregut per a «smarthost»:
> MUA (Mutt) -> MTA local -> MTA públic
>
> Amb això, el servidor públic de correu-e és el què ha d'acreditar-se a
> Internet com a fiable per als fil
usuaris volen enviar correu a internet que utilitzin un client
de correu (com el mutt) que permeti enviar correu a través d'un
servidor de correu remot (com Gmail).
M'havia quedant pendent de respondre aquest tema: això depèn de
les necessitats particulars. En concret, és molt habitual tenir
un MTA
t; usuaris volen enviar correu a internet que utilitzin un client
> > de correu (com el mutt) que permeti enviar correu a través d'un
> > servidor de correu remot (com Gmail).
>
> M'havia quedant pendent de respondre aquest tema: això depèn de
> les necessitats particulars. En concret
El 16/6/23 a les 21:26, Jordi ha escrit:
[...]
2023-06-15, 10:29 (+0200); Jordi escriu:
Ja fa un temps vaig voler configurar postfix i alguna altra cosa
i no
me'n vaig sortir, el que tinc ara son aplicacions que envien
notificacions o redirigeixo la sortida a mail o a mutt segons si
vull
Hola, Ernest:
> No és recomanable utilitzar postfix per enviar correu a
> internet. El més pràctic és utilitzar el postfix (o un altre
> MTA) per enviar correu localment al mateix ordinador, i si els
> usuaris volen enviar correu a internet que utilitzin un client
> de correu (c
di escriu:
> > > Ja fa un temps vaig voler configurar postfix i alguna altra cosa
> > > i no
> > > me'n vaig sortir, el que tinc ara son aplicacions que envien
> > > notificacions o redirigeixo la sortida a mail o a mutt segons si
> > > vull
> > &g
El 15/6/23 a les 18:05, Ernest Adrogué ha escrit:
2023-06-15, 10:29 (+0200); Jordi escriu:
Ja fa un temps vaig voler configurar postfix i alguna altra cosa i no
me'n vaig sortir, el que tinc ara son aplicacions que envien
notificacions o redirigeixo la sortida a mail o a mutt segons si vull
2023-06-15, 10:29 (+0200); Jordi escriu:
> Ja fa un temps vaig voler configurar postfix i alguna altra cosa i no
> me'n vaig sortir, el que tinc ara son aplicacions que envien
> notificacions o redirigeixo la sortida a mail o a mutt segons si vull
> local o remotament.
Vols dir que
El dc. 14 de 06 de 2023 a les 16:32 +, en/na Ernest Adrogué va
escriure:
> 2023-06-14, 11:02 (+0200); Jordi escriu:
> > Bon dia, ja sé que em donareu altres opcions però voldria redirigir
> > determinats correus locals a mutt de forma automàtica.
> >
> > És a dir
2023-06-14, 11:02 (+0200); Jordi escriu:
> Bon dia, ja sé que em donareu altres opcions però voldria redirigir
> determinats correus locals a mutt de forma automàtica.
>
> És a dir correu llegit amb mail que compleixi determinades condicions,
> redirigir-lo a mutt. Em podeu ori
Hola,
On Wed, Jun 14, 2023 at 11:49:18AM +0200, Xavier Drudis Ferran wrote:
> El Wed, Jun 14, 2023 at 11:02:36AM +0200, Jordi deia:
> > Bon dia, ja sé que em donareu altres opcions però voldria redirigir
> > determinats correus locals a mutt de forma automàtica.
> >
>
El Wed, Jun 14, 2023 at 11:02:36AM +0200, Jordi deia:
> Bon dia, ja sé que em donareu altres opcions però voldria redirigir
> determinats correus locals a mutt de forma automàtica.
>
> És a dir correu llegit amb mail que compleixi determinades condicions,
> redirigir-lo a mutt. Em
Bon dia, ja sé que em donareu altres opcions però voldria redirigir
determinats correus locals a mutt de forma automàtica.
És a dir correu llegit amb mail que compleixi determinades condicions,
redirigir-lo a mutt. Em podeu orientar ??
Salutaciosn
Jordi.
On 22/05/22 at 03:30, Marcelo Laia wrote:
> On 21/05/22 at 04:09, Marcelo Laia wrote:
> > Nowadays, email recipients had give me feedback that attached files that
> > I sent was corrupted. I use Mutt + msmtp + offlineimap and OAuth GMail
> > app implementation.
>
>
On 21/05/22 at 04:09, Marcelo Laia wrote:
> Nowadays, email recipients had give me feedback that attached files that
> I sent was corrupted. I use Mutt + msmtp + offlineimap and OAuth GMail
> app implementation.
After more tests, I found that if I use the mutt native smtp, attach is
On Sun 22 May 2022 at 09:15:22 (-0300), Marcelo Laia wrote:
> On 21/05/22 at 04:09, Marcelo Laia wrote:
> > Nowadays, email recipients had give me feedback that attached files that
> > I sent was corrupted. I use Mutt + msmtp + offlineimap and OAuth GMail
> > app implementa
1 - 100 of 8769 matches
Mail list logo
