fetchmail-users — User questions and discussion

Re: [fetchmail-users] Simple fetch and forward

[John <fet...@je...>]

>If your inbound server writes X-Original-To: headers, why is a script
needed?

>--
>Matthias Andree

Hi Matthias,

X-Original-To isn't always there. If I get a mail directed at a mailing list
or sent as a bcc then it isn't always obvious what the sender was.

I'm using fetchmail to receive the mail and drop it to a user on my server.
When
my Postfix gets that mail it can add an X-Original-To but this will be the
name of
the account specified in the "here" clause in fetchmail conf. This is not of
much
use so I don't do that. I did do this originally but soon realised there was
little point.

When the message hits procmail, I run a little script and this extracts a
likely
original destination address, irrespective if it was sent Bcc or via a list,
by
extracting the "Received:" header containing a "for" nearest the mail's
origin.
Procmail then delivers the mail into a user folder based on the address that
was
extracted: if the mail was destined for "ad...@do..." it hits a
folder called
domain.com/address. This is great as it sorts all my incoming mail from
various
services I subscribe to (I subscribe with a unique address to each one so I
can
track where my address is leaked from as I get spam).

I was originally trying to use Fetchmail's multidrop mode to do what I
wanted but
I didn't fully understand the anatomy of an email so I read the RFC and
re-thought
what I was doing. I don't know if I am doing this the best way, but what
I've got
works for me - it's just a prototype but it seems to be ok.

Thanks for your interest,
John

Re: [fetchmail-users] Multidrop fetchmail bouncing non-existing local addresses

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

On 7/28/06, Andy Hawkins <adh...@gm...> wrote:
>
> And in fairness, I did leave over a week between my original request
> and the reminder...

You've probably missed the fact that these days Matthias pretty much
is the entire fetchmail development team (or at least all of it you'll
see on the lists, I think some of the others are still around, if not
terribly active).  This means that there isn't a lot of developer time
available, hence why you rarely see him on the lists.

You're welcome to try the original maintainer, ESR, but some of us
have been trying to get a response from him for literally years now :)

-- 
                 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] Simple fetch and forward

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

"John" <fet...@je...> writes:

> I now let a user's mail hit Postfix as that user and I have written a small
> script that scans the mail and makes a "best guess" at the intended
> recipient by parsing the "Received", "Envelope-to" and "X-Original-To"
> fields.

If your inbound server writes X-Original-To: headers, why is a script needed?

-- 
Matthias Andree

Re: [fetchmail-users] Multidrop fetchmail bouncing non-existing local addresses

[Andy H. <adh...@gm...>]

Hi,

On 7/27/06, Matthias Andree <mat...@gm...> wrote:
> Hang on, you haven't paid 24x7 2-hour response support level.
> I've seen your questions, but not yet found the necessary time for research.

Apologies, I just wanted to make sure someone else had seen it. I
realise that support here is worth every penny I pay for it :)

And in fairness, I did leave over a week between my original request
and the reminder...

> you'll *have* to wait until it's your turn.

Understood.

Andy

Re: [fetchmail-users] Simple fetch and forward

[John <fet...@je...>]

Rob thanks for your suggestions.

I decided to step back from the problem. I've taken a day or so to read the
RFC material describing message formats and I have studied several incoming
messages. I now realise I can not expect the header information to contain
what I thought and have approached the problem from another angle.

I now let a user's mail hit Postfix as that user and I have written a small
script that scans the mail and makes a "best guess" at the intended
recipient by parsing the "Received", "Envelope-to" and "X-Original-To"
fields. I then deliver mail into a user folder from within Procmail by
altering the argumets to the deliver script, delivering into Cyrus imap.

Thanks for taking the time to respond to my query.

-----Original Message-----
From: fet...@li...
[mailto:fet...@li...]On Behalf Of Rob
MacGregor
Sent: 24 July 2006 21:21
To: fet...@li...
Subject: Re: [fetchmail-users] Simple fetch and forward

Re: [fetchmail-users] Multidrop fetchmail bouncing non-existing local addresses

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

"Andy Hawkins" <adh...@gm...> writes:

>> Ok. I've found a workaround by changing the postmaster setting to an
>> empty string. However, I suspect that's not a particularly good
>> idea...
>
> Anyone? ???

