fetchmail-users — User questions and discussion

Re: [fetchmail-users] How not to download mail for non-existing users?

[Yvan <nos...@ml...>]

Nedavno Matthias Andree pise:

| The best solution though is telling the upstream site what valid users
| are and have them reject messages for others


How do I do that?


-- 
      ___   ____
     /__/  /    \      ** Registrovani korisnik Linuksa #291606 **
    /  / \/  /\  \     ** Registered Linux user #291606 **
   /__/\____/--\__\    ** http://counter.li.org/ **

Re: [fetchmail-users] How not to download mail for non-existing users?

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

Ivan Imperl schrieb am 2007-02-22:

> Nedavno Rob MacGregor pise:
> 
> | Output of "fetchmail --configdump" (remember to remove passwords)?
> 
> # fetchmail --configdump
> TRUE=1; FALSE=0
> 
> os_type = 'linux'
> feature_options = ('pop3','imap','gssapi','etrn','odmr','ssl','inet6',)
> # Start of configuration initializer
> fetchmailrc = {
>     'poll_interval':0,
>     "logfile":"/var/log/fetchMailByIva",
>     "idfile":"/root/.fetchids",

Don't run fetchmail as root unless you must. Few sites have to.

>     "postmaster":"iva",
>     'bouncemail':TRUE,
>     'spambounce':FALSE,
>     "properties":"",
>     'invisible':FALSE,
>     'showdots':FALSE,
>     'syslog':FALSE,
>     # List of server entries begins here
>     'servers': [
>         # Entry for site `pop3.infosky.net' begins:
>         {
>             "pollname":"pop3.infosky.net",
>             'active':TRUE,
>             "via":None,
>             "protocol":"POP3",
>             "port":None,
>             'timeout':300,
>             'interval':0,
>             "envelope":"Received",

That's not robust. Use another header, see
http://home.pages.de/~mandree/mail/multidrop

> | Ok, you're running an old, unsupported and vulnerable version of
> | fetchmail (missed that the first time).  Upgrade to (at least) 6.3.6
> | before posting any further diagnostics.
> 
> I will, but before I do is it possible to do what I want with pop3 (to
> discard - not to download mail if username does not exist locally) ?
> Sunil Shetye in his mail thinks that it can not be done. Do you agree?

No way that works on all servers at least; and implementing a way to
avoid that would require (a) server cooperation, (b) downloading message
headers twice.

The best solution though is telling the upstream site what valid users
are and have them reject messages for others.

-- 
Matthias Andree

Re: [fetchmail-users] How not to download mail for non-existing users?

[Ivan I. <nos...@ml...>]

Nedavno Rob MacGregor pise:

| Ok, you're running an old, unsupported and vulnerable version of
| fetchmail (missed that the first time).  Upgrade to (at least) 6.3.6
| before posting any further diagnostics.

I upgraded to 6.3.7. And no change:

-------------------------------------------------------------------
# Configuration created Mon Dec  1 12:45:17 2003 by fetchmailconf
set logfile "/var/log/fetchMailByIva"
set postmaster "iva"
# set no bouncemail
set no spambounce
set properties ""

poll pop3.ourisp.net with proto POP3:
	localdomains ourdomain.org
       user 'ouruseratisp' there with password 'pass' is * here

antispam 550
-------------------------------------------------------------------
...
fetchmail: SMTP> MAIL FROM:<so...@so...> BODY=7BIT SIZE=1428
fetchmail: SMTP< 250 2.1.0 <so...@so...>... Sender ok
fetchmail: SMTP> RCPT TO:<Non...@ou...>
fetchmail: SMTP< 550 5.1.1 <Non...@ou...>... User \
	unknown
fetchmail: SMTP listener doesn't really like recipient address     \
	`Non...@ou...'
fetchmail: SMTP> RCPT TO:<iva@localhost>
fetchmail: SMTP< 250 2.1.5 <iva@localhost>... Recipient ok
fetchmail: no address matches; forwarding to iva.
fetchmail: SMTP> DATA
fetchmail: SMTP< 354 Enter mail, end with "." on a line by itself
#*fetchmail: SMTP>. (EOM)
fetchmail: SMTP< 250 2.0.0 l1N8Ccjq009290 Message accepted for delivery
fetchmail:  flushed
fetchmail: POP3> DELE 1
fetchmail: POP3< +OK
fetchmail: POP3> QUIT
fetchmail: POP3< +OK
fetchmail: SMTP> QUIT
fetchmail: SMTP< 221 2.0.0 something.somethingelse.org closing    \
	connection
fetchmail: 6.3.7 querying pop3.infosky.net (protocol POP3)        \
	at Fri 23 Feb 2007 09:12:39 AM CET: poll completed
fetchmail: normal termination, status 0
-------------------------------------------------------------------

-- 
      ___   ____
     /__/  /    \      ** Registrovani korisnik Linuksa #291606 **
    /  / \/  /\  \     ** Registered Linux user #291606 **
   /__/\____/--\__\    ** http://counter.li.org/ **

Re: [fetchmail-users] How not to download mail for non-existingusers?

[Stuart J. B. <sjb...@bl...>]

> -----Original Message-----
> From: fet...@li... 
> Subject: Re: [fetchmail-users] How not to download mail for 
> non-existingusers?

<snip>

> In pop3 protocol, fetchmail does not download the mail headers and
> body separately. This is because, the pop3 protocol does not allow
> download of the body of a mail separately. So, even if the mail has
> been refused, fetchmail still downloads the rest of the body.

POP3 has 'top' which fetches headers-only, but yes, can't get the body
seperately.

Stuart

Re: [fetchmail-users] How not to download mail for non-existing users?

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

On 2/22/07, Ivan Imperl <nos...@ml...> wrote:
> Nedavno Rob MacGregor pise:
>
> | Output of "fetchmail --configdump" (remember to remove passwords)?

Well, the anti-spam code is recognised so it should drop any emails
that your local SMTP server returns that code for.

> I will, but before I do is it possible to do what I want with pop3 (to
> discard - not to download mail if username does not exist locally) ?
> Sunil Shetye in his mail thinks that it can not be done. Do you agree?

Yes (well, I defer to his greater understanding of the protocol).

-- 
                 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] How not to download mail for non-existing users?

[Ivan I. <nos...@ml...>]

Nedavno Rob MacGregor pise:

| Output of "fetchmail --configdump" (remember to remove passwords)?

# fetchmail --configdump
TRUE=1; FALSE=0

os_type = 'linux'
feature_options = ('pop3','imap','gssapi','etrn','odmr','ssl','inet6',)
# Start of configuration initializer
fetchmailrc = {
    'poll_interval':0,
    "logfile":"/var/log/fetchMailByIva",
    "idfile":"/root/.fetchids",
    "postmaster":"iva",
    'bouncemail':TRUE,
    'spambounce':FALSE,
    "properties":"",
    'invisible':FALSE,
    'showdots':FALSE,
    'syslog':FALSE,
    # List of server entries begins here
    'servers': [
        # Entry for site `pop3.infosky.net' begins:
        {
            "pollname":"pop3.infosky.net",
            'active':TRUE,
            "via":None,
            "protocol":"POP3",
            "port":None,
            'timeout':300,
            'interval':0,
            "envelope":"Received",
            'envskip':0,
            "qvirtual":None,
            "auth":"any",
            'dns':TRUE,
            'uidl':FALSE,
            "aka":[],
            "localdomains":["ourdomain.net"],
            "interface":None,
            "monitor":None,
            "plugin":None,
            "plugout":None,
            "principal":None,
            'tracepolls':FALSE,
            'users': [
                {
                    "remote":"ouruseratisp",
                    "password":"pass",
                    'localnames':["root", '*'],
                    'fetchall':FALSE,
                    'keep':FALSE,
                    'flush':FALSE,
                    'rewrite':TRUE,
                    'stripcr':FALSE,
                    'forcecr':FALSE,
                    'pass8bits':FALSE,
                    'dropstatus':FALSE,
                    'dropdelivered':FALSE,
                    'mimedecode':FALSE,
                    'idle':FALSE,
                    "mda":None,
                    "bsmtp":None,
                    'lmtp':FALSE,
                    "netsec":None,
                    "preconnect":None,
                    "postconnect":None,
                    'limit':0,
                    'warnings':3600,
                    'fetchlimit':0,
                    'batchlimit':0,
                    'ssl':FALSE,
                    "sslkey":None,
                    "sslcert":None,
                    "sslproto":None,
                    'sslcertck':FALSE,
                    "sslcertpath":None,
                    "sslfingerprint":None,
                    'expunge':0,
                    "properties":None,
                    "smtphunt":["localhost"],
                    "fetchdomains":[],
                    "smtpaddress":None,
                    "smtpname":None,
                    'antispam':'550',
                    "mailboxes":[],
                }
                ,           ]
        }
    ]
}
# End of initializer


| Ok, you're running an old, unsupported and vulnerable version of
| fetchmail (missed that the first time).  Upgrade to (at least) 6.3.6
| before posting any further diagnostics.

I will, but before I do is it possible to do what I want with pop3 (to
discard - not to download mail if username does not exist locally) ?
Sunil Shetye in his mail thinks that it can not be done. Do you agree?



-- 
      ___   ____
     /__/  /    \      ** Registrovani korisnik Linuksa #291606 **
    /  / \/  /\  \     ** Registered Linux user #291606 **
   /__/\____/--\__\    ** http://counter.li.org/ **

Re: [fetchmail-users] How not to download mail for non-existing users?

[Ivan I. <nos...@ml...>]

Nedavno Sunil Shetye pise:


| In pop3 protocol, fetchmail does not download the mail headers and
| body separately. This is because, the pop3 protocol does not allow
| download of the body of a mail separately. So, even if the mail has
| been refused, fetchmail still downloads the rest of the body.
| 
| To avoid downloading the body, you will have to:
| - use imap instead of pop3,
| - set postmaster to "" (empty).


My ISP does not have imap, I have to use pop3.

I tried to setup postmaster to "", but mail still gets downloaded, it
only is not deleivered to my mailbox - not what I want.



-- 
      ___   ____
     /__/  /    \      ** Registrovani korisnik Linuksa #291606 **
    /  / \/  /\  \     ** Registered Linux user #291606 **
   /__/\____/--\__\    ** http://counter.li.org/ **

Re: [fetchmail-users] How not to download mail for non-existing users?

[Sunil S. <sh...@bo...>]

Quoting from Ivan Imperl's mail on Wed, Feb 21, 2007:
> set postmaster "iva"
> # set nobouncemail
> set no spambounce
> set properties ""
> 
> poll pop3.ourisp.net with proto POP3:

...

> Now to the problem. Recently we started to receive a lot of (large) mail
> that is for the users that do not exist (do not have accounts) on local
> mail server. Since this takes a lot of dial-up time, I was wondering if
> there is a possibility for fetchmail to delete such mail.

In pop3 protocol, fetchmail does not download the mail headers and
body separately. This is because, the pop3 protocol does not allow
download of the body of a mail separately. So, even if the mail has
been refused, fetchmail still downloads the rest of the body.

To avoid downloading the body, you will have to:
- use imap instead of pop3,
- set postmaster to "" (empty).

Note that if you set postmaster to "", you may not get any
notifications from fetchmail.

-- 
Sunil Shetye.

Re: [fetchmail-users] How not to download mail for non-existing users?

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

On 2/22/07, Ivan Imperl <nos...@ml...> wrote:
> Nedavno Rob MacGregor pise:
<--SNIP-->
> -----------------------------------------------------------------
> # Configuration created Mon Dec  1 12:45:17 2003 by fetchmailconf
> set logfile "/var/log/fetchMailByIva"
> set postmaster "iva"
> set no bouncemail
> set no spambounce
> set properties ""
>
> poll pop3.ourisp.net with proto POP3:
>         localdomains ourdomain.org
>        user 'ouruseratisp' there with password 'pass' is * here
>
> antispam 550

Output of "fetchmail --configdump" (remember to remove passwords)?

<--SNIP-->
> fetchmail: 6.2.0 querying pop3.infosky.net (protocol POP3) at Thu 22 \
>         Feb 2007 08:56:31 AM CET: poll completed

Ok, you're running an old, unsupported and vulnerable version of
fetchmail (missed that the first time).  Upgrade to (at least) 6.3.6
before posting any further diagnostics.

-- 
                 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] How not to download mail for non-existing users?

[Ivan I. <nos...@ml...>]

Nedavno Rob MacGregor pise:

| You could configure 550 as an anti-spam code (see the man page), but
| keep in mind that if somebody mis-types an email address it'll just
| get deleted and you'll never know.

I did. Here:


-----------------------------------------------------------------
# Configuration created Mon Dec  1 12:45:17 2003 by fetchmailconf
set logfile "/var/log/fetchMailByIva"
set postmaster "iva"
set no bouncemail
set no spambounce
set properties ""

poll pop3.ourisp.net with proto POP3:
	localdomains ourdomain.org
       user 'ouruseratisp' there with password 'pass' is * here

antispam 550
-----------------------------------------------------------------


but it had no difference:

-----------------------------------------------------------------
fetchmail: SMTP> MAIL FROM:<so...@so...> BODY=7BIT SIZE=1428
fetchmail: SMTP< 250 2.1.0 <so...@so...>... Sender ok
fetchmail: SMTP> RCPT TO:<Non...@ou...>
fetchmail: SMTP< 550 5.1.1 <Non...@ou...>... User \
	unknown
fetchmail: SMTP listener doesn't really like recipient address \
	`Non...@ou...'
fetchmail: SMTP> RCPT TO:<iva@localhost>
fetchmail: SMTP< 250 2.1.5 <iva@localhost>... Recipient ok
fetchmail: no address matches; forwarding to iva.
fetchmail: SMTP> DATA fetchmail: SMTP< 354 Enter mail, end with "." on\
	a line by itself
#*fetchmail: SMTP>. (EOM)
fetchmail: SMTP< 250 2.0.0 l1M7uVrX002878 Message accepted for delivery
fetchmail:  flushed
fetchmail: POP3> DELE 1
fetchmail: POP3< +OK
fetchmail: POP3> QUIT
fetchmail: POP3< +OK
fetchmail: 6.2.0 querying pop3.infosky.net (protocol POP3) at Thu 22 \
	Feb 2007 08:56:31 AM CET: poll completed
-----------------------------------------------------------------


So mail still gets downloaded (what I want to avoid) and forwarded to
me. Any suggestions?


-- 
      ___   ____
     /__/  /    \      ** Registrovani korisnik Linuksa #291606 **
    /  / \/  /\  \     ** Registered Linux user #291606 **
   /__/\____/--\__\    ** http://counter.li.org/ **

Re: [fetchmail-users] How not to download mail for non-existing users?

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

On 2/21/07, Ivan Imperl <nos...@ml...> wrote:
> My ISP forwards all mail for my domain at one account. I than use
> fetchmail to download all mail to my box, MailScanner to scan for
> spam and viruses (for winblows users) and sendmail distribute it to
> users on local network. Hire is my .fetchmailrc:
>
> # Configuration created Mon Dec  1 12:45:17 2003 by fetchmailconf
> set logfile "/var/log/fetchMailByIva"
> set postmaster "iva"
> # set nobouncemail
> set no spambounce
> set properties ""
>
> poll pop3.ourisp.net with proto POP3:
>         localdomains ourdomain.org
>        user 'ouruseratisp' there with password 'pass' is * here
>
> It's a low traffic on dial-up connection. Fedora Core 1 (about to be
> replaced with Debian etch).
>
> Now to the problem. Recently we started to receive a lot of (large) mail
> that is for the users that do not exist (do not have accounts) on local
> mail server. Since this takes a lot of dial-up time, I was wondering if
> there is a possibility for fetchmail to delete such mail.

