fetchmail-users — User questions and discussion

Re: [fetchmail-users] how to config fetchmail for www.inbox.com email

[Jakob H. <jh...@pl...>]

Quoting Weidong Cui:

Oh, and please put a note at the top of your mails about the C/R-system
you are using, so I won't waste my time by reading them...

Re: [fetchmail-users] how to config fetchmail for www.inbox.com email

[Jakob H. <jh...@pl...>]

Quoting Weidong Cui:

> fetchmail: POP3> TOP 1 99999999
> fetchmail: POP3< -ERR Syntax error, command unrecognized

use the "fetchall" option to make fetmail use RETR instead if the
default TOP.

Hm, TOP is an optional POP3 command (even though strongly encouraged by
the RFC), so maybe fetchmail should fall back if it's not working... or
use RETR by default, using TOP by default is stupid, IMO...

[fetchmail-users] how to config fetchmail for www.inbox.com email

[Weidong C. <cu...@in...>]

Hi, All,
I have a email account at www.inbox.com, but I can not use fetchmail to
received my email from there. Belowed are informations for my fetchmail
configuration and running output. So I read my email via webpage now.

Thanks in advance.

Weidong Cui
cu...@in...
Mon Oct  2 14:08:30 UTC 2006


********************************************************************************
My .fetchmailrc file:

# Configuration created Fri Sep 29 20:37:49 2006 by fetchmailconf 1.52 $Revision: 4740 $
set postmaster "weidong"
set bouncemail
set no spambounce
set properties ""

poll my.inbox.com proto pop3 and options no dns
       user 'cu...@in...' there with password 'passwordxxxxx' is 'weidong' here