Hang on, you haven't paid 24x7 2-hour response support level.
I've seen your questions, but not yet found the necessary time for research.

Send 30 Euro via PayPal and I'll look at your issue ASAP as long
as it doesn't take longer than 20 minutes (and send what I figured in
that period), else you'll *have* to wait until it's your turn.

-- 
Matthias Andree

Re: [fetchmail-users] [fetchmail]Multidrop fetchmail bouncing non-existing local addresses

[Andy H. <adh...@gm...>]

Hi,

On 7/19/06, Andy Hawkins <adh...@gm...> wrote:
> Hi,
>
> On 7/18/06, Rob MacGregor <rob...@gm...> wrote:
> > Give it another couple of days.  I'm reasonably sure somebody with
> > knowledge of the source will be by before the weekend.  The
> > development team is pretty small (not sure of the exact number, but I
> > suspect only 2 or 3).
>
> Ok. I've found a workaround by changing the postmaster setting to an
> empty string. However, I suspect that's not a particularly good
> idea...

Anyone? ???

Andy

Re: [fetchmail-users] Server CommonName mismatch

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

On 7/25/06, N.J. Mann <nj...@nj...> wrote:
> Hi,
>
> I have been using fetchmail for about three weeks now and I am very
> happy with it.  But... (You knew a "but" was going to be next. ;-) )
>
> Every time I poll my ISP I get the following errors:
>
> fetchmail: Server CommonName mismatch: localhost.localdomain != inmail.njm.f2s.com
> fetchmail: Server certificate verification error: self signed certificate

There was a recent thread on this.  The summary (assuming you don't
want to read the thread) was to either use an ISP with a clue, or do
what Volker advised and use the fingerprints.

-- 
                 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] Server CommonName mismatch

[Volker K. <hi...@pa...>]

> fetchmail: Server CommonName mismatch: localhost.localdomain != inmail.njm.f2s.com
> fetchmail: Server certificate verification error: self signed certificate

> So it looks like fetchmail is complaining about my ISPs setup.  Is that
> right?

Yes. Your ISP is using a self-baked certificate; it's cheap (i.e. free).
On the negative, your fetchmail (and browser, etc) have no idea whether
your ISP is trustworthy, or is in fact the person/entity it claims to
be. To teach fetchmail about both, you need to load your ISP's CA
(certificate authority) into your openssh setup. By doing so, you
personally assume liability for aforementioned claims to be true.

The use of certificates here is to increase security. Security here
means:

1) Each time you run fetchmail, the connection which is opened is
guaranteed to be to <someone> at the other end. You expect that someone
to be your ISP.

2) The connection is encrypted, and protected from eavesdropping by
anyone other than a) yourself, b) that "someone".

The trick is to make sure that the "someone" is in fact your ISP. With
self-signed certificates, the only guaranteed way to do so is to jump
into your car and to pick up the CA from your ISP in person.

The shortcut is to read out your ISP's certificate fingerprint, and to
load this into fetchmail 6.3.4 or above. This solves your problem, but
you then have two possibilities when you've loaded the fingerprint:

1) You loaded the fingerprint of your ISP's CA into fetchmail. You have
security as good as it'll possibly get. Self-signed cert or otherwise.

2) You loaded the fingerprint of an imposter, assuming the imposter to
be your ISP. Both you and the imposter will read your email.

Your alternative is quite likely using plain text passwords. Even
possibility 2) is an improvement to that, because reading your email is
restricted from everyone, to you and the imposter.

Volker

-- 
Volker Kuhlmann			is list0570 with the domain in header
http://volker.dnsalias.net/	Please do not CC list postings to me.

[fetchmail-users] Server CommonName mismatch

[N.J. M. <nj...@nj...>]

Hi,

I have been using fetchmail for about three weeks now and I am very
happy with it.  But... (You knew a "but" was going to be next. ;-) )

Every time I poll my ISP I get the following errors:

fetchmail: Server CommonName mismatch: localhost.localdomain != inmail.njm.f2s.com
fetchmail: Server certificate verification error: self signed certificate