You could configure 550 as an anti-spam code (see the man page), but
keep in mind that if somebody mis-types an email address it'll just
get deleted and you'll never know.

Note too that you really should have set the envelope header option to
correctly parse multi-drop emails - see the man page again.  Not doing
this can lead to email going places you weren't expecting (like being
dropped on the floor).

-- 
                 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] How not to download mail for non-existing users?

[Ivan I. <nos...@ml...>]

My ISP forwards all mail for my domain at one account. I than use
fetchmail to download all mail to my box, MailScanner to scan for
spam and viruses (for winblows users) and sendmail distribute it to
users on local network. Hire is my .fetchmailrc:

# Configuration created Mon Dec  1 12:45:17 2003 by fetchmailconf
set logfile "/var/log/fetchMailByIva"
set postmaster "iva"
# set nobouncemail
set no spambounce
set properties ""

poll pop3.ourisp.net with proto POP3:
        localdomains ourdomain.org
       user 'ouruseratisp' there with password 'pass' is * here

It's a low traffic on dial-up connection. Fedora Core 1 (about to be
replaced with Debian etch).

Now to the problem. Recently we started to receive a lot of (large) mail
that is for the users that do not exist (do not have accounts) on local
mail server. Since this takes a lot of dial-up time, I was wondering if
there is a possibility for fetchmail to delete such mail.



