fetchmail-users — User questions and discussion

Re: [fetchmail-users] Problems with line-wrapping and Apple Mail users

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

On 10/27/06, Rob MacGregor <rob...@gm...> wrote:
>
> No.  How your mail client treats the mail is beyond fetchmail's control.
>
> I'd suggest you confirm that it's a bug with Apple Mail by pointing it
> directly at your ISP and downloading a test email with a long URL.
> This should give you enough to allow you to file a bug report with
> Apple.

I should have said that the problem is that (it appears that) Apple
Mail isn't honouring format=flowed.  You'll almost certainly find that
the original email has the lines wrapped at 72 characters, hence why
Apple Mail displays the URLs wrapped at 72 characters.

You still can't fix this with fetchmail :)

-- 
                 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] Problems with line-wrapping and Apple Mail users

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

On 10/27/06, Chris Cera <ce...@cs...> wrote:
> All my coworkers that send me URLs using Apple Mail have links
> over 72 characters wrapped.  I have a feeling that the
> Content-Type line is the problem, particularly the format=flowed
> portion of the header.  Are there any options I can set in
> fetchmail to prevent this from happening?

No.  How your mail client treats the mail is beyond fetchmail's control.

I'd suggest you confirm that it's a bug with Apple Mail by pointing it
directly at your ISP and downloading a test email with a long URL.
This should give you enough to allow you to file a bug report with
Apple.

-- 
                 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] Problems with line-wrapping and Apple Mail users

[Chris C. <ce...@cs...>]

All my coworkers that send me URLs using Apple Mail have links
over 72 characters wrapped.  I have a feeling that the
Content-Type line is the problem, particularly the format=flowed
portion of the header.  Are there any options I can set in
fetchmail to prevent this from happening?  It appears as though
the source email, before I download it via fetchmail, is fine
when I use the web-based client.  The email they send is in
plain-text format.  The headers are below.  Any help is greatly
appreciated.  Thank you!

    Mime-Version: 1.0 (Apple Message framework v752.2)
    Content-Transfer-Encoding: 7bit
    Message-Id: <EB8...@dr...>
    Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
    To: Chris Cera <te...@te...>
    From: Test Person <te...@te...>
    Subject: long link...
    Date: Thu, 26 Oct 2006 18:48:42 -0400
    X-Mailer: Apple Mail (2.752.2)
    X-Identified-User: {1262:box101.test.com:drakonta:drakontas.com} {sentby:bopbeforesmtp 71.242.246.42 authed with drakontas.com}
    X-IMAPbase: 1161902931 1
    Status: RO
    X-Status:
    X-Keywords:
    X-UID: 1

-- 
Chris Cera                                         http://cera.us

Re: [fetchmail-users] How to tell fetchmail to skip problematic messages

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

On 10/26/06, Hasan Shatty <hs...@ya...> wrote:
> I have setup fetchmail to fetch from a multidrop pop account and deliver to
> a local MTA.
>
> Some messages (mostly spam or corrupted) cause the MTA to close the socket
> and not accept the message. In this case fetchmail will retry to deliver the
> same message again and mails will get accumulated until I delete the
> problematic messge from the queue.
>
> Is there a way to avoid this issue and let fetchmail simply delete the
> message or ignore it or deliver it to a local spool.

Correctly configure the MTA to provide an appropriate error code - see
the section titled "Spam Filtering" in the fetchmail man page.

-- 
                 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 to tell fetchmail to skip problematic messages

[Hasan S. <hs...@ya...>]

I have setup fetchmail to fetch from a multidrop pop account and deliver to a local MTA.
   
  Some messages (mostly spam or corrupted) cause the MTA to close the socket and not accept the message. In this case fetchmail will retry to deliver the same message again and mails will get accumulated until I delete the problematic messge from the queue.
   
  Is there a way to avoid this issue and let fetchmail simply delete the message or ignore it or deliver it to a local spool.
   
  My .fetchmailrc file as follows:
   
  set daemon 120
set logfile "/var/log/fetchmail"
set postmaster pos...@do...
set no bouncemail
poll mailserver.domain.com
        proto pop3
        localdomains domain.com
        envelope 1 Delivered-To:
        qvirtual '17-'
        no dns
        user "popuser"
        pass "password"
        to * here
        fetchall
        no keep
   
  Thanks

 		
---------------------------------
 All-new Yahoo! Mail - Fire up a more powerful email and get things done faster.

Re: [fetchmail-users] first time setup help

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