fetchmail: 6.3.4 querying my.inbox.com (protocol POP3) at Mon Oct  2 14:12:43 2006: poll started
fetchmail: POP3< +OK WM29.inbox.com POP3 server ready <386...@WM...>
fetchmail: POP3> CAPA
fetchmail: POP3< +OK Capability list follows
fetchmail: POP3< USER
fetchmail: POP3< SASL CRAM-MD5
fetchmail: POP3< UIDL
fetchmail: POP3< APOP
fetchmail: POP3< .
fetchmail: POP3> AUTH CRAM-MD5
fetchmail: POP3< + PDY4MDM0OUE3RjFCM0M4MDhAV00yOS5pbmJveC5jb20+
fetchmail: POP3> Y3Vpd2RAaW5ib3guY29tIGY4MWRhNjZiZGVmNDQ5YTgzNzhlOWQ3YzZmN2VmYmQx
fetchmail: POP3< +OK Authentication successful
fetchmail: POP3> STAT
fetchmail: POP3< +OK 30 101088
fetchmail: POP3> LAST
fetchmail: POP3< -ERR Syntax error, command unrecognized
fetchmail: Syntax error, command unrecognized
fetchmail: POP3> UIDL
fetchmail: POP3< +OK unique-id listing follows
fetchmail: POP3< 1 19
fetchmail: POP3< 2 21
fetchmail: POP3< 3 23
fetchmail: POP3< 4 28
fetchmail: POP3< 5 31
fetchmail: POP3< 6 33
fetchmail: POP3< 7 34
fetchmail: POP3< 8 35
fetchmail: POP3< 9 36
fetchmail: POP3< 10 37
fetchmail: POP3< 11 38
fetchmail: POP3< 12 39
fetchmail: POP3< 13 40
fetchmail: POP3< 14 41
fetchmail: POP3< 15 42
fetchmail: POP3< 16 43
fetchmail: POP3< 17 44
fetchmail: POP3< 18 45
fetchmail: POP3< 19 48
fetchmail: POP3< 20 50
fetchmail: POP3< 21 54
fetchmail: POP3< 22 55
fetchmail: POP3< 23 57
fetchmail: POP3< 24 58
fetchmail: POP3< 25 60
fetchmail: POP3< 26 68
fetchmail: POP3< 27 69
fetchmail: POP3< 28 71
fetchmail: POP3< 29 76
fetchmail: POP3< 30 77
fetchmail: POP3< .
30 messages for cu...@in... at my.inbox.com (101088 octets).
fetchmail: POP3> LIST 1
fetchmail: POP3< +OK 1 1086
fetchmail: POP3> TOP 1 99999999
fetchmail: POP3< -ERR Syntax error, command unrecognized
fetchmail: Syntax error, command unrecognized
fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:1 (1086 octets)
fetchmail: POP3> LIST 2
fetchmail: POP3< +OK 2 4863
fetchmail: POP3> TOP 2 99999999
fetchmail: POP3< -ERR Syntax error, command unrecognized
fetchmail: Syntax error, command unrecognized
fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:2 (4863 octets)
fetchmail: POP3> LIST 3
fetchmail: POP3< +OK 3 1910
fetchmail: POP3> TOP 3 99999999
fetchmail: POP3< -ERR Syntax error, command unrecognized
fetchmail: Syntax error, command unrecognized
fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:3 (1910 octets)
fetchmail: POP3> LIST 4
fetchmail: POP3< +OK 4 3888
fetchmail: POP3> TOP 4 99999999
fetchmail: POP3< -ERR Syntax error, command unrecognized
fetchmail: Syntax error, command unrecognized
fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:4 (3888 octets)
fetchmail: POP3> LIST 5
fetchmail: POP3< +OK 5 8147
fetchmail: POP3> TOP 5 99999999
fetchmail: POP3< -ERR Syntax error, command unrecognized
fetchmail: Syntax error, command unrecognized
fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:5 (8147 octets)
fetchmail: POP3> LIST 6
fetchmail: POP3< +OK 6 2100
fetchmail: POP3> TOP 6 99999999
fetchmail: POP3< -ERR Syntax error, command unrecognized
fetchmail: Syntax error, command unrecognized
fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:6 (2100 octets)
fetchmail: POP3> LIST 7
fetchmail: POP3< +OK 7 2699
fetchmail: POP3> TOP 7 99999999
fetchmail: POP3< -ERR Syntax error, command unrecognized
fetchmail: Syntax error, command unrecognized
fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:7 (2699 octets)
fetchmail: POP3> LIST 8
fetchmail: POP3< +OK 8 5581
fetchmail: POP3> TOP 8 99999999
fetchmail: POP3< -ERR Syntax error, command unrecognized
fetchmail: Syntax error, command unrecognized
fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:8 (5581 octets)
fetchmail: POP3> LIST 9
fetchmail: POP3< +OK 9 2733
fetchmail: POP3> TOP 9 99999999
fetchmail: POP3< -ERR Syntax error, command unrecognized
fetchmail: Syntax error, command unrecognized
fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:9 (2733 octets)
fetchmail: POP3> LIST 10
fetchmail: POP3< +OK 10 2574
fetchmail: POP3> TOP 10 99999999
fetchmail: POP3< -ERR Syntax error, command unrecognized
fetchmail: Syntax error, command unrecognized
fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:10 (2574 octets)
fetchmail: POP3> LIST 11
fetchmail: POP3< +OK 11 2272
fetchmail: POP3> TOP 11 99999999
fetchmail: POP3< -ERR Syntax error, command unrecognized
fetchmail: Syntax error, command unrecognized
fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:11 (2272 octets)
fetchmail: POP3> LIST 12
fetchmail: POP3< +OK 12 2619
fetchmail: POP3> TOP 12 99999999
fetchmail: POP3< -ERR Syntax error, command unrecognized
fetchmail: Syntax error, command unrecognized
fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:12 (2619 octets)
fetchmail: POP3> LIST 13
fetchmail: POP3< +OK 13 2141
fetchmail: POP3> TOP 13 99999999
fetchmail: POP3< -ERR Syntax error, command unrecognized
fetchmail: Syntax error, command unrecognized
fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:13 (2141 octets)
fetchmail: POP3> LIST 14
fetchmail: POP3< +OK 14 3577
fetchmail: POP3> TOP 14 99999999
fetchmail: POP3< -ERR Syntax error, command unrecognized
fetchmail: Syntax error, command unrecognized
fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:14 (3577 octets)
fetchmail: POP3> LIST 15
fetchmail: POP3< +OK 15 3430
fetchmail: POP3> TOP 15 99999999
fetchmail: POP3< -ERR Syntax error, command unrecognized
fetchmail: Syntax error, command unrecognized
fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:15 (3430 octets)
fetchmail: POP3> LIST 16
fetchmail: POP3< +OK 16 2461
fetchmail: POP3> TOP 16 99999999
fetchmail: POP3< -ERR Syntax error, command unrecognized
fetchmail: Syntax error, command unrecognized
fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:16 (2461 octets)
fetchmail: POP3> LIST 17
fetchmail: POP3< +OK 17 2145
fetchmail: POP3> TOP 17 99999999
fetchmail: POP3< -ERR Syntax error, command unrecognized
fetchmail: Syntax error, command unrecognized
fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:17 (2145 octets)
fetchmail: POP3> LIST 18
fetchmail: POP3< +OK 18 5079
fetchmail: POP3> TOP 18 99999999
fetchmail: POP3< -ERR Syntax error, command unrecognized
fetchmail: Syntax error, command unrecognized
fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:18 (5079 octets)
fetchmail: POP3> LIST 19
fetchmail: POP3< +OK 19 3480
fetchmail: POP3> TOP 19 99999999
fetchmail: POP3< -ERR Syntax error, command unrecognized
fetchmail: Syntax error, command unrecognized
fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:19 (3480 octets)
fetchmail: POP3> LIST 20
fetchmail: POP3< +OK 20 2166
fetchmail: POP3> TOP 20 99999999
fetchmail: POP3< -ERR Syntax error, command unrecognized
fetchmail: Syntax error, command unrecognized
fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:20 (2166 octets)
fetchmail: POP3> LIST 21
fetchmail: POP3< +OK 21 2123
fetchmail: POP3> TOP 21 99999999
fetchmail: POP3< -ERR Syntax error, command unrecognized
fetchmail: Syntax error, command unrecognized
fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:21 (2123 octets)
fetchmail: POP3> LIST 22
fetchmail: POP3< +OK 22 2280
fetchmail: POP3> TOP 22 99999999
fetchmail: POP3< -ERR Syntax error, command unrecognized
fetchmail: Syntax error, command unrecognized
fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:22 (2280 octets)
fetchmail: POP3> LIST 23
fetchmail: POP3< +OK 23 4069
fetchmail: POP3> TOP 23 99999999
fetchmail: POP3< -ERR Syntax error, command unrecognized
fetchmail: Syntax error, command unrecognized
fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:23 (4069 octets)
fetchmail: POP3> LIST 24
fetchmail: POP3< +OK 24 4070
fetchmail: POP3> TOP 24 99999999
fetchmail: POP3< -ERR Syntax error, command unrecognized
fetchmail: Syntax error, command unrecognized
fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:24 (4070 octets)
fetchmail: POP3> LIST 25
fetchmail: POP3< +OK 25 8202
fetchmail: POP3> TOP 25 99999999
fetchmail: POP3< -ERR Syntax error, command unrecognized
fetchmail: Syntax error, command unrecognized
fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:25 (8202 octets)
fetchmail: POP3> LIST 26
fetchmail: POP3< +OK 26 2249
fetchmail: POP3> TOP 26 99999999
fetchmail: POP3< -ERR Syntax error, command unrecognized
fetchmail: Syntax error, command unrecognized
fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:26 (2249 octets)
fetchmail: POP3> LIST 27
fetchmail: POP3< +OK 27 2249
fetchmail: POP3> TOP 27 99999999
fetchmail: POP3< -ERR Syntax error, command unrecognized
fetchmail: Syntax error, command unrecognized
fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:27 (2249 octets)
fetchmail: POP3> LIST 28
fetchmail: POP3< +OK 28 2496
fetchmail: POP3> TOP 28 99999999
fetchmail: POP3< -ERR Syntax error, command unrecognized
fetchmail: Syntax error, command unrecognized
fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:28 (2496 octets)
fetchmail: POP3> LIST 29
fetchmail: POP3< +OK 29 4344
fetchmail: POP3> TOP 29 99999999
fetchmail: POP3< -ERR Syntax error, command unrecognized
fetchmail: Syntax error, command unrecognized
fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:29 (4344 octets)
fetchmail: POP3> LIST 30
fetchmail: POP3< +OK 30 4055
fetchmail: POP3> TOP 30 99999999
fetchmail: POP3< -ERR Syntax error, command unrecognized
fetchmail: Syntax error, command unrecognized
fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:30 (4055 octets)
fetchmail: POP3> QUIT
fetchmail: POP3< +OK WM29.inbox.com POP3 server signing off
fetchmail: 6.3.4 querying my.inbox.com (protocol POP3) at Mon Oct  2 14:13:37 2006: poll completed
fetchmail: normal termination, status 1