Hire is a log of (small) unwanted mail:
-----------------------------------------------------------------------
fetchmail: SMTP< 250 2.0.0 l1J7MJS8002870 Message accepted for delivery
fetchmail:  flushed
fetchmail: POP3> DELE 1
fetchmail: POP3< +OK
fetchmail: POP3> TOP 2 99999999
fetchmail: POP3< +OK
fetchmail: reading message something.somethingelse.org:2 of 2 (1428 \
	octets)
fetchmail: SMTP> MAIL FROM:<som...@so...> BODY=7BIT SIZE=1428
fetchmail: SMTP< 250 2.1.0 <som...@so...>... Sender ok
fetchmail: SMTP> RCPT TO:<Non...@ou...>
fetchmail: SMTP< 550 5.1.1 <Non...@ou...>... User \
	unknown
fetchmail: SMTP error: 550 5.1.1 <Non...@ou...>...\
	User unknown
fetchmail: SMTP listener doesn't like recipient address \
	`Non...@ou...'
fetchmail: SMTP< 220 something.somethingelse.org ESMTP Sendmail \
	8.12.10/8.12.10; Mon, 19 Feb 2007 08:22:48 +0100
fetchmail: SMTP> HELO localhost
fetchmail: SMTP< 250 something.somethingelse.org Hello \
	something.somethingelse.org [127.0.0.1], pleased to meet you
fetchmail: SMTP> MAIL \
	FROM:<FET...@so...>
fetchmail: SMTP< 250 2.1.0 \
	<FET...@so...>... Sender ok
fetchmail: SMTP> RCPT TO:<som...@so...>
fetchmail: SMTP< 250 2.1.5 <som...@so...>... Recipient ok
fetchmail: SMTP> DATA
fetchmail: SMTP< 354 Enter mail, end with "." on a line by itself
fetchmail: SMTP: (bounce-message body)
fetchmail: SMTP>. (EOM)
fetchmail: SMTP< 250 2.0.0 l1J7MmS8002892 Message accepted for delivery
fetchmail: SMTP> QUIT
fetchmail: SMTP< 221 2.0.0 something.somethingelse.org closing \
	connection
fetchmail: SMTP> RCPT TO:<iva@localhost>
fetchmail: SMTP< 250 2.1.5 <iva@localhost>... Recipient ok
fetchmail: no address matches; forwarding to iva.
fetchmail: SMTP> DATA
fetchmail: SMTP< 354 Enter mail, end with "." on a line by itself
#*fetchmail: SMTP>. (EOM)
fetchmail: SMTP< 250 2.0.0 l1J7MJS9002870 Message accepted for delivery
fetchmail:  flushed
fetchmail: POP3> DELE 2
fetchmail: POP3< +OK
fetchmail: POP3> QUIT
fetchmail: POP3< +OK
fetchmail: 6.2.0 querying pop3.infosky.net (protocol POP3) at Mon 19
Feb 2007 08:22:49 AM CET: poll completed fetchmail: SMTP> QUIT
fetchmail: SMTP< 221 2.0.0 something.somethingelse.org closing
connection fetchmail: normal termination, status 0
-----------------------------------------------------------------------


As you can see mail was delivered to iva@localhost (me) as it is set in
~/.fetchmailrc. I can set postmaster to empty string, but mail still
gets downloaded (which is what I am trying to avoid), it only gets
discarded.

-- 
      ___   ____
     /__/  /    \      ** Registrovani korisnik Linuksa #291606 **
    /  / \/  /\  \     ** Registered Linux user #291606 **
   /__/\____/--\__\    ** http://counter.li.org/ **