On 10/25/06, wa...@wa... <wa...@wa...> wrote:
> 10242006 1901 GMT-6
>
> I'm on ubuntu 6.06LTS.
> I'm setting up fetchmail for the first time.
> I have a few questions on the settings.
>
> I have been reading the documentation but as this is all new to me, I
> want to make sure I'm getting this right.
>
> I used fetchmailconf to get started. It created this:
>
> set syslog
> set postmaster "wadesmart"
> set no bouncemail
> set no spambounce
> set properties ""
> set daemon 120
>
> poll mail.wadesmart.com
>      user 'wa...@wa...' there with password 'password' is
> 'wadesmart' here

That looks fine.

> That is all that it put down. So I'm reading the documentation and I see
> that there is supposed to be something else. I added:
>
> poll mail.wadesmart.com
>   uidl protocol pop3 auth password
>   user 'wa...@wa...' there with password 'password' is
> 'wadesmart' here
>   nokeep

UIDL is worth having, the other changes you shouldn't need.

> I read in the documentation that postmaster is usually 'root' so I
> wonder about this being 'wadesmart'.

That's the way I do it and it works fine.

-- 
                 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] first time setup help

[<wa...@wa...>]

10242006 1901 GMT-6

I'm on ubuntu 6.06LTS.
I'm setting up fetchmail for the first time.
I have a few questions on the settings.

I have been reading the documentation but as this is all new to me, I
want to make sure I'm getting this right.

I used fetchmailconf to get started. It created this:

set syslog
set postmaster "wadesmart"
set no bouncemail
set no spambounce
set properties ""
set daemon 120

poll mail.wadesmart.com
     user 'wa...@wa...' there with password 'password' is
'wadesmart' here

That is all that it put down. So I'm reading the documentation and I see
that there is supposed to be something else. I added:

poll mail.wadesmart.com
  uidl protocol pop3 auth password
  user 'wa...@wa...' there with password 'password' is
'wadesmart' here
  nokeep


I read in the documentation that postmaster is usually 'root' so I
wonder about this being 'wadesmart'.

Thanks for the help.

wade smart

Re: [fetchmail-users] Problem downloading fetchmail-6.3.5.tar.bz2

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

Uli Zappe <ul...@ri...> writes:

> Hi,
>
> I have not been able to download fetchmail-6.3.5.tar.bz2 from the  
> BerliOS server.
>
> Loading
>
>     http://download(2).berlios.de/fetchmail/fetchmail-6.3.5.tar.bz2
>
> always results in the message
>
>     "Too many clients for /fetchmail/fetchmail-6.3.5.tar.bz2"
>
> The number of downloads has remained at 4880 all the time.
>
> I was able to download fm635-daemon-logfile.patch and  
> fetchmail-6.3.5.tar.bz2.asc without any problem, so it's not a  
> general networking issue.

Gee, someone apparently trashed the file. I've filed a support request
and am uploading 00-fetchmail-6.3.5.tar.bz2 just now.

If that doesn't work:
http://home.pages.de/~mandree/fetchmail/

Please report future file corruption to me directly (Cc: is fine) so I
can see the report much sooner.

Thank you.

-- 
Matthias Andree

Re: [fetchmail-users] Problem downloading fetchmail-6.3.5.tar.bz2

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

On 10/22/06, Uli Zappe <ul...@ri...> wrote:
> Hi,
>
> I have not been able to download fetchmail-6.3.5.tar.bz2 from the
> BerliOS server.
>
> Loading
>
>     http://download(2).berlios.de/fetchmail/fetchmail-6.3.5.tar.bz2
>
> always results in the message
>
>     "Too many clients for /fetchmail/fetchmail-6.3.5.tar.bz2"
>
> The number of downloads has remained at 4880 all the time.

I can confirm this - looks like something broken at berlios :(

-- 
                 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] Problem downloading fetchmail-6.3.5.tar.bz2

[Uli Z. <ul...@ri...>]

Hi,

I have not been able to download fetchmail-6.3.5.tar.bz2 from the  
BerliOS server.

Loading

    http://download(2).berlios.de/fetchmail/fetchmail-6.3.5.tar.bz2

always results in the message

    "Too many clients for /fetchmail/fetchmail-6.3.5.tar.bz2"

The number of downloads has remained at 4880 all the time.

I was able to download fm635-daemon-logfile.patch and  
fetchmail-6.3.5.tar.bz2.asc without any problem, so it's not a  
general networking issue.

             Bye
                     Uli
________________________________________________________

   Uli Zappe, Solmsstraße 5, D-65189 Wiesbaden, Germany
   http://www.ritual.org
   Fon: +49-700-ULIZAPPE
   Fax: +49-700-ZAPPEFAX
________________________________________________________

Re: [fetchmail-users] fetchmail deletes imap messages

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

longbow <lo...@gm...> writes:

> i think i solved the problem on my own: i used the '-a' option in my
> local fetchmail command:
> /bin/su wolfgang -c '/usr/bin/fetchmail -a -f
> /home/wolfgang/.fetchmailrc -d 300 -L /home/wolfgang/fetchmail.log 2>&1'

