fetchmail-users — User questions and discussion

[fetchmail-users] [texmex@uni.de: fetchmail: oversized messages notification provides server info but lacks user info]

[Gregor Z. <te...@un...>]

[please Cc: me, i'm not subscribed to this list]

Hi,

this is a feature wish i posted as a debian bug report but
nothing happend.  Now I read (http://lwn.net/Articles/89403/)
there are plans to revive the development of fetchmail and so I
post this here...

Ciao; Gregor



----- Forwarded message from te...@un... -----

From: te...@un...
Date: Mon, 29 Sep 2003 13:20:26 +0200
Message-Id: <E1A...@pi...>
To: Debian Bug Tracking System <su...@bu...>
Subject: fetchmail: oversized messages notification provides server info but lacks
 user info

Package: fetchmail
Version: 6.2.4-2
Severity: normal

When polling several user accounts on the same server the user
gets several oversized messages notifications which do *not*
indicate to which account the notification belongs:

> The following oversized messages remain on the mail server pop.mailprovider.net:
>         1 msg 147133 octets long skipped by fetchmail.
[...]

If the user wants to get/delete one specific message s/he has to
search through all accounts on this server.

Please add the account info to the oversized messages
notification template.

Thanx, Gregor 


-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux pit 2.4.22 #1 Sa Sep 6 01:45:02 CEST 2003 i686
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro

Versions of packages fetchmail depends on:
ii  adduser                       3.51       Add and remove users and groups
ii  base-files                    3.0.10     Debian base system miscellaneous f
ii  debconf                       1.3.14     Debian configuration management sy
ii  debianutils                   2.5.5      Miscellaneous utilities specific t
ii  libc6                         2.3.2-8    GNU C Library: Shared libraries an
ii  libssl0.9.7                   0.9.7b-2   SSL shared libraries

-- debconf information:
* fetchmail/confwarn: 
* fetchmail/systemwide: true
* fetchmail/initdefaultswarn: 
* fetchmail/runasroot: false
  fetchmail/fetchidswarn: 


----- End forwarded message -----

RE: [fetchmail-users] Re: Help with warning: Illegal address syntax (berlios)

[Rob <rob...@ho...>]

> -----Original Message-----
> From: fet...@be... 
> [mailto:fet...@be...] On Behalf Of Rob Funk
> 
> I'm curious about what the broken Return-Path header looks 
> like.  It would 
> be nice if we could do something besides drop the message on 
> the floor.

Details are on the other list's archive, where this problem has had more
discussion :)  From memory there were 2 I saw, one that was concatenated with
the Received header, another that seemed to be missing the closing >.

What I, personally, would like is that any "broken" message (missing the
header line separator, addresses with invalid format etc), could optionally be
forwarded as a plain text attachment to the postamster address.  That way
those who want to receive everything can, and those who're happy to lose it on
the assumption is spam/virus/whatever related can drop it.


PLEASE - keep list traffic on the list.  Email sent directly to me may be
ignored utterly.

-- 
Rob | What part of "no" was it you didn't understand? 

Re: [fetchmail-users] Re: Help with warning: Illegal address syntax (berlios)

[Rob F. <rf...@fu...>]

Gary Sims wrote:
> OK, I have now seen that this isn't a fetchmail problem. I added the
> KEEP option to my fetchmailrc and I used telnet to talk to my ISP's POP3
> server. The Return-Path is broken when it is sent from my ISP.
> Interesting enough I also signed up to this BBC message on a web mail
> account and it arrives there OK without any corruption, so the problem
> is definatley with my ISP.

I'm curious about what the broken Return-Path header looks like.  It would 
be nice if we could do something besides drop the message on the floor.

-- 
==============================|   "A microscope locked in on one point
 Rob Funk <rf...@fu...> |Never sees what kind of room that it's in"
 http://www.funknet.net/rfunk |    -- Chris Mars, "Stuck in Rewind"

Re: [fetchmail-users] Re: Help with warning: Illegal address syntax (berlios)

[Gary S. <ga...@ga...>]

Hi everyone,

OK, I have now seen that this isn't a fetchmail problem. I added the KEEP 
option to my fetchmailrc and I used telnet to talk to my ISP's POP3 server. 
The Return-Path is broken when it is sent from my ISP. Interesting enough I 
also signed up to this BBC message on a web mail account and it arrives there 
OK without any corruption, so the problem is definatley with my ISP.

Thanks (everyone) for all your help.

Gary
-- 
Gary Sims (ga...@ga...)
Vulcan, Brasov, Romania

RE: [fetchmail-users] IDLE support broken?

[Rob <rob...@ho...>]

> -----Original Message-----
> From: fet...@be... 
> [mailto:fet...@be...] On Behalf Of Andreas
> Sent: Friday, July 23, 2004 1:29 PM
> 
> Sure:
> set postmaster "andreas"
> set bouncemail
> set properties ""
> set daemon 120
> 
> poll pop.server with proto IMAP auth password
>        user 'andreas' there is 'andreas' here options idle 
> ssl fetchall warnings 3600
>        mda '/usr/bin/procmail'
> 
> Or is there some syntax error?

If there was, fetchmail wouldn't start.

What I'm seeing is:

fetchmail: 6.2.5 querying imap.isp.co.uk (protocol IMAP) at Sat Jul 24
07:57:34 2004: poll started
fetchmail: IMAP< * OK isp IMAP4rev1 server ready.
fetchmail: IMAP> A0001 CAPABILITY
fetchmail: IMAP< * CAPABILITY IMAP4 IMAP4rev1 IDLE LOGIN-REFERRALS
MAILBOX-REFERRALS NAMESPACE LITERAL+ UIDPLUS CHILDREN
fetchmail: IMAP< A0001 OK CAPABILITY completed.
fetchmail: Protocol identified as IMAP4 rev 1
fetchmail: will idle after poll
fetchmail: IMAP> A0002 LOGIN "user" *
fetchmail: IMAP< A0002 OK LOGIN completed.
fetchmail: selecting or re-polling default folder
fetchmail: IMAP> A0003 SELECT "INBOX"
fetchmail: IMAP< * 0 EXISTS
fetchmail: IMAP< * 0 RECENT
fetchmail: IMAP< * FLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent)
fetchmail: IMAP< * OK [PERMANENTFLAGS (\Seen \Answered \Flagged \Deleted
\Draft $MDNSent)] Permanent flags
fetchmail: IMAP< * OK [UIDVALIDITY 350709] UIDVALIDITY value
fetchmail: IMAP< A0003 OK [READ-WRITE] SELECT completed.
fetchmail: 0 messages waiting after first poll
fetchmail: IMAP> A0004 IDLE
fetchmail: IMAP< + IDLE accepted, awaiting DONE command.