Re: [fetchmail-users] Fetchmail forwarding

[Michelle K. <lin...@fr...>]

Wha not install procmail and configure it as MDA for fetchmail?

Then add the following singel recipe to your ~/.procmailrc

   :0
   ! you...@gm...


Greetings
    Michelle Konzack
    Systemadministrator
    Tamay Dogan Network
    Debian GNU/Linux Consultant


-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/
##################### Debian GNU/Linux Consultant #####################
Michelle Konzack   Apt. 917                  ICQ #328449886
                   50, rue de Soultz         MSM LinuxMichi
0033/6/61925193    67100 Strasbourg/France   IRC #Debian (irc.icq.com)

Re: [fetchmail-users] fetchmail can't talk to dovecot

[Michelle K. <lin...@fr...>]

Am 2006-09-30 17:48:49, schrieb M. Fioretti:

> Being too clever for my own good, I have the home computer in such a
> state, thanks to a lot of experiments, that I cannot install other
> clients without a lot of work (my fault, yes). However, I have the

???

I see you are using mutt 1.5.9 so why not try

    imaps://youraccount@server.tld
    imap://youraccount@server.tld
    pop3://youraccount@server.tld


Greetings
    Michelle Konzack
    Systemadministrator
    Tamay Dogan Network
    Debian GNU/Linux Consultant