[fetchmail-users] fetchmail 6.3.7 regression fixes release

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

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

Greetings,

I am announcing the release of fetchmail 6.3.7.

This new stable version of fetchmail fixes two regressions that were
recently introduced into the security fix release 6.3.6, see below for
details.

The software is available from:
<http://developer.berlios.de/project/showfiles.php?group_id=1824&release_id=12245>

The fetchmail home page is:
<http://www.fetchmail.info/>  or  <http://fetchmail.berlios.de/>

These are the relevant changes in 6.3.7 since 6.3.6;
unless otherwise noted, changes to this release were made by Matthias Andree:

# FIXES FOR REGRESSIONS IN 6.3.6
* Fix KPOP. Patch by Miloslav Trmac.
* Fix repoll when server disconnects after opportunistic TLS failed for POP3.
  Berlios Bug #10133 = Gentoo Bug #163782 reported by Andrej Kacian.

# TRANSLATION UPDATES
* Japanese (Takeshi Hamasaki), Polish (Jakub Bogusz)

# CHANGES
* Consider getaddrinfo() on Darwin 9 (Mac OS X 10.5 "Leopard") thread-safe.
  Reported by Uli Zappe.

Best regards

- -- 
Matthias Andree
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFF2JDCvmGDOQUufZURAnXhAJ9isKNGpjQX8G6HTB6CvxjQfHIRmQCeLtsR
WBIHVcRoyddo4tL5fAVZoEY=
=7x5d
-----END PGP SIGNATURE-----

Re: [fetchmail-users] CommonName mismatch after fetchmail upgrade

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

thomas <tho...@gm...> writes:

> Hello,
>
> I have upgraded to fetchmail "6.3.6+NTLM+SDPS+SSL+NLS" (the one
> shipped with Debian Etch). My setup always worked sofar, but since I
> get the following error :
> fetchmail: pop.myuniversity.tld: upgrade to TLS succeeded.
> fetchmail: POP3> USER MYLOGIN
> fetchmail: POP3< +OK please send the PASS
> fetchmail: POP3> PASS *
> fetchmail: POP3< -ERR secure access to this account is disabled
> fetchmail: secure access to this account is disabled
> fetchmail: Authorization failure on MY...@po...

That is the actual issue here, not the mismatched TLS cert'.

JFTR: Fetchmail 6.3.6 does not (and 6.3.7) will not break the connection
just because of the mismatch, unless you request so (which means
--sslcertck). Future versions (6.4.X or something later) may however
make sslcertck the default.

Fetchmail has been sharing passwords with man-in-the-middle attackers in
its default configuration for too long and the new paradigm of a future
version will be that explicit configuration is required to allow
unsecure connections, rather than requiring explicit configuration to
secure connections.

And more for the records: If you want to disable TLS, first sell
myuniversity.tld's NOC a clue so they allow encrypted connections for
everyone, then set

            sslproto ''

in the run control file for your account until they've fixed their
servers or bought reasonable hardware to run their software on.

-- 
Matthias Andree

Re: [fetchmail-users] CommonName mismatch after fetchmail upgrade

[thomas <tho...@gm...>]

2007/2/17, Rob MacGregor <rob...@gm...>:
> > Maybe the certificate of my university is wrong, but the old version
> > of fetchmail had no problem to fetch the emails, so there must be a
> > workaround.
>
> The "old version" (you don't say which, but I suspect a pretty old
> one) obviously didn't attempt to support TLS.  Simply disable TLS:

Thanks a lot for your quick answer Rob, it works now.

I think the "old version" was 6.3.4-7. About the following version
shipped with Debian etch (6.3.6-rc3-1), I can read the following in
the distro-specific changelog:

fetchmail 6.3.5 and older had no way to enforce TLS. With those older
versions, TLS was always opportunistic, but fetchmail would happily
transmit the password in cleartext if STARTTLS failed. [...]
Configurations using --ssl --sslcertck however have been safe.

I think this is the reason why fetching emails worked until the
upgrade to 6.3.6. Anyway, problem fixed, re-thanks.

Thomas

Re: [fetchmail-users] CommonName mismatch after fetchmail upgrade

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

On 2/17/07, thomas <tho...@gm...> wrote:
> Hello,
>
> I have upgraded to fetchmail "6.3.6+NTLM+SDPS+SSL+NLS" (the one
> shipped with Debian Etch). My setup always worked sofar, but since I
> get the following error :
>
> fetchmail: 6.3.6 querying pop.myuniversity.tld (protocol POP3) at sam
> 17 fév 2007 21:40:46 CET: poll started
<---SNIP--->
> fetchmail: POP3< +OK start TLS negotiation
> fetchmail: Issuer Organization: Stalker Software, Inc.
> fetchmail: Issuer CommonName: stalker.com
> fetchmail: Server CommonName: myuniversity.tld
> fetchmail: Server CommonName mismatch: myuniversity.tld != pop.myuniversity.tld
> fetchmail: pop.myuniversity.tld key fingerprint:
> 17:A5:89:D2:05:6F:41:6B:32:4C:9E:14:78:02:59:B6
> fetchmail: Server certificate verification error: unable to get local
> issuer certificate
> fetchmail: Server certificate verification error: certificate not trusted
> fetchmail: Server certificate verification error: unable to verify the
> first certificate
> fetchmail: pop.myuniversity.tld: upgrade to TLS succeeded.
> fetchmail: POP3> USER MYLOGIN
> fetchmail: POP3< +OK please send the PASS
> fetchmail: POP3> PASS *
> fetchmail: POP3< -ERR secure access to this account is disabled
> fetchmail: secure access to this account is disabled
<----SNIP--->
> Maybe the certificate of my university is wrong, but the old version
> of fetchmail had no problem to fetch the emails, so there must be a
> workaround.

The "old version" (you don't say which, but I suspect a pretty old
one) obviously didn't attempt to support TLS.  Simply disable TLS:

http://www.fetchmail.info/fetchmail-FAQ.html#K6

-- 
                 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] CommonName mismatch after fetchmail upgrade

[thomas <tho...@gm...>]

Hello,

I have upgraded to fetchmail "6.3.6+NTLM+SDPS+SSL+NLS" (the one
shipped with Debian Etch). My setup always worked sofar, but since I
get the following error :