6.2.5 against whatever my ISP is running.  Relevant .fetchmailrc entries:

defaults proto pop3
        pass8bits
        fetchall
        no rewrite
        set invisible
        set no bouncemail
        set idfile      /etc/fetchids
poll imap.isp.co.uk
        proto imap
        auth password
        username "user" password "pass" to "wassit" here
        idle

I'm wondering if there was something relevant in the lines you snipped (I
doubt it, but you never know).


PLEASE - keep list traffic on the list.  Email sent directly to me may be
ignored utterly.

-- 
Rob | What part of "no" was it you didn't understand? 

[fetchmail-users] Re: Help with warning: Illegal address syntax (berlios)

[Graham W. <bo...@de...>]

On Fri, Jul 23, 2004 at 01:13:24PM +0300, Gary Sims wrote:
> Hi,

Hello.

> Clearly the address which fetchmail is submitting to the SMTP server in the 
> MAIL FROM command is broken. Of course the question is what was the origial 
> like. The problem is that I don't know as the message has now been deleted. 

Without the original message, it will be kind of difficult to determine
where the problem is. Is the original message at fault, or is fetchmail
mangling something somehow?

> Before this I removed the antispam option from my fetchmailrc file. However 
> the email is still being deleted even though it was not delivered or 
> non-delivered. Is that behaviour correct?

I don't think so. It seems like the SMTP server gave a 501 response, in
which case I would expect fetchmail to bounce the message. Maybe it
tried?

-- 
gram

Re: [fetchmail-users] IDLE support broken?

[Andreas <an...@co...>]

On Fri, Jul 23, 2004 at 09:20:05AM +0000, Rob MacGregor wrote:
> >From: Andreas <an...@co...>
> >
> >I was wondering if someone is being able to use IDLE support. I remember
> >seeing it working once, but it isn't anymore.
> 
> Is IDLE configured in your .fetchmailrc?

