Jerry | 11 Jun 21:24 2010
Face
Picon

Using "CAPA" with Hotmail

fetchmail release 6.3.17+RPA+SDPS+SSL+OPIE+NLS
FreeBSD-8.1-PRERELEASE/amd64

I have two accounts with Hotmail. Both accounts produce what appears to
be an error message during mail retrival:

fetchmail: POP3> CAPA
fetchmail: POP3< -ERR unrecognized command

The entire log for both accounts is shown below.

fetchmail: 6.3.17 querying pop3.live.com (protocol POP3) at Fri Jun 11 15:12:00 2010: poll started
fetchmail: Trying to connect to 65.55.172.253/995...connected.
fetchmail: Server certificate:
fetchmail: Unknown Organization
fetchmail: Issuer CommonName: Microsoft Secure Server Authority
fetchmail: Subject CommonName: pop3.live.com
fetchmail: pop3.live.com key fingerprint: B1:2B:88:14:85:7C:BF:C3:90:EB:F8:88:3E:A3:A5:39
fetchmail: pop3.live.com fingerprints match.
fetchmail: POP3< +OK BLU0-POP397 POP3 server ready
fetchmail: POP3> CAPA
fetchmail: POP3< -ERR unrecognized command
fetchmail: unrecognized command
fetchmail: Repoll immediately on USER <at> hotmail.com <at> pop3.hot.glbdns.microsoft.com
fetchmail: Trying to connect to 65.55.172.253/995...connected.
fetchmail: Server certificate:
fetchmail: Unknown Organization
fetchmail: Issuer CommonName: Microsoft Secure Server Authority
fetchmail: Subject CommonName: pop3.live.com
fetchmail: pop3.live.com key fingerprint: B1:2B:88:14:85:7C:BF:C3:90:EB:F8:88:3E:A3:A5:39
(Continue reading)

James Moe | 11 Jun 23:33 2010

Re: Using "CAPA" with Hotmail


On 06/11/2010 12:24 PM, Jerry wrote:
> fetchmail release 6.3.17+RPA+SDPS+SSL+OPIE+NLS
> FreeBSD-8.1-PRERELEASE/amd64
> 
> I have two accounts with Hotmail. Both accounts produce what appears to
> be an error message during mail retrival:
> 
> fetchmail: POP3> CAPA
> fetchmail: POP3< -ERR unrecognized command
> 
  This only indicates that the server does not support the CAPA command,
like it says. It is a "known good error." The log shows that fetchmail
ignores the error message since it is an optional feature (defaults are
assumed) and continues with the session.

--

-- 
James Moe
jimoe at sohnen-moe dot com
520.743.3936
Sunil Shetye | 12 Jun 10:55 2010

Re: Using "CAPA" with Hotmail

Hi Jerry,

Quoting from Jerry's mail on Fri, Jun 11, 2010:
> I have two accounts with Hotmail. Both accounts produce what appears to
> be an error message during mail retrival:
> 
> fetchmail: POP3> CAPA
> fetchmail: POP3< -ERR unrecognized command

It looks like capability probing is not supported. Please add 'auth
password' to your fetchmailrc to avoid this error message. Something
like this:

poll pop3.live.com
    protocol pop3
    auth password
    ...

--

-- 
Sunil Shetye.
Erick van Rijk | 14 Jun 15:24 2010

multi-drop problem on osx, duplicate emails received.

Hi All,
new to fetchmail and this list of course.
I've setup fetchmail to gather emails from a multi-drop email box on an external server.
But I have been having some issues:
1. duplicate emails are coming in when I have multiple recipients in the same multi-drop (tricky I know).
2. BCC seems to be going to postmaster always.

Both seem to be covered by the FAQ, but still i cannot seem to figure out what I am doing wrong (i think its more a
config error than a bug anyway).
Nevertheless I would really like to get this working properly and not being driven bonkers by multiple
emails of the same subject every time ;)