-a (= fetchall) and keep don't mix...

> and i think this confused the "keep" option in my .fetchmailrc. i tested
> a few mailsendings and everything seems to run fine. i also do not get
> the message
> fetchmail: restarting fetchmail (/home/USER/.fetchmailrc changed)
> Both fetchall and keep on in daemon mode is a mistake!

...and fetchmail complains here. So you have been warned about the mistake...

-- 
Matthias Andree

Re: [fetchmail-users] fetchmail deletes imap messages

[longbow <lo...@gm...>]

Rob MacGregor wrote:
> On 10/12/06, longbow <lo...@gm...> wrote:
> 
>> here it is:
>> poll MAILSERVER1 protocol IMAP   user "MAILBOXUSER1" password "PWD1"
>>    is LOCALUSER keep
>> poll MAILSERVER2 protocol POP3   user "MAILBOXUSER2" password "PWD2" ssl
>>   is LOCALUSER
> 
> Looks fine.
> 
>>  fetchmail --nosyslog -v -v
> 
> Should have been more explicit - can you provide that for a run
> showing a mail being downloaded.  That way we can confirm fetchmail's
> actions.
> 
>> fetchmail --configdump
> 
> Thanks, that shows your config is basically ok.
> 
>> hope you can help me with this.
> 
> Should be able to - the log showing a mail being downloaded from the
> IMAP server will tell me.
> 
hi!

i think i solved the problem on my own: i used the '-a' option in my
local fetchmail command:
/bin/su wolfgang -c '/usr/bin/fetchmail -a -f
/home/wolfgang/.fetchmailrc -d 300 -L /home/wolfgang/fetchmail.log 2>&1'

and i think this confused the "keep" option in my .fetchmailrc. i tested
a few mailsendings and everything seems to run fine. i also do not get
the message
fetchmail: restarting fetchmail (/home/USER/.fetchmailrc changed)
Both fetchall and keep on in daemon mode is a mistake!
fetchmail: starting fetchmail 6.3.4 daemon

the messages remain on the server and only unseen messages are beeing
fetched!!

thx a lot for the help!

greets
snIP3r

Re: [fetchmail-users] fetchmail deletes imap messages

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

On 10/12/06, longbow <lo...@gm...> wrote:

> here it is:
> poll MAILSERVER1 protocol IMAP   user "MAILBOXUSER1" password "PWD1"
>    is LOCALUSER keep
> poll MAILSERVER2 protocol POP3   user "MAILBOXUSER2" password "PWD2" ssl
>   is LOCALUSER

Looks fine.

>  fetchmail --nosyslog -v -v

Should have been more explicit - can you provide that for a run
showing a mail being downloaded.  That way we can confirm fetchmail's
actions.

> fetchmail --configdump

Thanks, that shows your config is basically ok.

> hope you can help me with this.

Should be able to - the log showing a mail being downloaded from the
IMAP server will tell me.

-- 
                 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 deletes imap messages

[longbow <lo...@gm...>]

Rob MacGregor wrote:
> On 10/12/06, longbow <lo...@gm...> wrote:
>> hi all!
>>
>> i think i have a problem with my fetchmail (config). i use it to get all
>> the email from my various accounts. in the .fetchmailrc in my home dir i
>> put something like this:
>>
>> poll MAILSERVER   protocol IMAP   user "MAILBOXUSERNAME" password
>> "THESECRET" is LOCALUSER  keep
> 
> Can we see the file (munge username and password)?  "Something like"
> isn't good enough.

here it is:
poll MAILSERVER1 protocol IMAP   user "MAILBOXUSER1" password "PWD1"
   is LOCALUSER keep
poll MAILSERVER2 protocol POP3   user "MAILBOXUSER2" password "PWD2" ssl
  is LOCALUSER
> 
> The output of "fetchmail --nosyslog -v -v" is also necessary and
> "fetchmail --configdump" would help (remember to munge username and
> password).
> 

 fetchmail --nosyslog -v -v