At first I throught the first one was due to something I was doing
wrong, but I now suspect it is nothing to do with me.  Can someone
confirm that please?  My change of mind stems from running
fetchmail -v -v -v and redirecting the output to a log file.  (The idea
for that came from a message I read earlier today on this list, so
lurking here for a while does pay. :-) )

In the log I get:

fetchmail: Old UID list from inmail.njm.f2s.com: <empty>
fetchmail: Scratch list of UIDs: <empty>
fetchmail: 6.3.4 querying inmail.njm.f2s.com (protocol POP3) at Tue Jul 25 10:43:33 2006: poll started
fetchmail: POP3< +OK imap3.freedom2surf.net Cyrus POP3 v2.2.12-Invoca-RPM-2.2.12-7 server ready <122...@im...>
fetchmail: POP3> CAPA
fetchmail: POP3< +OK List of capabilities follows
fetchmail: POP3< SASL DIGEST-MD5 CRAM-MD5
fetchmail: POP3< STLS
fetchmail: POP3< EXPIRE NEVER
fetchmail: POP3< LOGIN-DELAY 0
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< PIPELINING
fetchmail: POP3< RESP-CODES
fetchmail: POP3< AUTH-RESP-CODE
fetchmail: POP3< USER
fetchmail: POP3< IMPLEMENTATION Cyrus POP3 server v2.2.12-Invoca-RPM-2.2.12-7
fetchmail: POP3< .
fetchmail: POP3> STLS
fetchmail: POP3< +OK Begin TLS negotiation now
fetchmail: Issuer Organization: SomeOrganization
fetchmail: Issuer CommonName: localhost.localdomain
fetchmail: Server CommonName: localhost.localdomain
fetchmail: inmail.njm.f2s.com key fingerprint: E1:A1:1A:47:61:46:97:6D:F3:9D:BF:13:59:40:EA:E3
fetchmail: POP3> CAPA

(I hope my MUA hasn't mangled that too much.)

So it looks like fetchmail is complaining about my ISPs setup.  Is that
right?

For reference, I am running fetchmail 6.3.4 on FreeBSD v6.1 (STABLE).

Thanks in advance.

Cheers,
Nick.
-- 
"We're predicting third stage shutdown at 11 minutes 42 seconds."

Re: [fetchmail-users] Simple fetch and forward

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

On 7/24/06, John <fet...@je...> wrote:
> Fetchmail 6.3.4

That avoids the usual "upgrade to the latest version" chant :-)

> >2) Contents of .fetchmailrc
<---SNIP--->
> I was previously trying:
>
> poll mail.ispmailserver.net protocol pop3
>     aka forwarder1.com
>     envelope Received

(This is almost certainly your problem)

>     localdomains domain1.com domain2.com domain3.com
>     user my-username there pass my-password to * here

That's pretty close to what I've got, and it works for me.

I suspect the problem relates to the overloading of the Received
header.  Does your ISP use a Delivered-to or Envelope-to header?

> fetchmail: line rejected, four.mx.forwarder1.com is not an alias of the
> mailserver

Try the options below and, if it still fails, provide the output of
"fetchmail -v -v -v" for a BCC email.  That email's headers would help
too.

> Fetchmail seems to want to change headers and this is confusing things. If I
> can just get it to pass stuff through verbatim then I think it'll be ok.

You probably want to add the options to "set invisible" and "no rewrite".

-- 
                 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] Simple fetch and forward

[John <fet...@je...>]

>You can (that's what I'm doing).  What you're missing is providing us
>with any information to help you.

>So,

>1) Fetchmail version
Fetchmail 6.3.4

>2) Contents of .fetchmailrc

I've tried so many variants of the fetchmailrc file I don't really have
"one" to send. Here is what I have at the moment:

set logfile /var/log/fetchmail.log
set no bouncemail
set postmaster root
set daemon 1500

poll mail.ispmailserver.net protocol pop3
    user my-username pass my-password

I was previously trying:

poll mail.ispmailserver.net protocol pop3
    aka forwarder1.com
    envelope Received
    localdomains domain1.com domain2.com domain3.com
    user my-username there pass my-password to * here

I had to put in aka to get mail that had been forwarded by my domain's DNS
to be recognised when the Received lines were parsed. Without this I got the
below error on a Bcc:

fetchmail: line rejected, four.mx.forwarder1.com is not an alias of the
mailserver