fetchmail: 6.3.6 querying pop.myuniversity.tld (protocol POP3) at sam
17 fév 2007 21:40:46 CET: poll started
Trying to connect to 194.254.137.9/110...connected.
fetchmail: POP3< +OK POP3  Groupe ESSEC <792...@my...>
fetchmail: POP3> CAPA
fetchmail: POP3< +OK capability list follows
fetchmail: POP3< SASL LOGIN PLAIN CRAM-MD5 DIGEST-MD5 MSN
fetchmail: POP3< STLS
fetchmail: POP3< LAST
fetchmail: POP3< TOP
fetchmail: POP3< USER
fetchmail: POP3< PIPELINING
fetchmail: POP3< UIDL
fetchmail: POP3< IMPLEMENTATION CommuniGatePro
fetchmail: POP3< .
fetchmail: POP3> STLS
fetchmail: POP3< +OK start TLS negotiation
fetchmail: Issuer Organization: Stalker Software, Inc.
fetchmail: Issuer CommonName: stalker.com
fetchmail: Server CommonName: myuniversity.tld
fetchmail: Server CommonName mismatch: myuniversity.tld != pop.myuniversity.tld
fetchmail: pop.myuniversity.tld key fingerprint:
17:A5:89:D2:05:6F:41:6B:32:4C:9E:14:78:02:59:B6
fetchmail: Server certificate verification error: unable to get local
issuer certificate
fetchmail: Server certificate verification error: certificate not trusted
fetchmail: Server certificate verification error: unable to verify the
first certificate
fetchmail: POP3> CAPA
fetchmail: POP3< +OK capability list follows
fetchmail: POP3< SASL LOGIN PLAIN CRAM-MD5 DIGEST-MD5 MSN
fetchmail: POP3< LAST
fetchmail: POP3< TOP
fetchmail: POP3< USER
fetchmail: POP3< PIPELINING
fetchmail: POP3< UIDL
fetchmail: POP3< IMPLEMENTATION CommuniGatePro
fetchmail: POP3< .
fetchmail: pop.myuniversity.tld: upgrade to TLS succeeded.
fetchmail: POP3> USER MYLOGIN
fetchmail: POP3< +OK please send the PASS
fetchmail: POP3> PASS *
fetchmail: POP3< -ERR secure access to this account is disabled
fetchmail: secure access to this account is disabled
fetchmail: Authorization failure on MY...@po...
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Connection closed
fetchmail: 6.3.6 querying pop.myuniversity.tld (protocol POP3) at sam
17 fév 2007 21:40:47 CET: poll completed
fetchmail: Query status=3 (AUTHFAIL)

Maybe the certificate of my university is wrong, but the old version
of fetchmail had no problem to fetch the emails, so there must be a
workaround.

Thanks for the help
Thomas

Re: [fetchmail-users] Question about mailing lists

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

"Andrew N. Gray" <an...@gr...> writes:

> I would say working great, when compared to the pop3 connector for  
> exchange which is a complete PITA.

If Exchange works as "well" as Outlook 11 does, then "complete PITA" is
an euphemism.

> A couple more questions:
>
> if I want to check 20 pop accounts, should I run fetchmail in daemon  
> mode or via a cron.  Is there a way to get it to pause for a time  
> between each poll?

Functionally, the cron approach is a tad more robust, but can also emit
more warnings, since it stores less state information internally.

For the pausing, check something like

    postconnect "sleep 21"

after each poll statement. See the fetchmail and sleep manual pages.

-- 
Matthias Andree

Re: [fetchmail-users] Fetchmail not working Fedora Core 3 and FC 4

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

"Denny Stamos" <de...@st...> writes:

> I did a Yum install of Fetchmail on my Fedora Core 3 box. From the shell i type fetchmail and there is no
> response its just blank and i dont get a prompt back. I then have to do CRTL C to quit.

Probably a configuration issue.

Try "fetchmail --nosyslog -v -v" to see what it's doing... but read below.

> I upgraded to FC 4 with the latest binary of Fetchamail and the same problem. Ive tried yum remove fetchmail and then re-install and
> i get the same problem. Could i be missing a library file ?
>
> The version i have is 6.2.5.5-1

...if it's not a configuration issue you can fix for yourself, the next
paragraph applies:

fetchmail 6.2.X has been discontinued over a year ago.
Either ask Fedora for support, or update to 6.3.6 or 6.3.7-rc1.

-- 
Matthias Andree

[fetchmail-users] Updated Cygwin Package: fetchmail-6.3.6-1

[Jason T. <ja...@ti...>]

New News:
=== ====
I have updated the version of fetchmail to 6.3.6-1.  The tarballs should
be available on a Cygwin mirror near you shortly.

The only change between this version and the previous one is the
following:

    o update to version 6.3.6

If you are a Cygwin fetchmail user, then please upgrade ASAP because the
previous version has several security vulnerabilities.

Old News:
=== ====
Fetchmail is a remote mail retrieval and forwarding utility intended
for use over on-demand TCP/IP links, like SLIP or PPP connections.
Fetchmail supports every remote-mail protocol currently in use on the
Internet (POP2, POP3, RPOP, APOP, KPOP, all IMAPs, ESMTP ETRN, IPv6,
and IPSEC) for retrieval. Then Fetchmail forwards the mail through SMTP
so you can read it through your favorite mail client.

See the fetchmail home page for more details:

    http://fetchmail.berlios.de/

Please read the README file:

    /usr/share/doc/Cygwin/fetchmail-6.3.6.README

since it covers requirements, installation, known issues, etc.

Standard News:
======== ====
To update your installation, click on the "Install Cygwin now" link on
the http://cygwin.com/ web page.  This downloads setup.exe to your
system.  Then, run setup and answer all of the questions.

If you have questions or comments, please send them to the Cygwin
mailing list at: cy...@cy... .

              *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there.  It will be in the format:

cyg...@cy...

If you need more information on unsubscribing, start reading here:

http://sources.redhat.com/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that is available
starting at this URL.

Jason

--
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D  8784 1AFD E4CC ECF4 8EF6

Re: [fetchmail-users] IMAP problem

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

On 2/13/07, Alain Chofardet <Ala...@th...> wrote:
>
> The one I currently use is 6.3.2. But I've also tried 6.3.6. Exactly same
> behavior.

Well, it looks like fetchmail is doing what it's designed to, but that
the IMAP server responds differently according to how it's queried.
If you need support for this non-standard system you'll probably have
to convince the developers that it's necessary and then provide
patches.

Alternatively, try using a client that can correctly handle the
external body parts.

-- 
                 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] IMAP problem

[Alain C. <Ala...@th...>]

Hi.

fet...@li... wrote on 13/02/2007 08:20:01:

> On 2/12/07, Alain Chofardet <Ala...@th...> wrote:
> >
> > Hi.
> >
> > I'm quite a newbie with Fetchmail, and I've read the FAQs before 
writing to
> > this list.
> 
> But apparently not the one that tells you what to report :)
> 
Sorry for that.

> > This is my problem : I need to fetch mails from an IMAP account and 
direct
> > them to the local SMTP port. Fetchmail seems the perfect tool for 
that.
> > However, the mails I fetch from the IMAP account are mainly composed 
with an
> > attached file.
> 
> So, how about at least some of the details the FAQ asks for:
> 
> 1) Version of fetchmail

The one I currently use is 6.3.2. But I've also tried 6.3.6. Exactly same 
behavior.

> 
> 2) Contents of .fetchmailrc
> 
Quite simple :