-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/
##################### Debian GNU/Linux Consultant #####################
Michelle Konzack   Apt. 917                  ICQ #328449886
                   50, rue de Soultz         MSM LinuxMichi
0033/6/61925193    67100 Strasbourg/France   IRC #Debian (irc.icq.com)

Re: [fetchmail-users] fetchmail can't talk to dovecot

[Rob M. <rob...@gm...>]

On 9/30/06, M. Fioretti <mfi...@mc...> wrote:
> Here is the log:
>
> Sep 30 15:04:19 fm dovecot: Dovecot v1.0.rc7 starting up
> Sep 30 15:04:22 fm dovecot: auth(default): passwd-file /etc/dovecot_user_file: Read 1 users
> Sep 30 15:05:05 fm dovecot: auth(default): client in: AUTH      1       PLAIN   service=IMAPsecured  lip=::ffff:SERVER_IP_HERE rip=::ffff:CLient_IP_HERE       resp=LONG_STRING_HERE             VDBB
> Sep 30 15:05:05 fm dovecot: auth(default): passwd-file(user_name,::ffff:CLIENT_IP_HERE): unknown user
> Sep 30 15:05:07 fm dovecot: auth(default): client out: FAIL     1       user=user_name
> Sep 30 15:05:07 fm dovecot: imap-login: Aborted login: user=<user_name>, method=PLAIN, rip=::ffff:CLIENT_IP_HERE, lip=::ffff:SERVER_IP_HERE, TLS

Now, repeat with squirrelmail - I suspect you'll ffind either that
squirrelmail isn't using PLAIN, or is but not using TLS.  Worth
checking that you've allowed PLAIN in the auth methods for dovecot.

Alternatively, you're authenticating this with SASL and you need to
set the correct domain for authentication.

-- 
                 Please keep list traffic on the list.

Rob MacGregor
      Whoever fights monsters should see to it that in the process he
        doesn't become a monster.                  Friedrich Nietzsche

Re: [fetchmail-users] fetchmail can't talk to dovecot

[M. F. <mfi...@mc...>]

On Sat, Sep 30, 2006 21:30:52 PM +0200, Matthias Andree
(mat...@gm...) wrote:

> > of course, but the password should be the same, shouldn't it?
> 
> That depends on Dovecot configuration and is outside the scope of the
> fetchmail lists.
> Anyways, see <http://www.fetchmail.info/fetchmail-FAQ.html#K6>
 
just tried. sslproto ssl23 doesn't change anything.

In any case, I had already signalled the problem both here and on the
dovecot list, since I didn't know where to start from and, for all I
know, I could have made errors on both sides. Still not sure that that
is not the case...

Ciao,
	Marco

-- 
Marco Fioretti                    mfioretti, at the server mclink.it
Fedora Core 3 for low memory      http://www.rule-project.org/

Needs are a function of what other people have.

Re: [fetchmail-users] fetchmail can't talk to dovecot

[M. F. <mfi...@mc...>]

On Sat, Sep 30, 2006 17:38:37 PM +0100, Rob MacGregor
(rob...@gm...) wrote:

> Yes, but my point is that dovecot does not necessarily accept the
> authentication method that fetchmail is trying to use from a remote
> host (or even a local one).
> 
> I would advise you do the following:
> 
> 1) Increase the logging level on the dovecot server.  That will tell
> you why the connection is failing.

Done, see result below. Comments are welcome. THanks a lot also for
suggesting this:

> 2) Install fetchmail locally on the dovecot server.  Try doing a
> mail check both against localhost and it's external IP.

I'll do it tomorrow, if still needed (must really leave the keyboard
now).

Here is the log:

Sep 30 15:04:19 fm dovecot: Dovecot v1.0.rc7 starting up
Sep 30 15:04:22 fm dovecot: auth(default): passwd-file /etc/dovecot_user_file: Read 1 users
Sep 30 15:05:05 fm dovecot: auth(default): client in: AUTH      1       PLAIN   service=IMAPsecured  lip=::ffff:SERVER_IP_HERE rip=::ffff:CLient_IP_HERE       resp=LONG_STRING_HERE             VDBB
Sep 30 15:05:05 fm dovecot: auth(default): passwd-file(user_name,::ffff:CLIENT_IP_HERE): unknown user
Sep 30 15:05:07 fm dovecot: auth(default): client out: FAIL     1       user=user_name
Sep 30 15:05:07 fm dovecot: imap-login: Aborted login: user=<user_name>, method=PLAIN, rip=::ffff:CLIENT_IP_HERE, lip=::ffff:SERVER_IP_HERE, TLS

TIA,
	Marco

Re: [fetchmail-users] TwoAccounts

[Matthias A. <mat...@gm...>]

"Andrea Bencini" <and...@ti...> writes:

>> Good, just remember to run "newaliases" 
>
> I run "postalias" because I have "postfix".

Shouldn't make a difference if you're doing it properly.
Postfix runs postalias on the $alias_databases if you type "newaliases"... :-)

-- 
Matthias Andree

Re: [fetchmail-users] fetchmail can't talk to dovecot

[Matthias A. <mat...@gm...>]

"M. Fioretti" <mfi...@mc...> writes:

> What else could it be?
>
>> (Note that using squirrelmail doesn't necessarily test the same
>> connection methods,
>
> of course, but the password should be the same, shouldn't it?

That depends on Dovecot configuration and is outside the scope of the
fetchmail lists.
Anyways, see <http://www.fetchmail.info/fetchmail-FAQ.html#K6>

-- 
Matthias Andree

Re: [fetchmail-users] Fetchmail forwarding

[Rob M. <rob...@gm...>]

On 9/30/06, Spam Me <wel...@gm...> wrote:
> Hello,
> I appologize if this has been asked before, but I've search the archives and
> found no solution.

Well, output of "fetchmail -v -v -v" would be useful so we can work
out where it's going wrong.  You may also need to set smtpaddress and
provide a delivery destination in the poll line.

Output of "fetchmail --configdump" to show what fetchmail thinks of
your config would be handy too - don't forget to munge passwords.

-- 
                 Please keep list traffic on the list.

Rob MacGregor
      Whoever fights monsters should see to it that in the process he
        doesn't become a monster.                  Friedrich Nietzsche

Re: [fetchmail-users] fetchmail can't talk to dovecot

[Matthias A. <mat...@gm...>]

Marco Fioretti <mfi...@mc...> writes:

> Hello,
>
> I have dovecot q1.0-0_22.rc7 up and running on a server: I can read
> email from squirrelmail just fine. When I try to download email with
> fetchmail, however, I get the result below. Why is that happening? In
> dovecot.conf I have:
>
> protocols = imap imaps pop3,
>
> so why should pop3 or imap fail?

Because Dovecot offers TLS (STLS/STARTTLS) and fetchmail uses it..

> fetchmail: POP3> STLS
> fetchmail: POP3< +OK Begin TLS negotiation now.

> fetchmail: IMAP> A0003 CAPABILITY
> fetchmail: IMAP< * CAPABILITY IMAP4rev1 SASL-IR SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDRE
> N NAMESPACE LOGIN-REFERRALS AUTH=PLAIN AUTH=DIGEST-MD5
> fetchmail: IMAP< A0003 OK Capability completed.
> fetchmail: Protocol identified as IMAP4 rev 1
> fetchmail: IMAP> A0004 LOGIN "user_name" *
> fetchmail: IMAP< A0004 NO Authentication failed.
> fetchmail: IMAP> A0005 *

Whatever this is. Something's wrong here, but I'm not going to look at 6.3.2.

-- 
Matthias Andree

Re: [fetchmail-users] Fetchmail forwarding

[Matthias A. <mat...@gm...>]

"Spam Me" <wel...@gm...> writes:

> Hello,
> I appologize if this has been asked before, but I've search the archives and found no solution.
>
> What I'd like to do is have fetchmail collect mail from all my various email accounts, and forward everything to my gmail account.  I've
> been able to get the polling working properly, however I can't get the messages properly forwarding to my gmail account.  I was just
> wondering if I've set the smtp variables correctly (see .fetchmailrc included below)?  If i remove the two smtp lines, fetchmail happily
> runs and exits with no errors (however since I dont have any email software installed locally the mail doesn't actually go anywhere). 
> However, when I add the smtp lines the software hangs on the "reading message add...@gm...@gmail-pop.l.google.com:1 of 11 (2020
> octets)" line.

Please see http://www.fetchmail.info/fetchmail-FAQ.html#G3 -- and don't
post HTML to lists.

-- 
Matthias Andree

[fetchmail-users] Fetchmail forwarding

[Spam M. <wel...@gm...>]

Hello,
I appologize if this has been asked before, but I've search the archives and
found no solution.

What I'd like to do is have fetchmail collect mail from all my various email
accounts, and forward everything to my gmail account.  I've been able to get
the polling working properly, however I can't get the messages properly
forwarding to my gmail account.  I was just wondering if I've set the smtp
variables correctly (see .fetchmailrc included below)?  If i remove the two
smtp lines, fetchmail happily runs and exits with no errors (however since I
dont have any email software installed locally the mail doesn't actually go
anywhere).  However, when I add the smtp lines the software hangs on the
"reading message add...@gm...@gmail-pop.l.google.com:1 of 11 (2020
octets)" line.