The localdomains are my domains. This latter configuration is probably
nonsense but it got me close (but not exactly) to what I am trying to do. It
works for a specific case but is not really a solution.

Fetchmail seems to want to change headers and this is confusing things. If I
can just get it to pass stuff through verbatim then I think it'll be ok.

All help is much appreciated.

Re: [fetchmail-users] Simple fetch and forward

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

On 7/24/06, fet...@je... <fet...@je...> wrote:
> I don't want it to check messages, to try routing them, to change the
> headers, nothing. I just want it to get the mail from POP and send it to
> SMTP.
>
> I have stuff on Postfix, Procmail and Cyrus-IMAP that will handle
> validating a message so Fetchmail should not be trying to do this.
>
> Can I do this or am I missing something.

You can (that's what I'm doing).  What you're missing is providing us
with any information to help you.

So,

1) Fetchmail version

2) Contents of .fetchmailrc

-- 
                 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] Simple fetch and forward

[<fet...@je...>]

Hello,

I have a mailserver running Postfix, Procmail, Cyrus-IMAP and a bunch of
other stuff. It handles mail for users various domains obtained over SMTP.

I need to pull some additional mail off some POP mail servers and I have
tried to use Fetchmail to do this. I have got it working to an extent but
am falling foul of the multidrop mode.

I think my problems are because Fetchmail is trying to be too clever. I
would like it to get ALL mail from a pop3 mailbox and forward ALL mail,
unaltered, to my Postfix server listening on port 25.

I don't want it to check messages, to try routing them, to change the
headers, nothing. I just want it to get the mail from POP and send it to
SMTP.

I have stuff on Postfix, Procmail and Cyrus-IMAP that will handle
validating a message so Fetchmail should not be trying to do this.

Can I do this or am I missing something.

Many thanks,
John


--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .

Re: [fetchmail-users] [fetchmail]Multidrop fetchmail bouncing non-existing local addresses

[Andy H. <adh...@gm...>]

Hi,

On 7/18/06, Rob MacGregor <rob...@gm...> wrote:
> Give it another couple of days.  I'm reasonably sure somebody with
> knowledge of the source will be by before the weekend.  The
> development team is pretty small (not sure of the exact number, but I
> suspect only 2 or 3).

Ok. I've found a workaround by changing the postmaster setting to an
empty string. However, I suspect that's not a particularly good
idea...

Andy

Re: [fetchmail-users] [fetchmail]Multidrop fetchmail bouncing non-existing local addresses

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

On 7/18/06, Andy Hawkins <adh...@gm...> wrote:
> Hi,
>
> I guess the question I have is why my configuration works as I want
> (bounces mail to invalid addresses) when I run it interactively, but
> not when I run fetchmail as a daemon (as I'd rather do)?

Give it another couple of days.  I'm reasonably sure somebody with
knowledge of the source will be by before the weekend.  The
development team is pretty small (not sure of the exact number, but I
suspect only 2 or 3).

-- 
                 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] Bouncing invalid addresses

[Andy H. <adh...@gm...>]

Hi,

Ok, I did a bit more digging in the man page. I tried

set postmaster ""

And this appears to have cured it. However, the manual says:

"The --postmaster <name> option (keyword: set postmaster) specifies
the last-resort username to which multidrop mail is to be forwarded if
no matching local recipient can be found. It is also used as
destination of undeliverable mail if the 'bouncemail' global option is
off "

I have 'set bouncemail' in the top of my config file, so if I'm
reading that correctly it shouldn't be sending undeliverable mail to
the postmaster user.

Anyone?

Andy

Re: [fetchmail-users] [fetchmail]Multidrop fetchmail bouncing non-existing local addresses

[Andy H. <adh...@gm...>]

Hi,

