use of .forward file
hi: I place a .forward file in my home dir , according to man pages, I write an mail address in this file. So ,when I receive a mail ,it will be sent to that address， Did I understand wrong? thanks!
Re: .procmailrc configurations
On Wed, Jan 23, 2013 at 12:29:47PM -0500, Patrick Shanahan wrote: for mdir = MAILDIR=$HOME/mail ## your mail dir below /home/user :0: * ^TO_mutt/-users/@mutt/.org $MAILDIR/mutt-users = for maildir, note trailing / in the assigned location = MAILDIR=$HOME/mail ## your mail dir below /home/user :0: * ^TO_mutt/-users/@mutt/.org $MAILDIR/mutt-users/ AFAIR, maildir doesn't need locking whereas mbox does, so compare: :0: to :0 i.e. no trailing semicolon. -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X
Re: .procmailrc configurations
On Sat, Jan 26, 2013 at 02:18:37AM +1300, Chris Bannister wrote: On Wed, Jan 23, 2013 at 12:29:47PM -0500, Patrick Shanahan wrote: for mdir = MAILDIR=$HOME/mail ## your mail dir below /home/user :0: * ^TO_mutt/-users/@mutt/.org $MAILDIR/mutt-users = for maildir, note trailing / in the assigned location = MAILDIR=$HOME/mail ## your mail dir below /home/user :0: * ^TO_mutt/-users/@mutt/.org $MAILDIR/mutt-users/ AFAIR, maildir doesn't need locking whereas mbox does, so compare: :0: to :0 i.e. no trailing semicolon. Thanks! To make procmail wok fine . is a .forward file in my home dir a must ? -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X
Re: use of .forward file
* horseriver horseriv...@gmail.com [01-25-13 08:04]: I place a .forward file in my home dir , according to man pages, I write an mail address in this file. So ,when I receive a mail ,it will be sent to that address， Did I understand wrong? Have you *ever* considered reading the man pages concerning commands you are using? from man procmail: If procmail is not installed globally as the default mail delivery agent (ask your system administrator), you have to make sure it is invoked when your mail arrives. In this case your $HOME/.forward (beware, it has to be world readable) file should contain the line below. Be sure to include the single and double quotes, and unless you know your site to be running smrsh (the SendMail Restricted SHell), it must be an absolute path. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535@ http://linuxcounter.net
Re: .procmailrc configurations
* horseriver horseriv...@gmail.com [01-25-13 08:50]: On Sat, Jan 26, 2013 at 02:18:37AM +1300, Chris Bannister wrote: [...] AFAIR, maildir doesn't need locking whereas mbox does, so compare: :0: to :0 i.e. no trailing semicolon. Thanks! To make procmail wok fine . is a .forward file in my home dir a must ? man procmail -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535@ http://linuxcounter.net
Re: use of .forward file
* On 24 Jan 2013, horseriver wrote: hi: I place a .forward file in my home dir , according to man pages, I write an mail address in this file. So ,when I receive a mail ,it will be sent to that address， Did I understand wrong? In short: what you describe is reasonable to expect, but there are reasons why it might not happen. Are you having a problem? This is usually true in a unix system, but it depends on how the mail transport and delivery is set up, and that's largely a function of what OS you're using. On many Linux systems procmail is the local delivery agent (LDA), and procmail will use the .forward file as you described provided that permissions on your home directory and the .forward file itself are acceptable. On non-Linux systems, another program besides procmail usually does delivery unless the admin has changed it; but most LDAs honor the .forward file. Note that this is not related to mutt per se, so this may not be the best group to help. However we can perhaps point you in the right direction. -- David Champion • d...@bikeshed.us
Re: use of .forward file
On Fri, Jan 25, 2013 at 08:54:41AM -0500, Patrick Shanahan wrote: * horseriver horseriv...@gmail.com [01-25-13 08:04]: I place a .forward file in my home dir , according to man pages, I write an mail address in this file. So ,when I receive a mail ,it will be sent to that address， Did I understand wrong? Have you *ever* considered reading the man pages concerning commands you are using? from man procmail: If procmail is not installed globally as the default mail delivery agent (ask your system administrator), you have to make sure it is invoked when your mail arrives. In this case your $HOME/.forward (beware, it has to be world readable) file should contain the line below. Be sure to include the single and double quotes, and unless you know your site to be running smrsh (the SendMail Restricted SHell), it must be an absolute path. Thanks! I have already read this man page ,and I am reaching on these points all. My system now has one mail delivery agent named exim4. But I do not know is it the default mail delivery agent ? Can you tell me how to know the default mail delivery agent on my system? -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535@ http://linuxcounter.net
Config Files, and Remaining Confusion with html-mail
Assembled Wisdom! First, generically: I feel it is a source of difficulty that mutt relies on two config files, .muttrc and .mailcap. Perhaps one of the experts could give us a short exposition of the use of each of these files, and what to do when they conflict. That would help me get my second, personal, issue resolved. Second(personal issue): I'm still having problems with getting my html-mail to open(in a new tab) in my browser, which is Firefox(Debianers call it iceweasel). Often, when I use 'v' on an entry in my mutt display, and then Arrow down to 3 . . . . [text/html . . . ., and then press Enter, a new Tab does open in my browser, and I see the html-mail displayed nicely. Even then I get, in my browser-Tab: file:///home/alan/tmp/mutt.html, but there is no such file in my ~/tmp directory! But, too often, I get a quick new tab, a tenth of a second look at the html I want to see, and then mutt thinks better of it and I get a screen: File not found Iceweasel can't find the file at /home/alan/tmp/mutt.html The decision which way mutt will go between these two alternatives is, as far as I can see, quite arbitrary. For the record: I have the following entry in my .muttrc set tmpdir=~/tmp# where to store temp files This works fine when I'm writing my mail. For instance there is now a file in ~/tmp containing this text that I'm now working on. I also have an entry # set mailcap_path=/etc/mailcap:/usr/local/share/mailcap I uncommented this, but quickly put the comment back on! I have a huge /etc/mailcap, which I can't make head or tails of. Bottom line: there is some kind of a fight inside mutt about opening a tab in my browser; how can I reconcile this conflict. What I'd like of course is: when I hit 'v' I'd like that E-mail to be opened in a tab in my iceweasel/Firefox as best as possible. TIA for anticipated help! Alan -- Alan McConnell : http://globaltap.com/~alan/ No one minds what Jeffreys says . . it is not more than a week ago that I heard him speak disrespectfully of the Equator.(Sydney Smith)
Re: Config Files, and Remaining Confusion with html-mail
On Fri, Jan 25, 2013 at 09:28:05AM -0500, Alan McConnell wrote: First, generically: I feel it is a source of difficulty that mutt relies on two config files, .muttrc and .mailcap. Perhaps one of the experts could give us a short exposition of the use of each of these files, and what to do when they conflict. That would help me get my second, personal, issue resolved. .muttrc is Mutt's configuration. It is specific to Mutt. .mailcap is a general-purpose configuration file for anything that wants to know what you would like done with certain types of content. Lots of other tools also use .mailcap and /etc/mailcap. This is why they are separate. One belongs to Mutt and the other belongs to the world (including Mutt, which can use it). Second(personal issue): I'm still having problems with getting my html-mail to open(in a new tab) in my browser, which is Firefox(Debianers call it iceweasel). Often, when I use 'v' on an entry in my mutt display, and then Arrow down to 3 . . . . [text/html . . . ., and then press Enter, a new Tab does open in my browser, and I see the html-mail displayed nicely. Even then I get, in my browser-Tab: file:///home/alan/tmp/mutt.html, but there is no such file in my ~/tmp directory! But, too often, I get a quick new tab, a tenth of a second look at the html I want to see, and then mutt thinks better of it and I get a screen: File not found Iceweasel can't find the file at /home/alan/tmp/mutt.html The decision which way mutt will go between these two alternatives is, as far as I can see, quite arbitrary. You probably need to add ; needsterminal to your .mailcap entry for text/html so that Mutt will ask you to hit a key when the external program (Iceweasel) is finished. For more on .mailcap and how Mutt interprets it, see: http://www.mutt.org/doc/manual/manual-5.html especially the section Optional Fields. Background: This sounds like what is usually called a race condition. Two processes are trying to use the same resource without sufficient coordination. Some times one process completes first, other times the other completes first. This causes differing behavior at different times. Here, I expect that Mutt is writing out that temporary file, invoking Iceweasel, and then cleaning up the temporary file without concerning itself with whether Iceweasel has had time to start itself and open the file. If Iceweasel already has the file open, then Mutt can delete it now and it will go away when Iceweasel closes it. Otherwise Iceweasel goes to open the file it was told to show, and the file is not there, because it was already deleted by Mutt. There are at least two ways to cure a race. The simple one is to get one process to wait for the other to finish, or at least fully start. The more complex (but preferred if it is not too difficult) way is to have the processes tell each other how they're proceeding so that each can make good decisions. The simple way here is to get Mutt to wait until you tell it to proceed. -- Mark H. Wood, Lead System Programmer mw...@iupui.edu There's an app for that: your browser pgpomO_goarDy.pgp Description: PGP signature
Re: Config Files, and Remaining Confusion with html-mail
On Fri, Jan 25, 2013 at 12:26:11PM -0500, Mark H. Wood wrote:
[cut]
Second(personal issue): I'm still having problems with
getting my html-mail to open(in a new tab) in my browser,
which is Firefox(Debianers call it iceweasel). Often,
when I use 'v' on an entry in my mutt display, and then
Arrow down to 3 . . . . [text/html . . . ., and then
press Enter, a new Tab does open in my browser, and I see
the html-mail displayed nicely. Even then I get, in my
browser-Tab: file:///home/alan/tmp/mutt.html, but there
is no such file in my ~/tmp directory!
But, too often, I get a quick new tab, a tenth of a second
look at the html I want to see, and then mutt thinks better
of it and I get a screen:
File not found Iceweasel can't find the file at
/home/alan/tmp/mutt.html
The decision which way mutt will go between these two
alternatives is, as far as I can see, quite arbitrary.
You probably need to add ; needsterminal to your .mailcap entry for
text/html so that Mutt will ask you to hit a key when the external
program (Iceweasel) is finished. For more on .mailcap and how Mutt
interprets it, see:
http://www.mutt.org/doc/manual/manual-5.html
especially the section Optional Fields.
Background:
This sounds like what is usually called a race condition. Two
processes are trying to use the same resource without sufficient
coordination. Some times one process completes first, other times the
other completes first. This causes differing behavior at different
times.
Here, I expect that Mutt is writing out that temporary file, invoking
Iceweasel, and then cleaning up the temporary file without concerning
itself with whether Iceweasel has had time to start itself and open
the file. If Iceweasel already has the file open, then Mutt can
delete it now and it will go away when Iceweasel closes it. Otherwise
Iceweasel goes to open the file it was told to show, and the file is
not there, because it was already deleted by Mutt.
There are at least two ways to cure a race. The simple one is to get
one process to wait for the other to finish, or at least fully start.
The more complex (but preferred if it is not too difficult) way is to
have the processes tell each other how they're proceeding so that each
can make good decisions. The simple way here is to get Mutt to wait
until you tell it to proceed.
third one, less scientific but it works most of the times: add the
following lines to your ~/.mailcap
text/html; sensible-browser %s sleep 2; nametemplate=%s.html
text/html; w3m -I %{charset} -T text/html -dump %s; print=w3m -I
%{charset} -T text/html -dump %s; nametemplate=%s.html; copiousoutput
you can substitute sensible-browser with iceweasel or firefox. I don't
remember why I did not set the test field on the first line:
test=sh -c 'test $DISPLAY'
Re: use of .forward file
Incoming from David Champion:
* On 24 Jan 2013, horseriver wrote:
hi:
I place a .forward file in my home dir , according to man pages,
Note that this is not related to mutt per se, so this may not be the
best group to help. However we can perhaps point you in the right
Indeed.
And last I heard, .forward was deprecated. Your mail system may not
care whether it's there or not.
--
Any technology distinguishable from magic is insufficiently advanced.
(*) :(){ :|: };:
- -
who puts mails into mutt's mail folder?
hi: Would mutt call default mail delivery agent when startup? thanks!
Re: who puts mails into mutt's mail folder?
Here's the typical pattern: MUA - [MSA] - MTA - [.. more MTAs] - LDA - [Mailbox Store] - MUA Things in [brackets] may not be used, or may take altered forms in a specific configuration. Definitions: MUA - Mail User Agent. Examples: mutt, thunderbird, webmail MSA - Mail Submission Agent. This function could be built into the MUA, or built into an MTA, or it might be a separate queuing system. Most MTAs expose a submission interface that may or may not offer separate features from their MTA interface. Examples: SMTP service, pipe to /usr/lib/sendmail, pipe to msmtp, etc. MTA - Mail Transport Agent. The primary role of an MTA is to exchange mail around the internet. An MTA may be colocated with a user agent or a delivery facility such as IMAP, but it might not. Sometimes mail moves through many MTAs on its way to a destination, but this is less common than it used to me. Most mail today encounters two MTAs: one that is colocated with the sender's submission agent, and one that triggers local delivery for the recipient. LDA - Local Delivery Agent. An LDA is responsible for handling the disposition of the mail at a destination. An MTA determines that it is a final destination (based on arbitrarily complex rules, but often just a hostname list for which it's responsible). Then it hands the mail to an LDA and awaits the LDA's assertion that delivery was performed. Procmail can be used as an LDA, but there are others. An LDA might delivery to a spool file where an MUA can retrieve it, or it might deposit the mail into a message store such as an IMAP server. Mailbox Store. Not all recipients use this, of course, but many do. To answer your question finally: An MUA (such as mutt) never interacts directly with an LDA. It either retrieves messages from a mutually-agreed location (e.g. /var/mail/username) or it contacts a message store (e.g. an IMAP server). * On 25 Jan 2013, horseriver wrote: hi: Would mutt call default mail delivery agent when startup? thanks! -- David Champion • d...@bikeshed.us
Re: who puts mails into mutt's mail folder?
* horseriver horseriv...@gmail.com [01-25-13 13:24]: Would mutt call default mail delivery agent when startup? 1st, please start new threads when you change subject/topic. mutt reads mail mda delivers mail mta transfers mail fetchmail gets mail, is a mda -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535@ http://linuxcounter.net
Re: Config Files, and Remaining Confusion with html-mail
Incoming from Mark H. Wood:
On Fri, Jan 25, 2013 at 09:28:05AM -0500, Alan McConnell wrote:
First, generically: I feel it is a source of difficulty that
mutt relies on two config files, .muttrc and .mailcap. Perhaps
.mailcap is a general-purpose configuration file for anything that
wants to know what you would like done with certain types of content.
Lots of other tools also use .mailcap and /etc/mailcap.
This is why they are separate. One belongs to Mutt and the other
belongs to the world (including Mutt, which can use it).
That was a beautiful exposition. I want to mention one addition to
it:
set mailcap_path=~/mutt/mailcap
Meaning, you can have a ~/.mailcap, *and* you can have a mutt specific
mailcap, if you like that sort of thing. So if you sometimes read
mail or deal with attachments with a program other than mutt, it'll do
it its way instead of mutt's way, and mutt will do it mutt's way.
Personally, I think reading mail in a GUI is insane (but that's just
me). Oh yeah:
# set use_mailcap
Commented out here; not sure what it's for or what it does. I should
look into that.
--
Any technology distinguishable from magic is insufficiently advanced.
(*) :(){ :|: };:
- -
Re: use of .forward file
On Fri, Jan 25, 2013 at 11:19:55AM +0800, horseriver wrote: hi: I place a .forward file in my home dir , according to man pages, I write an mail address in this file. So ,when I receive a mail ,it will be sent to that address， Did I understand wrong? Why are you posting this to a mutt list? -- Bob Holtzman If you think you're getting free lunch, check the price of the beer. Key ID: 8D549279 signature.asc Description: Digital signature
Macro for viewing photos in pgp signature
Hi, I sometimes receive messages with an embedded photo and I wonder how do display it easily from within mutt. On the console the photo can be viewed using gpg --edit-key keyID showphoto quit 1) Has someone maybe already written a macro that does exactly this? 2) If not, how do I extract the keyID from the message which I can feed to gpg? Marco signature.asc Description: Digital signature
Re: Config Files, and Remaining Confusion with html-mail
On Fri, Jan 25, 2013 at 12:53:20PM -0700, s. keeling wrote: Incoming from Mark H. Wood: On Fri, Jan 25, 2013 at 09:28:05AM -0500, Alan McConnell wrote: First, generically: I feel it is a source of difficulty that mutt relies on two config files, .muttrc and .mailcap. Perhaps .mailcap is a general-purpose configuration file for anything that wants to know what you would like done with certain types of content. Lots of other tools also use .mailcap and /etc/mailcap. This is why they are separate. One belongs to Mutt and the other belongs to the world (including Mutt, which can use it). That was a beautiful exposition. LOL It may seem beautiful to some, but it can't help anyone with a practical problem. Mr Wood wrote further: You probably need to add ; needsterminal to your .mailcap entry for text/html so that Mutt will ask you to hit a key when the external program (Iceweasel) is finished. sigh My iceweasel(aka Firefox) runs, and displays in the middle of my screen, from the moment my computer is turned on in the morning till I use it to talk to my DSL modem to shut down my connection in the evening, preparatory to shutdown -h now. For more on .mailcap and how Mutt interprets it, see: http://www.mutt.org/doc/manual/manual-5.html I've pored over the whole document, including this section. It is likely my stupidity that makes me unable to find in it why the .muttrc and the .mailcap are fighting with each other Re Race Conditions. Unless I am mistaken, mutt is written as a single, un-threaded process; I believe that 'me' is (justly) proud of this achievement. So I do not understand how two processes can be involved here. Let me say once again, as clearly as I can: when the mutt pager tells me(when I press 'v') that there is a text/html E-mail there, and I select it, I want a new tab to open on my browser, and whatever is in that text/html file?/version? to be displayed in that tab. This now happens most of the time; I want it to happen all the time. I hope that some judicious adjustment of my .mailcap and my .muttrc can make this happen. Best wishes, Alan -- Alan McConnell : http://globaltap.com/~alan/ No one minds what Jeffreys says . . it is not more than a week ago that I heard him speak disrespectfully of the Equator.(Sydney Smith)
Re: Config Files, and Remaining Confusion with html-mail
Alan McConnell wrote:
Re Race Conditions. Unless I am mistaken, mutt is
written as a single, un-threaded process; I believe that
'me' is (justly) proud of this achievement. So I do
not understand how two processes can be involved here.
I see you posted an email about this back on December 19th too.
Although I thought Patrick Shanahan explained it clearly then, and just
now Mark H. Wood did again, I'll take a shot and try to (even) more
verbosely explain what is going on and why it's causing you a problem.
The normal view attachment process for mutt is:
1. Create temp file
2. Launch viewer process
3. Wait for viewer to exit
4. Delete temp file
Assuming you already have a main firefox window running, when you
invoke firefox -new-tab %s, it does not block. It simply notifies
your main running firefox process to open a tab pointing to %s and then
exits right away. There is now a race condition. Does mutt delete
the temp file before or after your main firefox process creates the new
tab pointing to it?
Here are two (simplified) tables showing the basic ways this can play
out:
mutt firefox -new-tabmain firefox
1. Create temp file
2. Launch ff -new-tab %s
3. Notify main firefox
process to create a
new tab %s
4. Exit
5. Creates new tab
pointing to %s
6. Wait for ff -new-tab
to exit
7. Delete temp file %s
-or-
mutt firefox -new-tabmain firefox
1. Create temp file
2. Launch ff -new-tab %s
3. Notify main firefox
process to create a
new tab %s
4. Exit
5. Wait for ff -new-tab
to exit
6. Delete temp file %s
7. Creates new tab
pointing to %s
8. Error - No such
file
Which one happens depends on which process gets control after step 4:
the main firefox process or mutt. In the first case, main firefox is
able to find the file and read it in. In the second case, main firefox
can't open the file, and you get an error message. In either case,
though, if you go look for the file in /tmp, the file will be gone
because mutt has already deleted it.
There is no completely clean way to fix this, because there is no way to
know how long the main firefox will need %s to be around. If you only
intend to quickly view the file and then close the tab, the best way is
to have mutt sleep after invoking firefox -new-tab. Try modifying
your .mailcap invocation to:
text/html; firefox -new-tab '%s' sleep 10; test=
^^^
add this
The idea is that even if the second scenario happens, mutt will just
sleep instead of deleting the temp file. Hopefully the main firefox
will have a chance to run and read that file in before the sleep ends
and mutt deletes the file.
Race conditions are complicated, and this explanation is not complete,
but I hope this helps.
-Kevin
signature.asc
Description: Digital signature
Re: .procmailrc configurations
Incoming from Patrick Shanahan:
* horseriver horseriv...@gmail.com [01-25-13 08:50]:
To make procmail wok fine . is a .forward file in my home dir a
must ?
man procmail
Even better: http://www.procmail.org/era/lists.html
If we discussed everything that works with mutt on the mutt-users
list, any mention of mutt itself would be difficult to find. That
would be unfortunate.
I apologize if I've done anything to encourage that (and I likely
have; stopping now).
Have a lovely weekend! :-)
--
Any technology distinguishable from magic is insufficiently advanced.
(*) :(){ :|: };:
- -
Re: Config Files, and Remaining Confusion with html-mail
Incoming from Alan McConnell:
sigh My iceweasel(aka Firefox) runs, and displays in the
middle of my screen, from the moment my computer is turned
Just a suggestion ... isolate the problem. Swap out firefox. In my
~/mutt/mailcap:
text/html; w3m -I %{charset} -T text/html -dump; copiousoutput
Bon chance.
--
Any technology distinguishable from magic is insufficiently advanced.
(*) :(){ :|: };:
- -
Re: who puts mails into mutt's mail folder?
On Fri, Jan 25, 2013 at 02:17:27PM -0500, Patrick Shanahan wrote: * horseriver horseriv...@gmail.com [01-25-13 13:24]: Would mutt call default mail delivery agent when startup? mutt reads mail mda delivers mail mta transfers mail fetchmail gets mail, is a mda Thanks! 1. Is fetchmail alwayes running at deamon mode ,fectching mail by timer ? or it is called by mutt when mutt startup? 2. What is the use of mail command ? It seems to be a mda too.So I do not how to distinguish between mail and fetchmail. If I want to use fetchmail ,need I remove the mail mda? -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535@ http://linuxcounter.net
Re: who puts mails into mutt's mail folder?
* horseriver horseriv...@gmail.com [01-26-13 00:09]: On Fri, Jan 25, 2013 at 02:17:27PM -0500, Patrick Shanahan wrote: * horseriver horseriv...@gmail.com [01-25-13 13:24]: Would mutt call default mail delivery agent when startup? mutt reads mail mda delivers mail mta transfers mail fetchmail gets mail, is a mda Thanks! 1. Is fetchmail alwayes running at deamon mode ,fectching mail by timer ? or it is called by mutt when mutt startup? it is as *you* configure it, man fetchmail 2. What is the use of mail command ? It seems to be a mda too.So I do not how to distinguish between mail and fetchmail. If I want to use fetchmail ,need I remove the mail mda? /usr/bin/mail, is *not* an mda. man mail You *really* need to look at the applications' documentation. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535@ http://linuxcounter.net -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535@ http://linuxcounter.net
Re: use of .forward file
On Fri, Jan 25, 2013 at 12:37:06PM +0800, horseriver wrote: I have already read this man page ,and I am reaching on these points all. My system now has one mail delivery agent named exim4. But I do not know is it the default mail delivery agent ? Can you tell me how to know the default mail delivery agent on my system? For a start exim4 is an MTA (mail transport agent) You really need to read to some basic docs about how mail can be handled on a Unix/Linux system. A hint which helped me when I first started, was sending a mail is a totally different procedure to recieving a mail. -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X
Re: who puts mails into mutt's mail folder?
Incoming from horseriver:
On Fri, Jan 25, 2013 at 02:17:27PM -0500, Patrick Shanahan wrote:
* horseriver horseriv...@gmail.com [01-25-13 13:24]:
Would mutt call default mail delivery agent when startup?
mutt reads mail
mda delivers mail
mta transfers mail
fetchmail gets mail, is a mda
Why are you not reading the suggested documentation? Patrick's advice
is spot on. All of your questions so far are easily answered by the
suggested docs.
1. Is fetchmail alwayes running at deamon mode ,fectching mail by
timer ? or it is called by mutt when mutt startup?
fetchmail can be run as a daemon or can be invoked by users. Which is
best for you? Read the docs!
2. What is the use of mail command ? It seems to be a mda too.So I
No, mail is an MUA just like mutt. Now, you're becoming annoying. At
a terminal, do this:
xman -notopbox -bothshown
That's a pointy-clicky interface to the manpages. Now PLEASE read
some documentation!
Grr. Thank you.
--
Any technology distinguishable from magic is insufficiently advanced.
(*) :(){ :|: };:
- -
Re: use of .forward file
On Fri, Jan 25, 2013 at 12:37:06PM +0800, horseriver wrote: I have already read this man page ,and I am reaching on these points all. My system now has one mail delivery agent named exim4. Umm, no. Have a look at: http://www.tldp.org/HOWTO/Mail-Administrator-HOWTO-3.html http://www.unix.com/unix-dummies-questions-answers/ http://dsl.org/cookbook/cookbook_38.html http://lowfatlinux.com/linux-read-email.html http://lowfatlinux.com/linux-send-email.html http://www.linuxtopia.org/HowToGuides/linux_email_setup_guide/linux_email_intro1.html http://www.linuxhomenetworking.com/wiki/index.php/Quick_HOWTO_:_Ch21_:_Configuring_Linux_Mail_Servers http://docstore.mik.ua/orelly/linux/run/ch16_02.htm http://www.northernjourney.com/opensource/newbies/newb024.html http://www.linux.org/article/view/mail-servers http://wiki2.dovecot.org/MailServerOverview http://en.wikipedia.org/wiki/Mail_delivery_agent etc... etc... etc... -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X