poll 192.168.1.2 protocol IMAP:
user 100 with password 100 options norewrite

My first attempt had no option at all. I've also tried options around 
MIME, but with no success.

> 3) Output of "fetchmail -v -v --nosyslog" (and any other command line

OK. This is fetchmail -v -v -nosyslog

fetchmail: 6.3.2 interroge 192.168.1.2 (protocole IMAP) à mar 13 fév 
2007 11:57:00 CET : récupération en cours
fetchmail: IMAP< * OK Talk_It IMAP4rev1 v10.210 server ready
fetchmail: IMAP> A0001 CAPABILITY
fetchmail: IMAP< * CAPABILITY IMAP4 IMAP4REV1 NAMESPACE SCAN SORT X-NBX 
THREAD=ORDEREDSUBJECT
fetchmail: IMAP< A0001 OK CAPABILITY completed
fetchmail: Protocole identifié comme étant IMAP4 rev 
fetchmail: IMAP> A0002 LOGIN * "100"
fetchmail: IMAP< A0002 OK LOGIN completed
fetchmail: sélection ou re-réception du dossier par défaut
fetchmail: IMAP> A0003 SELECT "INBOX"
fetchmail: IMAP< * 20 EXISTS
fetchmail: IMAP< * OK [UIDVALIDITY 1038355870] UID validity status
fetchmail: IMAP< * OK [UIDNEXT 26] Predicted next UID
fetchmail: IMAP< * FLAGS (\Answered \Flagged \Deleted \Draft \Seen)
fetchmail: IMAP< * OK [PERMANENTFLAGS (\* \Answered \Flagged \Deleted 
\Draft \Seen)] Permanent flags
fetchmail: IMAP< * OK [UNSEEN 17] 17 is first unseen message in 
/htfs0/var/mail/uid202
fetchmail: IMAP< * 4 RECENT
fetchmail: IMAP< A0003 OK [READ-WRITE] SELECT completed
fetchmail: 20 messages en attente après le premier poll
fetchmail: IMAP> A0004 EXPUNGE
fetchmail: IMAP< A0004 OK Mailbox checkpointed, but no messages deleted
fetchmail: 20 messages en attente après la purge
fetchmail: IMAP> A0005 SEARCH UNSEEN NOT DELETED
fetchmail: IMAP< * SEARCH 17 18 19 20
fetchmail: 17 n'est pas vu
fetchmail: 18 n'est pas vu
fetchmail: 19 n'est pas vu
fetchmail: 20 n'est pas vu
fetchmail: IMAP< A0005 OK SEARCH completed
fetchmail: 17 est le premier a n'avoir pas été vu
20 messages (16 déjà vus) pour 100 dans 192.168.1.2.
message 100@192.168.1.2:1 ignoré non éliminé
message 100@192.168.1.2:2 ignoré non éliminé
message 100@192.168.1.2:3 ignoré non éliminé
message 100@192.168.1.2:4 ignoré non éliminé
message 100@192.168.1.2:5 ignoré non éliminé
message 100@192.168.1.2:6 ignoré non éliminé
message 100@192.168.1.2:7 ignoré non éliminé
message 100@192.168.1.2:8 ignoré non éliminé
message 100@192.168.1.2:9 ignoré non éliminé
message 100@192.168.1.2:10 ignoré non éliminé
message 100@192.168.1.2:11 ignoré non éliminé
message 100@192.168.1.2:12 ignoré non éliminé
message 100@192.168.1.2:13 ignoré non éliminé
message 100@192.168.1.2:14 ignoré non éliminé
message 100@192.168.1.2:15 ignoré non éliminé
message 100@192.168.1.2:16 ignoré non éliminé
fetchmail: IMAP> A0006 FETCH 17:20 RFC822.SIZE
fetchmail: IMAP< * 17 FETCH (RFC822.SIZE 1117)
fetchmail: IMAP< * 18 FETCH (RFC822.SIZE 1116)
fetchmail: IMAP< * 19 FETCH (RFC822.SIZE 1116)
fetchmail: IMAP< * 20 FETCH (RFC822.SIZE 1116)
fetchmail: IMAP< A0006 OK FETCH completed
fetchmail: IMAP> A0007 FETCH 17 RFC822.HEADER
fetchmail: IMAP< * 17 FETCH (RFC822.HEADER {432}
lecture du message 100@192.168.1.2:17 parmi 20 (432 octets dans 
l'en-tête)
fetchmail: SMTP< 220 domino.talk-it.fr ESMTP Service (Lotus Domino Release 
7.0.2FP1) ready at Tue, 13 Feb 2007 11:57:01 +0100
fetchmail: SMTP> EHLO Talk-It.talk-it.fr
fetchmail: SMTP< 250-domino.talk-it.fr Hello Talk-It.talk-it.fr 
([127.0.0.1]), pleased to meet you
fetchmail: SMTP< 250-DSN
fetchmail: SMTP< 250-SIZE
fetchmail: SMTP< 250 PIPELINING
fetchmail: réexpédition vers localhost
fetchmail: SMTP> MAIL FROM:<101@192.168.1.2> SIZE=1117
fetchmail: SMTP< 250 101@192.168.1.2... Sender OK
fetchmail: SMTP> RCPT TO:<notes@localhost>
fetchmail: SMTP< 250 notes@localhost... Recipient OK
fetchmail: SMTP> DATA
fetchmail: SMTP< 354 Enter message, end with "." on a line by itself
fetchmail: IMAP< )
fetchmail: IMAP< A0007 OK FETCH completed
fetchmail: IMAP> A0008 FETCH 17 BODY.PEEK[TEXT]
fetchmail: IMAP< * 17 FETCH (BODY[TEXT] {685}
 (685 octets dans le corps) fetchmail: IMAP< )
fetchmail: IMAP< A0008 OK FETCH completed
fetchmail: SMTP>. (EOM)
fetchmail: SMTP< 250 Message accepted for delivery
 éliminé
fetchmail: IMAP> A0009 STORE 17 +FLAGS (\Seen \Deleted)
fetchmail: IMAP< * 17 FETCH (FLAGS (\Recent \Seen \Deleted))
fetchmail: IMAP< A0009 OK STORE completed
fetchmail: IMAP> A0010 EXPUNGE
fetchmail: IMAP< * 17 EXPUNGE
fetchmail: IMAP< * 19 EXISTS
fetchmail: IMAP< * 3 RECENT
fetchmail: IMAP< A0010 OK Expunged 1 messages
fetchmail: IMAP> A0011 FETCH 17 RFC822.HEADER
fetchmail: IMAP< * 17 FETCH (RFC822.HEADER {432}
lecture du message 100@192.168.1.2:18 parmi 20 (432 octets dans 
l'en-tête)
fetchmail: réexpédition vers localhost
fetchmail: SMTP> MAIL FROM:<101@192.168.1.2> SIZE=1116
fetchmail: SMTP< 250 101@192.168.1.2... Sender OK
fetchmail: SMTP> RCPT TO:<notes@localhost>
fetchmail: SMTP< 250 notes@localhost... Recipient OK
fetchmail: SMTP> DATA
fetchmail: SMTP< 354 Enter message, end with "." on a line by itself
fetchmail: IMAP< )
fetchmail: IMAP< A0011 OK FETCH completed
fetchmail: IMAP> A0012 FETCH 17 BODY.PEEK[TEXT]
fetchmail: IMAP< * 17 FETCH (BODY[TEXT] {684}
 (684 octets dans le corps) fetchmail: IMAP< )
fetchmail: IMAP< A0012 OK FETCH completed
fetchmail: SMTP>. (EOM)
fetchmail: SMTP< 250 Message accepted for delivery
 éliminé
fetchmail: IMAP> A0013 STORE 17 +FLAGS (\Seen \Deleted)
fetchmail: IMAP< * 17 FETCH (FLAGS (\Recent \Seen \Deleted))
fetchmail: IMAP< A0013 OK STORE completed
fetchmail: IMAP> A0014 EXPUNGE
fetchmail: IMAP< * 17 EXPUNGE
fetchmail: IMAP< * 18 EXISTS
fetchmail: IMAP< * 2 RECENT
fetchmail: IMAP< A0014 OK Expunged 1 messages
fetchmail: IMAP> A0015 FETCH 17 RFC822.HEADER
fetchmail: IMAP< * 17 FETCH (RFC822.HEADER {432}
lecture du message 100@192.168.1.2:19 parmi 20 (432 octets dans 
l'en-tête)
fetchmail: réexpédition vers localhost
fetchmail: SMTP> MAIL FROM:<101@192.168.1.2> SIZE=1116
fetchmail: SMTP< 250 101@192.168.1.2... Sender OK
fetchmail: SMTP> RCPT TO:<notes@localhost>
fetchmail: SMTP< 250 notes@localhost... Recipient OK
fetchmail: SMTP> DATA
fetchmail: SMTP< 354 Enter message, end with "." on a line by itself
fetchmail: IMAP< )
fetchmail: IMAP< A0015 OK FETCH completed
fetchmail: IMAP> A0016 FETCH 17 BODY.PEEK[TEXT]
fetchmail: IMAP< * 17 FETCH (BODY[TEXT] {684}
 (684 octets dans le corps) fetchmail: IMAP< )
fetchmail: IMAP< A0016 OK FETCH completed
fetchmail: SMTP>. (EOM)
fetchmail: SMTP< 250 Message accepted for delivery
 éliminé
fetchmail: IMAP> A0017 STORE 17 +FLAGS (\Seen \Deleted)
fetchmail: IMAP< * 17 FETCH (FLAGS (\Recent \Seen \Deleted))
fetchmail: IMAP< A0017 OK STORE completed
fetchmail: IMAP> A0018 EXPUNGE
fetchmail: IMAP< * 17 EXPUNGE
fetchmail: IMAP< * 17 EXISTS
fetchmail: IMAP< * 1 RECENT
fetchmail: IMAP< A0018 OK Expunged 1 messages
fetchmail: IMAP> A0019 FETCH 17 RFC822.HEADER
fetchmail: IMAP< * 17 FETCH (RFC822.HEADER {432}
lecture du message 100@192.168.1.2:20 parmi 20 (432 octets dans 
l'en-tête)
fetchmail: réexpédition vers localhost
fetchmail: SMTP> MAIL FROM:<101@192.168.1.2> SIZE=1116
fetchmail: SMTP< 250 101@192.168.1.2... Sender OK
fetchmail: SMTP> RCPT TO:<notes@localhost>
fetchmail: SMTP< 250 notes@localhost... Recipient OK
fetchmail: SMTP> DATA
fetchmail: SMTP< 354 Enter message, end with "." on a line by itself
fetchmail: IMAP< )
fetchmail: IMAP< A0019 OK FETCH completed
fetchmail: IMAP> A0020 FETCH 17 BODY.PEEK[TEXT]
fetchmail: IMAP< * 17 FETCH (BODY[TEXT] {684}
 (684 octets dans le corps) fetchmail: IMAP< )
fetchmail: IMAP< A0020 OK FETCH completed
fetchmail: SMTP>. (EOM)
fetchmail: SMTP< 250 Message accepted for delivery
 éliminé
fetchmail: IMAP> A0021 STORE 17 +FLAGS (\Seen \Deleted)
fetchmail: IMAP< * 17 FETCH (FLAGS (\Recent \Seen \Deleted))
fetchmail: IMAP< A0021 OK STORE completed
fetchmail: IMAP> A0022 EXPUNGE
fetchmail: IMAP< * 17 EXPUNGE
fetchmail: IMAP< * 16 EXISTS
fetchmail: IMAP< * 0 RECENT
fetchmail: IMAP< A0022 OK Expunged 1 messages
fetchmail: sélection ou re-réception du dossier par défaut
fetchmail: 0 message en attente après le nouveau poll
fetchmail: IMAP> A0023 LOGOUT
fetchmail: IMAP< * BYE Talk_It IMAP4rev1 server terminating connection
fetchmail: IMAP< A0023 OK LOGOUT completed
fetchmail: SMTP> QUIT
fetchmail: SMTP< 221 domino.talk-it.fr SMTP Service closing transmission 
channel
fetchmail: 6.3.2 interroge 192.168.1.2 (protocole IMAP) à mar 13 fév 
2007 11:57:05 CETÂ : interrogation finie
fetchmail: ne permute pas les listes d'UIDs, aucun UID vu dans cette 
requête
fetchmail: Effacement du fichier fetchids.
fetchmail: terminaison normale, état 0
fetchmail: Effacement du fichier fetchids.





> 4) The OS you're using
> 
The OS is Suse Linux Enterprise Server 10.

Regards.

Alain CHOFARDET

Re: [fetchmail-users] IMAP problem

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

On 2/12/07, Alain Chofardet <Ala...@th...> wrote:
>
> Hi.
>
> I'm quite a newbie with Fetchmail, and I've read the FAQs before writing to
> this list.

But apparently not the one that tells you what to report :)

> This is my problem : I need to fetch mails from an IMAP account and direct
> them to the local SMTP port. Fetchmail seems the perfect tool for that.
> However, the mails I fetch from the IMAP account are mainly composed with an
> attached file.

So, how about at least some of the details the FAQ asks for:

1) Version of fetchmail

2) Contents of .fetchmailrc

3) Output of "fetchmail -v -v --nosyslog" (and any other command line
arguments you usually use)

