fetchmail-users

[fetchmail-users] fetchmail multidrop problem

[jay s. <jay...@ya...>]

Hi Group,

I have two qmailtoaster server install on Fedora Core 2
old qmailtoaster version is 1.0.6
new qmailtoaster version is 1.2.9
I am trying to fetch mail on local server of Fedora core 2 fetchmail fetchmail-6.2.5-2
I also tested the same things with Centos 4.4 along with fetchmail fetchmail-6.2.5-6.el4.5

Old qmailtoaster working fine with fetchmail multidrop
But new qmailtoaster giving some problem when using
fetchmail multidrop option.
Both server giving different header. Header is pasted below.

I have ex...@ab... id in which fo...@ab... and
ba...@ab... are two alias id configure.
When i send mail from Out side to this to both user.
now when i see the header of foo's mail header it
shows Delivered-To: ex...@ab... alog with
respecting id.
that is Delivered-To: fo...@ab....
how can i remove Delivered-To: ex...@ab... line
from header while downloading

Because of this foo and bar getting multliple mails in new server.

I am using following fetchmailrc file
set postmaster "pos...@ab..."
set bouncemail
set no spambounce

poll xx.xx.xx.xx with proto pop3 timeout 60  and options no dns uidl
envelope Delivered-To:

localdomains abc.com
user 'ex...@ab...' there with password 'secret' is * here options forcecr dropdelivered

To run Fetchmail i am using the following /sbin/getmail :--
fetchmail -v -v --showdots -e 1 -Q abc.com- -f /root/.fetchmailrc >> /var/log/fetchmail.log &

I have tryed envelop header option for new server but that not working with with new servermail header
My question is what should i put to get the mail for mutidrop box for new server so that mails will not get repeat.

##########################################
New server header.
#####################################

Return-Path: <mah...@ga...>
Delivered-To: ex...@ab...
Received: (qmail 19564 invoked by uid 89); 14 Mar 2007
07:47:30 -0000
Delivered-To: fo...@ab...
Received: (qmail 19554 invoked by uid 89); 14 Mar 2007
07:47:30 -0000
DomainKey-Status: good
Received: by simscan 1.2.0 ppid: 19530, pid: 19534, t:
2.8761s
     scanners: attach: 1.2.0 clamav:
0.88.4/m:40/d:2123 spam: 3.1.7
X-Spam-Checker-Version: SpamAssassin 3.1.7
(2006-10-05) on
     mail.abc.com
X-Spam-Level:
X-Spam-Status: No, score=-0.0 required=4.0
tests=BAYES_00,HTML_30_40,
     HTML_MESSAGE,HTML_SHORT_LENGTH,SARE_MSGID_LONG40
autolearn=no
     version=3.1.7
Received: from unknown (HELO an-out-0708.google.com)
(209.85.132.243)
     by mail.abc.com with SMTP; 14 Mar 2007 07:47:27
-0000
Received-SPF: pass (mail.abc.com: SPF record at
_spf.google.com designates 209.85.132.243 as permitted
sender)
Received: by an-out-0708.google.com with SMTP id
b6so96165ana
     for <fo...@ab...>; Wed, 14 Mar 2007 00:46:54
-0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed;
     d=gmail.com; s=beta;

h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type;

b=VM6B3EUF55YGc0hD8rttVCj3xwwAjKNYY4P2F1spZ8an+GuLd0sdXTV1dfeKTFg5IlY/7ywbJOM+BIeGi45InHevbTqPQ5mryRyY6076CgAI1BpWPe3tG22DIZU0MnNDHHgoFlFiRNK4b+JbFl2ln/4sm+/qqe/AhGhBwFs1fk0=
DomainKey-Signature: a=rsa-sha1; c=nofws;
     d=gmail.com; s=beta;

h=received:message-id:date:from:to:subject:mime-version:content-type;

b=XnRk+FjLVJcKMXEQoM/ZgraRQ4UykVgV2B/Nt9fHlC0J11EzJNkPXGw0cuHYqX6zF6R27GVgHscUW0JMEleAWoXaXhyabhhv0TkTcaqDLmp5DPRz6TfVxo6TBpnKc9DxMYK4QCCB39HBQQh9Y7cM8OfZBsM7v8a/EHEYg6H3rzg=
Received: by 10.100.44.13 with SMTP id
r13mr1486586anr.1173858414344;
     Wed, 14 Mar 2007 00:46:54 -0700 (PDT)