I guess the question I have is why my configuration works as I want
(bounces mail to invalid addresses) when I run it interactively, but
not when I run fetchmail as a daemon (as I'd rather do)?

Anyone?

Andy

Re: [fetchmail-users] [fetchmail]Multidrop fetchmail bouncing non-existing local addresses

[Andy H. <adh...@gm...>]

Hi,

On 7/17/06, Matthias Andree <mat...@gm...> wrote:
> On Mon, 17 Jul 2006, Andy Hawkins wrote:
>
> > I don't want to bounce it because it's Spam, I want to bounce it
> > because the destination address isn't valid.
>
> Then why doesn't your upstream server know it's invalid and reject the
> message right away?

I have a server on the net that handles mail for my domains. It does
this by just putting all mail for each domain into one mailbox (one
per domain). I don't want to have to set up an individual mailbox for
each account in each domain I have.

When the mail is downloaded via fetchmail, my local machine knows what
accounts are valid and will bounce any that aren't. Fetchmail appears
to be sending bounce message, but then delivering the message to the
postmaster address anyway. I just want to turn off this postmaster
delivery for mail that should be bounced.

Andy

[fetchmail-users] Fwd: Fwd: [fetchmail]Multidrop fetchmail bouncing non-existing local addresses

[Andy H. <adh...@gm...>]

Hi,


On 7/17/06, Rob MacGregor <rob...@gm...> wrote:
> It wouldn't hurt to provide the output of "fetchmail --configdump" so
> we can see what fetchmail thinks of it's config file.

Below (I've cut out the entries for the other servers I check, but
they're all very similar in terms of configuration).

TRUE=1; FALSE=0

os_type = 'linux'
feature_options = ('pop3','imap','sdps','etrn','odmr','ssl',)
# Start of configuration initializer
fetchmailrc = {
  'poll_interval':0,
  "logfile":None,
  "idfile":"/var/lib/fetchmail/.fetchids",
  "postmaster":"fetchmail",
  'bouncemail':TRUE,
  'spambounce':FALSE,
  "properties":None,
  'invisible':FALSE,
  'showdots':TRUE,
  'syslog':FALSE,
  # List of server entries begins here
  'servers': [
      # Entry for site `xxx.xxx.xxx.xxx' begins:
      {
          "pollname":"xxx.xxx.xxx.xxx",
          'active':TRUE,
          "via":None,
          "protocol":"POP3",
          "service":None,
          'timeout':300,
          'interval':0,
          "envelope":"Delivered-To",
          'envskip':1,
          "qvirtual":"45-",
          "auth":"any",
          'dns':TRUE,
          'uidl':TRUE,
          "aka":[],
          "localdomains":["xxx.xxx.xxx"],
          "interface":None,
          "monitor":None,
          "plugin":None,
          "plugout":None,
          "principal":None,
          'tracepolls':FALSE,
          'users': [
              {
                  "remote":"xx...@xx...",
                  "password":"xxxxxxx",
                  'localnames':["fetchmail", '*'],
                  '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":"",
                  'sslcertck':FALSE,
                  "sslcertpath":None,
                  "sslfingerprint":None,
                  'expunge':0,
                  "properties":None,
                  "smtphunt":["localhost"],
                  "fetchdomains":[],
                  "smtpaddress":"yyy.yyy.yyy",
                  "smtpname":None,
                  'antispam':'',
                  "mailboxes":[],
              }
              ,           ]
      }
  ]
}
# End of initializer

Re: [fetchmail-users] Fwd: [fetchmail]Multidrop fetchmail bouncing non-existing local addresses

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

As it says in the .sig - please keep list traffic on the list.  Your
message has *NOT* been forwarded.

On 7/17/06, Andy Hawkins <adh...@gm...> wrote:
> Hi,

-- 
                 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] Fwd: [fetchmail]Multidrop fetchmail bouncing non-existing local addresses

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

On 7/17/06, Andy Hawkins <adh...@gm...> wrote:
>
> Should we continue this here for now, or move to there?

Here :-)  Very few people watch the old lists.  As far as I can tell
mostly only me.

> > On 7/17/06, Andy Hawkins <adh...@gm...> wrote:
> > Upgrade to 6.3.4
>
> Ok, didn't want to do that as it involves building from source, but
> I've done that now.

Great.

> > Spam messages almost never have a legit return address.  All you'll
> > end up doing is annoying some poor innocent sod, and possibly becoming
> > a spam source yourself.  Better to drop them on the floor.
>
> True, but I want legitimate mail (but with invalid addresses) to be
> bounced so that the sender knows they've got it wrong.

As long as you're aware of the risks.  Keep an eye on the volume of
bounces.  If/when people realise what you're doing they may target you
for a spam run (basically using you to "bounce" the spam to the
recipient).