I'm using version 6.3.2, and my .fetchmailrc is below (where I want to
collect messages from address1 and forward them to address 2):

poll pop.gmail.com
  proto POP3
  port 995
  user 'add...@gm...'
  ssl

smtphost 'smtp1.sympatico.ca'
smtpname 'add...@gm...'

fetchall
keep

Thanks for any help!
Dan

Re: [fetchmail-users] fetchmail can't talk to dovecot

[Rob M. <rob...@gm...>]

On 9/30/06, M. Fioretti <mfi...@mc...> wrote:
> Being too clever for my own good, I have the home computer in such a
> state, thanks to a lot of experiments, that I cannot install other
> clients without a lot of work (my fault, yes). However, I have the
> password stored in the browser, so I don't have to type it every time
> I check email with squirrelmail. I have looked at what firefox
> transmits thanks to the live http headers extension.
>
> The same password which, sent to squirrelmail via the form, works,
> doesn't work if I copy it (correcting urlencoding, of course) into the
> fetchmail script...
>
> What else could it be?

Lots of things, not least being the authentication method used and the
configuration of dovecot.

I should point out that, given that your install of fetchmail works
against other remote servers the problem is almost certainly related
to the configuration of the dovecot server.

> of course, but the password should be the same, shouldn't it?

Yes, but my point is that dovecot does not necessarily accept the
authentication method that fetchmail is trying to use from a remote
host (or even a local one).

I would advise you do the following:

1) Increase the logging level on the dovecot server.  That will tell
you why the connection is failing.

2) Install fetchmail locally on the dovecot server.  Try doing a mail
check both against localhost and it's external IP.

3) Try any other remote client from the linux box.

At the very least you need to do (1).  Until you do that we don't know
why the dovecot server isn't accepting the connections.

-- 
                 Please keep list traffic on the list.

Rob MacGregor
      Whoever fights monsters should see to it that in the process he
        doesn't become a monster.                  Friedrich Nietzsche

Re: [fetchmail-users] fetchmail can't talk to dovecot

[M. F. <mfi...@mc...>]

On Wed, Sep 27, 2006 17:04:05 PM +0100, Rob MacGregor
(rob...@gm...) wrote:

> Well, one quick test would be to use any other IMAP/POP client (from
> the home linux PC) against the remote server to confirm that the
> username/password are correct.

Being too clever for my own good, I have the home computer in such a
state, thanks to a lot of experiments, that I cannot install other
clients without a lot of work (my fault, yes). However, I have the
password stored in the browser, so I don't have to type it every time
I check email with squirrelmail. I have looked at what firefox
transmits thanks to the live http headers extension.

The same password which, sent to squirrelmail via the form, works,
doesn't work if I copy it (correcting urlencoding, of course) into the
fetchmail script...

What else could it be?