fetchmail: 6.3.4 querying MAILSERVER1 (protocol IMAP) at Thu Oct 12
17:42:05 2006: poll started
fetchmail: IMAP< * OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE
THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE ACL ACL2=UNION]
Courier-IMAP ready. Copyright 1998-2004 Double Precision, Inc.  See
COPYING for distribution information.
fetchmail: IMAP> A0001 CAPABILITY
fetchmail: IMAP< * CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE
THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE ACL ACL2=UNION
fetchmail: IMAP< A0001 OK CAPABILITY completed
fetchmail: Protocol identified as IMAP4 rev 1
fetchmail: IMAP> A0002 LOGIN "MAILBOXUSER1" *
fetchmail: IMAP< A0002 OK LOGIN Ok.
fetchmail: selecting or re-polling default folder
fetchmail: IMAP> A0003 SELECT "INBOX"
fetchmail: IMAP< * FLAGS (\Draft \Answered \Flagged \Deleted \Seen \Recent)
fetchmail: IMAP< * OK [PERMANENTFLAGS (\* \Draft \Answered \Flagged
\Deleted \Seen)] Limited
fetchmail: IMAP< * 0 EXISTS
fetchmail: IMAP< * 0 RECENT
fetchmail: IMAP< * OK [UIDVALIDITY 1159609714] Ok
fetchmail: IMAP< * OK [MYRIGHTS "acdilrsw"] ACL
fetchmail: IMAP< A0003 OK [READ-WRITE] Ok
fetchmail: 0 messages waiting after first poll
fetchmail: No mail for MAILBOXUSER1 at MAILSERVER1
fetchmail: IMAP> A0004 LOGOUT
fetchmail: IMAP< * BYE Courier-IMAP server shutting down
fetchmail: IMAP< A0004 OK LOGOUT completed
fetchmail: 6.3.4 querying MAILSERVER1 (protocol IMAP) at Thu Oct 12
17:42:06 2006: poll completed
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: 6.3.4 querying MAILSERVER2 (protocol POP3) at Thu Oct 12
17:42:06 2006: poll started
fetchmail: Issuer Organization: THE ORGANIZATION
fetchmail: Issuer CommonName: Certification Authority (CA) 2005
fetchmail: Server CommonName: MAILSERVER2
fetchmail: MAILSERVER1 key fingerprint:
72:72:A9:AE:DD:11:DA:01:C4:9D:29:D8:88:C7:74:39
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< +OK CommuniGate Pro POP3 Server 5.0.2 ready
<88610.1160667726@MAILSERVER2>
fetchmail: POP3> CAPA
fetchmail: POP3< +OK capability list follows
fetchmail: POP3< SASL LOGIN PLAIN
fetchmail: POP3< LAST
fetchmail: POP3< TOP
fetchmail: POP3< USER
fetchmail: POP3< PIPELINING
fetchmail: POP3< UIDL
fetchmail: POP3< IMPLEMENTATION CommuniGatePro
fetchmail: POP3< .
fetchmail: POP3> USER MAILBOXUSER2
fetchmail: POP3< +OK please send the PASS
fetchmail: POP3> PASS *
fetchmail: POP3< +OK 0 messages (0 bytes)
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for MAILBOXUSER2 at MAILSERVER2
fetchmail: POP3> QUIT
fetchmail: POP3< +OK CommuniGate Pro POP3 Server connection closed
fetchmail: 6.3.4 querying MAILSERVER2 (protocol POP3) at Thu Oct 12
17:42:08 2006: poll completed
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: Deleting fetchids file.
fetchmail: normal termination, status 1
fetchmail: Deleting fetchids file.





fetchmail --configdump
TRUE=1; FALSE=0