That isn't theory - that's a pretty standard spam tactic.

> Below:
>
<---SNIP--->
> fetchmail: SMTP> RCPT TO:<yyy@yyy.yyy>
> fetchmail: SMTP< 550 unknown user
> fetchmail: SMTP error: 550 unknown user
> fetchmail: SMTP listener doesn't like recipient address `yyy@yyy.yyy'
> fetchmail: SMTP< 220 zzz.zzz.zzz ESMTP Exim 4.50 Mon, 17 Jul 2006 16:15:41 +0100
> fetchmail: SMTP> HELO zzz.zzz.zzz
> fetchmail: SMTP< 250 zzz.zzz.zzz Hello localhost [127.0.0.1]
> fetchmail: SMTP> MAIL FROM:<>
> fetchmail: SMTP< 250 OK
> fetchmail: SMTP> RCPT TO:<xx...@xx...>
> fetchmail: SMTP< 250 Accepted
> fetchmail: SMTP> DATA
> fetchmail: SMTP< 354 Enter message, ending with "." on a line by itself
> fetchmail: SMTP: (bounce-message body)
> fetchmail: SMTP>. (EOM)
> fetchmail: SMTP< 250 OK id=1G2Uov-0005GD-HY
> fetchmail: SMTP> QUIT
> fetchmail: SMTP< 221 zzz.zzz.zzz closing connection
> fetchmail: SMTP> RCPT TO:<postmaster@zzz.zzz.zzz>
> fetchmail: SMTP< 250 Accepted
> fetchmail: no address matches; forwarding to postmaster.
<---SNIP--->
>
> It looks like it has sent a bounce, but still forwarded the mail to
> the postmaster.

Not sure why it did that - hopefully one of the maintainers will come
by and have an idea what's going on.

It wouldn't hurt to provide the output of "fetchmail --configdump" so
we can see what fetchmail thinks of it's config file.

-- 
                 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] Fwd: [fetchmail]Multidrop fetchmail bouncing non-existing local addresses

[Andy H. <adh...@gm...>]

Hi,


On 7/17/06, Rob MacGregor <rob...@gm...> wrote:
> These lists are depreciated - please use the lists found at www.fetchmail.info

Should we continue this here for now, or move to there?

> On 7/17/06, Andy Hawkins <adh...@gm...> wrote:
> Upgrade to 6.3.4

Ok, didn't want to do that as it involves building from source, but
I've done that now.

> Spam messages almost never have a legit return address.  All you'll
> end up doing is annoying some poor innocent sod, and possibly becoming
> a spam source yourself.  Better to drop them on the floor.

True, but I want legitimate mail (but with invalid addresses) to be
bounced so that the sender knows they've got it wrong.

> Otherwise, once you've upgraded to 6.3.4 please submit the output of
> "fetchmail -v -v -v" showing the problem.

This is the config:

set bouncemail
poll xxx.xxx.xxx.xxx
       protocol pop3
       envelope 1 "Delivered-To"
       qvirtual "45-"
       localdomains xxx.xxx.xxx
       username xx...@xx... password "xxxxxx" is * here
       nokeep smtpaddress zzz.zzz.zzz
Below:

fetchmail: POP3> RETR 7
fetchmail: POP3< +OK 475 octets follow.
reading message xx...@xx...@yyy.yyy:7 of 7 (475 octets)
About to rewrite Return-Path: <yyy@yyy.yyy>
Rewritten version is Return-Path: <yyy@yyy.yyy>

About to rewrite From: yyy@yyy.yyy
Rewritten version is From: yyy@yyy.yyy

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