4) The OS you're using

> The fetch body[text] command seems to be the one used by fetchmail and
> doesn't download the file.

Correction - results in the IMAP server providing the original email

> The "fetch body[]" command works for what I have to do.

And in that case the IMAP server seems to be providing the remote part
of the message for you (the "missing" body part in the first email is
external, so there's nothing for fetchmail to download).

I'd say the IMAP server is behaving strangely, but I'm not sure what
the expected behavior for external body parts is.

-- 
                 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] IMAP problem

[Alain C. <Ala...@th...>]

Hi.

I'm quite a newbie with Fetchmail, and I've read the FAQs before writing 
to this list.

This is my problem : I need to fetch mails from an IMAP account and direct 
them to the local SMTP port. Fetchmail seems the perfect tool for that.
However, the mails I fetch from the IMAP account are mainly composed with 
an attached file.

When using fetchmail, the downloaded mail contains only some text (an 
hypertext link to the file).
When using a mail reader (Outlook or Thunderbird), the mail seems to be 
complete (ie the file is downloaded).

To understand what happened, I ran telnet, and these are some 
transcriptions for the IMAP dialog :


-----------------------------------------------------------------------
Talk-It:~ # telnet 192.168.1.2 143
Trying 192.168.1.2...
Connected to 192.168.1.2.
Escape character is '^]'.
* OK Talk_It IMAP4rev1 v10.210 server ready