os_type = 'linux'
feature_options = ('pop3','imap','rpa','sdps','etrn','odmr','ssl',)
# Start of configuration initializer
fetchmailrc = {
    'poll_interval':0,
    "logfile":None,
    "idfile":"/home/LOCALUSER/.fetchids",
    "postmaster":"LOCALUSER",
    'bouncemail':TRUE,
    'spambounce':FALSE,
    "properties":None,
    'invisible':FALSE,
    'showdots':TRUE,
    'syslog':FALSE,
    # List of server entries begins here
    'servers': [
        # Entry for site `MAILSERVER1' begins:
        {
            "pollname":"MAILSERVER1",
            'active':TRUE,
            "via":None,
            "protocol":"IMAP",
            "service":None,
            'timeout':300,
            'interval':0,
            "envelope":"Received",
            'envskip':0,
            "qvirtual":None,
            "auth":"any",
            'dns':TRUE,
            'uidl':FALSE,
            "aka":[],
            "localdomains":[],
            "interface":None,
            "monitor":None,
            "plugin":None,
            "plugout":None,
            "principal":None,
            'tracepolls':FALSE,
            'users': [
                {
                    "remote":"MAILBOXUSER1",
                    "password":"PWD1",
                    'localnames':["LOCALUSER"],
                    'fetchall':FALSE,
                    'keep':TRUE,
                    'flush':FALSE,
                    'limitflush':FALSE,
                    'rewrite':TRUE,
                    'stripcr':FALSE,
                    'forcecr':FALSE,
                    'pass8bits':FALSE,
                    'dropstatus':FALSE,
                    'dropdelivered':FALSE,
                    'mimedecode':FALSE,
                    'idle':FALSE,
                    "mda":None,
                    "bsmtp":None,
                    'lmtp':FALSE,
                    "preconnect":None,
                    "postconnect":None,
                    'limit':0,
                    'warnings':3600,
                    'fetchlimit':0,
                    'fetchsizelimit':100,
                    'fastuidl':4,
                    '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':'',
                    "mailboxes":[],
                }
                ,           ]
        }
        ,
        # Entry for site `MAILSERVER2' begins:
        {
            "pollname":"MAILSERVER2",
            'active':TRUE,
            "via":None,
            "protocol":"POP3",
            "service":None,
            'timeout':300,
            'interval':0,
            "envelope":"Received",
            'envskip':0,
            "qvirtual":None,
            "auth":"any",
            'dns':TRUE,
            'uidl':FALSE,
            "aka":[],
            "localdomains":[],
            "interface":None,
            "monitor":None,
            "plugin":None,
            "plugout":None,
            "principal":None,
            'tracepolls':FALSE,
            'users': [
                {
                    "remote":"MAILBOXUSER2",
                    "password":"PWD2",
                    'localnames':["LOCALUSER"],
                    'fetchall':FALSE,
                    'keep':FALSE,
                    'flush':FALSE,
                    'limitflush':FALSE,
                    'rewrite':TRUE,
                    'stripcr':FALSE,
                    'forcecr':FALSE,
                    'pass8bits':FALSE,
                    'dropstatus':FALSE,
                    'dropdelivered':FALSE,
                    'mimedecode':FALSE,
                    'idle':FALSE,
                    "mda":None,
                    "bsmtp":None,
                    'lmtp':FALSE,
                    "preconnect":None,
                    "postconnect":None,
                    'limit':0,
                    'warnings':3600,
                    'fetchlimit':0,
                    'fetchsizelimit':100,
                    'fastuidl':4,
                    'batchlimit':0,
                    'ssl':TRUE,
                    "sslkey":None,
                    "sslcert":None,
                    "sslproto":None,
                    'sslcertck':FALSE,
                    "sslcertpath":None,
                    "sslfingerprint":None,
                    'expunge':0,
                    "properties":None,
                    "smtphunt":["localhost"],
                    "fetchdomains":[],
                    "smtpaddress":None,
                    "smtpname":None,
                    'antispam':'',
                    "mailboxes":[],
                }
                ,           ]
        }
    ]
}
# End of initializer



>> this runs perfect expect that the fetchmail daemon is deleting the
>> messages in the remote server's inbox. i read in the manual that
>> deleteing is the default action and adding "keep" should keep the
>> messages on the remote side. i tried it and fetchmail recognizes that
>> the config has changed by diplaying this:
> 
> This isn't normal for the config you're talking about - I poll an IMAP
> server with keep and it doesn't delete the messages.
> 
> The possibilities are that either you've not got a valid configuration
> or the remote server is doing something it shouldn't.  The information
> I've asked for will help identify which.

well i thought so too...

> 
> (Oh, and I'd suggest you read the FAQ, which details what you should
> provide when reporting something you think is a bug).
> 

hope you can help me with this.

thx
longbow

Re: [fetchmail-users] fetchmail deletes imap messages

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

On 10/12/06, longbow <lo...@gm...> wrote:
> hi all!
>
> i think i have a problem with my fetchmail (config). i use it to get all
> the email from my various accounts. in the .fetchmailrc in my home dir i
> put something like this:
>
> poll MAILSERVER   protocol IMAP   user "MAILBOXUSERNAME" password
> "THESECRET" is LOCALUSER  keep

Can we see the file (munge username and password)?  "Something like"
isn't good enough.

The output of "fetchmail --nosyslog -v -v" is also necessary and
"fetchmail --configdump" would help (remember to munge username and
password).

> this runs perfect expect that the fetchmail daemon is deleting the
> messages in the remote server's inbox. i read in the manual that
> deleteing is the default action and adding "keep" should keep the
> messages on the remote side. i tried it and fetchmail recognizes that
> the config has changed by diplaying this:

This isn't normal for the config you're talking about - I poll an IMAP
server with keep and it doesn't delete the messages.

The possibilities are that either you've not got a valid configuration
or the remote server is doing something it shouldn't.  The information
I've asked for will help identify which.

(Oh, and I'd suggest you read the FAQ, which details what you should
provide when reporting something you think is a bug).

-- 
                 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 deletes imap messages

[longbow <lo...@gm...>]

hi all!

i think i have a problem with my fetchmail (config). i use it to get all
the email from my various accounts. in the .fetchmailrc in my home dir i
put something like this:

poll MAILSERVER   protocol IMAP   user "MAILBOXUSERNAME" password
"THESECRET" is LOCALUSER  keep