fetchmail: passed through xx...@xx... matching xxx.xxx.xxx
fetchmail: SMTP< 220 zzz.zzz.zzz ESMTP Exim 4.50 Mon, 17 Jul 2006 16:15:41 +0100
fetchmail: SMTP> EHLO zzz.zzz.zzz
fetchmail: SMTP< 250-zzz.zzz.zzz Hello localhost [127.0.0.1]
fetchmail: SMTP< 250-SIZE 52428800
fetchmail: SMTP< 250-PIPELINING
fetchmail: SMTP< 250 HELP
fetchmail: forwarding to localhost
fetchmail: SMTP> MAIL FROM:<xx...@xx...> SIZE=475
fetchmail: SMTP< 250 OK
fetchmail: SMTP> RCPT TO:<yyy@yyy.yyy>
fetchmail: SMTP< 550 unknown user
fetchmail: SMTP error: 550 unknown user
fetchmail: SMTP listener doesn't like recipient address `yyy@yyy.yyy'
fetchmail: SMTP< 220 zzz.zzz.zzz ESMTP Exim 4.50 Mon, 17 Jul 2006 16:15:41 +0100
fetchmail: SMTP> HELO zzz.zzz.zzz
fetchmail: SMTP< 250 zzz.zzz.zzz Hello localhost [127.0.0.1]
fetchmail: SMTP> MAIL FROM:<>
fetchmail: SMTP< 250 OK
fetchmail: SMTP> RCPT TO:<xx...@xx...>
fetchmail: SMTP< 250 Accepted
fetchmail: SMTP> DATA
fetchmail: SMTP< 354 Enter message, ending with "." on a line by itself
fetchmail: SMTP: (bounce-message body)
fetchmail: SMTP>. (EOM)
fetchmail: SMTP< 250 OK id=1G2Uov-0005GD-HY
fetchmail: SMTP> QUIT
fetchmail: SMTP< 221 zzz.zzz.zzz closing connection
fetchmail: SMTP> RCPT TO:<postmaster@zzz.zzz.zzz>
fetchmail: SMTP< 250 Accepted
fetchmail: no address matches; forwarding to postmaster.
fetchmail: SMTP> DATA
fetchmail: SMTP< 354 Enter message, ending with "." on a line by itself
#*fetchmail: SMTP>. (EOM)
fetchmail: SMTP< 250 OK id=1G2Uov-0005GC-Kh
 not flushed
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Bye-bye.
fetchmail: SMTP> QUIT
fetchmail: SMTP< 221 zzz.zzz.zzz closing connection
fetchmail: 6.3.4 querying yyy.yyy.yyy (protocol POP3) at Mon Jul 17
16:15:41 2006: poll completed
fetchmail: swapping UID lists
fetchmail: Writing fetchids file.
fetchmail: normal termination, status 0
fetchmail: Writing fetchids file.

It looks like it has sent a bounce, but still forwarded the mail to
the postmaster.

Any ideas?

Andy

Re: [fetchmail-users] Has anyone ever seen "Fetchmail saw more than N timouts while attempting to get mail from ..."

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

On 7/15/06, Matthias Andree <mat...@gm...> wrote:
> Greetings!
>
> Has anyone ever seen warning messages of his fetchmail running in daemon
> mode that were like:
>
>   Fetchmail saw more than 20 timouts while attempting to get mail from
>   foo@bar.  This could mean that your mailserver is stuck, or that your
>   SMTP listener is wedged, or that your mailbox file on the server has
>   been corrupted by a server error.  You can run `fetchmail -v -v' to
>   diagnose the problem. Fetchmail won't poll this mailbox again until
>   you restart it.

I'm not aware of having ever seen such a message, despite periods of
24 hours and more when my ISP's mail server has been offline (and
easily polled a couple of hundred times).

-- 
                 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] Has anyone ever seen "Fetchmail saw more than N timouts while attempting to get mail from ..."

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

Greetings!

Has anyone ever seen warning messages of his fetchmail running in daemon
mode that were like:

  Fetchmail saw more than 20 timouts while attempting to get mail from
  foo@bar.  This could mean that your mailserver is stuck, or that your
  SMTP listener is wedged, or that your mailbox file on the server has
  been corrupted by a server error.  You can run `fetchmail -v -v' to
  diagnose the problem. Fetchmail won't poll this mailbox again until
  you restart it.

If you've seen these, please report the fetchmail version (type this to
print it, the first line suffices: fetchmail -V | head) and your
operating system and version (type "uname -a" without quote marks to get
this).

This message is supposed to be mailed to a user since 4.6.7, but the
code I've looked at makes it rather unlikely (not to say impossible) to
ever be mailed on operating systems that I'm used to. Before removing
the relevant code for the 6.3.5 update, I'd like to know if someone is
getting these messages.

Thanks!

Kind regards,

-- 
Matthias Andree