Regariding issue 1. I noticed the following.
When I get the email messages of say 2 email addresses in the same multidrop.
there are two separate identical emails in the mailbox in this case.
Fetchmail fetches and deletes the first email and doesn't touch the second one.
Even when I set fetchall it just reads it and leaves it alone until the second time it fetches email and
processes it as new email.
So it its read but not flushed. Any idea what can cause this?
I included the log what I get when running fetchmail via fetchmailconf.
Also the system output of fetchmail --version.

Hope that anyone can show me what i'm doing wrong since its just puzzeling me at the moment
thanks
Erick

fetchmail: WARNING: Running as root is discouraged.
fetchmail: 6.3.11 querying mail.myserver.com (protocol POP3) at Mon, 14 Jun 2010 15:18:11 +0200 (CEST):
poll started
Trying to connect to 217.115.197.2/110...connected.
(Continue reading)

Rob MacGregor | 14 Jun 18:51 2010
Picon

Re: multi-drop problem on osx, duplicate emails received.

On Mon, Jun 14, 2010 at 14:24, Erick van Rijk <erick <at> bergehenegouwen.com> wrote:
> Hi All,
> new to fetchmail and this list of course.
> I've setup fetchmail to gather emails from a multi-drop email box on an external server.
> But I have been having some issues:
> 1. duplicate emails are coming in when I have multiple recipients in the same multi-drop (tricky I know).
> 2. BCC seems to be going to postmaster always.

Both of those suggest either that your provider isn't providing an
X-Envelope-To header, or you're not using the one that's there.

> fetchmail: WARNING: Running as root is discouraged.
> fetchmail: 6.3.11 querying mail.myserver.com (protocol POP3) at Mon, 14 Jun 2010 15:18:11 +0200
(CEST): poll started

Please update to the current release

A copy of the config file would have been a lot easier to parse  ;)
From what I can tell it looks like you haven't configured an
Envelope-To header - see the man page under "THE USE AND ABUSE OF
MULTIDROP MAILBOXES".  If you believe you have then please provide the
actual .fetchmailrc file and the full headers of any sample email.

--

-- 
                 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
(Continue reading)

Erick van Rijk | 15 Jun 00:12 2010

Re: multi-drop problem on osx, duplicate emails received.

Hi Rob,

On Jun 14, 2010, at 6:51 PM, Rob MacGregor wrote:

> On Mon, Jun 14, 2010 at 14:24, Erick van Rijk <erick <at> bergehenegouwen.com> wrote:
>> Hi All,
>> new to fetchmail and this list of course.
>> I've setup fetchmail to gather emails from a multi-drop email box on an external server.
>> But I have been having some issues:
>> 1. duplicate emails are coming in when I have multiple recipients in the same multi-drop (tricky I know).
>> 2. BCC seems to be going to postmaster always.
> 
> Both of those suggest either that your provider isn't providing an
> X-Envelope-To header, or you're not using the one that's there.
Attached raw header info below. Indeed there is no X-Envelope-To header
> 
>> fetchmail: WARNING: Running as root is discouraged.
>> fetchmail: 6.3.11 querying mail.myserver.com (protocol POP3) at Mon, 14 Jun 2010 15:18:11 +0200
(CEST): poll started
> 
> Please update to the current release
> 
> A copy of the config file would have been a lot easier to parse  ;)
> From what I can tell it looks like you haven't configured an
> Envelope-To header - see the man page under "THE USE AND ABUSE OF
> MULTIDROP MAILBOXES".  If you believe you have then please provide the
> actual .fetchmailrc file and the full headers of any sample email.

So I'm sort of wondering if I the upstream server is actually usable for multi-drop?

(Continue reading)

Rob MacGregor | 15 Jun 07:52 2010
Picon

Re: multi-drop problem on osx, duplicate emails received.

On Mon, Jun 14, 2010 at 23:12, Erick van Rijk <erick <at> bergehenegouwen.com> wrote:
>
> So I'm sort of wondering if I the upstream server is actually usable for multi-drop?

