fetchmail-users

[fetchmail-users] help needed - BCC problem

[Admin A. <att...@gm...>]

Hi all
i installed fetchmail few days ago and since then i have problem with BCC
field. I sent from mycompany domain mail to yahoo mail and to testdomain in
BCC field.
Fethcmail is working with regular To/Cc mails

I tried many variations and neither helped.
I hope anyone can find problem.

----------------------------------------------
here is my conf file for fetchmail

poll pop.myisp.com proto pop3
 aka MyISPname envelope 0 Received localdomains mytestdomain.com
mail.mytestdomain.com:
user mypop3user with pass mypass is * here

- i tried with envelope 0 1 2 (but thats not logical regardin in first line
i see correct e-mail from Received line.
dunno if ":" after domain name is needed, but i tried with and without.
- i tried withouth aka MyISPname and with it...

-----------------------------------------------
i have installed postfix/cyrus imapd/mysql/web cyradm - combo and all is
working ok except mentioned above.


here is log from  fetchmail -v -v

==========================================

linux-mail:# fetchmail -v -v -f .fetchmailrc
fetchmail: WARNING: Running as root is discouraged.
fetchmail: 6.3.4 querying pop.myisp.com (protocol POP3) at Wed Apr 26
13:43:18 2006:

poll started
fetchmail: POP3< +OK POP3 Server Ready <285...@my...>
fetchmail: POP3> CAPA
fetchmail: POP3< -ERR
fetchmail: Repoll immediately on beb...@po...
fetchmail: POP3< +OK POP3 Server Ready <285...@my...>
fetchmail: POP3> USER mypop3user
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< +OK
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 1 8652
fetchmail: POP3> LAST
fetchmail: POP3< -ERR
fetchmail: POP3> UIDL
fetchmail: POP3< +OK
fetchmail: POP3< 1 <0.0...@my...>
fetchmail: 1 is unseen
fetchmail: POP3< .
1 message for mypop3user at pop.myisp.com (8652 octets).
fetchmail: POP3> LIST 1
fetchmail: POP3< +OK 1 8652
fetchmail: POP3> TOP 1 99999999
fetchmail: POP3< +OK
reading message myp...@po...:1 of 1 (8652 octets)
fetchmail: analyzing Received line:
Received: for <te...@my... >
fetchmail: no Received address found       <---- !!!???? how is this
logical!?
fetchmail: analyzing Received line:
Received: from gateway.mycompany.com [XXX.XXX.XX.XX ] by MyISPname with SMTP
on Wed,

26 Apr 2006 13:44:17 +0200
fetchmail: line accepted, MyISPname is an alias of the mailserver
fetchmail: no Received address found
fetchmail: analyzing Received line:
Received: from testpc1 by mycompany.com
        (MDaemon.PRO.v8.1.5.R)
        with ESMTP id md50000169342.msg
        for <te...@my...>; Wed, 26 Apr 2006 13:49:03 +0200
fetchmail: line rejected, mycompany.com is not an alias of the mailserver
About to rewrite From: "John" <jo...@my...>
Rewritten version is From: "John" <jo...@my...>

About to rewrite To: "'John'" <joh...@ya... >
Rewritten version is To: "'John'" <joh...@ya...>

fetchmail: no local matches, forwarding to postmaster
fetchmail: SMTP< 220 mail.mytestdomain.com ESMTP Postfix (2.2.9)
fetchmail: SMTP> EHLO linux-mail
fetchmail: SMTP< 250-mail.mytestdomain.com
fetchmail: SMTP< 250-PIPELINING
fetchmail: SMTP< 250-SIZE 10240000
fetchmail: SMTP< 250-VRFY
fetchmail: SMTP< 250-ETRN
fetchmail: SMTP< 250-AUTH LOGIN PLAIN
fetchmail: SMTP< 250-AUTH=LOGIN PLAIN
fetchmail: SMTP< 250 8BITMIME
fetchmail: forwarding to localhost
fetchmail: SMTP> MAIL FROM:<jo...@my...> SIZE=8652
fetchmail: SMTP< 250 Ok
fetchmail: SMTP> RCPT TO:<postmaster@localhost >
fetchmail: SMTP< 250 Ok
fetchmail: SMTP> DATA
fetchmail: SMTP< 354 End data with <CR><LF>.<CR><LF>
#*******************************************************.***************************


****************.****************************.****************************.*********

*********************.**************.*************.**********fetchmail:
message

myp...@po...:1 was not the expected length (8687 actual != 8652

expected)
fetchmail: SMTP>. (EOM)
fetchmail: SMTP< 250 Ok: queued as 7048A6F4E3
 flushed
fetchmail: POP3> DELE 1
fetchmail: POP3< +OK
fetchmail: POP3> QUIT
fetchmail: POP3< +OK
fetchmail: SMTP> QUIT
fetchmail: SMTP< 221 Bye
fetchmail: 6.3.4 querying pop.myisp.com (protocol POP3) at Wed Apr 26
13:43:19 2006:

poll completed
fetchmail: swapping UID lists
fetchmail: Deleting fetchids file.
fetchmail: normal termination, status 0
fetchmail: Deleting fetchids file.



Best Regards and tnx in advance

Re: [fetchmail-users] help needed - BCC problem

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

On 5/3/06, Admin Att <att...@gm...> wrote:
> poll pop.myisp.com proto pop3
>  aka MyISPname envelope 0 Received localdomains mytestdomain.com
> mail.mytestdomain.com:
> user mypop3user with pass mypass is * here
>
> - i tried with envelope 0 1 2 (but thats not logical regardin in first line

Do you have details in anything other than the Received headers?  If
not then you're in a hiding to nothing.  Please see the man page for
warnings for the problems of abusing this header for envelope
information.

--
                 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] help needed - BCC problem

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

"Admin Att" <att...@gm...> writes:

> Hi all
> i installed fetchmail few days ago and since then i have problem with BCC
> field.

See http://home.pages.de/~mandree/mail/multidrop to see which multidrop
scenarios work reliably and which don't.

Many MTAS omit the recipient from Received: headers when there is more
than one as is the case in Bcc setups, although that does not appear to
be the problem here (but it might if you wrote to two different Bcc:
recipients of your own domain)

> reading message myp...@po...:1 of 1 (8652 octets)
> fetchmail: analyzing Received line:
> Received: for < te...@my... >
> fetchmail: no Received address found       <---- !!!???? how is this logical!?

fetchmail expects a "by some.host.name for <so...@ex...>" format,
and also performs some checking on some.host.name - if that doesn't fit,
it doesn't accept the address.

> Received: from testpc1 by mycompany.com
>         (MDaemon.PRO.v8.1.5.R)
>         with ESMTP id md50000169342.msg
>         for <te...@my...>; Wed, 26 Apr 2006 13:49:03 +0200
> fetchmail: line rejected, mycompany.com is not an alias of the mailserver

So it likes this header better because it has the "by mycompany.com"
before "for <te...@my...>" - but doesn't accept the "by"
part.  You might trick fetchmail into believing that by adding

aka mycompany.com

to your configuration (before the "user" keyword). I don't know if that
works though -- no guarantees.

I suggest:

1. check if there is a better header. If not, try to arrange for one,
   such as X-Original-To, Envelope-To, Delivered-To. See the URL above,
   and feel free to quote the URL to your ISP. If you have got a better
   header, adjust the Envelope option accordingly.

2. do not run fetchmail as root - that's a basic safety measure to limit
   impact should a bug I have overseen be discovered. Since you are
   forwarding via SMTP, fetchmail does not need root privileges.

   Create a "fetchmail" user, copy /etc/fetchmailrc
   to ~fetchmail/.fetchmailrc and use this command to start fetchmail
   under the fetchmail user account:

   su fetchmail -c "fetchmail"

-- 
Matthias Andree