this runs perfect expect that the fetchmail daemon is deleting the
messages in the remote server's inbox. i read in the manual that
deleteing is the default action and adding "keep" should keep the
messages on the remote side. i tried it and fetchmail recognizes that
the config has changed by diplaying this:

fetchmail: restarting fetchmail (/home/USER/.fetchmailrc changed)
Both fetchall and keep on in daemon mode is a mistake!
fetchmail: starting fetchmail 6.3.4 daemon

and it still gets the messages and deletes them from remote server. i
wonder about this behavoiur of fetchmail cause if i use IMAP than i want
the messages to stay on the server, not getting them deleted! why cant i
use daemon mode and the keep option?

is there a possibility to fix this??

thx in advance

snIP3r

[fetchmail-users] patch for fetchmail 6.3.5 stable release

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

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

Well,

a problem with --logfile rendering it useless went undetected through
the 6.3.5-beta* phase.

I have uploaded fm635-daemon-logfile.patch to the BerliOS site at
<http://developer.berlios.de/project/showfiles.php?group_id=1824> that
is supposed to fix this problem. Feedback as to whether it really fixes
- --logfile /SOME/LOG.FILE is needed. Expected behavior is that IN DAEMON
MODE, output shows up in the logfile. Note you cannot use syslog at the
same time. In doubt:

fetchmail -q
fetchmail --daemon 900 --nosyslog --logfile /SOME/LOG.FILE

Please reply to fet...@li... (Reply-To set) or to
fetchmail-devel@... if you have more technical comments.

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

iD8DBQFFLI/YvmGDOQUufZURAvv1AJsHU8McNOE7QU9tbXTy4ywtBTqyGwCgm2nA
qh2SZznc+I291KTxZadpnWg=
=ADSQ
-----END PGP SIGNATURE-----

[fetchmail-users] fetchmail 6.3.5 stable release

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

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

Greetings,

I am announcing the release of fetchmail 6.3.5. This new stable version
of fetchmail fixes several minor bugs and revises the FAQ.

- ---------------------------------------------------------------------
NOTE THAT THE CCIL.ORG MAILING LISTS ARE DEPRECATED AND WILL BE SHUT
DOWN LATER THIS YEAR. Please subscribe to the new lists at
<https://developer.berlios.de/mail/?group_id=1824>:
- - for fetchmail-announce subscribers: subscribe to fetchmail-announce
- - for fetchmail-friends subscribers: subscribe to fetchmail-users
- ---------------------------------------------------------------------

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

The fetchmail home pages are:
<http://www.fetchmail.info/>  or  <http://fetchmail.berlios.de/>

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

fetchmail 6.3.5 (released 2006-10-09):

# DEPRECATED FEATURES AND MAJOR INCOMPATIBLE CHANGE ADVANCE WARNINGS
* The MX and host alias DNS lookups that fetchmail performs in multidrop mode
  are obsolete, deprecated and may be removed from a future fetchmail version.
  They have never supported IPv6 (including IPv6-mapped IPv4) anyhow.
  Non-DNS based alias keywords such as "aka" will remain in fetchmail.
* The monitor and interface options may be removed from a future fetchmail
  version as they are not sufficiently portable.
* POP2 is obsolete.
  Support for POP2 may be removed from a future fetchmail version.
* RPOP is obsolete, support may be removed from a future fetchmail release.
* --sslcertck may become a default setting in a future fetchmail version.
* The multidrop To/Cc guessing code along with the fragile duplicate suppressor
  is deprecated and may be removed from a future release.
* The "envelope Received" option may be removed from a future release, because
  the Received header was never meant to be machine-readable, the format varies
  widely, and various other differences in behavior make parsing Received an
  unreliable undertaking. The enveloper option as such will remain though, in
  order to support Delivered-To, X-Envelope-To, X-Original-To and similar.
  See also <http://home.pages.de/~mandree/mail/multidrop>.
* The --enable-fallback (fall back to MDA if MTA unavailable) may be removed
  from a future fetchmail release.
* The "protocol auto" default inside fetchmail may be removed from a future
  fetchmail release. Explicit configuration of the protocol is recommended.
* Kerberos IV support may be removed from a future fetchmail release.
* SIGHUP wakeup may be removed from a future fetchmail release and cause it
  to terminate.
* Support for operating systems that are not sufficiently POSIX compliant may be
  removed or operation on such systems may be suboptimal for future releases.

# KNOWN BUGS AND WORKAROUNDS:
  (this section floats upwards through the NEWS to be on top of the list)