Sure:
set postmaster "andreas"
set bouncemail
set properties ""
set daemon 120

poll pop.server with proto IMAP auth password
       user 'andreas' there is 'andreas' here options idle ssl fetchall warnings 3600
       mda '/usr/bin/procmail'

Or is there some syntax error?

RE: [fetchmail-users] fetchmail and assp

[Rob <rob...@ho...>]

> -----Original Message-----
> From: fet...@be... 
> [mailto:fet...@be...] On Behalf Of James Moe
>
>    Wow! This must be a baffler!

No, more a case that fetchmail isn't designed to handle such a badly behaved
SMTP listener.  Your choices are:

1) Submit a patch to fetchmail to cope with non RFC compliant SMTP listeners
2) Use something other than ASSP that's not so badly broken


PLEASE - keep list traffic on the list.  Email sent directly to me may be
ignored utterly.

-- 
Rob | What part of "no" was it you didn't understand? 

Re: [fetchmail-users] fetchmail and assp

[James M. <ji...@so...>]

James Moe wrote:
>   fetchmail release 6.2.4+SSL+NLS
> [...]
>   What is more worrisome is that just before the abort, fetchmail says 
> the message was flushed, implying a lost message.
> 
>   Is there some way to have fetchmail re-connect with assp rather than 
> abort?
> 
> fetchmail: terminated with signal 13
> 
   Wow! This must be a baffler!

-- 
jimoe at sohnen-moe dot com

[fetchmail-users] Help with warning: Illegal address syntax (berlios)

[Gary S. <ga...@ga...>]

Hi,

This is a problem which is on going on the fetchmail-friends list at ccil.org. 
I thought I would post it here as well in case people have migrated. Any help 
will would mich appreciated.

+++++++++++++

I have a dial up connection and I am using latest fetchmail (6.2.5) to get the 
mail from a POP3 mailbox and I am using postfix (V1.1.11) as the local SMTP 
server and all this is running on RedHat 9.0.

In general my email is getting through but I do get the following errors in my 
mail logs.

Jul 18 13:25:51 exodus postfix/smtpd[25020]: warning: Illegal address syntax 
from unknown[127.0.0.1] in MAIL command: 
<col...@li...: (qmail 
21055 invoked from network); 18 Jul 2004 07:09:56 -0000>

It is about a message which I am expecting... I am guessing the error is 
occuring when fetchmail talks to postfix to submit the message for local 
delivery.

Looking at the "illegal address" it is clear that the Received line is mixed 
in with the address.

I have now traced one of my problem messages with fetchmail -v -v and this is 
what I get


fetchmail: POP3> LIST 7
fetchmail: POP3< +OK 7 8568
fetchmail: POP3> TOP 7 99999999
fetchmail: POP3< +OK headers follow.
reading message gar...@ma...:7 of 8 (8568 octets)
About to rewrite Return-Path: 
<c615952fff0eb8febd27fbc7b1dd4792bdeb77a3023419e0f4063f69cReceived: (qmail 
22262 invoked from network); 23 Jul 2004 04:01:03 -0000
Rewritten version is Return-Path: 
<c615952fff0eb8febd27fbc7b1dd4792bdeb77a3023419e0f4063f69cReceived: (qmail 
22262 invoked from network); 23 Jul 2004 04:01:03 -0000

About to rewrite Reply-To: 
c61...@eb...
Rewritten version is Reply-To: 
c61...@eb...

About to rewrite From: "BBC daily email" <dai...@bb...>
Rewritten version is From: "BBC daily email" <dai...@bb...>

About to rewrite To: ga...@ga...
Rewritten version is To: ga...@ga...