If it doesn't have some form of Delivered-To header then it isn't.

> set postmaster "admin"
> set bouncemail
> set no spambounce
> set softbounce
> set properties ""
> set daemon 60
> poll mail. myserver.com with proto POP3 envelope Received: and options no dns uidl

Note that parsing the Received header will be dropped in a future
release because it isn't reliable.

>    localdomains myserver.com
>       user 'catch_all <at>  myserver.com' there with password 'xxxxx' is 'admin' 'test' 'one' 'two' here
options flush fetchall

> Delivered-To: admin <at> myserver.com
<---SNIP--->
> X-Original-To: catch_all <at>  myserver.com
> Delivered-To: catch_all <at>  myserver.com

Hmmm, well those last 2 lines are no help (and reminds me of One and
One), but if your system didn't insert the first header there then
you've got a chance to get this working.

(Continue reading)

Erick van Rijk | 15 Jun 09:04 2010

Re: multi-drop problem on osx, duplicate emails received.


On Jun 15, 2010, at 7:52 AM, Rob MacGregor wrote:

> On Mon, Jun 14, 2010 at 23:12, Erick van Rijk <erick <at> bergehenegouwen.com> wrote:
>> 
>> So I'm sort of wondering if I the upstream server is actually usable for multi-drop?
> 
> If it doesn't have some form of Delivered-To header then it isn't.
Unfortunately chances are high that it doesn't at the moment, I need to call the datacenter for this.
> 
>> set postmaster "admin"
>> set bouncemail
>> set no spambounce
>> set softbounce
>> set properties ""
>> set daemon 60
>> poll mail. myserver.com with proto POP3 envelope Received: and options no dns uidl
> 
> Note that parsing the Received header will be dropped in a future
> release because it isn't reliable.
So i've noticed ;)

> 
>>    localdomains myserver.com
>>       user 'catch_all <at>  myserver.com' there with password 'xxxxx' is 'admin' 'test' 'one' 'two' here options
flush fetchall
> 
> 
>> Delivered-To: admin <at> myserver.com
> <---SNIP--->
(Continue reading)

Matthias Andree | 15 Jun 11:10 2010
Picon
Picon

Re: multi-drop problem on osx, duplicate emails received.

> X-Original-To: catch_all <at>  myserver.com
> Delivered-To: catch_all <at>  myserver.com

How does the MX manage to get *this* in the headers? This looks like a  
massive misconfiguration upstream. They are *rewriting* X-Original-To:,  
which (with Postfix at least) is usually one of the /safest/ ways to  
convey the /original/ header, as the name purports.

Contact them and have them cease rewriting the local part to catch_all <at> .   
They may possibly be reinjecting messages somehow/somewhere.

Haven't checked your headers deeper than this though.

--

-- 
Matthias Andree
Lorenzo Milesi | 25 Jun 00:06 2010
Picon

poblems with pop3 and expunge

Hi.

I configured a system fetchmail to use expunge, in order to be sure I could delete mails.
Sadly, this doesn't seem to work...
My /etc/fetchmailrc looks as follows:

set daemon 300
set syslog
defaults proto pop3 timeout 18000 uidl expunge 500
poll my.mail.server proto pop3 
    user "my_account" password "my_pass" is "user"  keep expunge 50

but I see no command after the 50th deleted mail. It goes straight to the end, when the pop3 server takes ages
to respond to QUIT (I have a lot of messages on this mbox), so wasting time.
I tried several times but no way.

What's wrong?

I'm issuing the folowing:
su - fetchmail -c "/usr/bin/fetchmail -F -d0 -f /etc/fetchmailrc -i
/var/lib/fetchmail/.fetchmail-UIDL-cache "

using fm 6.3.6-1etch2 on debian etch.

thanks
--

-- 
Lorenzo Milesi - lorenzo.milesi <at> yetopen.it

YetOpen S.r.l. - http://www.yetopen.it/
Via Torri Tarelli 19 - 23900 Lecco - ITALY -
(Continue reading)


Gmane