* fetchmail does not handle messages without Message-ID header well
  (See sourceforge.net bug #780933)
* Sun Workshop 6 (SPARC) is known to miscompile the lexer in 64-bit mode.
  Either compile 32-bit code or use GCC to compile 64-bit fetchmail.
  Note that fetchmail doesn't take advantage of 64-bit code anyways,
  so compiling 32-bit SPARC code should be fine.
* fetchmail expects Received: headers in a particular format when parsing
  envelopes.
* fetchmail does not track pending deletes over crashes
* the command line interface is a bit narrow-minded sometimes, for instance,
  fetchmail -s doesn't work with a running daemon
* some of the logging output is not very helpful
* some of the documentation is still not up to date

# BUG FIXES:
* For protocols such as IMAP that are not delimited by "." lines, truncate the
  input buffer when the message has been completely read, to avoid taking
  trailing garbage into the message if the terminal CRLF is missing. Fixes
  Debian Bug#312415. (Patch suggested by Mike Jones, Manchester Univ.).
* When using NTLM authentication, use regular IMAP response code handler after
  completing NTLM handshake, for robustness and consistency.
  (Taken from the NetBSD portable packages collection, patch-ac.)
* Support Kerberos installations where krb5.h and perhaps roken.h are in
  .../include/krb5.  Taken from NetBSD portable packages collection patch-ae.
* On NetBSD, link against -lroken -lcom_err if --with-kerberos is enabled.
* Drop #include <com_err.h> from Kerberos 5 header file, fixes compile error on
  SUSE Linux 10.0.
* Fix des_pcbc_encrypt compile warnings in kerberos.c line 246.
* If krb5-config provides gssapi library information, use that rather than
  guessing.
* Improve --with-gssapi auto detection for /usr-based GSSAPI installs.
* Fix --with-gssapi builds for NetBSD 3.0.
* Improve KAME/getnameinfo.c portability to Linux libc5 systems.
  Based on a patch by Dan Fandrich.
* Provide INET6 to KAME/getnameinfo.c (only useful on IPv6-enabled systems that
  lack getnameinfo, and there only visible in some Received: headers).
  Found by Dan Fandrich.
* POP3: some UID flags may not be set properly on UIDL lists. (Sunil Shetye)
* Make IMAP4 IDLE work on servers that do not update RECENT counts.
  Reported by Lars Tewes.
* IMAP4 patch by Sunil Shetye:
  - do not depend on server updating RECENT counts at all
  - also enter IDLE loop when messages are present on the server.
* Fix --flush description in the manual page, fetchmail does not mark messages
  seen unless it has successfully delivered them. Suggested by Frederic Marchal.
* Fetchmail no longer attempts to stat the "-" file in daemon mode -- this is a
  special name to read the RC file from stdin, and cannot always be re-read
  anyways. BerliOS bug #7858.
* When looking up ports for a service, the lookup succeeds and the returned
  address family isn't IPv4 or IPv6, properly free the allocated memory from the
  service lookup. Found by Uli Zappe.
* When looking up ports for a service, only look up TCP ports.
* Avoid compiling empty files, to avoid diagnostics from strict compilers.
* If the lockfile ends before the process ID, treat it as stale and unlink it.
  Reported by Justin Pryzby, Debian Bug #376603.
* SIGHUP wake-up behavior was broken since 5.9.13's Cygwin changes, in that for
  non-root users, SIGHUP would abort the first poll and subsequently interfere
  with new polls, and SIGHUP would be ignored for root users. SIGHUP now matches
  documented behavior. SIGUSR1 has always been a wakeup signal for both root
  (undocumented) and non-root users. See also the deprecation warning above.
* Track getaddrinfo() results to properly free them after timeouts and make sure
  that getaddrinfo() isn't interrupted by a timeout (which breaks on MacOS X),
  reported by Uli Zappe.  This should fix Debian Bug#294547 and Bug#377135.
* --logfile is now handled more carefully, errors opening the logfile are
  now reported to the TTY where fetchmail was started from.
* fetchmail now complains and aborts when it cannot properly daemonize itself.
* fix compilation on systems that don't know struct addrinfo (Solaris 2.6).
* ignore SIGPIPE signals and rely on functions to return EPIPE instead. This is
  necessary because the former longjmp() from the signal handler is unsafe and
  makes the whole fetchmail behavior undefined after the event.
* 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.

# CHANGES:
* Rename all fetchmail-internal lock_* functions to fm_lock_*. Obsoletes
  NetBSD portable packages collection patch-ah, patch-ai and patch-aj.
* Configure prints a warning (but proceeds) if Kerberos IV support is enabled.
* In verbose mode, log every IP fetchmail tries to connect to, to avoid
  misleading the user. Suppress EAFNOSUPPORT errors from socket() call, too.
  Fixes Debian Bug #361825, reported by Daniel Baur.
* In idle mode, fetchmail complains about the fetchall option.
* When a connection fails, log not only the IP address, but also host and
  service name and the port number. Log the latter when trying to connect in
  verbose mode, too.
* Keep syslog output at one line per message (this works if no errors occur).
* Fetchmail in verbose mode now logs if it opportunistically upgrades a POP3
  or IMAP connection to TLS security with STLS/STARTTLS.
* fetchmail now supports fo...@ex...=bar user mappings for multidrop boxes.
* switch setjmp/longjmp to sigsetjmp/siglongjmp
* IMAP now supports the EXTERNAL authentication method, courtesy of
  Götz 'nimrill' Babin-Ebell, BerliOS patch #1095 with minor changes.
* The sslproto keywords are now case insensitive, courtesy of
  Götz 'nimrill' Babin-Ebell, BerliOS patch #1095.
* When going to sleep, log for how long.  Suggested by Claudia Ludwig.
* When the server name cannot be canonicalized, log the gai_strerror value.

# TRANSLATION UPDATES:
* 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)