> (Note that using squirrelmail doesn't necessarily test the same
> connection methods,

of course, but the password should be the same, shouldn't it?

TIA,
	Marco

-- 
Marco Fioretti                    mfioretti, at the server mclink.it
Fedora Core 3 for low memory      http://www.rule-project.org/

The biggest problem with communication is the illusion that it has occurred
                                                           read on Slashdot

Re: [fetchmail-users] fetchmail can't talk to dovecot

[Rob M. <rob...@gm...>]

On 9/27/06, Marco Fioretti <mfi...@mc...> wrote:
>
> In which way? My understanding is that, with those settings, secure
> connection should be tried but, if failing, unsecure one would be used
> without problems. That's why I wrote what I wrote? Where am I wrong here?

I have exactly zero experience of dovecot, so couldn't tell you.  Some
POP/IMAP servers however default to requiring SSL for unsecure auth
methods.

> No, sorry. The remote server runs postfix + dovecot + squirrelmail just fine.
> Fetchmail runs on my _home_ linux PC: it works fine with other accounts on _other_
> servers (all pop3) which I do not administer. Only on this box which I'm setting
> up myself there is this problem between the home fetchmail and the remote dovecot.
>
> I'll try the test and settings you suggested tonight at home and report. In the
> meantime any feedback (especially to my answers in this message) is greatly appreciated.

Well, one quick test would be to use any other IMAP/POP client (from
the home linux PC) against the remote server to confirm that the
username/password are correct.

(Note that using squirrelmail doesn't necessarily test the same
connection methods, squirrelmail may be configured to use the loopback
interface, which may have different, eg lower, security settings).

-- 
                 Please keep list traffic on the list.

Rob MacGregor
      Whoever fights monsters should see to it that in the process he
        doesn't become a monster.                  Friedrich Nietzsche

Re: [fetchmail-users] fetchmail can't talk to dovecot

[Marco F. <mfi...@mc...>]

Rob wrote:

> > (I'll fix the certificates problem after I've managed to get 
> > in successfully with plain imap or pop3)
> 
> They may be linked.

In which way? My understanding is that, with those settings, secure
connection should be tried but, if failing, unsecure one would be used
without problems. That's why I wrote what I wrote? Where am I wrong here?

> > (note: fetchmail is regularly working on other accounts)
> 
> On this server?  If so it points directly to a username/password
> mismatch between the server and fetchmail.

No, sorry. The remote server runs postfix + dovecot + squirrelmail just fine.
Fetchmail runs on my _home_ linux PC: it works fine with other accounts on _other_
servers (all pop3) which I do not administer. Only on this box which I'm setting
up myself there is this problem between the home fetchmail and the remote dovecot.

I'll try the test and settings you suggested tonight at home and report. In the
meantime any feedback (especially to my answers in this message) is greatly appreciated.

Ciao,
Marco

Re: [fetchmail-users] fetchmail can't talk to dovecot

[Rob M. <rob...@gm...>]

On 9/27/06, Marco Fioretti <mfi...@mc...> wrote:
> Hello,
>
> I have dovecot q1.0-0_22.rc7 up and running on a server: I can read
> email from squirrelmail just fine. When I try to download email with
> fetchmail, however, I get the result below. Why is that happening? In
> dovecot.conf I have:
>
> protocols = imap imaps pop3,
>
> so why should pop3 or imap fail? Where should I look?
>
> (I'll fix the certificates problem after I've managed to get in
> successfully with plain imap or pop3)

They may be linked.

> (note: fetchmail is regularly working on other accounts)

On this server?  If so it points directly to a username/password
mismatch between the server and fetchmail.

The errors provided by fetchmail suggest you're either requiring
SSL/TLS for logins or you've got an error in the username or password
in the fetchmail config.

I'd advise you increase the logging level on the server and retry.

-- 
                 Please keep list traffic on the list.

Rob MacGregor
      Whoever fights monsters should see to it that in the process he
        doesn't become a monster.                  Friedrich Nietzsche

[fetchmail-users] fetchmail can't talk to dovecot

[Marco F. <mfi...@mc...>]

Hello,

I have dovecot q1.0-0_22.rc7 up and running on a server: I can read
email from squirrelmail just fine. When I try to download email with
fetchmail, however, I get the result below. Why is that happening? In
dovecot.conf I have:

protocols = imap imaps pop3,

so why should pop3 or imap fail? Where should I look?

(I'll fix the certificates problem after I've managed to get in
successfully with plain imap or pop3)

(note: fetchmail is regularly working on other accounts)

Thanks,

	Marco

fetchmail: 6.3.2 querying my.server (protocol POP3) at Wed 27 Sep 2006 12:15:17 AM CEST: poll started
fetchmail: POP3< +OK Dovecot ready.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK
fetchmail: POP3< CAPA
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< STLS
fetchmail: POP3< USER
fetchmail: POP3< SASL PLAIN DIGEST-MD5
fetchmail: POP3< .
fetchmail: POP3> STLS
fetchmail: POP3< +OK Begin TLS negotiation now.
fetchmail: Issuer Organization: SomeOrganization
fetchmail: Issuer CommonName: localhost.localdomain
fetchmail: Server CommonName: localhost.localdomain
fetchmail: Server CommonName mismatch: localhost.localdomain != my.server
fetchmail: my.server key fingerprint: ...
fetchmail: Server certificate verification error: self signed certificate
fetchmail: POP3> CAPA
fetchmail: POP3< +OK
fetchmail: POP3< CAPA
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< USER
fetchmail: POP3< SASL PLAIN DIGEST-MD5
fetchmail: POP3< .
fetchmail: POP3> USER user_name
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< -ERR Authentication failed.
fetchmail: Authentication failed.
fetchmail: Authorization failure on user_name at my.server
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Logging out
fetchmail: 6.3.2 querying my.server (protocol POP3) at Wed 27 Sep 2006 12:15:21 AM CEST: poll completed
fetchmail: Query status=3 (AUTHFAIL)
fetchmail: Writing fetchids file.
fetchmail: normal termination, status 3
fetchmail: Writing fetchids file.

if I try with IMAP the part after the certificate verification error is:

fetchmail: IMAP> A0003 CAPABILITY
fetchmail: IMAP< * CAPABILITY IMAP4rev1 SASL-IR SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDRE
N NAMESPACE LOGIN-REFERRALS AUTH=PLAIN AUTH=DIGEST-MD5
fetchmail: IMAP< A0003 OK Capability completed.
fetchmail: Protocol identified as IMAP4 rev 1
fetchmail: IMAP> A0004 LOGIN "user_name" *
fetchmail: IMAP< A0004 NO Authentication failed.
fetchmail: IMAP> A0005 *
fetchmail: Authorization failure on user_name at my.server
fetchmail: IMAP> A0006 LOGOUT
fetchmail: IMAP< A0005 BAD Error in IMAP command received by server.
fetchmail: IMAP< * BYE Logging out

and I don't see any error message related to this in the server log.

Re: [fetchmail-users] TwoAccounts

[Andrea B. <and...@ti...>]

> Good, just remember to run "newaliases" 

I run "postalias" because I have "postfix".

bye
Andrea

Re: [fetchmail-users] TwoAccounts

[Matthias A. <mat...@gm...>]

"Andrea Bencini" <and...@ti...> writes:

>> But doesn't work on qmail --
>
> My MTA is postfix.

Good, just remember to run "newaliases" after the changes to the aliases
file (and be sure to set alias_maps and alias_database correctly and to
edit the right file).

-- 
Matthias Andree

[fetchmail-users] fetchmail 6.3.5-beta3 snapshot

[Matthias A. <mat...@gm...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Greetings,

I have uploaded a new fetchmail beta 6.3.5-beta3 snapshot to a temporary
download location: <http://www.dt.e-technik.uni-dortmund.de/~ma/fetchmail/>

Changes in fetchmail 6.3.5-beta3 since 6.3.5-beta2:

* Avoid crash in env.c/host_fqdn if we cannot canonicalize our own hostname.
  Reported by Alexander Holler.
* SSL fix by Miloslav Trmac (Red Hat): free the SSL contexts after the
  connection, to avoid from growing SSL certpaths without bounds, avoid using
  SSL contexts for unrelated connections, and to fix Red Hat Bug #206346.
* When going to sleep, log for how long.  Suggested by Claudia Ludwig.
* Catalan/ca (Ernest Adrogué Calveras), Japanese/ja (Takeshi Hamasaki) - also
  made gettext 0.15 ready, Polish/pl (Jakub Bogusz), Russian/ru (Pavel
  Maryanov), Spanish/es (Héctor García Álvarez), Vietnamese/vi (Clytie Siddall)

Happy fetching,
Matthias Andree
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFFGFsivmGDOQUufZURAqhNAJ0QMXKB2d+YvI0hcJjDxgCHzDy4HwCgujiI
gDwT8x3wcUkq1asRN1wHTL4=
=Bvhi
-----END PGP SIGNATURE-----

Re: [fetchmail-users] Is it possible to save one email per file using bsmtp?

[Rob M. <rob...@gm...>]

On 9/23/06, Aaron Wasserott <aa...@vi...> wrote:
> I would like to be able to save each email fetched in it's own file. Is
> there a way to do this using the option bsmtp? The manual page for the
> .fetchmailrc file states that there is an option to bsmtp which is -o.

You may need to write your own LDA (local delivery agent), or
configure your local LDA accordingly.  I'm pretty sure this has been
discussed in the past, so a search of the archives should help.

-- 
                 Please keep list traffic on the list.

Rob MacGregor
      Whoever fights monsters should see to it that in the process he
        doesn't become a monster.                  Friedrich Nietzsche

Re: [fetchmail-users] TwoAccounts

[Andrea B. <and...@ti...>]

> But doesn't work on qmail --

My MTA is postfix.
Andrea