Received: by 10.100.7.2 with HTTP; Wed, 14 Mar 2007
00:46:54 -0700 (PDT)
Message-ID:
<1f2...@ma...>
Date: Wed, 14 Mar 2007 13:16:54 +0530
From: "Mahesh Wadekar" <mah...@ga...>
To: fo...@ab..., ba...@ab...
Subject: test 9
MIME-Version: 1.0
Content-Type: multipart/alternative;
     boundary="----=_Part_33866_9804086.1173858414323"


############################################
Old Server mail header.
##########################################

Return-Path: <mah...@gm...>
Delivered-To: ipc...@xy...
Received: (qmail 4189 invoked by uid 501); 14 Mar 2007
08:01:48 -0000
Received: from mah...@gm... by
ns2.brisk-india.com by uid 107 with qmail-scanner-1.22

 (clamdscan: 0.65. f-prot: 4.4.7/3.14.13.
Clear:RC:1(192.168.1.1):.
 Processed in 0.430508 secs); 14 Mar 2007 08:01:48
-0000
X-Qmail-Scanner-Mail-From: mah...@gm... via
Processed in 0.430508 secs)
Received: from unknown (HELO ns1.pqr.com)
(192.168.1.1)
  by 192.168.1.3 with AES256-SHA encrypted SMTP; 14
Mar 2007 08:01:47 -0000
Received: from an-out-0708.google.com
(an-out-0708.google.com [209.85.132.241])
        by ns1.pqr.com (8.13.1/8.13.1) with ESMTP id
l2E7jW0o031240
        for <fo...@xy...>; Wed, 14 Mar 2007 13:15:33 +0530
Received: by an-out-0708.google.com with SMTP id
d30so92962and
        for <fo...@xy...>; Wed, 14 Mar 2007 00:48:50
-0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed;
        d=gmail.com; s=beta;

h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type;

b=SlL0Py3R6fFqcj+9zRm/6B3pXBE/rhgcavULMV2QBkptzuKqamb1qNmG09Snm/xBp26wUEJRiagXg7NztSkum5MQa//fM7iMnetqJH6OsZYuPxkfFSTjTl257M8Wp/3cjsAyM5AYTePz89LHupwXWrjgBhomQYoZKi5d5sxIhIk=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
h=received:message-id:date:from:to:subject:mime-version:content-type;

b=hcvoH6oC2EIE50iMGd1PptQGXiTPC7LnpQFozW175p7rGf8H9V78IvHeavunRM0LuJCdCBKtyxznxAsOIXmMWa7JDVFnb46Rgz1QZO786xFaKDYdBb7+PAvMc/VBJ5Ue3mvfIfAA5AN1kq4+kwvQ3rzP0svkt/6LB4QNaDG7+KI=
Received: by 10.100.144.11 with SMTP id
r11mr1572276and.1173858530649;
        Wed, 14 Mar 2007 00:48:50 -0700 (PDT)
Received: by 10.100.7.2 with HTTP; Wed, 14 Mar 2007
00:48:50 -0700 (PDT)
Message-ID:
<1f2...@ma...>
Date: Wed, 14 Mar 2007 13:18:50 +0530
From: "Mahesh Wadekar" <mah...@gm...>
To: fo...@xy..., ba...@xy...
Subject: test 10
MIME-Version: 1.0
Content-Type: multipart/alternative;
        boundary="----=_Part_33874_31836033.1173858530628"
X-yoursite-MailScanner-Information: Please contact the
ISP for more information
X-yoursite-MailScanner: Found to be clean
X-yoursite-MailScanner-SpamCheck: not spam,
SpamAssassin (score=-0.013,
required 4, BAYES_00 -2.60, HTML_30_40 0.37,
HTML_MESSAGE 0.00,
        HTML_SHORT_LENGTH 1.57, SARE_MSGID_LONG40 0.64)
X-MailScanner-From: mah...@gm...


------=_Part_33874_31836033.1173858530628
Content-Type: text/plain; charset=ISO-8859-1;
format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

test 10

------=_Part_33874_31836033.1173858530628
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

test 10<br>

------=_Part_33874_31836033.1173858530628--


Plz help me
Thanks & Regard's
Jayesh


 
---------------------------------
Food fight? Enjoy some healthy debate
in the Yahoo! Answers Food & Drink Q&A.

Re: [fetchmail-users] fetchmail multidrop problem

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

On 3/14/07, jay shi <jay...@ya...> wrote:

> I am trying to fetch mail on local server of Fedora core 2 fetchmail
> fetchmail-6.2.5-2
> I also tested the same things with Centos 4.4 along with fetchmail
> fetchmail-6.2.5-6.el4.5

Standard advice - upgrade to the latest version (6.3.7 ISTR).

> When i send mail from Out side to this to both user.
> now when i see the header of foo's mail header it
> shows Delivered-To: ex...@ab... alog with
> respecting id.
> that is Delivered-To: fo...@ab....
> how can i remove Delivered-To: ex...@ab... line
> from header while downloading

Fetchmail doesn't do that - however as documented in the manual you
can provide a count of the number of lines to ignore.  In your case
you'd use "Envelope Delivered-To 1"

-- 
                 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 multidrop problem

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

Keep the traffic on the list.  If you don't then I'll simply ignore
any email from you...

On 3/15/07, jay shi <jay...@ya...> wrote:
> Hi Rob
>             Thanks For ur quick response
>             Now i ugrade the fetchmail to fetchmail 6.3.7 but still i am
> strugling
>
>             I used the option "envelope Delivered-To 1" in .fetchmailrc file
>
>             But while running the getmail it giving me the sysntax error

And what error would that be?  My crystal ball is broken today.

>             In man fetchmail  i got the following option
>
> -E <line> | --envelope <line>
>               (Keyword: envelope; Multidrop only)
>               In the configuration file, an enhanced syntax is used:
>               envelope [<count>] <line>
>
>             what could be the  correct option ? for skipping lines

Ah, maybe it's "envelope 1 Delivered-To".  I've never come across a
mail system that's broken enough to insert multiple delivered to
headers before :)

-- 
                 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 multidrop problem

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

Rob MacGregor schrieb:
> Ah, maybe it's "envelope 1 Delivered-To".  I've never come across a
> mail system that's broken enough to insert multiple delivered to
> headers before :)

You mean internal forwarding chains that use useless rewritten
addresses? IOW, those need not necessarily broken.

But I agree, inaccurate messages won't help debugging in any way.

MA

Re: [fetchmail-users] fetchmail multidrop problem

[jay s. <jay...@ya...>]

Hi Rob & friends,
               Sorry for my long mail, i just put for understanding purpose only.Plz don't ignore my mail, i am in trouble .
               well i use ur specified option "envelope 1 Delivered-To"  but still getting no  effect. The user foo & bar getting double mails.
              what should i do next ?

Thanks & Regards
Jayesh
               

Rob MacGregor <rob...@gm...> wrote: Keep the traffic on the list.  If you don't then I'll simply ignore
any email from you...

On 3/15/07, jay shi  wrote:
> Hi Rob
>             Thanks For ur quick response
>             Now i ugrade the fetchmail to fetchmail 6.3.7 but still i am
> strugling
>
>             I used the option "envelope Delivered-To 1" in .fetchmailrc file
>
>             But while running the getmail it giving me the sysntax error

And what error would that be?  My crystal ball is broken today.

>             In man fetchmail  i got the following option
>
> -E 
 | --envelope 

>               (Keyword: envelope; Multidrop only)
>               In the configuration file, an enhanced syntax is used:
>               envelope [] 

>
>             what could be the  correct option ? for skipping lines

Ah, maybe it's "envelope 1 Delivered-To".  I've never come across a
mail system that's broken enough to insert multiple delivered to
headers before :)

-- 
                 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 mailing list
fet...@li...
https://lists.berlios.de/mailman/listinfo/fetchmail-users


 
---------------------------------
Expecting? Get great news right away with email Auto-Check.
Try the Yahoo! Mail Beta.

Re: [fetchmail-users] fetchmail multidrop problem

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

On 3/16/07, jay shi <jay...@ya...> wrote:
> Hi Rob & friends,
>                Sorry for my long mail, i just put for understanding purpose only.Plz don't ignore my mail, i am in trouble .
>                well i use ur specified option "envelope 1 Delivered-To"  but still getting no  effect. The user foo & bar getting double mails.
>               what should i do next ?

Right, please go back and read the FAQ.  It tells you what you're
supposed to be providing.

1) Version of fetchmail.  Until that's (at least) 6.3.7 don't bother
going any further.

2) Contents of .fetchmailrc

3) Command line arguments

4) Output of "--nosyslog --nodetach -vvv" (yes, that's three -v
options, enabling debug mode) for a problem email

5) Matching entries from the log of your SMTP server (and what it is)

See also the FAQ:

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

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