fetchmail: forwarding to localhost
fetchmail: SMTP> MAIL 
FROM:<c615952fff0eb8febd27fbc7b1dd4792bdeb77a3023419e0f4063f69cReceived: 
(qmail 22262 invoked from network); 23 Jul 2004 04:01:03 
-00...@ma...> BODY=8BITMIME SIZE=8568
fetchmail: SMTP< 501 Bad address syntax
fetchmail: SMTP error: 501 Bad address syntax
fetchmail: SMTP< 220 exodus.aca-vulcan.ro ESMTP Postfix
fetchmail: SMTP> HELO localhost
fetchmail: SMTP< 250 exodus.aca-vulcan.ro
fetchmail: SMTP> MAIL FROM:<FETCHMAIL-DAEMON@exodus>
fetchmail: SMTP< 250 Ok
fetchmail: SMTP> RCPT 
TO:<c615952fff0eb8febd27fbc7b1dd4792bdeb77a3023419e0f4063f69cReceived: (qmail 
22262 invoked from network); 23 Jul 2004 04:01:03 -0000>
fetchmail: SMTP< 501 Bad address syntax
fetchmail: SMTP> QUIT
fetchmail: SMTP< 221 Bye
fetchmail: SMTP> RSET
fetchmail: SMTP< 250 Ok
...... flushed
fetchmail: POP3> DELE 7
fetchmail: POP3< +OK Deleted.


Clearly the address which fetchmail is submitting to the SMTP server in the 
MAIL FROM command is broken. Of course the question is what was the origial 
like. The problem is that I don't know as the message has now been deleted. 

Before this I removed the antispam option from my fetchmailrc file. However 
the email is still being deleted even though it was not delivered or 
non-delivered. Is that behaviour correct?

Any more clues?

Thanks,

Gary
-- 
Gary Sims (ga...@ga...)
Vulcan, Brasov, Romania

RE: [fetchmail-users] IDLE support broken?

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

>From: Andreas <an...@co...>
>
>I was wondering if someone is being able to use IDLE support. I remember
>seeing it working once, but it isn't anymore.

Is IDLE configured in your .fetchmailrc?

Certainly I've had it work, when configured, in 6.2.5.

  Please DO NOT send me ANY email directly unless it's a privacy issue.
       Reply-to mangled to assist those who don't read the above.
--
Rob  |  What part of "no" was it you didn't understand?

[fetchmail-users] IDLE support broken?

[Andreas <an...@co...>]

I was wondering if someone is being able to use IDLE support. I remember
seeing it working once, but it isn't anymore.

A trace:
fetchmail: IMAP< * OK [CAPABILITY IMAP4 IMAP4REV1 STARTTLS LOGIN-REFERRALS AUTH=PLAIN AUTH=LOGIN] pop.domain IMAP4rev1 2000.287cl at Thu, 22 Jul 2004 14:55:53 -0300 (EST)
fetchmail: IMAP> A0001 CAPABILITY
fetchmail: IMAP< * CAPABILITY IMAP4 IMAP4REV1 STARTTLS NAMESPACE IDLE MAILBOX-REFERRALS SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND LOGIN-REFERRALS AUTH=PLAIN AUTH=LOGIN
fetchmail: IMAP< A0001 OK CAPABILITY completed
fetchmail: will idle after poll
fetchmail: IMAP> A0002 LOGIN "andreas" *
fetchmail: IMAP< * CAPABILITY IMAP4 IMAP4REV1 STARTTLS NAMESPACE IDLE MAILBOX-REFERRALS SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND
fetchmail: IMAP< A0002 OK LOGIN completed
fetchmail: IMAP> A0003 SELECT "INBOX"
(...)
fetchmail: IMAP< A0011 OK Expunged 1 messages
fetchmail: IMAP> A0012 LOGOUT
fetchmail: IMAP< * BYE imap.domain IMAP4rev1 server terminating connection
fetchmail: IMAP< A0012 OK LOGOUT completed
fetchmail: 6.2.5 querying pop.domain (protocol IMAP) at Qui 22 Jul 2004 14:02:46 BRT: poll completed

It hastn't issued any IDLE command, even though it detected IDLE support...

The server is uw-imap and fetchmail is version 6.2.5. If it makes any difference, I'm running this over
imaps (the trace above is from fetchmail -N -v).

Re: [fetchmail-users] PLEASE I NEED YOUR ASSISTANCE AND HELP

[James M. <ji...@so...>]

   List members: One or more of your computers is infected with viruses or 
trojans.
   Sterilize your infested computers.

-- 
jimoe at sohnen-moe dot com

[fetchmail-users] fetchmail and assp

[James M. <ji...@so...>]

Hello,
   fetchmail release 6.2.4+SSL+NLS
   I have fetchmail forward mail to a bayseian mail classifier, assp 