# CONTRIBUTED SCRIPTS:
* PopDel.py was revised by Joshua Crawford to display the From: address and
  list every email, even if it has no Subject: header; and not delete the wrong
  message in the presence of mail without Subject: headers.

Regards,

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

iD8DBQFFKfHwvmGDOQUufZURAgKqAKDKa6mUkNnJGMjXMSupaL9u5oCSzwCbBv+C
G+3g7/T/1Rteh1hSP2TCDeA=
=oOOH
-----END PGP SIGNATURE-----

Re: [fetchmail-users] Fetchmail forwarding

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

Michelle Konzack schrieb am 2006-10-01:

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

Because procmail is an unmaintained piece of unconfigurable software (to
many at least) and even such simple recipes are usually wrong - yours
for instance destroys envelope information and is up to nice forwarding
loops...

-- 
Matthias Andree

Re: [fetchmail-users] smtphost option

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

> poll mail.tin.it proto pop3 user 'andrea' with password 'mypassword'
> to andrea smtphost server/2345
It's working.
Thank
Andrea

Re: [fetchmail-users] smtphost option

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

On 10/2/06, Andrea Bencini <and...@ti...> wrote:
> In .fetchmailrc file how and where can I put the option "smtphost
> serve/2345"?

Clearly documented in the man page.

> For example, in .fetcmailrc file I have this string
> poll mail.tin.it proto pop3 user 'andrea' with password 'mypassword' to
> andrea1
>
> Can I put that option? and what is the form to put it?

The man page specifies it as a user option, so (unchecked):

poll mail.tin.it proto pop3 user 'andrea' with password 'mypassword'
to andrea smtphost server/2345

Should work

-- 
                 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...>]

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

[fetchmail-users] smtphost option

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

In .fetchmailrc file how and where can I put the option "smtphost
serve/2345"?

For example, in .fetcmailrc file I have this string
poll mail.tin.it proto pop3 user 'andrea' with password 'mypassword' to
andrea1

Can I put that option? and what is the form to put it?
Thank
Andrea

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

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

Quoting Weidong Cui:

> 33 messages for cu...@in... at my.inbox.com (119345 octets).
> fetchmail: POP3> LIST 1

So inbox.com's POP3 is not compliant to RFC1939.
fetchmail could work around that (not hard to do that), but I'm not sure
 if we should really work around all kinds of brokenness. OTOH, taking a
glance at pop3.c, I'd say the code is already there...

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

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

Thanks,

I did it as you said, ( fetchmail -a , and add "options fetchall" in my config file). but it output:

fetchmail: 6.3.4 querying my.inbox.com (protocol POP3) at Mon Oct  2 17:23:10 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< + PDAyMzU5OTM0MDdCNEM4MDhAV00yOS5pbmJveC5jb20+
fetchmail: decoded as <023...@WM...>
fetchmail: POP3> Y3Vpd2RAaW5ib3guY29tIDQ5NzJmNDg0ZTYyOGUyODM5MDBkZGRlYjQ3YTJhNzU0
fetchmail: POP3< +OK Authentication successful
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 33 119345
33 messages for cu...@in... at my.inbox.com (119345 octets).
fetchmail: POP3> LIST 1
fetchmail: POP3< -ERR error during operation
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 17:23:15 2006: poll completed
fetchmail: Query status=4 (PROTOCOL)
fetchmail: Deleting fetchids file.
fetchmail: normal termination, status 4
fetchmail: Deleting fetchids file.


> -----Original Message-----
> From: jh...@pl...
> Sent: Mon, 02 Oct 2006 14:52:59 +0200
> To: cu...@in...
> Subject: Re: [fetchmail-users] how to config fetchmail for www.inbox.com
> email
> 
> 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...