Re: ProcMail, WAS: Re: Fetchmail and Gmail
On Tue, 25 Aug 2009 13:32:21 +0300 Micha mi...@post.tau.ac.il wrote: On 8/24/2009 11:34 PM, Paul Cartwright wrote: On Mon August 24 2009, Micha wrote: Personally I use fetchmail + procmail to fetch and filter my mail I use fetchmail to pull in my mail for all my domain accounts. Kmail pulls it all in via my local user. From there I have many, MANY filters to put mail in separate folders. what benefit would I get from procmail? ... 3. Text file with regular expression based rules that you know where it resides and can back it up and human read it As the resident Sylpheed fanboy, I must point out that Sylph stores all its configuration, including its filter rules (which can utilize regex's), in fairly easy to understand XML files under $HOME/.sylpheed-2.0. Celejar -- mailmin.sourceforge.net - remote access via secure (OpenPGP) email ssuds.sourceforge.net - A Simple Sudoku Solver and Generator -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ProcMail, WAS: Re: Fetchmail and Gmail
On Tue, 25 Aug 2009 13:44:57 +0300 Andrei Popescu andreimpope...@gmail.com wrote: On Ma,25.aug.09, 13:32:21, Micha wrote: On the downside, if you want to explicitly pull mail now, pulling mail from kmail doesn't pull the mail off your accounts, you need to do that explicitly from the command line Not very familiar with kmail, but claws-mail (sylpheed too?) has configurable Actions which you can use to run external programs/scripts. Of course Sylph does ;) Celejar -- mailmin.sourceforge.net - remote access via secure (OpenPGP) email ssuds.sourceforge.net - A Simple Sudoku Solver and Generator -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ProcMail, WAS: Re: Fetchmail and Gmail
On Tue, Aug 25, 2009 at 10:57:01PM EDT, Celejar wrote: On Tue, 25 Aug 2009 13:32:21 +0300 Micha mi...@post.tau.ac.il wrote: ... 3. Text file with regular expression based rules that you know where it resides and can back it up and human read it As the resident Sylpheed fanboy, I must point out that Sylph stores all its configuration, including its filter rules (which can utilize regex's), in fairly easy to understand XML files under $HOME/.sylpheed-2.0. Nice.. So it should be fairly straightforward to generate a procmail .rc file and move the filters where they rightly belong.. :-) CJ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ProcMail, WAS: Re: Fetchmail and Gmail
On Tue, Aug 25 2009, Andrei Popescu wrote: On Mon,24.Aug.09, 20:56:27, Paul Cartwright wrote: but looking at the procmailrc( now non-existant), then thinking about my 200 kmail filters, I'm not sure I could tackle that task.. maildir (and procmail too as I hear, but I don't like its syntax) is *very* powerful. I recently did a major rewrite on my maildrop rules. I had one rule for each Debian list, now I have exactly one: # These are the lists.debian.org lists if (/^List-Id:.*debian-(.*)\.lists.debian.org/) { to Maildir/.debian.$MATCH1 } Similar for googlegroups, alioth, ... All that was needed was a bit of folder renaming ;) Hmm. Here is my Debian section; this pulls out emails for my packages from the pts, discards all other devel-changes mail; pulls out boring debbugs email, send bugs for my package into a package specific folder, pulls out mail sent to bugs I reported separately, and then files every debian group to a separate folder. Oh, I used to separate out ballots and votes, etc, but that is mostly done away with. After mailagent, procmail seems ... underpowered. manoj ## ## ## #Debian # ## ## ## ## INITIAL X-PTS-Package: /([-\w]+)/ { ANNOTATE -d X-Agent-list 'pkg-%1'; ASSIGN list 'pkg-%1'; REJECT MailingList }; # X-Mailing-List To Resent-From Resent-To Resent-Reply-To Cc INITIAL X-Loop: /debian-devel-changes/i { REJECT JUNK; }; # Do not wish to see acks for bug reports INITIAL From: /own...@bugs.debian.org/, Subject: /Bug#\d+: Acknowledgement / { REJECT JUNK; }; # These have little information really INITIAL From: /own...@bugs.debian.org/, Subject: /Bug#\d+: Info received/i { REJECT ClosedBugs }; INITIAL X-Loop: /debian-bugs-dist/i{ REJECT DEBIANBUGS }; INITIAL X-Loop: /own...@bugs.debian.org/i { REJECT DEBIANBUGS }; INITIAL X-Loop X-Mailing-List To Resent-From Resent-To Resent-Reply-To Cc: /lists.debian.org/i { REJECT DEBIAN }; INITIAL X-Loop X-Mailing-List To Resent-From Resent-To Resent-Reply-To Cc: /debian-ctte/i { REJECT DEBIAN }; INITIAL X-Loop: /deity/i { ASSIGN list deity; REJECT MailingList }; INITIAL Sender From: /install...@ftp-master.debian.org/ { ASSIGN list 'installed'; REJECT MailingList }; # Handle My own bugs DEBIANBUGS To Resent-CC: /Manoj Srivastava/ { REJECT MYBUGS }; MYBUGS X-Debian-PR-Package: /([-\w]+)/ { ANNOTATE -d X-Agent-list 'pkg-%1'; ASSIGN list 'pkg-%1'; REJECT MailingList }; # Resent-To: Manoj Srivastava is for bugs I reported MYBUGS /./ { ASSIGN list 'debian'; ANNOTATE -d X-Agent-list unknown-bug-list; REJECT MailingList; }; #handle policy bugs DEBIANBUGS X-Debian-PR-Package: /debian-policy/ { ASSIGN list 'debian-policy'; ANNOTATE -d X-Agent-list debian-list; REJECT MailingList; }; DEBIANBUGS X-Debian-PR-Package: /general/ { ASSIGN list 'debian-devel'; ANNOTATE -d X-Agent-list general-bugs; REJECT MailingList; }; DEBIANBUGS X-Debian-PR-Package: /wnpp/ { ASSIGN list 'wnpp'; ANNOTATE -d X-Agent-list debian-list; REJECT MailingList; }; DEBIANBUGS Subject: /\[proposal\]/i, X-Debian-PR-Package: /debian-policy/ { ASSIGN list 'debian-policy'; ANNOTATE -d X-Agent-list debian-list; REJECT MailingList; }; DEBIANBUGS All: /./ { ASSIGN list 'debian-bugs'; ANNOTATE -d X-Agent-list debian-list; REJECT MailingList; }; DEBIAN X-Loop: /(debian-bugs-(closed|forwarded))(-(request|dist))?...@lists.debian.org/i { REJECT ClosedBugs }; DEBIAN X-Loop X-Mailing-List To Resent-From Resent-To Resent-Reply-To Cc : /(debian-ctte+)(-(request|dist|private))?...@debian.org/gi { ASSIGN list '%1'; ANNOTATE -d X-Agent-list debian-list; REJECT MailingList; }; DEBIAN Subject: /CFV: Proposal/, X-Loop: /debian-vote/ { REJECT VOTE }; DEBIAN X-Loop: /(debian-[\w-]+)(-(request|dist))?...@lists.debian.org/gi { ASSIGN list '%1'; SUBST #list /-(digest|request|dist)//gi; SUBST #list /devel-changes/changes/i; ANNOTATE -d X-Agent-list debian-list; REJECT MailingList; }; VOTE Body: /^\s*I vote\s+\w+\s+on/i { UNIQUE -a (vote); VACATION off; MESSAGE ~/etc/mail/voteack; REJECT VOTEACK; }; VOTE
Re: ProcMail, WAS: Re: Fetchmail and Gmail
On 2009-08-25 23:30, Chris Jones wrote: On Tue, Aug 25, 2009 at 10:57:01PM EDT, Celejar wrote: On Tue, 25 Aug 2009 13:32:21 +0300 Micha mi...@post.tau.ac.il wrote: ... 3. Text file with regular expression based rules that you know where it resides and can back it up and human read it As the resident Sylpheed fanboy, I must point out that Sylph stores all its configuration, including its filter rules (which can utilize regex's), in fairly easy to understand XML files under $HOME/.sylpheed-2.0. Nice.. So it should be fairly straightforward to generate a procmail .rc file and move the filters where they rightly belong.. Or, if you are in your right mind, maildrop. -- Obsession with preserving cultural heritage is a racist impediment to moral, physical and intellectual progress. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Fetchmail and Gmail
On Sun, Aug 23, 2009 at 9:30 PM, Ron Johnsonron.l.john...@cox.net wrote: On 2009-08-23 14:09, Rob Gom wrote: Hi all, could anyone explain to me why fetchmail is needed in the first place? Now *this* is an excellent flame! Why do you consider my opinion as flamewar, whereas I only expect some simple answers? From user's point of view it is something additional. Instead of configuring mail setup in single place (MUA, mail program), one has to set it up both in MUA (retrieve mail from local mail box) and fetchmail configuration file. It's not that difficult. Really. In my (ordinary user) opinion configuring mail program from its gui and text file somewhere in the filesystem is more difficult than editing only one place. And, believe me or not, there are people who prefer graphical interfaces for some tasks, finding them more convenient than command line. The latter (IMHO) has very limited functionality of password encryption handling, Sure it doess, with POPS. Maybe I haven't been understood well. My mail provider gives me a password. In mail program I add it to some wallet or let mail program to encrypt it after setting up. If I want to use fetchmail, I have to write it there in plain text (correct me if I'm wrong), which is not what I like doing. no gui integration Boo fscking hoo. I beg your pardon? - it is needed to launch text editor to edit specific file... Again, boo fscking hoo. Does this setup have any advantages? Yes, it does, since it fetches your mail *for you* from your ISP's POP server, and can send it to an MTA, which passes it thru SpamAssassin and then an MDA, which then filters your email into separate folders depending on topic or sender. So? Where's the advantage? My mail program fetches mail *for me* from my ISP's POP server, passes it thru any filter (let it be spamassassin), then writes it to separate folders depending on basically anything. Fetchmail, MTA, MDA avoided, whereas the same purpose achieved. Easier. Another benefit: for the longest time, ISPs had very small mailbox sizes, and some still do. fetchmail/getmail running in daemon mode or through cron every X minutes will keep your ISP mailbox relatively empty, even if you go away on vacation. Only if my computer (desktop) stays powered on all the time which is not the case. And mailboxes are big enough. It is counterintuitive Remember, *ix is both a desktop and serve at the same time. Thus, break out of your Windows Mentality. It seems that you strongly believe in that. Please, don't underestimate others technical knowledge. I am able to set up fetchmail et al, but I don't find it necessary nor logical. Let the engine be complicated as hell (fetchmail, MUA, MTA, MDA, spamassassin, others), but also let user only touch the steering wheel and ignition button. and non ergonomic, isn't it? Ergonomics has nothing to with fetchmail. But it has something to do with setting up your working environment. Unless automatically fetching mail so that you don't have to is considered ergonomic. The above makes no sense to me, sorry. Are there any mail programs which allow seamless integration with fetchmail/getmail? All MTAs and MDAs, and Maildir, seamlessly integrate with fetchmail. Are there any mail programs, which allow all mail server settings (server, port, user, password, ..) to be passed to/handled by fetchmail? Like a checkbox don't download it by yourself, let fetchmail to do it for you. Regards, Robert -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Fetchmail and Gmail
On Mon,24.Aug.09, 11:37:53, Rob Gom wrote: Maybe I haven't been understood well. My mail provider gives me a password. In mail program I add it to some wallet or let mail program to encrypt it after setting up. If I want to use fetchmail, I have to write it there in plain text (correct me if I'm wrong), which is not what I like doing. Storing the password encrypted in some file has no benefit over storing the password in plain text, because anyone who gets the hash will be able to access your mail. And if you don't use SSL for connecting to the mail server you can encrypt the password as much as you like on your system, because it will be transmitted in clear over the wire. A potential attacker doesn't even have to break in your system. Even if you manage to avoid all these issues, root would still be able to get your password (basically you must assume you can't protect yourself from root). Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Re: Fetchmail and Gmail
On Mon,24.Aug.09, 11:37:53, Rob Gom wrote: So? Where's the advantage? My mail program fetches mail *for me* from my ISP's POP server, passes it thru any filter (let it be spamassassin), then writes it to separate folders depending on basically anything. Fetchmail, MTA, MDA avoided, whereas the same purpose achieved. Easier. Yes, in many cases it is, but the separate tools approach is more flexible and more powerful. Initially moved my mail retrieval+sorting outside the GUI client because it couldn't download mail in a separate thread. Then I also moved the sending for similar reasons. The added benefit is that switching mail clients is much easier now: SMTP server: localhost IMAP server: localhost and I'm done. Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Re: Fetchmail and Gmail
... From user's point of view it is something additional. Instead of configuring mail setup in single place (MUA, mail program), one has to set it up both in MUA (retrieve mail from local mail box) and fetchmail configuration file. It's not that difficult. Really. In my (ordinary user) opinion configuring mail program from its gui and text file somewhere in the filesystem is more difficult than editing only one place. And, believe me or not, there are people who That is your opinion, others don't think that way. That is why there are different options. Plus, fetchmail is MUCH older than gui email programs. Personally I use fetchmail + procmail to fetch and filter my mail This way I can easily switch mail clients, also my mail client doesn't have to be running all the time using up memory and cpu. prefer graphical interfaces for some tasks, finding them more convenient than command line. The latter (IMHO) has very limited functionality of password encryption handling, Sure it doess, with POPS. Maybe I haven't been understood well. My mail provider gives me a password. In mail program I add it to some wallet or let mail program to encrypt it after setting up. If I want to use fetchmail, I have to write it there in plain text (correct me if I'm wrong), which is not what I like doing. no gui integration Boo fscking hoo. I beg your pardon? - it is needed to launch text editor to edit specific file... Again, boo fscking hoo. Does this setup have any advantages? Yes, it does, since it fetches your mail *for you* from your ISP's POP server, and can send it to an MTA, which passes it thru SpamAssassin and then an MDA, which then filters your email into separate folders depending on topic or sender. So? Where's the advantage? My mail program fetches mail *for me* from my ISP's POP server, passes it thru any filter (let it be spamassassin), then writes it to separate folders depending on basically anything. Fetchmail, MTA, MDA avoided, whereas the same purpose achieved. Easier. Another benefit: for the longest time, ISPs had very small mailbox sizes, and some still do. fetchmail/getmail running in daemon mode or through cron every X minutes will keep your ISP mailbox relatively empty, even if you go away on vacation. Only if my computer (desktop) stays powered on all the time which is not the case. And mailboxes are big enough. It is counterintuitive Remember, *ix is both a desktop and serve at the same time. Thus, break out of your Windows Mentality. It seems that you strongly believe in that. Please, don't underestimate others technical knowledge. I am able to set up fetchmail et al, but I don't find it necessary nor logical. Let the engine be complicated as hell (fetchmail, MUA, MTA, MDA, spamassassin, others), but also let user only touch the steering wheel and ignition button. and non ergonomic, isn't it? Ergonomics has nothing to with fetchmail. But it has something to do with setting up your working environment. Unless automatically fetching mail so that you don't have to is considered ergonomic. The above makes no sense to me, sorry. Are there any mail programs which allow seamless integration with fetchmail/getmail? All MTAs and MDAs, and Maildir, seamlessly integrate with fetchmail. Are there any mail programs, which allow all mail server settings (server, port, user, password, ..) to be passed to/handled by fetchmail? Like a checkbox don't download it by yourself, let fetchmail to do it for you. Regards, Robert -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Fetchmail and Gmail
On Mon, Aug 24, 2009 at 1:01 PM, Andrei Popescuandreimpope...@gmail.com wrote: On Mon,24.Aug.09, 11:37:53, Rob Gom wrote: [cut] Ok, so now I see the reasons to move: 1. Power flexibility: (if one needs something more than what mail application can offer) Yes, in many cases it is, but the separate tools approach is more flexible and more powerful. [cut] 2. Mail program limitations: Initially moved my mail retrieval+sorting outside the GUI client because it couldn't download mail in a separate thread. Then I also moved the (this is also my case - KMail famous bug) As for: Storing the password encrypted in some file has no benefit over storing the password in plain text, because anyone who gets the hash will be able to access your mail. And if you don't use SSL for connecting to the mail server you can encrypt the password as much as you like on your system, because it will be transmitted in clear over the wire. A potential attacker doesn't even have to break in your system. To clarify: I don't send passwords in plain text over the net (mainly SSL/TLS). And I believe that storing passwords encrypted is always safer than storing them unencrypted. Regards, Robert -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Fetchmail and Gmail
On 8/24/2009 3:05 PM, Rob Gom wrote: On Mon, Aug 24, 2009 at 1:01 PM, Andrei Popescuandreimpope...@gmail.com wrote: On Mon,24.Aug.09, 11:37:53, Rob Gom wrote: [cut] Ok, so now I see the reasons to move: 1. Power flexibility: (if one needs something more than what mail application can offer) Yes, in many cases it is, but the separate tools approach is more flexible and more powerful. [cut] 2. Mail program limitations: Initially moved my mail retrieval+sorting outside the GUI client because it couldn't download mail in a separate thread. Then I also moved the (this is also my case - KMail famous bug) As for: Storing the password encrypted in some file has no benefit over storing the password in plain text, because anyone who gets the hash will be able to access your mail. And if you don't use SSL for connecting to the mail server you can encrypt the password as much as you like on your system, because it will be transmitted in clear over the wire. A potential attacker doesn't even have to break in your system. To clarify: I don't send passwords in plain text over the net (mainly SSL/TLS). And I believe that storing passwords encrypted is always safer than storing them unencrypted. On the other hand I forgot my password several times (way too many password protected accounts each with it's own password restrictions) and it saved me that I could just open the file and see the password. After I download the mail it's on my system anyway, and if you occasionally change the password then the problem is solved Regards, Robert -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Fetchmail and Gmail
On Monday 24 August 2009 07:05:18 Rob Gom wrote: I believe that storing passwords encrypted is always safer than storing them unencrypted. Well, then you would be wrong. I an unattended program can take the bytes stored in the inode(s) and send your password to your ISP then a program written by an attacker can take the same bytes and send your password back to the attacker. Technically the password is not encrypted in this case, only obfuscated. If your password requires getting a passphrase/key/whatever from you, it can't be used by non-interactive programs. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Fetchmail and Gmail
On Mon August 24 2009, Micha wrote: On the other hand I forgot my password several times (way too many password protected accounts each with it's own password restrictions) and it saved me that I could just open the file and see the password. try keepassX, a great little app ( linux windows) for storing your logins/passwords/URLs for almost anything.. all you need to remember is THE ONE keepassX password:) -- Paul Cartwright Registered Linux user # 367800 Registered Ubuntu User #12459 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
ProcMail, WAS: Re: Fetchmail and Gmail
On Mon August 24 2009, Micha wrote: Personally I use fetchmail + procmail to fetch and filter my mail I use fetchmail to pull in my mail for all my domain accounts. Kmail pulls it all in via my local user. From there I have many, MANY filters to put mail in separate folders. what benefit would I get from procmail? -- Paul Cartwright Registered Linux user # 367800 Registered Ubuntu User #12459 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RE: ProcMail, WAS: Re: Fetchmail and Gmail
From: Paul Cartwright [mailto:a...@pcartwright.com] Sent: Monday, August 24, 2009 1:35 PM On Mon August 24 2009, Micha wrote: Personally I use fetchmail + procmail to fetch and filter my mail I use fetchmail to pull in my mail for all my domain accounts. Kmail pulls it all in via my local user. From there I have many, MANY filters to put mail in separate folders. what benefit would I get from procmail? The processing happens at the server level instead of the client level. This means the mail is already filed into the proper folders when you launch your favorite mail client. This also means you can easily move back and forth between mail clients and not have to rewrite the rules for each client, if the client even supports filters. This is especially useful if you also have a webmail server running on your computer. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ProcMail, WAS: Re: Fetchmail and Gmail
On 2009-08-24 17:11, Kevin Ross wrote: From: Paul Cartwright [mailto:a...@pcartwright.com] Sent: Monday, August 24, 2009 1:35 PM On Mon August 24 2009, Micha wrote: Personally I use fetchmail + procmail to fetch and filter my mail I use fetchmail to pull in my mail for all my domain accounts. Kmail pulls it all in via my local user. From there I have many, MANY filters to put mail in separate folders. what benefit would I get from procmail? The processing happens at the server level instead of the client level. This means the mail is already filed into the proper folders when you launch your favorite mail client. This also means you can easily move back and forth between mail clients and not have to rewrite the rules for each client, if the client even supports filters. This is especially useful if you also have a webmail server running on your computer. But if Paul is asking the benefit of procmail over competing MDAs like maildrop, then the benefit is cryptic line noise a la Perl. -- Obsession with preserving cultural heritage is a racist impediment to moral, physical and intellectual progress. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ProcMail, WAS: Re: Fetchmail and Gmail
On Mon August 24 2009, Ron Johnson wrote: But if Paul is asking the benefit of procmail over competing MDAs like maildrop, then the benefit is cryptic line noise a la Perl. what I'm asking is.. will it benefit me to change the way I do email and add another program into the mix. right now I do fetchmail to /var/mail/myuser kmail picks up the mail, does all the filtering... when I fire up icedove, it is a totally separate set of folders emails ( dating back 2 years:) I'm not sure I understand how I can use procmail to put mail into filtered folders that any mail program can read. It would be nice to be able to switch programs still have all my mail in the same folders.. but looking at the procmailrc( now non-existant), then thinking about my 200 kmail filters, I'm not sure I could tackle that task.. -- Paul Cartwright Registered Linux user # 367800 Registered Ubuntu User #12459 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RE: ProcMail, WAS: Re: Fetchmail and Gmail
From: Paul Cartwright [mailto:a...@pcartwright.com] Sent: Monday, August 24, 2009 5:56 PM On Mon August 24 2009, Ron Johnson wrote: But if Paul is asking the benefit of procmail over competing MDAs like maildrop, then the benefit is cryptic line noise a la Perl. what I'm asking is.. will it benefit me to change the way I do email and add another program into the mix. right now I do fetchmail to /var/mail/myuser kmail picks up the mail, does all the filtering... when I fire up icedove, it is a totally separate set of folders emails ( dating back 2 years:) I'm not sure I understand how I can use procmail to put mail into filtered folders that any mail program can read. It would be nice to be able to switch programs still have all my mail in the same folders.. but looking at the procmailrc( now non-existant), then thinking about my 200 kmail filters, I'm not sure I could tackle that task.. Personally I use Maildirs. Mail is delivered to a Maildir folder under each user's home directory. Folders in your mail client are also folders in the Maildir. Many mail clients can read Maildirs (Evolution being one. Possibly Icedove, not sure though.) Procmail understands Maildirs. You just tell it the folder name you want a message copied to in your rules. You can also use an IMAP server, as I do. IMAP allows folders, unlike POP3. And most IMAP servers understand Maildirs. Then just point any mail client to the IMAP server (which can be localhost), and your mail client will display the folder hierarchy. Webmail servers will connect to an IMAP server running on the localhost, so then you will be able to access your email from any web browser anywhere, assuming your computer is reachable from the Internet, and still see all your folders. Also, personally I use a different mail filtering program, not procmail, but the basic functionality is the same. -- Kevin -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ProcMail, WAS: Re: Fetchmail and Gmail
On 2009-08-24 19:56, Paul Cartwright wrote: On Mon August 24 2009, Ron Johnson wrote: But if Paul is asking the benefit of procmail over competing MDAs like maildrop, then the benefit is cryptic line noise a la Perl. what I'm asking is.. will it benefit me to change the way I do email and add another program into the mix. right now I do fetchmail to /var/mail/myuser kmail picks up the mail, does all the filtering... when I fire up icedove, it is a totally separate set of folders emails ( dating back 2 years:) I'm not sure I understand how I can use procmail to put mail into filtered folders that any mail program can read. It would be nice to be able to switch programs still have all my mail in the same folders.. but looking at the procmailrc( now non-existant), then thinking about my 200 kmail filters, I'm not sure I could tackle that task.. Adding to Kevin's excellent points: The Windows Way (actually pioneered by Netscape, but who's quibbling?) combines server and client functionality into the MUA. This was needed on Win3.1 and Win9X, and tradition has kept it afloat. On Linux, though, mail clients don't have to be so do-all. By using a mail retriever, you've made the important First Step in divesting your Mail User Agent from non-User functionality. The next step is to integrate procmail with fetchmail and have it deposit the email in a client-neutral location. Maildir and IMAP were designed for this very purpose. Then you will be able to use whatever MUA you want (or Mutt, if you are using Testing or Sid, and X ever craps out for a few days), on whatever machine you desire (as long as it is networked with your main PC). -- Obsession with preserving cultural heritage is a racist impediment to moral, physical and intellectual progress. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Fetchmail and Gmail
Hi all, could anyone explain to me why fetchmail is needed in the first place? From user's point of view it is something additional. Instead of configuring mail setup in single place (MUA, mail program), one has to set it up both in MUA (retrieve mail from local mail box) and fetchmail configuration file. The latter (IMHO) has very limited functionality of password encryption handling, no gui integration - it is needed to launch text editor to edit specific file... Does this setup have any advantages? It is counterintuitive and non ergonomic, isn't it? Are there any mail programs which allow seamless integration with fetchmail/getmail? Regards, Robert -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Fetchmail and Gmail
Rob Gom rgom.deb...@gmail.com writes: [...] Are there any mail programs which allow seamless integration with fetchmail/getmail? If by that you mean allow you to get your mail via POP or IMAP without editing any configuration files, sure, all of the GUI mail clients do this: Thunderbird, KMail, Evolution, etc. -Scott. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Fetchmail and Gmail
On 2009-08-23 14:09, Rob Gom wrote: Hi all, could anyone explain to me why fetchmail is needed in the first place? Now *this* is an excellent flame! From user's point of view it is something additional. Instead of configuring mail setup in single place (MUA, mail program), one has to set it up both in MUA (retrieve mail from local mail box) and fetchmail configuration file. It's not that difficult. Really. The latter (IMHO) has very limited functionality of password encryption handling, Sure it doess, with POPS. no gui integration Boo fscking hoo. - it is needed to launch text editor to edit specific file... Again, boo fscking hoo. Does this setup have any advantages? Yes, it does, since it fetches your mail *for you* from your ISP's POP server, and can send it to an MTA, which passes it thru SpamAssassin and then an MDA, which then filters your email into separate folders depending on topic or sender. Another benefit: for the longest time, ISPs had very small mailbox sizes, and some still do. fetchmail/getmail running in daemon mode or through cron every X minutes will keep your ISP mailbox relatively empty, even if you go away on vacation. It is counterintuitive Remember, *ix is both a desktop and serve at the same time. Thus, break out of your Windows Mentality. and non ergonomic, isn't it? Ergonomics has nothing to with fetchmail. Unless automatically fetching mail so that you don't have to is considered ergonomic. Are there any mail programs which allow seamless integration with fetchmail/getmail? All MTAs and MDAs, and Maildir, seamlessly integrate with fetchmail. -- Featuring GRATUITOUS ALIEN NUDITY -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Fetchmail and Gmail
On Thu, 20 Aug 2009, Andrei Popescu wrote: flame Fetchmail and Gmail both seem strange to me. Getting them to actually work together must be a dark art :) /flame What's so strange about fetchmail? I admit this is uninformed, but it seems to me like fetchmail tries to be many things, but not particularly good at anything: Your flame worked! -- Girish Kulkarni - Allahabad, India - athene.org.in/girish -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Fetchmail and Gmail
On Fri,21.Aug.09, 11:43:04, Girish Kulkarni wrote: On Thu, 20 Aug 2009, Andrei Popescu wrote: flame Fetchmail and Gmail both seem strange to me. Getting them to actually work together must be a dark art :) /flame What's so strange about fetchmail? I admit this is uninformed, but it seems to me like fetchmail tries to be many things, but not particularly good at anything: Your flame worked! Apparently :( I'll stop responding to this thread now. Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Re: Fetchmail and Gmail
On 2009-08-21 02:18, Andrei Popescu wrote: On Fri,21.Aug.09, 11:43:04, Girish Kulkarni wrote: On Thu, 20 Aug 2009, Andrei Popescu wrote: flame Fetchmail and Gmail both seem strange to me. Getting them to actually work together must be a dark art :) /flame What's so strange about fetchmail? I admit this is uninformed, but it seems to me like fetchmail tries to be many things, but not particularly good at anything: Your flame worked! Apparently :( Honestly, that was a lame flame. Mainly because it was a good segue into why you don't like it, instead of a raw blast of vituperation. I'm not really complaining, though. I'll stop responding to this thread now. -- Featuring GRATUITOUS ALIEN NUDITY -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Fetchmail and Gmail
On 2009-08-17 12:20, Andrei Popescu wrote: [snip] flame Fetchmail and Gmail both seem strange to me. Getting them to actually work together must be a dark art :) /flame What's so strange about fetchmail? -- Featuring GRATUITOUS ALIEN NUDITY -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Fetchmail and Gmail
On Thu,20.Aug.09, 06:40:29, Ron Johnson wrote: On 2009-08-17 12:20, Andrei Popescu wrote: [snip] flame Fetchmail and Gmail both seem strange to me. Getting them to actually work together must be a dark art :) /flame What's so strange about fetchmail? I admit this is uninformed, but it seems to me like fetchmail tries to be many things, but not particularly good at anything: - it has a daemon mode reported to hang - retrieves mail via POP3 and IMAP only to inject it back to SMTP - ESR mentioned he wanted to make the configuration syntax easy. Apparently he made it so easy that a dedicated editor is needed I know fetchmail can be run from cron, deliver to an MDA (or directly) and the configuration can be written directly by a human, but I prefer getmail for that :) Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Re: Fetchmail and Gmail
On 2009-08-20 11:44, Andrei Popescu wrote: On Thu,20.Aug.09, 06:40:29, Ron Johnson wrote: On 2009-08-17 12:20, Andrei Popescu wrote: [snip] flame Fetchmail and Gmail both seem strange to me. Getting them to actually work together must be a dark art :) /flame What's so strange about fetchmail? I admit this is uninformed, but it seems to me like fetchmail tries to be many things, but not particularly good at anything: - it has a daemon mode reported to hang Hang, really? Glad I started out using it via cron. - retrieves mail via POP3 and IMAP only to inject it back to SMTP Sure, the locally-running MTA. - ESR mentioned he wanted to make the configuration syntax easy. Apparently he made it so easy that a dedicated editor is needed Sentence-like, which it is! But everyone speaks in different ways, especially ESLs. I know fetchmail can be run from cron, deliver to an MDA (or directly) and the configuration can be written directly by a human, but I prefer getmail for that :) Like I prefer fetchmail injecting mail into the local MTA, which also handles local mail. -- Featuring GRATUITOUS ALIEN NUDITY -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Fetchmail and Gmail
Andrei Popescu writes: [Fetchmail] retrieves mail via POP3 and IMAP only to inject it back to SMTP That's a feature. ESR mentioned he wanted to make the configuration syntax easy. It's trivial: just name-value pairs. Apparently he made it so easy that a dedicated editor is needed Because editing a file terrifies some people. -- John Hasler -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Fetchmail and Gmail
Ron writes: Sentence-like, which [Fetchmail configuration] is! It can appear to be, but the extra words are ignored. You can just use name-value pairs, which I think are clearer. There is a special editor (fetchmailconf) for those who fear configuration files (quite common, unfortunately). -- John Hasler -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Fetchmail and Gmail
On Thu, 20 Aug 2009 19:44:33 +0300 Andrei Popescu andreimpope...@gmail.com wrote: ... I admit this is uninformed, but it seems to me like fetchmail tries to be many things, but not particularly good at anything: - it has a daemon mode reported to hang Been using it for about 10 years now, on machines that stay up for months at a time, didn't hang yet. - retrieves mail via POP3 and IMAP only to inject it back to SMTP ? - ESR mentioned he wanted to make the configuration syntax easy. Apparently he made it so easy that a dedicated editor is needed Didn't know there was a dedicated editor. Made my config based solely on the man page, back when I was still coming to terms with basic Linux usage. -- Carlos Sousa -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Fetchmail and Gmail
On Mon, 17 Aug 2009, Andrei Popescu wrote: Fetchmail and Gmail both seem strange to me. Getting them to actually work together must be a dark art :) True! :-) -- Girish Kulkarni - Allahabad, India - athene.org.in/girish -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Fetchmail and Gmail
On Thu, 13 Aug 2009, Ron Johnson wrote: Slightly OT, but when you try again, use the --expunge option so that when you restart fetchmail Yes, this worked. Thanks! -- Girish Kulkarni - Allahabad, India - athene.org.in/girish -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Fetchmail and Gmail
On Sun, 16 Aug 2009, Andrei Popescu wrote: While downloading archived messages (around 20 thousand of them, 800 MB) from my Gmail account via POP3, Fetchmail stopped after fetching 9985 messages. It now keeps saying that there are 549 read messages on the server but clearly, there are many more. Did you check that or are you just assuming? I'm asking because from my experience gmail was *deleting* mails as soon as retrieved via POP3 (but not via IMAP). Yes, my Gmail deletes messages too, when they are retrieved via POP3 (you can make it not to). But I could use their web interface to check that I did indeed have all those unread messages. Fetchmail's option combination 'ssl nokeep expunge 20' seems to be working for me now, although honestly, I don't understand why that should be necessary. Thanks, Girish. -- Girish Kulkarni - Allahabad, India - athene.org.in/girish -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Fetchmail and Gmail
On Mon,17.Aug.09, 18:26:04, Girish Kulkarni wrote: Yes, my Gmail deletes messages too, when they are retrieved via POP3 (you can make it not to). But I could use their web interface to check that I did indeed have all those unread messages. Fetchmail's option combination 'ssl nokeep expunge 20' seems to be working for me now, although honestly, I don't understand why that should be necessary. flame Fetchmail and Gmail both seem strange to me. Getting them to actually work together must be a dark art :) /flame Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Re: Fetchmail and Gmail
On Thu,13.Aug.09, 16:17:30, Girish Kulkarni wrote: Hello, I'm having an issue with Fetchmail and Gmail on my system (Lenny). It will help if someone could help understand what's going on. While downloading archived messages (around 20 thousand of them, 800 MB) from my Gmail account via POP3, Fetchmail stopped after fetching 9985 messages. It now keeps saying that there are 549 read messages on the server but clearly, there are many more. Did you check that or are you just assuming? I'm asking because from my experience gmail was *deleting* mails as soon as retrieved via POP3 (but not via IMAP). Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Re: Fetchmail and Gmail
I don't know if this helps but by default thunderbird will just copy them not delete I have to manually delete emails from my account to sync with what I already downloaded to my machine. On Sun, Aug 16, 2009 at 2:36 PM, Andrei Popescu andreimpope...@gmail.comwrote: On Thu,13.Aug.09, 16:17:30, Girish Kulkarni wrote: Hello, I'm having an issue with Fetchmail and Gmail on my system (Lenny). It will help if someone could help understand what's going on. While downloading archived messages (around 20 thousand of them, 800 MB) from my Gmail account via POP3, Fetchmail stopped after fetching 9985 messages. It now keeps saying that there are 549 read messages on the server but clearly, there are many more. Did you check that or are you just assuming? I'm asking because from my experience gmail was *deleting* mails as soon as retrieved via POP3 (but not via IMAP). Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iQEcBAEBCAAGBQJKiG28AAoJEHNWs3jeoi3pe0IH/1HA5WStNfsCpcVVLmjtZZz/ /qy4DFTwCnu+jwYWxzriUnfv54P8y6YCHEhuzcX6htD/anUVtTpuZwgkLR+Ph8ul Gdz34DtBNKngqBvDK4y62suHKYR9D6bIiMllGzkzkgryGaAbCqCw65aj+nz200rq QXyP2Cln+mudFtA9F6WWtLsI0em0A58laI/+MpVaBTwD8jOVVvcAZf/zqnlrbMcd Ws4VDIwOfY2qgIK4gpA0ItLmJ/NbeFa1OzrTZpbUrUVsPGu4Z9n+beiWaMdAtQG2 eYVTvfNH+cNhE3BVMFbGkB8fdMW7Kcub9QExYXe/1rlylfaODdGuVCpQJZgTLHk= =uDzb -END PGP SIGNATURE-
Re: fetchmail et IPv6 [résolu]
claude a écrit : [...] cat /etc/hosts 127.0.0.1 localhost 192.168.0.40avalokiteshvara.lokaavalokiteshvara # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts Comme dit dans une autre réponse, je vais voir en enlevant la ligne : ::1 localhost ip6-localhost ip6-loopback Après quelques heures, pas d'effets de bord indésirables constatées, donc ça parait être la bonne solution. Pour rappel, fetchmail se plaignait dans mes logs : fetchmail[19825]: Échec de connexion avec localhost:smtp [::1/25] : Connexion refusée. Merci à ceux qui ont répondu. -- Claude Thomassin -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
fetchmail et IPv6
Bonjour, Depuis quelques temps, mes logs font ressortir la ligne suivante : fetchmail[19825]: Échec de connexion avec localhost:smtp [::1/25] : Connexion refusée. J'ai cherché du côté de la doc de fetchmail (man/readme and Co) puis directement sur le site de fetchmail où j'ai trouvé une FAQ pas trop à jour... Mais rien concernant ce problème. Cependant, ça n'a pas été tout à fait inutile puisqu'on j'ai vu qu'on pouvait indiquer à fetchmail par quelle interface passer. La FAQ mentionne une ligne à ajouter dans fetchmailrc : interface eth0/192.168.0.40/255.255.255.0 Je l'ai donc positionné en première ligne dans fetchmailrc et, sans redémarrer fetchmail, ça marchait bien... Sauf que j'ai dû rebooter ma machine et là, plus de mail mais un message d'erreur au lancement de fetchmail pour me dire que la ligne est incorrecte :( Du coup, je l'ai passée en commentaire et fetchmail remarche correctement mais toujours avec ce message qui commence à m'agacer. Une idée pour m'en sortir ? -- Claude Thomassin -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Re: fetchmail et IPv6
claude cthomassin2...@free.fr writes: Bonjour, Bonjour, Depuis quelques temps, mes logs font ressortir la ligne suivante : fetchmail[19825]: Échec de connexion avec localhost:smtp [::1/25] : Connexion refusée. [...] Une idée pour m'en sortir ? En indiquant 127.0.0.1 comme smtphost, cf. : http://lists.berlios.de/pipermail/fetchmail-users/2007-March/000930.html -- Nicolas -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Re: fetchmail et IPv6
Bonjour, On Thu, Aug 13, 2009 at 10:54:30AM +0200, claude wrote: Bonjour, Depuis quelques temps, mes logs font ressortir la ligne suivante : fetchmail[19825]: Échec de connexion avec localhost:smtp [::1/25] : Connexion refusée. J'ai eu le même problème. Je me suis débarrassé de ce message avec : # dpkg-reconfigure -plow exim4-config j'ai supprimé 127.0.0.1 de Liste d'adresses IP où Exim sera en attente de connexions SMTP entrantes : J'ai également laissé en blanc la ligne Autres destinations dont le courriel doit être accepté : Si tu utilises exim, évidemment. A+ -- Pierre Meurisse -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Re: fetchmail et IPv6
Salut, claude a écrit : Depuis quelques temps, mes logs font ressortir la ligne suivante : fetchmail[19825]: Échec de connexion avec localhost:smtp [::1/25] : Connexion refusée. Par pure curiosité, que contient ton fichier /etc/hosts ? -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Re: fetchmail et IPv6
Pierre Meurisse a écrit : [...] Je me suis débarrassé de ce message avec : # dpkg-reconfigure -plow exim4-config j'ai supprimé 127.0.0.1 de Liste d'adresses IP où Exim sera en attente de connexions SMTP entrantes : J'ai également laissé en blanc la ligne Autres destinations dont le courriel doit être accepté : Si tu utilises exim, évidemment. J'utilise Postfix et je ne suis pas certain qu'il soit content si j'enlève localhost. Pour l'instant, j'ai ça dans mon /etc/postfix/main.cf : mynetworks = 127.0.0.0/8 192.168.0.0/24 Je vais tester ça aussi pour voir, on ne sait jamais :D -- Claude Thomassin -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Re: fetchmail et IPv6
Nicolas KOWALSKI a écrit : [...] En indiquant 127.0.0.1 comme smtphost, cf. : http://lists.berlios.de/pipermail/fetchmail-users/2007-March/000930.html Le paramètre smtphost ne semble pas exister dans postif mais, par contre un : postconf | grep smtp me sort pleins de trucs dont : smtp_bind_address = 127.0.0.1 smtp_bind_address6 = Je vais donc tenter la soluce donnée dans le mail que tu m'as indiqué, à savoir désactiver localhost en ipv6. D'ailleurs, pas très au courant en ce qui concerne ipv6, je me demande si ::1 est une adresse valide pour localhost ? Je crois avoir lu (je ne sais plus trop où) que l'entête pour un réseau privé serait plutôt fe80: ? -- Claude Thomassin -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Re: fetchmail et IPv6
Pascal Hambourg a écrit : [...] Par pure curiosité, que contient ton fichier /etc/hosts ? Bizarrement, ma réponse ne semble pas être passé alors je reposte. DSL si ça arrive en double : cat /etc/hosts 127.0.0.1 localhost 192.168.0.40avalokiteshvara.lokaavalokiteshvara # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts Comme dit dans une autre réponse, je vais voir en enlevant la ligne : ::1 localhost ip6-localhost ip6-loopback si cela règle mon pb. Mais dans ce cas, cela ne risque-t-il pas de perturber le fonctionnement en ipv6 ? Pour l'instant, je n'ai pas eu trop le temps de me pencher là-dessus mais c'est dans ma todo-list ;) -- Claude Thomassin -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Re: fetchmail et IPv6
Le 13 août 09 à 15:28, claude a écrit : Je vais donc tenter la soluce donnée dans le mail que tu m'as indiqué, à savoir désactiver localhost en ipv6. D'ailleurs, pas très au courant en ce qui concerne ipv6, je me demande si ::1 est une adresse valide pour localhost ? Je crois avoir lu (je ne sais plus trop où) que l'entête pour un réseau privé serait plutôt fe80: ? ip6-localhost existe, et renvoi sur ::1 Exim4, dans sa configuration, accepte l'IP sous forme 1 Essaye, dans le doute… Damien Clauzel -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Fetchmail and Gmail
Hello, I'm having an issue with Fetchmail and Gmail on my system (Lenny). It will help if someone could help understand what's going on. While downloading archived messages (around 20 thousand of them, 800 MB) from my Gmail account via POP3, Fetchmail stopped after fetching 9985 messages. It now keeps saying that there are 549 read messages on the server but clearly, there are many more. Gmail settings were untouched and Fetchmail is run with proto POP3 and options ssl and nokeep. I've tried toggling nokeep. What could be happening here? Any suggestions how I could correct it? I'm interested in getting all that e-mail via Fetchmail so that Procmail could sort it out nicely for me. Apologies if this is OT. I've had a discussion on the Gmail help forum (www.google.com/support/forum/p/gmail/thread?tid=62df06f1e7b8fd4c) and on #debian. I'm also aware of what the Fetchmail FAQ says about Gmail (fetchmail.berlios.de/fetchmail-FAQ.html#I9) but would like to know if that is indeed what is hitting me here. Thanks, Girish. -- Girish Kulkarni - Allahabad, India - athene.org.in/girish -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Fetchmail and Gmail
On 2009-08-13 16:17 (+0530), Girish Kulkarni wrote: While downloading archived messages (around 20 thousand of them, 800 MB) from my Gmail account via POP3, Fetchmail stopped after fetching 9985 messages. It now keeps saying that there are 549 read messages on the server but clearly, there are many more. Gmail settings were untouched and Fetchmail is run with proto POP3 and options ssl and nokeep. I've tried toggling nokeep. What could be happening here? Any suggestions how I could correct it? I'm interested in getting all that e-mail via Fetchmail so that Procmail could sort it out nicely for me. Maybe the messages are somehow flagged as seen so they are not fetched again. Did you try fetchall option/keyword? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Fetchmail and Gmail
On 2009-08-13 05:47, Girish Kulkarni wrote: Hello, I'm having an issue with Fetchmail and Gmail on my system (Lenny). It will help if someone could help understand what's going on. While downloading archived messages (around 20 thousand of them, 800 MB) from my Gmail account via POP3, Fetchmail stopped after fetching 9985 messages. It now keeps saying that there are 549 read messages on the server but clearly, there are many more. Gmail settings were untouched and Fetchmail is run with proto POP3 and options ssl and nokeep. I've tried toggling nokeep. What could be happening here? Any suggestions how I could correct it? I'm interested in getting all that e-mail via Fetchmail so that Procmail could sort it out nicely for me. Apologies if this is OT. I've had a discussion on the Gmail help forum (www.google.com/support/forum/p/gmail/thread?tid=62df06f1e7b8fd4c) and on #debian. I'm also aware of what the Fetchmail FAQ says about Gmail (fetchmail.berlios.de/fetchmail-FAQ.html#I9) but would like to know if that is indeed what is hitting me here. Slightly OT, but when you try again, use the --expunge option so that when you restart fetchmail -e count | --expunge count (keyword: expunge) Arrange for deletions to be made final after a given number of messages. Under POP2 or POP3, fetchmail cannot make dele‐ tions final without sending QUIT and ending the session -- with this option on, fetchmail will break a long mail retrieval session into multiple sub-sessions, sending QUIT after each sub-session. This is a good defense against line drops on POP3 servers. -- Scooty Puff, Sr The Doom-Bringer -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: fetchmail socket error
On 2009-08-11 17:17 (-0400), Paul Cartwright wrote: I have fetchmail set to fetchall. If I set it to keep, can I use a laptop, setup that account as IMAP on the laptop and also retrieve that same email? I mean setup a kmail account as IMAP.. on the laptop. Yes, you can. The mail will be kept on the server but it will be marked as old or already seen when you read it through fetchmail or laptop's IMAP connection. Already seen old mail won't be fetched twice with fetchmail, unless you use --fetchall (or keyword fetchall in .fetchmailrcc) with fetchmail. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: fetchmail socket error
On Wed August 12 2009, Teemu Likonen wrote: Yes, you can. The mail will be kept on the server but it will be marked as old or already seen when you read it through fetchmail or laptop's IMAP connection. Already seen old mail won't be fetched twice with fetchmail, unless you use --fetchall (or keyword fetchall in .fetchmailrcc) with fetchmail. thanks, that explains what I am looking for, thank you! -- Paul Cartwright Registered Linux user # 367800 Registered Ubuntu User #12459 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: fetchmail socket error
Paul Cartwright schrieb: Aug 10 16:31:47 paulandcilla fetchmail[16965]: timeout after 300 seconds waiting to connect to server email_host.com. fetchmail cannot connect to the server it should poll (your mail domain host). As you can reach that host via webmail (HTTP, Port 80) and IMAP, it does not seem to be a network problem. Maybe the POP3 daemon on that host is not running / running very slowly? How do you poll your mail with fetchmail? Using POP3 or IMAP? If you have configured fetchmail to fetch your mail via POP3, you should try if _that_ works (not only webmail and IMAP). The easiest way would be telnetting to port 110 on your mail domain host and see if you can get a connection. -thh -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: fetchmail socket error
On Tue August 11 2009, Thomas Hochstein wrote: fetchmail cannot connect to the server it should poll (your mail domain host). As you can reach that host via webmail (HTTP, Port 80) and IMAP, it does not seem to be a network problem. Maybe the POP3 daemon on that host is not running / running very slowly? that's what I am thinking.. IMAP in Kontact seems to be working, but I'm getting double emails... How do you poll your mail with fetchmail? Using POP3 or IMAP? If you have configured fetchmail to fetch your mail via POP3, you should try if _that_ works (not only webmail and IMAP). The easiest way would be telnetting to port 110 on your mail domain host and see if you can get a connection. I use POP3. wow.. I just tried to telnet to port 110. 60 seconds later, no connection. tried port 25, responded instantly. can I setup fetchmail for IMAP? -- Paul Cartwright Registered Linux user # 367800 Registered Ubuntu User #12459 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: fetchmail socket error
On Tue, Aug 11, 2009 at 05:48:51AM -0400, Paul Cartwright wrote: On Tue August 11 2009, Thomas Hochstein wrote: fetchmail cannot connect to the server it should poll (your mail domain host). As you can reach that host via webmail (HTTP, Port 80) and IMAP, it does not seem to be a network problem. Maybe the POP3 daemon on that host is not running / running very slowly? that's what I am thinking.. IMAP in Kontact seems to be working, but I'm getting double emails... How do you poll your mail with fetchmail? Using POP3 or IMAP? If you have configured fetchmail to fetch your mail via POP3, you should try if _that_ works (not only webmail and IMAP). The easiest way would be telnetting to port 110 on your mail domain host and see if you can get a connection. I use POP3. wow.. I just tried to telnet to port 110. 60 seconds later, no connection. tried port 25, responded instantly. can I setup fetchmail for IMAP? yes. proto imap man fetchmailrc and there is the question of whether they meant to drop pop3 support. it's possible that it died and they don't know it. A signature.asc Description: Digital signature
Re: fetchmail socket error
On Tue August 11 2009, Andrew Sackville-West wrote: can I setup fetchmail for IMAP? yes. proto imap man fetchmailrc well, I saw IMAP as a fetchmail possibility.. but I guess my guess is more how do I DO IT. with IMAP I thought the server was more like the repository, and your mail client was just the portal to get to it. If I tell fetchmail to use IMAP, I guess I'm not sure how to setup kmail for my 7 accounts that will be coming in via fetchmail. Does that make more better sense? -- Paul Cartwright Registered Linux user # 367800 Registered Ubuntu User #12459 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: fetchmail socket error
On 2009-08-11 16:35 (-0400), Paul Cartwright wrote: If I tell fetchmail to use IMAP, I guess I'm not sure how to setup kmail for my 7 accounts that will be coming in via fetchmail. Does that make more better sense? I have two IMAP accounts but I don't like to store the mail on the remote server so I use fetchmail to fetch all mail on remote servers to my spool file in /var/mail directory. Then my mail client (Gnus) is configured to get mail just from the local spool file and nowhere else. Is this the kind of setup you are looking for? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: fetchmail socket error
On Tue August 11 2009, Teemu Likonen wrote: I have two IMAP accounts but I don't like to store the mail on the remote server so I use fetchmail to fetch all mail on remote servers to my spool file in /var/mail directory. Then my mail client (Gnus) is configured to get mail just from the local spool file and nowhere else. Is this the kind of setup you are looking for? yes, I think that is what I have ended up with! I removed all of my IMAP/POP3 accounts, used fetchmail, setup each account as IMAP, restarted fetchmail, and things seem to be coming in to /var/mail/user and each user has a local account setup in kmail.. I have fetchmail set to fetchall. If I set it to keep, can I use a laptop, setup that account as IMAP on the laptop and also retrieve that same email? I mean setup a kmail account as IMAP.. on the laptop. -- Paul Cartwright Registered Linux user # 367800 Registered Ubuntu User #12459 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: fetchmail socket error
On 2009-08-10 15:36, Paul Cartwright wrote: I have been getting this error, and I'm not sure what it means or what is wrong. I have fetchmail setup to pull the email from my domain accounts to local users. I set this up in a fetchmailrc file. this morning I noticed there was no new email, but when I went to webmail ( squirrelmail) on my hosts servers, there was email . This is the error message I am getting in /var/log/syslog: Aug 10 16:31:47 paulandcilla fetchmail[16965]: timeout after 300 seconds waiting to connect to server email_host.com. Aug 10 16:31:47 paulandcilla fetchmail[16965]: socket error while fetching from my_user_email+my_host@email_host.com Aug 10 16:31:47 paulandcilla fetchmail[16965]: Query status=2 (SOCKET) mail.err has similar messages: Aug 10 16:31:47 paulandcilla fetchmail[16965]: socket error while fetching from my_user_email+my_host@email_host.com The same think occasionally happens to me. Sometimes the messages eventually gets transferred, but sometimes I have to use this python script to delete the offending message from the POP server. import getpass, poplib, string, sys import re import readline def check_re(d, patt_re, patt, s): mo = patt_re.search(s) if mo: d[patt] = s return d M = poplib.POP3('pop.east.cox.net') #M.set_debuglevel(2) try: M.user(sys.argv[1]) except: x = sys.exc_info ()[1] print 'login failed' print x sys.exit() try: M.pass_(sys.argv[2]) except: print sys.exc_info ()[1] sys.exit() from_pattern = re.compile(^from\:) subj_pattern = re.compile(^subject\:) date_pattern = re.compile(^date\:) msft1_pattern = re.compile(\ ^content-disposition: attachment; filename=) try: w = M.list() except: print sys.exc_info ()[1] sys.exit() print w[0] print w[1] print w[2] size_array = w[1] numMessages = len(size_array) print 'Num emails ', numMessages for i in range(1, numMessages+1): d = {'from':'','subj':'','date': '','attach': '','haggis': ''} b = ['==',\ '=='] x = M.top(i, 20) a = string.split(size_array[i-1], ' ') ndx = int(a[0]) bcnt = int(a[1]) b.append(('%d %d' % (ndx, bcnt))) for y in x[1]: y1 = y.lower() d = check_re(d, from_pattern, 'from', y1) d = check_re(d, subj_pattern, 'subj', y1) d = check_re(d, date_pattern, 'date', y1) d = check_re(d, msft1_pattern, 'attach', y1) for c in b: print c print d['from'] print d['subj'] print d['date'] print d['attach'] r = raw_input('Action?[_D_elete,_P_rint,_S_kip,_Q_uit] - ') if r in ('D', 'd'): M.dele(i) if r in ('P', 'p'): txt = M.retr(i)[1] for i in txt: print i if r in ('Q', 'q'): M.quit() sys.exit() M.quit() print '' print '' print '' print '' -- Scooty Puff, Sr The Doom-Bringer -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
fetchmail socket error
I have been getting this error, and I'm not sure what it means or what is wrong. I have fetchmail setup to pull the email from my domain accounts to local users. I set this up in a fetchmailrc file. this morning I noticed there was no new email, but when I went to webmail ( squirrelmail) on my hosts servers, there was email . This is the error message I am getting in /var/log/syslog: Aug 10 16:31:47 paulandcilla fetchmail[16965]: timeout after 300 seconds waiting to connect to server email_host.com. Aug 10 16:31:47 paulandcilla fetchmail[16965]: socket error while fetching from my_user_email+my_host@email_host.com Aug 10 16:31:47 paulandcilla fetchmail[16965]: Query status=2 (SOCKET) mail.err has similar messages: Aug 10 16:31:47 paulandcilla fetchmail[16965]: socket error while fetching from my_user_email+my_host@email_host.com -- Paul Cartwright Registered Linux user # 367800 Registered Ubuntu User #12459 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: fetchmail socket error
Paul Cartwright: this morning I noticed there was no new email, but when I went to webmail ( squirrelmail) on my hosts servers, there was email . This is the error message I am getting in /var/log/syslog: Aug 10 16:31:47 paulandcilla fetchmail[16965]: timeout after 300 seconds waiting to connect to server email_host.com. Either your internet / network connection is down or the server doesn't reply for some reason. J. -- I spend money without thinking on products and clothes that I believe will enhance my social standing. [Agree] [Disagree] http://www.slowlydownward.com/NODATA/data_enter2.html signature.asc Description: Digital signature
Re: fetchmail socket error
On Mon, Aug 10, 2009 at 04:36:00PM -0400, Paul Cartwright wrote: I have been getting this error, and I'm not sure what it means or what is wrong. I have fetchmail setup to pull the email from my domain accounts to local users. I set this up in a fetchmailrc file. this morning I noticed there was no new email, but when I went to webmail ( squirrelmail) on my hosts servers, there was email . This is the error message I am getting in /var/log/syslog: Aug 10 16:31:47 paulandcilla fetchmail[16965]: timeout after 300 seconds waiting to connect to server email_host.com. is the pop or imap server running? A signature.asc Description: Digital signature
Re: fetchmail socket error
On Mon August 10 2009, Jochen Schulz wrote: Aug 10 16:31:47 paulandcilla fetchmail[16965]: timeout after 300 seconds waiting to connect to server email_host.com. Either your internet / network connection is down or the server doesn't reply for some reason. I never lose my internet connection. When I go to mail domain host, and try webmail, I see that there are emails there, yet my debian box gives me this error and doesn't get my emails. I understand webmail and pop3 are different services, I cannot answer about the server.. it does reply, as I can get webmail. do I need to try to telnet to it? -- Paul Cartwright Registered Linux user # 367800 Registered Ubuntu User #12459 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: fetchmail socket error
On Mon August 10 2009, Andrew Sackville-West wrote: is the pop or imap server running? not my box, this is my domain hosting service.. I can log on via webmail and see that there is email there. -- Paul Cartwright Registered Linux user # 367800 Registered Ubuntu User #12459 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: fetchmail socket error
On Mon, Aug 10, 2009 at 06:12:58PM -0400, Paul Cartwright wrote: On Mon August 10 2009, Andrew Sackville-West wrote: is the pop or imap server running? not my box, this is my domain hosting service.. I can log on via webmail and see that there is email there. try telnet to imap or pop3 port. if that fails to connect, then it's a problem on their end, likely. A signature.asc Description: Digital signature
Re: fetchmail socket error
On Mon August 10 2009, Andrew Sackville-West wrote: try telnet to imap or pop3 port. if that fails to connect, then it's a problem on their end, likely. well, I stopped fetchmail, and created an IMAP account ( in kmail) for my user that I had in fetchmail. when I clicked on the inbox of the new imap account, I pulled in 20-30 emails from earlier today... sounds like a fetchmail config issue, but I didn't add/change anything except to add the users.. here is the beginning of my /etc/fetchmailrc ( everything up to the user lines): set daemon300# Pool every 5 minutes set syslog# log through syslog facility set no bouncemail# avoid loss on 4xx errors # on the other hand, 5xx errors get # more dangerous... # Defaults === # Set antispam to -1, since it is far safer to use that together with # no bouncemail defaults: timeout 300 antispam -1 batchlimit 0 -- Paul Cartwright Registered Linux user # 367800 Registered Ubuntu User #12459 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: fetchmail (procmail mutt) : timeout socket error
Le Wednesday 29 July 2009 18:46:21 Michaël Pierson, vous avez écrit : [...] Voici un extrait de '~.fetchmail.log' avec dépassement de délai et erreur socket et 10' plus tard la réception du mail pour ce compte. ... fetchmail: démarrage de fetchmail 6.3.9-rc2 en tâche de fond fetchmail: mise en sommeil à mer 29 jui 2009 12:17:16 CEST pour 300 secondes fetchmail: réveillé à mer 29 jui 2009 12:22:16 CEST fetchmail: 1 message pour x...@gmail.com dans pop.gmail.com (464589 octets). fetchmail: lecture du message x...@gmail.com@gmail-pop.l.google.com:1 parmi 1 (464589 octets) éliminé fetchmail: mise en sommeil à mer 29 jui 2009 12:22:18 CEST pour 300 secondes fetchmail: réveillé à mer 29 jui 2009 12:27:18 CEST fetchmail: délai dépassé après 300 secondes d'attente du serveur mail.voo.be. fetchmail: erreur socket durant la réception de y...@voo.be@mail.voo.be fetchmail: État de la requête=2 (SOCKET) fetchmail: mise en sommeil à mer 29 jui 2009 12:32:20 CEST pour 300 secondes fetchmail: réveillé à mer 29 jui 2009 12:37:20 CEST fetchmail: 1 message pour y...@voo.be dans mail.voo.be (470460 octets). fetchmail: lecture du message y...@voo.be@mrouterout.brutele.be:1 parmi 1 (470460 octets) éliminé fetchmail: mise en sommeil à mer 29 jui 2009 12:37:22 CEST pour 300 secondes ... Tu pourrais montrer la configuration du compte avec 'mail.voo.be' ? C'est un compte imap , pop3 , ... ? Voici l'intégrale de '~/.fetchmailrc': # compte FAI: poll mail.voo.be protocol pop3 username y...@voo.be password aa # 1er compte gmail: poll pop.gmail.com protocol pop3 port 995 username x...@gmail.com password b ssl # 2eme compte gmail: poll pop.gmail.com protocol pop3 port 995 username z...@gmail.com password c ssl Et par la suite, tu utilises 'sendmail', 'procmail' ou un serveur SMTP ? Pour les mails entrants, j'utilise procmail afin de trier, SpamAssassin pour filtrer et enfin Mutt comme lecteur. Pour fixer l'utilisation de procmail avec fetchmail, il est possible d'ajouter cette ligne au début et avant les comptes: defaults mda '/usr/bin/procmail -Y -d %T' sans cette ligne, les messages seront réexpédiés via SMTP vers le serveur localhost (par défaut). Tu as un serveur SMTP actif sur le port 25 qui accepte les messages sans authentification ? D'ailleurs, un excellent moyen pour 'visualiser' comment les paramètres de ton fichier de configuration est interprété est d'utiliser l'option '-V' de fetchmail : % fetchmail -V -f ~/.fetchmailrc Pour les envois, j'utilise Mutt et msmtp pour me connecter à un serveur smtp gmail 'host smtp.gmail.com'. Postfix pour les mails en local. C'est excessif ! Tu as déjà msmtp qui rempli cette tâche !! Pour l'erreur socket, le man de fetchmail dit: An error was encountered when attempting to open a socket to retrieve mail. If you don't know what a socket is, don't worry about it -- just treat this as an 'unrecoverable error'. This error can also be because a protocol fetchmail wants to use is not listed in /etc/services. POP3 est bien un protocole définit dans /etc/services. Nous voilà alors avec une erreur irrécupérable. :( Non. L'erreur pourrait venir par le fait que tu n'utilises pas le paramètre 'mda' en réexpédiant les messages de fetchmail par SMTP au lieu d'utiliser directement procmail. Dans ce cas de figure, il est possible d'utiliser une variable d'environnement an lançant fetchmail de cette manière: % env SOCKS_CONF=/dev/null /usr/bin/fetchmail \ --daemon 300 \ --logfile ~/.fetchmail.log \ --pidfile ~/.fetchmail.pid Il faudrait aussi regarder les logs de Postfix quand fetchmail réinjecte les messages sur le serveur SMTP localhost:25 Tu renvois les messages sur un compte SMTP ? Non. Si il n'y a pas de paramètre mda fixer sur par exemple procmail, les messages sont réexpédies sur ton compte local de ton serveur SMTP. Donc oui. @+ -- (o_ (/)_ S e r g e -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Re: fetchmail (procmail mutt) : timeout socket error
Le jeudi 30 juillet 2009 à 08:11:22, se...@srv0.ath.cx a écrit : Le Wednesday 29 July 2009 18:46:21 Michaël Pierson, vous avez écrit : [...] Voici un extrait de '~.fetchmail.log' avec dépassement de délai et erreur socket et 10' plus tard la réception du mail pour ce compte. ... fetchmail: démarrage de fetchmail 6.3.9-rc2 en tâche de fond fetchmail: mise en sommeil à mer 29 jui 2009 12:17:16 CEST pour 300 secondes fetchmail: réveillé à mer 29 jui 2009 12:22:16 CEST fetchmail: 1 message pour x...@gmail.com dans pop.gmail.com (464589 octets). fetchmail: lecture du message x...@gmail.com@gmail-pop.l.google.com:1 parmi 1 (464589 octets) éliminé fetchmail: mise en sommeil à mer 29 jui 2009 12:22:18 CEST pour 300 secondes fetchmail: réveillé à mer 29 jui 2009 12:27:18 CEST fetchmail: délai dépassé après 300 secondes d'attente du serveur mail.voo.be. fetchmail: erreur socket durant la réception de y...@voo.be@mail.voo.be fetchmail: État de la requête=2 (SOCKET) fetchmail: mise en sommeil à mer 29 jui 2009 12:32:20 CEST pour 300 secondes fetchmail: réveillé à mer 29 jui 2009 12:37:20 CEST fetchmail: 1 message pour y...@voo.be dans mail.voo.be (470460 octets). fetchmail: lecture du message y...@voo.be@mrouterout.brutele.be:1 parmi 1 (470460 octets) éliminé fetchmail: mise en sommeil à mer 29 jui 2009 12:37:22 CEST pour 300 secondes ... Tu pourrais montrer la configuration du compte avec 'mail.voo.be' ? C'est un compte imap , pop3 , ... ? Voici l'intégrale de '~/.fetchmailrc': # compte FAI: poll mail.voo.be protocol pop3 username y...@voo.be password aa # 1er compte gmail: poll pop.gmail.com protocol pop3 port 995 username x...@gmail.com password b ssl # 2eme compte gmail: poll pop.gmail.com protocol pop3 port 995 username z...@gmail.com password c ssl Et par la suite, tu utilises 'sendmail', 'procmail' ou un serveur SMTP ? Pour les mails entrants, j'utilise procmail afin de trier, SpamAssassin pour filtrer et enfin Mutt comme lecteur. Pour fixer l'utilisation de procmail avec fetchmail, il est possible d'ajouter cette ligne au début et avant les comptes: defaults mda '/usr/bin/procmail -Y -d %T' sans cette ligne, les messages seront réexpédiés via SMTP vers le serveur localhost (par défaut). oui: % fetchmail -V -f ~/.fetchmailrc Les messages seront réexpédiés via SMTP vers : localhost (par défaut) après modification: Les messages seront acheminés avec /usr/bin/procmail -Y -d %T. Tu as un serveur SMTP actif sur le port 25 qui accepte les messages sans authentification ? Comment le savoir? D'ailleurs, un excellent moyen pour 'visualiser' comment les paramètres de ton fichier de configuration est interprété est d'utiliser l'option '-V' de fetchmail : % fetchmail -V -f ~/.fetchmailrc Pour les envois, j'utilise Mutt et msmtp pour me connecter à un serveur smtp gmail 'host smtp.gmail.com'. Postfix pour les mails en local. C'est excessif ! Tu as déjà msmtp qui rempli cette tâche !! Oui et je souhaites aborder plusieurs points: 1-Tout d'abord un éclairage: Le MTA Postfix gère le mail en local et l'envoi des mails. Msmtp transmet le mail à un server smtp (ici gmail) qui lui s'occupe de la livraison. Msmtp dit au MUA Mutt de l'appeler à la place du MTA Postfix. Je comprend donc bien que Msmtp fait le job à la place de postfix en ce qui concerne l'envoi des mails. Quid du mail en local? Qui s'en occupe dans ce cas? 2-Revenons une étape en arrière: Msmtp n'est pas installé et je cherche à contacter le server smtp gmail à partir de Mutt. Dans '~/.muttrc' j'utilise la ligne set smtp_url='smtps://x...@gmail.com:z...@smtp.gmail.com:465' qui provoque le message : authentificateurs non disponibles Je ne résoudrait pas ce point mais je le contourne en installant msmtp. J'aimerai revenir sur cette erreur pour comprendre. 3-Revenons encore une étape plus en arrière: J'utilise un seul compte mail: celui de mon FAI. Postfix gère les mails via smtp.voo.be J'adapte le champ From fonction du destinataire avec dans '~/muttrc': send-hook '~C ^...@lists\.debian\.org$''my_hdr From: Michaël Pierson x...@gmail.com' Ces envois sont considérés comme du spam par mon Fai. Il semblerait que celà soit le résultat d'une policy de Gmail indiquant que seul les servers smtp.gmail peuvent délivrer des mails gmail (suis je compréhensible?). 4- Voilà pourquoi actuellement, je cherche à obtenir ( et Msmtp semble être idéal) quelque chose comme: destinataire A j'utilise From x...@gmail.com et smpt gmail avec identifiant XXX destinataire B j'utilise From y...@gmail.com et smpt gmail avec identifiant YYY destinataire C j'utilise From z...@voo.be et smtp.voo.be Pour l'erreur socket, le man de fetchmail dit: An error was encountered when attempting to open a socket to retrieve mail. If you don't know what a socket is, don't
Re: fetchmail (procmail mutt) : timeout socket error
Le Thursday 30 July 2009 15:45:57 Michaël Pierson, vous avez écrit : Le jeudi 30 juillet 2009 à 08:11:22, se...@srv0.ath.cx a écrit : [...] sans cette ligne, les messages seront réexpédiés via SMTP vers le serveur localhost (par défaut). oui: % fetchmail -V -f ~/.fetchmailrc Les messages seront réexpédiés via SMTP vers : localhost (par défaut) après modification: Les messages seront acheminés avec /usr/bin/procmail -Y -d %T. Tu as un serveur SMTP actif sur le port 25 qui accepte les messages sans authentification ? Comment le savoir? C'est normal que le MTA accepte une session SMTP sans authentification sur localhost ou 127.0.0.1. Par contre pour ne pas ouvrir une porte au spam, il doit être soit fermé pour l'extérieure, ou utiliser un mécanisme d'authentification. Pour le tester, avec 'telnet' en local: * légende: - : réponse du serveur; - : envoie d'une commande. % telnet 127.0.0.1 25 Trying localhost ... Connected to localhost (127.0.0.1). Escape character is '^]'. - 220 mail.X ESMTP Exim 4.69 Thu, 30 Jul 2009 16:48:19 +0200 - MAIL FROM:m...@localhost.localdomain - 250 OK - RCPT TO: utilisat...@localhost.localdomain - 250 Accepted - DATA - 354 Enter message, ending with . on a line by itself - Mon message de teste terminé par un point - . - 250 OK id=1MWWwA-0002hZ-HY - QUIT - 221 mail.X closing connection Connection closed by foreign host. Un message de m...@localhost.localdomain a été envoyé à utilisat...@localhost.localdomain. Pour les envois, j'utilise Mutt et msmtp pour me connecter à un serveur smtp gmail 'host smtp.gmail.com'. Postfix pour les mails en local. C'est excessif ! Tu as déjà msmtp qui rempli cette tâche !! Oui et je souhaites aborder plusieurs points: 1-Tout d'abord un éclairage: Le MTA Postfix gère le mail en local et l'envoi des mails. Msmtp transmet le mail à un server smtp (ici gmail) qui lui s'occupe de la livraison. Msmtp dit au MUA Mutt de l'appeler à la place du MTA Postfix. Je comprend donc bien que Msmtp fait le job à la place de postfix en ce qui concerne l'envoi des mails. Quid du mail en local? Qui s'en occupe dans ce cas? Je ne comprends pas bien. Tu veux dire comment envoyer un message avec 'mail' (car avec Mutt c'est bon) ? Du style : % echo 'Mon message texte' | mail -s Object utilisat...@domaine.com Le programme 'mail' utilise '/usr/lib/sendmail' pour l'envoie des messages. Tu peux ajouter un autre chemin pour utiliser 'Msmtp' : * Pour tous: % echo 'set sendmail=/usr/bin/msmtp' /etc/nail.rc * Par utilisateur: % echo 'set sendmail=/usr/bin/msmtp' ~/.mailrc * Ou un lien : /usr/lib/sendmail - /usr/bin/msmtp De même avec Mutt pour qu'il utilise 'Msmtp'. Donc plus besoin de Postfix 2-Revenons une étape en arrière: Msmtp n'est pas installé et je cherche à contacter le server smtp gmail à partir de Mutt. Dans '~/.muttrc' j'utilise la ligne set smtp_url='smtps://x...@gmail.com:z...@smtp.gmail.com:465' qui provoque le message : authentificateurs non disponibles Je ne résoudrait pas ce point mais je le contourne en installant msmtp. J'aimerai revenir sur cette erreur pour comprendre. Moi aussi J'aimerai comprendre. Tu disais qu'avec ton ancêtre (etch) mutt fonctionnait bien. Avec la même configuration ( Msmtp et Postfix ) ? 3-Revenons encore une étape plus en arrière: J'utilise un seul compte mail: celui de mon FAI. Postfix gère les mails via smtp.voo.be J'adapte le champ From fonction du destinataire avec dans '~/muttrc': send-hook '~C ^...@lists\.debian\.org$''my_hdr From: Michaël Pierson x...@gmail.com' Ces envois sont considérés comme du spam par mon Fai. Il semblerait que celà soit le résultat d'une policy de Gmail indiquant que seul les servers smtp.gmail peuvent délivrer des mails gmail (suis je compréhensible?). Si tu postais le message avec les entêtes du message considéré spam, on pourait l'analysé. Aussi en utilisant le service 'echo' de 'cict.fr': % echo teste | mail -s teste robotm...@cict.fr C'est un robot de test de message, il renvoie les entêtes pour bien les analyser. 4- Voilà pourquoi actuellement, je cherche à obtenir ( et Msmtp semble être idéal) quelque chose comme: destinataire A j'utilise From x...@gmail.com et smpt gmail avec identifiant XXX destinataire B j'utilise From y...@gmail.com et smpt gmail avec identifiant YYY destinataire C j'utilise From z...@voo.be et smtp.voo.be * La doc de Mutt en français: http://cedricduval.free.fr/mutt/fr/sitehtml/manual.html Les Muttés de la liste te dirons mieux comment configurer Mutt avec des profiles. * Exemple configuration avec profile en français: http://www.bidon.ca/Mutt.html Il faudrait aussi regarder les logs de Postfix quand fetchmail réinjecte les messages sur le serveur SMTP localhost:25 Dans /var/log/syslog? Il me semble que c'est /var/log/maillog sur debian (?). % grep -E (reject|warning|error|fatal|panic): /var/log/maillog ou % tail -F /var/log
Re: fetchmail (procmail mutt) : timeout socket error
Le Sunday 26 July 2009 12:43:52 Michaël Pierson, vous avez écrit : Le vendredi 24 juillet 2009 à 01:25:47, se...@srv0.ath.cx a écrit : Le Friday 24 July 2009 00:34:30 Michaël Pierson, vous avez écrit : Le mercredi 22 juillet 2009 à 10:24:45, Edi Stojicevic a écrit : * Michaël Pierson michael.y.f.pier...@gmail.com [2009-07-22 19:03:35 +0200] wrote : Je relève mes mails tous les quart d'heure (crontab): */15 * * * * fetchmail --silent Pourquoi ne pas mettre dans ton ~/.fetchmailrc set daemon 900 oui pourquoi pas Ce 22 juillet (à quelques autres reprises) j'ai reçu de Cron Deamon le mail suivant: fetchmail: timeout after 300 seconds waiting for server mail.voo.be. fetchmail: socket error while fetching from *m...@*server* fetchmail: Query status=2 (SOCKET) Jj'ai rien dans /var/log/mail.info et dans /var/log/mail.(err|log) ? non rien du tout * Avec ces lignes ( au debut de ~/.fetchmailrc ): set no syslog set logfile ~/.fetchmail.log Lignes ajoutées le 24 juillet en début de fichier comme recommandé. 2 nouveaux messages mails de Cron Deamon le 25. Je n'ai pas de fichier ~/.fetchmail.log créé. @+ Michaël Salut; Il y a deux manières d'utiliser fetchmail: - mode utilisateur ( un fichier ~/.fetchmailrc par utilisateur ); - mode système ( un unique fichier /etc/fetchmailrc pour tous les utilisateurs et administré par un utilisateur spécifique ou root ). Les paramètres utilisés pour chaque mode sont certaines fois différents, et le mode de lancement différents aussi, mais ils n'utilisent pas un service cron. Celui qui t'intéresse est certainement le mode utilisateur, avec un fichier de configuration placé dans le 'home' de l'utilisateur: ~/.fetchmailrc Pour lancer fetchmail automatiquement en mode 'daemon' lorsque l'utilisateur se connecte ( login ), on utilise soit '~/.bash_login' ou '~/.bash_profile' en y ajoutant: if [ -f ~/.fetchmailrc -a -x /usr/bin/fetchmail ]; then # Vérification des permissions if [ $(stat -c '%U %a' ~/.fetchmailrc) != $USER 600 ]; then chown -h $USER ~/.fetchmailrc chmod -f 0600 ~/.fetchmailrc fi # Si il y a une instance de fetchmail if [ -f ~/.fetchmail.pid ]; then PIDSTATUS=/proc/$(head -n 1 ~/.fetchmail.pid)/status if [ -f $PIDSTATUS -a $(grep fetchmail $PIDSTATUS) ]; then /usr/bin/fetchmail --quit sleep 1 fi fi # Lancement de fetchmail en mode daemon # avec interval entre ramassage de 300 s # et journal des actions. /usr/bin/fetchmail \ --daemon 300 \ --logfile ~/.fetchmail.log \ --pidfile ~/.fetchmail.pid fi Par la suite pour terminer proprement fetchmail en sortant, on ajout à '~/.bash_logout': if [ -f ~/.fetchmail.pid ]; then PIDSTATUS=/proc/$(head -n 1 ~/.fetchmail.pid)/status if [ -f $PIDSTATUS -a $(grep fetchmail $PIDSTATUS) ]; then /usr/bin/fetchmail --quit fi fi @+ -- (o_ (/)_ S e r g e -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Re: fetchmail (procmail mutt) : timeout socket error
Le mercredi 29 juillet 2009 à 08:30:18, se...@srv0.ath.cx a écrit : Le Sunday 26 July 2009 12:43:52 Michaël Pierson, vous avez écrit : Le vendredi 24 juillet 2009 à 01:25:47, se...@srv0.ath.cx a écrit : Le Friday 24 July 2009 00:34:30 Michaël Pierson, vous avez écrit : Le mercredi 22 juillet 2009 à 10:24:45, Edi Stojicevic a écrit : * Michaël Pierson michael.y.f.pier...@gmail.com [2009-07-22 19:03:35 +0200] wrote : Je relève mes mails tous les quart d'heure (crontab): */15 * * * * fetchmail --silent Pourquoi ne pas mettre dans ton ~/.fetchmailrc set daemon 900 oui pourquoi pas Ce 22 juillet (à quelques autres reprises) j'ai reçu de Cron Deamon le mail suivant: fetchmail: timeout after 300 seconds waiting for server mail.voo.be. fetchmail: socket error while fetching from *m...@*server* fetchmail: Query status=2 (SOCKET) Jj'ai rien dans /var/log/mail.info et dans /var/log/mail.(err|log) ? non rien du tout * Avec ces lignes ( au debut de ~/.fetchmailrc ): set no syslog set logfile ~/.fetchmail.log Lignes ajoutées le 24 juillet en début de fichier comme recommandé. 2 nouveaux messages mails de Cron Deamon le 25. Je n'ai pas de fichier ~/.fetchmail.log créé. @+ Michaël Salut; Il y a deux manières d'utiliser fetchmail: - mode utilisateur ( un fichier ~/.fetchmailrc par utilisateur ); - mode système ( un unique fichier /etc/fetchmailrc pour tous les utilisateurs et administré par un utilisateur spécifique ou root ). Les paramètres utilisés pour chaque mode sont certaines fois différents, et le mode de lancement différents aussi, mais ils n'utilisent pas un service cron. Celui qui t'intéresse est certainement le mode utilisateur, avec un fichier de configuration placé dans le 'home' de l'utilisateur: ~/.fetchmailrc Pour lancer fetchmail automatiquement en mode 'daemon' lorsque l'utilisateur se connecte ( login ), on utilise soit '~/.bash_login' ou '~/.bash_profile' en y ajoutant: if [ -f ~/.fetchmailrc -a -x /usr/bin/fetchmail ]; then # Vérification des permissions if [ $(stat -c '%U %a' ~/.fetchmailrc) != $USER 600 ]; then chown -h $USER ~/.fetchmailrc chmod -f 0600 ~/.fetchmailrc fi # Si il y a une instance de fetchmail if [ -f ~/.fetchmail.pid ]; then PIDSTATUS=/proc/$(head -n 1 ~/.fetchmail.pid)/status if [ -f $PIDSTATUS -a $(grep fetchmail $PIDSTATUS) ]; then /usr/bin/fetchmail --quit sleep 1 fi fi # Lancement de fetchmail en mode daemon # avec interval entre ramassage de 300 s # et journal des actions. /usr/bin/fetchmail \ --daemon 300 \ --logfile ~/.fetchmail.log \ --pidfile ~/.fetchmail.pid fi Comme j'utilise zsh, j'ai ajouté ces lignes dans '~.zshrc' Par la suite pour terminer proprement fetchmail en sortant, on ajout à '~/.bash_logout': if [ -f ~/.fetchmail.pid ]; then PIDSTATUS=/proc/$(head -n 1 ~/.fetchmail.pid)/status if [ -f $PIDSTATUS -a $(grep fetchmail $PIDSTATUS) ]; then /usr/bin/fetchmail --quit fi fi Et pour sortir proprement j'ai créé un '~.zshrc_logout' Voici un extrait de '~.fetchmail.log' avec dépassement de délai et erreur socket et 10' plus tard la réception du mail pour ce compte. ... fetchmail: démarrage de fetchmail 6.3.9-rc2 en tâche de fond fetchmail: mise en sommeil à mer 29 jui 2009 12:17:16 CEST pour 300 secondes fetchmail: réveillé à mer 29 jui 2009 12:22:16 CEST fetchmail: 1 message pour x...@gmail.com dans pop.gmail.com (464589 octets). fetchmail: lecture du message x...@gmail.com@gmail-pop.l.google.com:1 parmi 1 (464589 octets) éliminé fetchmail: mise en sommeil à mer 29 jui 2009 12:22:18 CEST pour 300 secondes fetchmail: réveillé à mer 29 jui 2009 12:27:18 CEST fetchmail: délai dépassé après 300 secondes d'attente du serveur mail.voo.be. fetchmail: erreur socket durant la réception de y...@voo.be@mail.voo.be fetchmail: État de la requête=2 (SOCKET) fetchmail: mise en sommeil à mer 29 jui 2009 12:32:20 CEST pour 300 secondes fetchmail: réveillé à mer 29 jui 2009 12:37:20 CEST fetchmail: 1 message pour y...@voo.be dans mail.voo.be (470460 octets). fetchmail: lecture du message y...@voo.be@mrouterout.brutele.be:1 parmi 1 (470460 octets) éliminé fetchmail: mise en sommeil à mer 29 jui 2009 12:37:22 CEST pour 300 secondes ... @+ -- (o_ (/)_ S e r g e -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org -- Lisez la FAQ de la liste avant de poser une question : http
Re: fetchmail (procmail mutt) : timeout socket error
Le Wednesday 29 July 2009 15:15:49 Michaël Pierson, vous avez écrit : Le mercredi 29 juillet 2009 à 08:30:18, se...@srv0.ath.cx a écrit : Le Sunday 26 July 2009 12:43:52 Michaël Pierson, vous avez écrit : Le vendredi 24 juillet 2009 à 01:25:47, se...@srv0.ath.cx a écrit : Le Friday 24 July 2009 00:34:30 Michaël Pierson, vous avez écrit : Le mercredi 22 juillet 2009 à 10:24:45, Edi Stojicevic a écrit : * Michaël Pierson michael.y.f.pier...@gmail.com [2009-07-22 19:03:35 +0200] wrote : Je relève mes mails tous les quart d'heure (crontab): */15 * * * * fetchmail --silent Pourquoi ne pas mettre dans ton ~/.fetchmailrc set daemon 900 oui pourquoi pas Ce 22 juillet (à quelques autres reprises) j'ai reçu de Cron Deamon le mail suivant: fetchmail: timeout after 300 seconds waiting for server mail.voo.be. fetchmail: socket error while fetching from *m...@*server* fetchmail: Query status=2 (SOCKET) Jj'ai rien dans /var/log/mail.info et dans /var/log/mail.(err|log) ? non rien du tout * Avec ces lignes ( au debut de ~/.fetchmailrc ): set no syslog set logfile ~/.fetchmail.log Lignes ajoutées le 24 juillet en début de fichier comme recommandé. 2 nouveaux messages mails de Cron Deamon le 25. Je n'ai pas de fichier ~/.fetchmail.log créé. @+ Michaël Salut; Il y a deux manières d'utiliser fetchmail: - mode utilisateur ( un fichier ~/.fetchmailrc par utilisateur ); - mode système ( un unique fichier /etc/fetchmailrc pour tous les utilisateurs et administré par un utilisateur spécifique ou root ). Les paramètres utilisés pour chaque mode sont certaines fois différents, et le mode de lancement différents aussi, mais ils n'utilisent pas un service cron. Celui qui t'intéresse est certainement le mode utilisateur, avec un fichier de configuration placé dans le 'home' de l'utilisateur: ~/.fetchmailrc Pour lancer fetchmail automatiquement en mode 'daemon' lorsque l'utilisateur se connecte ( login ), on utilise soit '~/.bash_login' ou '~/.bash_profile' en y ajoutant: if [ -f ~/.fetchmailrc -a -x /usr/bin/fetchmail ]; then # Vérification des permissions if [ $(stat -c '%U %a' ~/.fetchmailrc) != $USER 600 ]; then chown -h $USER ~/.fetchmailrc chmod -f 0600 ~/.fetchmailrc fi # Si il y a une instance de fetchmail if [ -f ~/.fetchmail.pid ]; then PIDSTATUS=/proc/$(head -n 1 ~/.fetchmail.pid)/status if [ -f $PIDSTATUS -a $(grep fetchmail $PIDSTATUS) ]; then /usr/bin/fetchmail --quit sleep 1 fi fi # Lancement de fetchmail en mode daemon # avec interval entre ramassage de 300 s # et journal des actions. /usr/bin/fetchmail \ --daemon 300 \ --logfile ~/.fetchmail.log \ --pidfile ~/.fetchmail.pid fi Comme j'utilise zsh, j'ai ajouté ces lignes dans '~.zshrc' Par la suite pour terminer proprement fetchmail en sortant, on ajout à '~/.bash_logout': if [ -f ~/.fetchmail.pid ]; then PIDSTATUS=/proc/$(head -n 1 ~/.fetchmail.pid)/status if [ -f $PIDSTATUS -a $(grep fetchmail $PIDSTATUS) ]; then /usr/bin/fetchmail --quit fi fi Et pour sortir proprement j'ai créé un '~.zshrc_logout' Voici un extrait de '~.fetchmail.log' avec dépassement de délai et erreur socket et 10' plus tard la réception du mail pour ce compte. ... fetchmail: démarrage de fetchmail 6.3.9-rc2 en tâche de fond fetchmail: mise en sommeil à mer 29 jui 2009 12:17:16 CEST pour 300 secondes fetchmail: réveillé à mer 29 jui 2009 12:22:16 CEST fetchmail: 1 message pour x...@gmail.com dans pop.gmail.com (464589 octets). fetchmail: lecture du message x...@gmail.com@gmail-pop.l.google.com:1 parmi 1 (464589 octets) éliminé fetchmail: mise en sommeil à mer 29 jui 2009 12:22:18 CEST pour 300 secondes fetchmail: réveillé à mer 29 jui 2009 12:27:18 CEST fetchmail: délai dépassé après 300 secondes d'attente du serveur mail.voo.be. fetchmail: erreur socket durant la réception de y...@voo.be@mail.voo.be fetchmail: État de la requête=2 (SOCKET) fetchmail: mise en sommeil à mer 29 jui 2009 12:32:20 CEST pour 300 secondes fetchmail: réveillé à mer 29 jui 2009 12:37:20 CEST fetchmail: 1 message pour y...@voo.be dans mail.voo.be (470460 octets). fetchmail: lecture du message y...@voo.be@mrouterout.brutele.be:1 parmi 1 (470460 octets) éliminé fetchmail: mise en sommeil à mer 29 jui 2009 12:37:22 CEST pour 300 secondes ... Tu pourrais montrer la configuration du compte avec 'mail.voo.be' ? C'est un compte imap , pop3 , ... ? Et par la suite, tu utilises 'sendmail', 'procmail' ou un serveur SMTP ? Pour l'erreur socket, le man de fetchmail dit: An error was encountered when attempting to open a socket to retrieve mail. If you don't
Re: fetchmail (procmail mutt) : timeout socket error
Le mercredi 29 juillet 2009 à 04:54:40, se...@srv0.ath.cx a écrit : Le Wednesday 29 July 2009 15:15:49 Michaël Pierson, vous avez écrit : Le mercredi 29 juillet 2009 à 08:30:18, se...@srv0.ath.cx a écrit : Le Sunday 26 July 2009 12:43:52 Michaël Pierson, vous avez écrit : Le vendredi 24 juillet 2009 à 01:25:47, se...@srv0.ath.cx a écrit : Le Friday 24 July 2009 00:34:30 Michaël Pierson, vous avez écrit : Le mercredi 22 juillet 2009 à 10:24:45, Edi Stojicevic a écrit : * Michaël Pierson michael.y.f.pier...@gmail.com [2009-07-22 19:03:35 +0200] wrote : Je relève mes mails tous les quart d'heure (crontab): */15 * * * * fetchmail --silent Pourquoi ne pas mettre dans ton ~/.fetchmailrc set daemon 900 oui pourquoi pas Ce 22 juillet (à quelques autres reprises) j'ai reçu de Cron Deamon le mail suivant: fetchmail: timeout after 300 seconds waiting for server mail.voo.be. fetchmail: socket error while fetching from *m...@*server* fetchmail: Query status=2 (SOCKET) Jj'ai rien dans /var/log/mail.info et dans /var/log/mail.(err|log) ? non rien du tout * Avec ces lignes ( au debut de ~/.fetchmailrc ): set no syslog set logfile ~/.fetchmail.log Lignes ajoutées le 24 juillet en début de fichier comme recommandé. 2 nouveaux messages mails de Cron Deamon le 25. Je n'ai pas de fichier ~/.fetchmail.log créé. @+ Michaël Salut; Il y a deux manières d'utiliser fetchmail: - mode utilisateur ( un fichier ~/.fetchmailrc par utilisateur ); - mode système ( un unique fichier /etc/fetchmailrc pour tous les utilisateurs et administré par un utilisateur spécifique ou root ). Les paramètres utilisés pour chaque mode sont certaines fois différents, et le mode de lancement différents aussi, mais ils n'utilisent pas un service cron. Celui qui t'intéresse est certainement le mode utilisateur, avec un fichier de configuration placé dans le 'home' de l'utilisateur: ~/.fetchmailrc Pour lancer fetchmail automatiquement en mode 'daemon' lorsque l'utilisateur se connecte ( login ), on utilise soit '~/.bash_login' ou '~/.bash_profile' en y ajoutant: if [ -f ~/.fetchmailrc -a -x /usr/bin/fetchmail ]; then # Vérification des permissions if [ $(stat -c '%U %a' ~/.fetchmailrc) != $USER 600 ]; then chown -h $USER ~/.fetchmailrc chmod -f 0600 ~/.fetchmailrc fi # Si il y a une instance de fetchmail if [ -f ~/.fetchmail.pid ]; then PIDSTATUS=/proc/$(head -n 1 ~/.fetchmail.pid)/status if [ -f $PIDSTATUS -a $(grep fetchmail $PIDSTATUS) ]; then /usr/bin/fetchmail --quit sleep 1 fi fi # Lancement de fetchmail en mode daemon # avec interval entre ramassage de 300 s # et journal des actions. /usr/bin/fetchmail \ --daemon 300 \ --logfile ~/.fetchmail.log \ --pidfile ~/.fetchmail.pid fi Comme j'utilise zsh, j'ai ajouté ces lignes dans '~.zshrc' Par la suite pour terminer proprement fetchmail en sortant, on ajout à '~/.bash_logout': if [ -f ~/.fetchmail.pid ]; then PIDSTATUS=/proc/$(head -n 1 ~/.fetchmail.pid)/status if [ -f $PIDSTATUS -a $(grep fetchmail $PIDSTATUS) ]; then /usr/bin/fetchmail --quit fi fi Et pour sortir proprement j'ai créé un '~.zshrc_logout' Voici un extrait de '~.fetchmail.log' avec dépassement de délai et erreur socket et 10' plus tard la réception du mail pour ce compte. ... fetchmail: démarrage de fetchmail 6.3.9-rc2 en tâche de fond fetchmail: mise en sommeil à mer 29 jui 2009 12:17:16 CEST pour 300 secondes fetchmail: réveillé à mer 29 jui 2009 12:22:16 CEST fetchmail: 1 message pour x...@gmail.com dans pop.gmail.com (464589 octets). fetchmail: lecture du message x...@gmail.com@gmail-pop.l.google.com:1 parmi 1 (464589 octets) éliminé fetchmail: mise en sommeil à mer 29 jui 2009 12:22:18 CEST pour 300 secondes fetchmail: réveillé à mer 29 jui 2009 12:27:18 CEST fetchmail: délai dépassé après 300 secondes d'attente du serveur mail.voo.be. fetchmail: erreur socket durant la réception de y...@voo.be@mail.voo.be fetchmail: État de la requête=2 (SOCKET) fetchmail: mise en sommeil à mer 29 jui 2009 12:32:20 CEST pour 300 secondes fetchmail: réveillé à mer 29 jui 2009 12:37:20 CEST fetchmail: 1 message pour y...@voo.be dans mail.voo.be (470460 octets). fetchmail: lecture du message y...@voo.be@mrouterout.brutele.be:1 parmi 1 (470460 octets) éliminé fetchmail: mise en sommeil à mer 29 jui 2009 12:37:22 CEST pour 300 secondes ... Tu pourrais montrer la configuration du compte avec 'mail.voo.be' ? C'est un compte imap , pop3 , ... ? Voici l'intégrale de '~/.fetchmailrc
Re: fetchmail (procmail mutt) : timeout socket error
Le vendredi 24 juillet 2009 à 01:25:47, se...@srv0.ath.cx a écrit : Le Friday 24 July 2009 00:34:30 Michaël Pierson, vous avez écrit : Le mercredi 22 juillet 2009 à 10:24:45, Edi Stojicevic a écrit : * Michaël Pierson michael.y.f.pier...@gmail.com [2009-07-22 19:03:35 +0200] wrote : Je relève mes mails tous les quart d'heure (crontab): */15 * * * * fetchmail --silent Pourquoi ne pas mettre dans ton ~/.fetchmailrc set daemon 900 oui pourquoi pas Ce 22 juillet (à quelques autres reprises) j'ai reçu de Cron Deamon le mail suivant: fetchmail: timeout after 300 seconds waiting for server mail.voo.be. fetchmail: socket error while fetching from *m...@*server* fetchmail: Query status=2 (SOCKET) Jj'ai rien dans /var/log/mail.info et dans /var/log/mail.(err|log) ? non rien du tout * Avec ces lignes ( au debut de ~/.fetchmailrc ): set no syslog set logfile ~/.fetchmail.log Lignes ajoutées le 24 juillet en début de fichier comme recommandé. 2 nouveaux messages mails de Cron Deamon le 25. Je n'ai pas de fichier ~/.fetchmail.log créé. @+ Michaël @+ -- (o_ (/)_ S e r g e -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Re: fetchmail (procmail mutt) : timeout socket error
Le Friday 24 July 2009 00:34:30 Michaël Pierson, vous avez écrit : Le mercredi 22 juillet 2009 à 10:24:45, Edi Stojicevic a écrit : * Michaël Pierson michael.y.f.pier...@gmail.com [2009-07-22 19:03:35 +0200] wrote : Je relève mes mails tous les quart d'heure (crontab): */15 * * * * fetchmail --silent Pourquoi ne pas mettre dans ton ~/.fetchmailrc set daemon 900 oui pourquoi pas Ce 22 juillet (à quelques autres reprises) j'ai reçu de Cron Deamon le mail suivant: fetchmail: timeout after 300 seconds waiting for server mail.voo.be. fetchmail: socket error while fetching from *m...@*server* fetchmail: Query status=2 (SOCKET) Jj'ai rien dans /var/log/mail.info et dans /var/log/mail.(err|log) ? non rien du tout * Avec ces lignes ( au debut de ~/.fetchmailrc ): set no syslog set logfile ~/.fetchmail.log @+ -- (o_ (/)_ S e r g e -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Re: fetchmail (procmail mutt) : timeout socket error
Le mercredi 22 juillet 2009 à 10:24:45, Edi Stojicevic a écrit : * Michaël Pierson michael.y.f.pier...@gmail.com [2009-07-22 19:03:35 +0200] wrote : Je relève mes mails tous les quart d'heure (crontab): */15 * * * * fetchmail --silent Pourquoi ne pas mettre dans ton ~/.fetchmailrc set daemon 900 oui pourquoi pas Ce 22 juillet (à quelques autres reprises) j'ai reçu de Cron Deamon le mail suivant: fetchmail: timeout after 300 seconds waiting for server mail.voo.be. fetchmail: socket error while fetching from *m...@*server* fetchmail: Query status=2 (SOCKET) Jj'ai rien dans /var/log/mail.info et dans /var/log/mail.(err|log) ? non rien du tout -- .''`. Edi Stojicevic : :' : Debian GNU/Linux user, admin developer - http://www.debian.org `. `~' French speaking Debian website founder - http://www.debianworld.org `-GPG Key Id : 0x1237B032 -- -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
fetchmail (procmail mutt) : timeout socket error
Je relève mes mails tous les quart d'heure (crontab): */15 * * * * fetchmail --silent Ce 22 juillet (à quelques autres reprises) j'ai reçu de Cron Deamon le mail suivant: fetchmail: timeout after 300 seconds waiting for server mail.voo.be. fetchmail: socket error while fetching from *m...@*server* fetchmail: Query status=2 (SOCKET) Jj'ai rien dans /var/log/mail.info Le dernier message date du 19 juillet Une idée ou une direction de recherche?
Re: fetchmail (procmail mutt) : timeout socket error
* Michaël Pierson michael.y.f.pier...@gmail.com [2009-07-22 19:03:35 +0200] wrote : Je relève mes mails tous les quart d'heure (crontab): */15 * * * * fetchmail --silent Pourquoi ne pas mettre dans ton ~/.fetchmailrc set daemon 900 Ce 22 juillet (à quelques autres reprises) j'ai reçu de Cron Deamon le mail suivant: fetchmail: timeout after 300 seconds waiting for server mail.voo.be. fetchmail: socket error while fetching from *m...@*server* fetchmail: Query status=2 (SOCKET) Jj'ai rien dans /var/log/mail.info Le dernier message date du 19 juillet Une idée ou une direction de recherche? et dans /var/log/mail.(err|log) ? -- .''`. Edi Stojicevic : :' : Debian GNU/Linux user, admin developer - http://www.debian.org `. `~' French speaking Debian website founder - http://www.debianworld.org `-GPG Key Id : 0x1237B032 -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Re: Help config Postfix Fetchmail Mutt pour Gmail
Michaël Pierson michaelpierso...@gmail.com writes: Hors j'utilise 3 comptes mails différents. Existe t il une solution pour utiliser les *smpt* respectifs? Dans ce cas-là, j'utiliserais msmtp, qui est capable facilement de changer de serveur smtp cible en fonction de l'adresse d'expéditeur. Dans le ~/.muttrc, il *faut* enlever l'option smtp_url, et mettre à la place l'appel à msmtp, plus diverses options qui indiqueront comment invoquer msmtp correctement: set sendmail=/usr/bin/msmtp set use_envelope_from=yes set use_8bitmime set allow_8bit=yes set mime_forward=yes set use_from=yes Puis, dans le ~/.msmtprc, il faut indiquer quels sont les comptes smtp disponibles. Le fichier /usr/share/doc/msmtp/examples/msmtprc-user.example donne un bon exemple des possibilités. -- Nicolas -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Re: Help config Postfix Fetchmail Mutt pour Gmail
Le dimanche 28 juin 2009 à 12:50:48, Nicolas KOWALSKI a écrit : Michaël Pierson michaelpierso...@gmail.com writes: Hors j'utilise 3 comptes mails différents. Existe t il une solution pour utiliser les *smpt* respectifs? Dans ce cas-là, j'utiliserais msmtp, qui est capable facilement de changer de serveur smtp cible en fonction de l'adresse d'expéditeur. Nicolas, c'est ce que je cherche. Je plonge dans la documentation. Merci pour l'aide, Michaël Dans le ~/.muttrc, il *faut* enlever l'option smtp_url, et mettre à la place l'appel à msmtp, plus diverses options qui indiqueront comment invoquer msmtp correctement: set sendmail=/usr/bin/msmtp set use_envelope_from=yes set use_8bitmime set allow_8bit=yes set mime_forward=yes set use_from=yes Puis, dans le ~/.msmtprc, il faut indiquer quels sont les comptes smtp disponibles. Le fichier /usr/share/doc/msmtp/examples/msmtprc-user.example donne un bon exemple des possibilités. -- Nicolas -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Re: Help config Postfix Fetchmail Mutt pour Gmail
Michaël Pierson michael.y.f.pier...@gmail.com writes: Nicolas KOWALSKI a écrit : Michaël Pierson michael.y.f.pier...@gmail.com writes: Bonjour, Bonjour, Je découvre les mails en console et il me reste a configurer l'envoi de mails via smtp.gmail.com en ssl ou tsl port 465 ou 587 avec authentification: nom + mot de passe. Est ce bien /etc/postfix/main.cf qui doit-être modifier?Ou bien uniquement .muttrc? Y a t il d'autres fichiers à modifier? Il existe la variable smtp_url à mettre dans le ~/.muttrc, cf. http://www.mutt.org/doc/devel/manual.html#smtp-url Je pencherais pour une valeur du style: smtp_url=smtps://michael.y.f.pier...@smtp.gmail.com/ set smtp_url='smtps://michael.y.f.pierson:motdepa...@smtp.gmail.com:465/' Mutt me répond La session smtp a échoué : 535 5.7.1http://mail.google.com/support/bin/answer Ce lien ne donne rien... Je viens d'essayer avec: set smtp_url=smtps://nicolas.kowal...@smtp.gmail.com/ Donc, sans numéro de port, et avec le slash terminal. Aucun problème de mon côté ; mutt me demande mon mot de passe, puis le mail est bien envoyé. -- Nicolas -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Re: Help config Postfix Fetchmail Mutt pour Gmail
Le samedi 27 juin 2009 à 09:50:22, Nicolas KOWALSKI a écrit : Michaël Pierson michael.y.f.pier...@gmail.com writes: Nicolas KOWALSKI a écrit : Michaël Pierson michael.y.f.pier...@gmail.com writes: Bonjour, Bonjour, Je découvre les mails en console et il me reste a configurer l'envoi de mails via smtp.gmail.com en ssl ou tsl port 465 ou 587 avec authentification: nom + mot de passe. Est ce bien /etc/postfix/main.cf qui doit-être modifier?Ou bien uniquement .muttrc? Y a t il d'autres fichiers à modifier? Il existe la variable smtp_url à mettre dans le ~/.muttrc, cf. http://www.mutt.org/doc/devel/manual.html#smtp-url Je pencherais pour une valeur du style: smtp_url=smtps://michael.y.f.pier...@smtp.gmail.com/ set smtp_url='smtps://michael.y.f.pierson:motdepa...@smtp.gmail.com:465/' Mutt me répond La session smtp a échoué : 535 5.7.1http://mail.google.com/support/bin/answer Ce lien ne donne rien... Je viens d'essayer avec: set smtp_url=smtps://nicolas.kowal...@smtp.gmail.com/ Donc, sans numéro de port, et avec le slash terminal. Aucun problème de mon côté ; mutt me demande mon mot de passe, puis le mail est bien envoyé. set smtp_url='smtps://michael.y.f.pier...@gmail:mot_de_pa...@smtp.gmail.com:465' Oui Nicolas, celà fonctionne, Merci! Je vous écris en utilisant Mutt. d:-) Dans la doc de mutt; *Setting this variable overrides the value of the $sendmail variable.* Donc tous les envois utilisent *mpt_url* définit ci-dessus... :-| Hors j'utilise 3 comptes mails différents. Existe t il une solution pour utiliser les *smpt* respectifs? -- Nicolas -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Help config Postfix Fetchmail Mutt pour Gmail
Bonjour, Je découvre les mails en console et il me reste a configurer l'envoi de mails via smtp.gmail.com en ssl ou tsl port 465 ou 587 avec authentification: nom + mot de passe. Est ce bien /etc/postfix/main.cf qui doit-être modifier?Ou bien uniquement .muttrc? Y a t il d'autres fichiers à modifier? Pouvez vous m'aider sur la procédure à suivre ou me diriger vers un tutoriel francophone? Voici où j'en suis: Fetchmail récupère les mails pour trois comptes: moncom...@voo.be moncomp...@gmail.com moncomp...@gmail.com ; qui sont ensuite triés par procmail, spamassassin et enfin lus avec Mutt. Postfix est configuré avec le relayhost de mon fai. et gère le mail en local et l'envoi des mails (Il ne s'agit pas d'un vrai serveur de mail avec entrées dns) 10:36 m...@gogol ~% postconf -n                    alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases append_dot_mydomain = no biff = no config_directory = /etc/postfix inet_interfaces = all mailbox_command = procmail -a "$EXTENSION" mailbox_size_limit = 0 mydestination = gogol.brutele.be, localhost.brutele.be, localhost myhostname = gogol.brutele.be mynetworks = 127.0.0.0/8 myorigin = /etc/mailname recipient_delimiter = + relayhost = smtp.voo.be smtp_tls_session_cache_database = btree:${queue_directory}/smtp_scache smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU) smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key smtpd_tls_session_cache_database = btree:${queue_directory}/smtpd_scache smtpd_use_tls = yes unknown_local_recipient_reject_code = 450 Dès qu'il est possible d'envoyer des mails via Gmail, je décommente dans .muttrc la ligne suivante #send-hook '~t Â...@lists\.debian\.org$' 'my_hdr From: moi moncomp...@gmail.com' afin d'utiliser mon adresse gmail abonné aux listes debian (ici je vous écrit en utilisant Icedove - tiens avec Icedove pas besoin de modifier postfix. Pourquoi? Est il possible de faire de même avec mutt? Je suis largé! :-( D'avance merci, Michaël -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs "From" et "Reply-To:" Pour vous DESABONNER, envoyez un message avec comme objet "unsubscribe" vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Help config Postfix Fetchmail Mutt pour Gmail
Bonjour, Je découvre les mails en console et il me reste a configurer l'envoi de mails via smtp.gmail.com en ssl ou tsl port 465 ou 587 avec authentification: nom + mot de passe. Est ce bien /etc/postfix/main.cf qui doit-être modifier?Ou bien uniquement .muttrc? Y a t il d'autres fichiers à modifier? Pouvez vous m'aider sur la procédure à suivre ou me diriger vers un tutoriel francophone? Voici où j'en suis: Fetchmail récupère les mails pour trois comptes: moncom...@voo.be moncomp...@gmail.com moncomp...@gmail.com ; qui sont ensuite triés par procmail, spamassassin et enfin lus avec Mutt. Postfix est configuré avec le relayhost de mon fai. et gère le mail en local et l'envoi des mails (Il ne s'agit pas d'un vrai serveur de mail avec entrées dns) 10:36 m...@gogol ~% postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases append_dot_mydomain = no biff = no config_directory = /etc/postfix inet_interfaces = all mailbox_command = procmail -a $EXTENSION mailbox_size_limit = 0 mydestination = gogol.brutele.be, localhost.brutele.be, localhost myhostname = gogol.brutele.be mynetworks = 127.0.0.0/8 myorigin = /etc/mailname recipient_delimiter = + relayhost = smtp.voo.be smtp_tls_session_cache_database = btree:${queue_directory}/smtp_scache smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU) smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key smtpd_tls_session_cache_database = btree:${queue_directory}/smtpd_scache smtpd_use_tls = yes unknown_local_recipient_reject_code = 450 Dès qu'il est possible d'envoyer des mails via Gmail, je décommente dans .muttrc la ligne suivante #send-hook '~t Â...@lists\.debian\.org$' 'my_hdr From: moi moncomp...@gmail.com' afin d'utiliser mon adresse gmail abonné aux listes debian (ici je vous écrit en utilisant Icedove - tiens avec Icedove pas besoin de modifier postfix. Pourquoi? Est il possible de faire de même avec mutt? Je suis largé! :-( D'avance merci, Michaël -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Re: Help config Postfix Fetchmail Mutt pour Gmail
Michaël Pierson michael.y.f.pier...@gmail.com writes: Bonjour, Bonjour, Je découvre les mails en console et il me reste a configurer l'envoi de mails via smtp.gmail.com en ssl ou tsl port 465 ou 587 avec authentification: nom + mot de passe. Est ce bien /etc/postfix/main.cf qui doit-être modifier?Ou bien uniquement .muttrc? Y a t il d'autres fichiers à modifier? Il existe la variable smtp_url à mettre dans le ~/.muttrc, cf. http://www.mutt.org/doc/devel/manual.html#smtp-url Je pencherais pour une valeur du style: smtp_url=smtps://michael.y.f.pier...@smtp.gmail.com/ -- Nicolas -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Re: Help config Postfix Fetchmail Mutt pour Gmail
Nicolas KOWALSKI a écrit : Michaël Pierson michael.y.f.pier...@gmail.com writes: Bonjour, Bonjour, Je découvre les mails en console et il me reste a configurer l'envoi de mails via smtp.gmail.com en ssl ou tsl port 465 ou 587 avec authentification: nom + mot de passe. Est ce bien /etc/postfix/main.cf qui doit-être modifier?Ou bien uniquement .muttrc? Y a t il d'autres fichiers à modifier? Il existe la variable smtp_url à mettre dans le ~/.muttrc, cf. http://www.mutt.org/doc/devel/manual.html#smtp-url Je pencherais pour une valeur du style: smtp_url=smtps://michael.y.f.pier...@smtp.gmail.com/ set smtp_url='smtps://michael.y.f.pierson:motdepa...@smtp.gmail.com:465/' Mutt me répond "La session smtp a échoué : 535 5.7.1http://mail.google.com/support/bin/answer Ce lien ne donne rien... set smtp_url='smtp://michael.y.f.pier...@gmail.com:motdepa...@smtp.gmail.com:465/' Mutt indique qu'il se connecte à smtp.gmail.com... (sans réaction) -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs "From" et "Reply-To:" Pour vous DESABONNER, envoyez un message avec comme objet "unsubscribe" vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Re: Help config Postfix Fetchmail Mutt pour Gmail
Michaël Pierson wrote: Il existe la variable smtp_url à mettre dans le ~/.muttrc, cf. http://www.mutt.org/doc/devel/manual.html#smtp-url set smtp_url='smtps://michael.y.f.pierson:motdepa...@smtp.gmail.com:465/' Mutt me répond La session smtp a échoué : 535 5.7.1http://mail.google.com/support/bin/answer Ce lien ne donne rien... il ne faut pas mettre de slash à la fin. -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Re: Help config Postfix Fetchmail Mutt pour Gmail
Thomas Harding a écrit : Michaël Pierson wrote: Il existe la variable smtp_url à mettre dans le ~/.muttrc, cf. http://www.mutt.org/doc/devel/manual.html#smtp-url set smtp_url='smtps://michael.y.f.pierson:motdepa...@smtp.gmail.com:465/' Mutt me répond La session smtp a échoué : 535 5.7.1http://mail.google.com/support/bin/answer Ce lien ne donne rien... il ne faut pas mettre de slash à la fin. ok J'ai le message: L'authentification SASL a échoué -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Re: Help config Postfix Fetchmail Mutt pour Gmail
Nicolas KOWALSKI a écrit : Michaël Pierson michael.y.f.pier...@gmail.com writes: Bonjour, Bonjour, Je découvre les mails en console et il me reste a configurer l'envoi de mails via smtp.gmail.com en ssl ou tsl port 465 ou 587 avec authentification: nom + mot de passe. Est ce bien /etc/postfix/main.cf qui doit-être modifier?Ou bien uniquement .muttrc? Y a t il d'autres fichiers à modifier? Il existe la variable smtp_url à mettre dans le ~/.muttrc, cf. http://www.mutt.org/doc/devel/manual.html#smtp-url Je pencherais pour une valeur du style: smtp_url=smtps://michael.y.f.pier...@smtp.gmail.com/ set smtp_url='smtps://michael.y.f.pierson:motdepa...@smtp.gmail.com:465/' Mutt me répond La session smtp a échoué : 535 5.7.1http://mail.google.com/support/bin/answer Ce lien ne donne rien... set smtp_url='smtp://michael.y.f.pier...@gmail.com:motdepa...@smtp.gmail.com:465/' Mutt indique qu'il se connecte à smtp.gmail.com... (sans réaction) -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
squeeze, dns, fetchmail error
How to troubleshoot this error? I've done hours of googling but can't find anything that helps. fetchmail: couldn't find canonical DNS name of pop-server.triad.rr.com (pop-server.triad.rr.com): Name or service not known fetchmail: Query status=11 (DNS) If I replace pop-server.triad.rr.com with the IP in .fetchmailrc, then fetchmail works fine, and very fast. ping and nslookup get the dns done as expected. Here is my ~/.fetchmailrc: # pop-server.triad.rr.com # IP is 71.74.56.73 poll pop-server.triad.rr.com proto pop3 auth password user hlawson password PASSWD sslproto ssl23 Something very similar happens with emacs gnus in relation to its news server. This is a squeeze trial install. My regular Debian is lenny, and it works fine. For some reason, squeeze puts the ethernet interface on eth0, while in lenny it's eth1. Hugh -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: squeeze, dns, fetchmail error
On Wed, 6 May 2009, Hugh Lawson wrote: How to troubleshoot this error? I've done hours of googling but can't find anything that helps. fetchmail: couldn't find canonical DNS name of pop-server.triad.rr.com (pop-server.triad.rr.com): Name or service not known fetchmail: Query status=11 (DNS) If I replace pop-server.triad.rr.com with the IP in .fetchmailrc, then fetchmail works fine, and very fast. ping and nslookup get the dns done as expected. Here is my ~/.fetchmailrc: # pop-server.triad.rr.com # IP is 71.74.56.73 poll pop-server.triad.rr.com proto pop3 auth password user hlawson password PASSWD sslproto ssl23 Something very similar happens with emacs gnus in relation to its news server. This is a squeeze trial install. My regular Debian is lenny, and it works fine. guess: Is all the DNS servers in the resolv.conf correctly reporing the name resolution ? If no can you remove all but one of the DNS entries in the resolv.conf and check if fetchmail works ! Alternatively: You can install strace and check what is exactly happening (you can see the connect command and then who is replying that the DNS resoltion failed etc., ... ) For some reason, squeeze puts the ethernet interface on eth0, while in lenny it's eth1. Hugh -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Bhasker C V Registered linux user #306349 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: squeeze, dns, fetchmail error
Bhasker C V bhas...@unixindia.com writes: On Wed, 6 May 2009, Hugh Lawson wrote: fetchmail: couldn't find canonical DNS name of pop-server.triad.rr.com (pop-server.triad.rr.com): Name or service not known fetchmail: Query status=11 (DNS) Bhasker C V: Is all the DNS servers in the resolv.conf correctly reporing the name resolution ? Yes. Judging by the output of nslookup and ping. Alternatively: You can install strace and check I tried this, but the output was over my head. Another thing. The fetchmail (and gnus) problem is intermittent. Most of the time I get the error as above, but now and then fetchmail works as expected. Remember that this error occurs in a trial install of squeeze. On the same hardware my lenny install, which I'm using now, works fine. I suspect some misconfiguration of the squeeze system as it relates to dns for applications. -- Hugh Lawson hlaw...@triad.rr.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: getmail vs fetchmail, WAS: Re: fetchmail and DNS resolution
On Fri, 2009-04-03 at 16:54 +0300, Andrei Popescu wrote: On Fri,03.Apr.09, 04:22:11, Ron Johnson wrote: On 2009-04-03 02:06, Andrei Popescu wrote: [snip] AFAIK fetchmail defaults to delivering your mail by using a local SMTP. This is a Bad Thing (tm), because it can create a lot of problems, How so? , | NOTE: DO NOT USE sendmail (or any other MTA queue-injection command) AS YOUR | DELIVERY INSTRUCTION. If you're using sendmail, in its capacity as an MTA queue injection command, I think you're not using local SMTP. My fetchmail config does do smtp; it just connects to localhost on port 25. I'm not sure what problems he's referring to with queue injection, but I haven't noticed any with my usage of smtp. Richard -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: getmail vs fetchmail, WAS: Re: fetchmail and DNS resolution
Ron Johnson wrote: On 2009-04-03 08:54, Andrei Popescu wrote: On Fri,03.Apr.09, 04:22:11, Ron Johnson wrote: On 2009-04-03 02:06, Andrei Popescu wrote: [snip] AFAIK fetchmail defaults to delivering your mail by using a local SMTP. This is a Bad Thing (tm), because it can create a lot of problems, YMMV How so? It (fetchmail-Postfix/SpamAssassin-maildrop-~/Maildir) has been working perfectly on my system for 4 years. Let me quote Charles Cazabon (ok, he's the author of getmail, but sure knows a lot about mail handling): Smells of Appeal To Authority. A morally superior person like me would *never* do that It sounds to me like something I just read recently, about the whole 'considered harmful' slag. http://en.wikipedia.org/wiki/Considered_harmful , | NOTE: DO NOT USE sendmail (or any other MTA queue-injection command) AS YOUR | DELIVERY INSTRUCTION. Unless you're a mail expert (and you're not), | re-injection of retrieved mail (with getmail or other agents) is virtually | guaranteed to cause one or more of lost mail, misdirected mail, bad late | bounces, leakage of delivery information, and other problems. ` Maybe getmail has a design flaw, or CC thinks that everyone still uses Sendmail. This was just a few days ago on the official getmail mailing list, in reply to someone asking how to use the MTA for delivery. If you are interested in more details search the archives of the getmail list. What the heck is an MTA for??? Right: transporting mail, usually on port 25. Postfix does a wonderfully boring job of receiving from fetchmail and cron, linking to SpamAssassin, then sending to my MDA. -- J -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
getmail vs fetchmail, WAS: Re: fetchmail and DNS resolution
On Thu April 2 2009, Anthony Campbell wrote: Probably not an answer to the OP, but when I was having trouble with fetchmail a year ago I changed to getmail and the problems went away immediately. It's easier to configure and more reliable. I just recently setup fetchmail on my lenny box. Went to the Falko HOW-TO on sourceforge, copied one of his lines for fetchmailrc, changed it to my info, added the rest of my emails, domain ISP, and all my mail started coming in to my local user account!. It changed my kmail setup to 1 account, from 8. What was easier about getmail? -- Paul Cartwright Registered Linux user # 367800 Registered Ubuntu User #12459 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: getmail vs fetchmail, WAS: Re: fetchmail and DNS resolution
On Thu,02.Apr.09, 06:05:42, Paul Cartwright wrote: On Thu April 2 2009, Anthony Campbell wrote: Probably not an answer to the OP, but when I was having trouble with fetchmail a year ago I changed to getmail and the problems went away immediately. It's easier to configure and more reliable. I just recently setup fetchmail on my lenny box. Went to the Falko HOW-TO on sourceforge, copied one of his lines for fetchmailrc, changed it to my info, added the rest of my emails, domain ISP, and all my mail started coming in to my local user account!. It changed my kmail setup to 1 account, from 8. What was easier about getmail? AFAIK fetchmail defaults to delivering your mail by using a local SMTP. This is a Bad Thing (tm), because it can create a lot of problems, YMMV Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Re: getmail vs fetchmail, WAS: Re: fetchmail and DNS resolution
On 2009-04-03 02:06, Andrei Popescu wrote: [snip] AFAIK fetchmail defaults to delivering your mail by using a local SMTP. This is a Bad Thing (tm), because it can create a lot of problems, YMMV How so? It (fetchmail-Postfix/SpamAssassin-maildrop-~/Maildir) has been working perfectly on my system for 4 years. -- Scooty Puff, Sr The Doom-Bringer -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: getmail vs fetchmail, WAS: Re: fetchmail and DNS resolution
AFAIK fetchmail defaults to delivering your mail by using a local SMTP. This is a Bad Thing (tm), because it can create a lot of problems, YMMV I don't know getmail, but what I like about fetchmail's delivery through the local SMTP server is that I can use procmail to filter my messages. Can getmail do this? - Norbert -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: getmail vs fetchmail, WAS: Re: fetchmail and DNS resolution
Norbert Zeh n...@cs.dal.ca writes: AFAIK fetchmail defaults to delivering your mail by using a local SMTP. This is a Bad Thing (tm), because it can create a lot of problems, YMMV I don't know getmail, but what I like about fetchmail's delivery through the local SMTP server is that I can use procmail to filter my messages. Can getmail do this? Yes, from my getmailrc: , | [destination] | type = MDA_external | path = /usr/bin/procmail | unixfrom = True ` - Norbert Tom -- and everything is plastic and everyone's sarcastic and all your food is frozen, it needs to be defrosted -- Regina Spektor - Ghost of a corporate future -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: getmail vs fetchmail, WAS: Re: fetchmail and DNS resolution
On Fri, Apr 03, 2009 at 07:30 -0300, Norbert Zeh wrote: AFAIK fetchmail defaults to delivering your mail by using a local SMTP. This is a Bad Thing (tm), because it can create a lot of problems, YMMV I don't know getmail, but what I like about fetchmail's delivery through the local SMTP server is that I can use procmail to filter my messages. Can getmail do this? Yes it can. Have a look at: http://pyropus.ca/software/getmail/faq.html#faq-integrating-procmail It basically boils down to the following settings in your getmailrc: --- snip --- [destination] type = MDA_external path = /usr/bin/procmail unixfrom = True --- snip --- I have used this setup for some time now and am quite happy with it. Wolodja signature.asc Description: Digital signature
Re: getmail vs fetchmail, WAS: Re: fetchmail and DNS resolution
On Fri, Apr 3, 2009 at 11:59 AM, Wolodja Wentland wentl...@cl.uni-heidelberg.de wrote: On Fri, Apr 03, 2009 at 07:30 -0300, Norbert Zeh wrote: AFAIK fetchmail defaults to delivering your mail by using a local SMTP. This is a Bad Thing (tm), because it can create a lot of problems, YMMV I don't know getmail, but what I like about fetchmail's delivery through the local SMTP server is that I can use procmail to filter my messages. Can getmail do this? Yes it can. Have a look at: http://pyropus.ca/software/getmail/faq.html#faq-integrating-procmail It basically boils down to the following settings in your getmailrc: --- snip --- [destination] type = MDA_external path = /usr/bin/procmail unixfrom = True --- snip --- I have used this setup for some time now and am quite happy with it. The same is possible in fetchmail with the -m option. /M -- Magnus Therning(OpenPGP: 0xAB4DFBA4) magnus@therning.org Jabber: magnus@therning.org http://therning.org/magnus identi.ca|twitter: magthe -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org