(anti-spam smtp proxy). One of assp's features is to block messages with 
executable attachments. If one is found, it rejects the message and 
returns an status code of 500 to the sender (fetchmail).
   Apparently assp closes the connection after returning the error message 
since signal 13 (broken pipe) is raised in fetchmail. At which time 
fetchmail terminates. It looks like this happens on the *next* connection 
attempt with assp.
   What is more worrisome is that just before the abort, fetchmail says 
the message was flushed, implying a lost message.

   Is there some way to have fetchmail re-connect with assp rather than abort?


fetchmail: reading message moe...@lo...:2 of 2 (42695 
octets) fetchmail: SMTP error: 500 Executable attachments are not allowed 
-- Compress before mailing.
fetchmail: SMTP listener refused delivery
fetchmail:  flushed
fetchmail: 1 message for cherie at localhost (5458 octets).
fetchmail: reading message ch...@lo...:1 of 1 (5458 octets) 
fetchmail:  flushed
fetchmail: terminated with signal 13


-- 
jimoe at sohnen-moe dot com

Re: [fetchmail-users] Spam

[Rob F. <rf...@fu...>]

Laurence wrote:
> I transferred to berlios from the ccil list a couple of days ago to get
> away from the "esr virus-removed" spam and already I've had a Nigerian
> spam and one from some Chinese dude via the list.  Is there any spam
> checking on this list?  Maybe sign ups should be approved by a
> moderator?

Sorry about that.  I just changed it to members-only posting, which should 
help a lot.  Since joining the list requires confirmation, I doubt 
spammers will bother.  If they do, I'll have to consider moderating 
subscriptions.

> Maybe I should transfer back to ccil?!

Hey, maybe you can talk them into giving you admin access.  :-)

-- 
==============================|   "A microscope locked in on one point
 Rob Funk <rf...@fu...> |Never sees what kind of room that it's in"
 http://www.funknet.net/rfunk |    -- Chris Mars, "Stuck in Rewind"

Re: [fetchmail-users] Spam

[Laurence <lj...@hb...>]

I transferred to berlios from the ccil list a couple of days ago to get away
from the "esr virus-removed" spam and already I've had a Nigerian spam and
one from some Chinese dude via the list.  Is there any spam checking on this
list?  Maybe sign ups should be approved by a moderator?

Looking back through the archives on berlios:

4 messages are spam
1 message is real

Maybe I should transfer back to ccil?!

Laurence

[fetchmail-users] fetchmail doesn't delete mail on 501 response - mail piles up

[John F. <jo...@mi...>]

I use fetchmail 6.2.3 passing mail onto postfix via smtp.
Occasionally, I get a malformed email in my isp
mailbox with an envelope from address like this
peter@61.172.247.54.  That is unacceptable to
postfix which gives a 501 response straight after
MAIL FROM

This is part of the SMTP session:

 In:  MAIL FROM:<peter@61.172.247.54> SIZE=240722
 Out: 501 Bad address syntax
 In:  RSET
 Out: 250 Ok

However the mail stays on the pop server and mail just
piles up there until I enter and cancel it manually. Once
I cancel that mail, everything proceeds ok. I'm not interested
in the contents of the message (it originates from a worm)
but I don't like the need for manual intervention to get
things unblocked.

This is what fetchmail logs
Jun 21 18:18:47 turate fetchmail[1145]: 1 message for
isp...@ng... at pop.ngi.it (240722 octets).
Jun 21 18:18:47 turate fetchmail[1145]: reading message
isp...@ng...@pop.ngi.it:1 of 1 (240722 octets)
Jun 21 18:18:48 turate fetchmail[1145]:  flushed
Jun 21 18:18:48 turate fetchmail[1145]: client/server protocol error while
fetching from pop.ngi.it
Jun 21 18:18:48 turate fetchmail[1145]: Query status=4 (PROTOCOL)
Jun 21 18:18:56 turate fetchmail[1145]: sleeping at Mon Jun 21 18:18:56 2004


Here's fetchmailrc

set daemon 300
set postmaster fet...@mi...
set no bouncemail
set no spambounce
set syslog

poll "pop.ngi.it"
protocol pop3 interval 1 no envelope
username "isp...@mu..."
password "xxxxxxx"
is loc...@mi... here fetchall
smtphost mail.michaweb.net
antispam 501

Any ideas while fetchmail cannot delete the message?

Thanks,
John