* BAD Null command
login 100 100
login BAD Command unrecognized/login please: 100
LOGIN 100 100
LOGIN BAD Command unrecognized/login please: 100
0001 LOGIN 100 100
0001 OK LOGIN completed
0002 list
0002 BAD Missing required argument to LIST
0002 list "*" "*"
* LIST (\NoInferiors) NIL INBOX
0002 OK LIST completed
0003 select INBOX
* NO Mailbox is open by another process, access is readonly
* 15 EXISTS
* OK [UIDVALIDITY 1038355870] UID validity status
* OK [UIDNEXT 21] Predicted next UID
* FLAGS (\Answered \Flagged \Deleted \Draft \Seen)
* OK [PERMANENTFLAGS ()] Permanent flags
* 0 RECENT
0003 OK [READ-ONLY] SELECT completed
0004 fetch 1 body[text]
* 1 FETCH (BODY[TEXT] {684}
This is a multi-part message in MIME format.

--Part.0001_32C9D122_000AF8A4.00E0BB00C727
Content-Type: message/external-body; access-type=local-file;
        name="/htfs0/data/0/5/7/5/8/10517515.113";
        size=6472;
        xtype="audio/wav"

Content-Type: audio/wav
Content-ID: <0001_32C9D122_000AF8A4.00E0BB00C727>
Content-Transfer-Encoding: binary

--Part.0001_32C9D122_000AF8A4.00E0BB00C727
Content-Type: application/octet-stream;
        name="message.url"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
        filename="message.url"

[InternetShortcut]
URL=http://192.168.1.2:8889/htfs0/data/0/5/7/5/8/10517515.113.wav

--Part.0001_32C9D122_000AF8A4.00E0BB00C727--

)
0004 OK FETCH completed
-------------------------------------------------------------------------

The fetch body[text] command seems to be the one used by fetchmail and 
doesn't download the file.


Continuing with another fetch command :




-----------------------------------------------------------------------------
0005 fetch BODY[]
0005 BAD Missing required argument to FETCH
0005 fetch 1 BODY[]
* 1 FETCH (BODY[] {9885}
Received: via tmail-4.1(5) for uid202; Wed, 1 Jan 1997 03:51:15 +0100 
(MET)
From: <anonymous>
To: "Talk-It" <100@192.168.1.2>
Date: Wed, 1 Jan 1997 03:51:14 +0100 (MET)
Subject: Call Answering Message from Ligne_1/820222180
MIME-Version: 1.0 (Voice 2.0)
Content-Type: multipart/voice-message; 
boundary="Part.0001_32C9D122_000AF8A4.00E0BB00C727"
Content-Transfer-Encoding: 7bit
Message-ID: <0001_32C9D122_000AF8A4.00E0BB00C727>

This is a multi-part message in MIME format.

--Part.0001_32C9D122_000AF8A4.00E0BB00C727
Content-Type: audio/wav; name="10517515x113.wav"
Content-Transfer-Encoding: base64
Content-Disposition: inline; filename="10517515x113.wav"

UklGRjQZAABXQVZFZm10IBQAAAARAAEAQB8AANcPAAAAAQQAAgD5AWZhY3QEAAAAUTEAAGRh
dGEAGQAAuQEnAMuaMSWRzIoxJZG8m1EkkcyKMCWB25owNJHbmzE1gcyaMDWBvJwwNILrqjBE
gdqbMDSC26swJpLLqzE1gtqrIDWC25wgNAHqmhA0Acq7ODaByqs4NQLqqyBEgsm7IEQCyqwg
U4LKqyg1EturIEQCypwoQwLaqjlEAcqrKEUBuqwoNAPqmyhEAbqdGDSC2ps4NQHanCAzg+uq

(...)
MNCAgAQIwIAAAAAECAwIQIAAwIAABAjAgECAAMCAAAQIwIAABAjAgAAECAwIQIAM7P8BADAR
DAhAgAAMCAQIwIBACwkAQIDAgECAAAwIQMAACAAEDAMNCEjAAJM80ICABAjAgAAECMCAAAQI
DAhAgAAMCAQIwIAABAjAgAAECAwIQIDAgABAgADAgECAAAwIQIDAgECAAAwIBAjAgECAAAwI
QIAADAhAgAAMCECAAAwIBAgMCAQIwIBAgAAMCECAAAwIQIAADAhAgAAMCECAAAwIQIDAgECA
wIBAgAAMCECAAAwIQIAADAhAgAAMCAAECAAAwIAABAgADEiAAMCAQDvAgAATAZsJEwGbCRMB
mwkAEwGwmQATsZkAEwGwmTARAJsJMBEAmwkwEQCwmQATAXJmY3QEAAAAAQAAAA==

--Part.0001_32C9D122_000AF8A4.00E0BB00C727
Content-Type: application/octet-stream;
        name="message.url"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
        filename="message.url"

[InternetShortcut]
URL=http://192.168.1.2:8889/htfs0/data/0/5/7/5/8/10517515.113.wav

--Part.0001_32C9D122_000AF8A4.00E0BB00C727--

)
0005 OK FETCH completed
--------------------------------------------------------------------

The "fetch body[]" command works for what I have to do.

Well, at this time, I don't really what or who is wrong in my case. Does 
that mean that the IMAP server is not clean regarding protocol ?
Could someone help me to solve my problem.

Regards.

Alain CHOFARDET

[fetchmail-users] Fetchmail not working Fedora Core 3 and FC 4

[Denny S. <de...@st...>]

Hi Everyone,

I did a Yum install of Fetchmail on my Fedora Core 3 box. From the shell i
type fetchmail and there is no
response its just blank and i dont get a prompt back. I then have to do CRTL
C to quit.

I upgraded to FC 4 with the latest binary of Fetchamail and the same
problem. Ive tried yum remove fetchmail and then re-install and
i get the same problem. Could i be missing a library file ?

The version i have is 6.2.5.5-1

thanks for nay help.

Denny