fetchmail-users — User questions and discussion

Re: [fetchmail-users] fetchmail on server unable to connect to postfix

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

M. Fioretti wrote:
> Rob wrote:

> > Note that rejecting unqualified HELO values while being fully
> > RFC compliant...
>
> Yes, we're aware of this and in _our_ particular case we should be
> fine. For now, at least.

Ideally in your smtpd restrictions you should tell postfix to 
permit_mynetworks *before* reject_non_fqdn_hostname and 
reject_invalid_hostname.  And be sure mynetworks includes 127.0.0.0/8.


> smtphost the.full.machine.name
>
> still yelds (may this depend on the fetchmail version???):
>
> fetchmail: SMTP> EHLO localhost

I'm pretty sure this depends on the fetchmail version; a check of the NEWS 
file shows that there's been a lot of work on the smtphost feature since 
6.2.  OTOH the current man page doesn't seem to clearly talk about 
HELO/EHLO.

-- 
==============================|   "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] fetchmail on server unable to connect to postfix

[M. F. <mfi...@ne...>]

Rob wrote:

> Marco wrote:
> > I take this to mean that setting smtpaddress as above isn't
> > enough to not make fetchmail send an helo different than localhost....
>
> Right, having taken a moment to dive into the code, the value
> of the HELO/ELHO string that is presented is the value of smtphost.
> This defaults to localhost - change this to the fully qualified name
> of the host

Unfortunately this doesn't seem enough. Doing a

poll pop3.myisp.com with proto POP3 tracepolls
   user myaccount there with pass "thepassword" is mfi...@ne...
here keep smtphost the.full.machine.name

still yelds (may this depend on the fetchmail version???):

fetchmail: About to rewrite To: mya...@my...
Rewritten version is To: mya...@my...

fetchmail: SMTP< 220 the.full.machine.name ESMTP Postfix
fetchmail: SMTP> EHLO localhost
fetchmail: SMTP< 250-the.full.machine.name
fetchmail: SMTP< 250-PIPELINING
fetchmail: SMTP< 250-SIZE 10240000
fetchmail: SMTP< 250-ETRN
fetchmail: SMTP< 250-STARTTLS
fetchmail: SMTP< 250-ENHANCEDSTATUSCODES
fetchmail: SMTP< 250-8BITMIME
fetchmail: SMTP< 250 DSN
fetchmail: forwarding to the.full.machine.name
fetchmail: SMTP> MAIL FROM:<a_test_address> SIZE=1192
fetchmail: SMTP< 250 2.1.0 Ok
fetchmail: SMTP> RCPT TO:<mfi...@ne...>
fetchmail: SMTP< 504 5.5.2 <localhost>: Helo command rejected: need
fully-qualified hostname
fetchmail: SMTP error: 504 5.5.2 <localhost>: Helo command rejected: need
fully-qualified hostname
fetchmail: SMTP listener doesn't like recipient address
`mfi...@ne...'

> Note that rejecting unqualified HELO values while being fully
> RFC compliant...

Yes, we're aware of this and in _our_ particular case we should be
fine. For now, at least.

> Which is why I went directly to the postfix site for that snippet,
> and I don't even use postfix :)

exactly my point. When the underlying terminology and standards are,
shall we say, so peculiar, it doesn't matter much which server one
uses, does it? Whereas having _already_ acquired_ over time an in-depth
knowledge and understanding of the lingo helps a lot. This is where
I hope to arrive, of course.

Thanks for any further help! As a side note, I hope this thread continues
until the problem is solved via fetchmail also because... I'm learning
more about fetchmail this afternoon, thanks to this thread, than by
reading the docs again and again...

Marco

Re: [fetchmail-users] fetchmail on server unable to connect to postfix

[Frederic M. <fre...@wo...>]

M. Fioretti a écrit :
>>> Helo command rejected: need fully-qualified hostname
>>>       
>> So, fix your postfix configuration
>>     
>
> As I mentioned in the original message, I cannot easily change (for
> reasons which are everything but technical...) the postfix configuration.
> Unless I *am* sure that it is really the only possible way to fix this, that
> is. Otherwise I would have posted straight to the postfix list.
>
> For the record, here is the complete excerpt of the postfix refusal I get
> _WITH_:
>
>    poll pop3.myprovider.com with proto POP3 tracepolls
>       user myaccount there with pass "the password" is root here keep
>       smtpaddress exact_output_of_hostname_command_here
>
> Aug 16 14:41:55 machinename postfix/smtpd[5641]: NOQUEUE: reject: RCPT
> from localhost[127.0.0.1]: 504 5.5.2 <localhost>: Helo command rejected:
> need fully-qualified hostname; from=<testaddress>
> to=<root@exact_output_of_hostname_command_here> proto=ESMTP
> helo=<localhost>
>
> I take this to mean that setting smtpaddress as above isn't enough to
> not make fetchmail send an helo different than localhost. Is this correct,
> and if yes, isn't there any other way to make fetchmail helo something
> else?
>   
According to fetchmail's man page smtpaddress adds the domain to the 
rcpt to, not to the helo of the envelope.

Have a look at your /etc/hosts. Does the address 127.0.0.1 resolves 
first to the name of the machine or to localhost as is usually the case 
by default ?

If localhost is the first name, could you rewrite /etc/hosts to put the 
machine name (what you want to see in the helo) as the first name 
matching 127.0.0.1 ? Something like:

127.0.0.1   machinename.domain.dom   machinename  localhost.localdomain  
localhost

My guess is that localhost may be the first name matching 127.0.0.1 and 
fetchmail uses it in the helo.

Frederic

Re: [fetchmail-users] fetchmail on server unable to connect to postfix

[M. F. <mfi...@ne...>]

On Thu, August 16, 2007 3:49 pm, Frederic Marchal wrote:
> According to fetchmail's man page smtpaddress adds the domain to the
> rcpt to, not to the helo of the envelope.
>
> Have a look at your /etc/hosts. Does the address 127.0.0.1 resolves
> first to the name of the machine or to localhost as is usually the case
> by default ?
>
> If localhost is the first name, could you rewrite /etc/hosts to put the
> machine name (what you want to see in the helo) as the first name
> matching 127.0.0.1 ? Something like:
>
> 127.0.0.1   machinename.domain.dom   machinename  localhost.localdomain
> localhost
>
> My guess is that localhost may be the first name matching 127.0.0.1 and
> fetchmail uses it in the helo.
>

Frederic,

thanks for your suggestion. /etc/hosts was indeed defaulting to localhost
and localhost.localdomain as the only values for 127.0.0.1

Changing it as you suggest _does_ (will it impact other services???):

     127.0.0.1 machinename.domain.dom localhost localhost.localdomain

causes "hostname" to return "machinename.domain.dom". It is not enough,
however, to make fetchmail helo with that value, or so I understand:

################################################################
fetchmail: About to rewrite To: my_...@my...
Rewritten version is To: my_...@my...

fetchmail: SMTP< 220 machinename.domain.dom ESMTP Postfix
fetchmail: SMTP> EHLO localhost
fetchmail: SMTP< 250-machinename.domain.dom
fetchmail: SMTP< 250-PIPELINING
fetchmail: SMTP< 250-SIZE 10240000
fetchmail: SMTP< 250-ETRN
fetchmail: SMTP< 250-STARTTLS
fetchmail: SMTP< 250-ENHANCEDSTATUSCODES
fetchmail: SMTP< 250-8BITMIME
fetchmail: SMTP< 250 DSN
fetchmail: forwarding to localhost
fetchmail: SMTP> MAIL FROM:<a_t...@ya...> SIZE=1192
fetchmail: SMTP< 250 2.1.0 Ok
fetchmail: SMTP> RCPT TO:<mfi...@ne...>
fetchmail: SMTP< 504 5.5.2 <localhost>: Helo command rejected: need
fully-qualified hostname
fetchmail: SMTP error: 504 5.5.2 <localhost>: Helo command rejected: need
fully-qualified hostname
fetchmail: SMTP listener doesn't like recipient address
`mfi...@ne...'

##############################################################

having smtpaddress set or not in the fetchmailrc file doesn't change
anything. What now?

Thanks,
Marco

Re: [fetchmail-users] fetchmail on server unable to connect to postfix

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

On 8/16/07, M. Fioretti <mfi...@ne...> wrote:
>
> The one I reported is the default one in Centos 4.4, I'll try to
> have it upgraded asap, thanks. Not that it would make any difference wrt
> this problem, would it? Now:

It probably wouldn't, but I don't know all the changes that have gone
into fetchmail in the interim.

> I take this to mean that setting smtpaddress as above isn't enough to
> not make fetchmail send an helo different than localhost. Is this correct,
> and if yes, isn't there any other way to make fetchmail helo something
> else?

Right, having taken a moment to dive into the code, the value of the
HELO/ELHO string that is presented is the value of smtphost.  This
defaults to localhost - change this to the fully qualified name of the
host and ensure that it is configured to NOT reject connections that
provide it's own name as the HELO value.

Note that rejecting unqualified HELO values while being fully RFC
compliant will trip up a large number of MUAs (particularly those from
Microsoft).  If you don't expect any mail clients to ever connect
directly you'll probably be ok.

> Generally, I have no problem at all to study man pages. The specific
> problem I have with email related docs is that it's really hard to
> figure out, unless one already knows the whole terminology and protocols
> in advance, to know what to search for.
>
> Even placing the whole error message in google, as I usually do, doesn't
> yeld much when email is concerned. I know this for a fact, that's why I
> also need a bit of pointers from mailing lists.

Which is why I went directly to the postfix site for that snippet, and
I don't even use postfix :)

-- 
                 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 on server unable to connect to postfix

[M. F. <mfi...@ne...>]

On Thu, Aug 16, 2007 13:12:41 PM +0100, Rob MacGregor
(rob...@gm...) wrote:
> On 8/16/07, M. Fioretti <mfi...@ne...> wrote:
> Please upgrade to 6.3.8

The one I reported is the default one in Centos 4.4, I'll try to
have it upgraded asap, thanks. Not that it would make any difference wrt
this problem, would it? Now:

> > Helo command rejected: need fully-qualified hostname
> So, fix your postfix configuration

As I mentioned in the original message, I cannot easily change (for
reasons which are everything but technical...) the postfix configuration.
Unless I *am* sure that it is really the only possible way to fix this, that
is. Otherwise I would have posted straight to the postfix list.

For the record, here is the complete excerpt of the postfix refusal I get
_WITH_:

   poll pop3.myprovider.com with proto POP3 tracepolls
      user myaccount there with pass "the password" is root here keep
      smtpaddress exact_output_of_hostname_command_here

Aug 16 14:41:55 machinename postfix/smtpd[5641]: NOQUEUE: reject: RCPT
from localhost[127.0.0.1]: 504 5.5.2 <localhost>: Helo command rejected:
need fully-qualified hostname; from=<testaddress>
to=<root@exact_output_of_hostname_command_here> proto=ESMTP
helo=<localhost>

I take this to mean that setting smtpaddress as above isn't enough to
not make fetchmail send an helo different than localhost. Is this correct,
and if yes, isn't there any other way to make fetchmail helo something
else?

With respect to this:
> Having taken 2 seconds to consult the postfix documentation.. I suspect
> you actually want to further consult the postfix documentation

Generally, I have no problem at all to study man pages. The specific
problem I have with email related docs is that it's really hard to
figure out, unless one already knows the whole terminology and protocols
in advance, to know what to search for.

Even placing the whole error message in google, as I usually do, doesn't
yeld much when email is concerned. I know this for a fact, that's why I
also need a bit of pointers from mailing lists.

Thanks for your patience,
Marco

-- 
Help *everybody* love Free Standards and Software:
http://digifreedom.net

Re: [fetchmail-users] fetchmail on server unable to connect to postfix

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

On 8/16/07, M. Fioretti <mfi...@ne...> wrote:
<---SNIP--->
> Now I want to reuse that file on a Centos server, separate from my home
> desktop, running postfix, dovecot and fetchmail-6.2.5-6.0.1.el4

Please upgrade to 6.3.8

> fetchmail always gets from postfix:
>
> Helo command rejected: need fully-qualified hostname

So, fix your postfix configuration :)  You may find that setting the
fetchmail keyword smtpaddress to something that is qualified will help
(see the man page).

<---SNIP--->
>
> Why does the rc file which works fine at home fail on the server?
> OK, if I understand correctly, the problem is that _postfix_ is
> configured differently, and it's not a fetchmail problem.

Correct, this is a postfix configuration issue.

> Alternatively, pointers to the specific postfix setting causing this are
> also welcome.

Having taken 2 seconds to consult the postfix documentation:

http://www.seaglass.com/postfix/faq.html#dapp

Provides details as to the setting that causes this.  I suspect you
actually want to further consult the postfix documentation to
whitelist localhost from that test.

-- 
                 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] fetchmail on server unable to connect to postfix

[M. F. <mfi...@ne...>]

Hello,

I have on my home computer the working fetchmail rc file shown below, to
download all the messages from my ISP pop3 server to my home box.

Now I want to reuse that file on a Centos server, separate from my home
desktop, running postfix, dovecot and fetchmail-6.2.5-6.0.1.el4

On that server there is no user "marco". There are only virtual email
users, and I'd rather not add other Unix users there. On the server there
is ad-hoc user without shell which is only used by postfix and dovecot to
deliver messages to mailboxes:

# grep mail_only_account /etc/passwd:

mail_only_account:x:2000:2000::/home/mail_only_account:/bin/false

However, if I run as user mail_only_account:

/usr/bin/fetchmail -vv  -f /usr/local/etc/Fetchmail/always

fetchmail always gets from postfix:

Helo command rejected: need fully-qualified hostname

no matter what I write in place of "marco": root, this complete address
mfi...@ne..., whatever.

More in detail:

fetchmail: SMTP< 220 the.server.com ESMTP Postfix
fetchmail: SMTP> EHLO localhost
fetchmail: SMTP< 250-the.server.com
fetchmail: SMTP< 250-PIPELINING
fetchmail: SMTP< 250-SIZE 10240000
fetchmail: SMTP< 250-ETRN
fetchmail: SMTP< 250-STARTTLS
fetchmail: SMTP< 250-ENHANCEDSTATUSCODES
fetchmail: SMTP< 250-8BITMIME
fetchmail: SMTP< 250 DSN
fetchmail: forwarding to localhost
fetchmail: SMTP> MAIL FROM:<test_address> BODY=8BITMIME SIZE=1471
fetchmail: SMTP< 250 2.1.0 Ok
fetchmail: SMTP> RCPT TO:<mfi...@ne...>
fetchmail: SMTP< 504 5.5.2 <localhost>: Helo command rejected: need
fully-qualified hostname

Why does the rc file which works fine at home fail on the server?
OK, if I understand correctly, the problem is that _postfix_ is
configured differently, and it's not a fetchmail problem. However, I am
not sure if I can (ask to) change the postfix configuration right now, so
I'd be very grateful if somebody could let me know if there is any
possibility to "patch" it by passing some other option to fetchmail.

Alternatively, pointers to the specific postfix setting causing this are
also welcome.

Thank you in advance for any feedback,
           Marco

##################################################
content of /usr/local/etc/Fetchmail/always:

set logfile "/var/log/procmail_logs/log_fetch_mail"
#set postmaster "root"
set nobouncemail
set properties ""
#set daemon 60
set no syslog

poll pop3.my_isp.com with proto POP3 tracepolls
   user mycustomer_login there with pass "thepassword" is marco here keep

-- 
Help *everybody* love Free Standards and Software:
http://digifreedom.net

Re: [fetchmail-users] Recipient address rejected: User unknown in local recipient table

[Johan V. <fet...@bo...>]

> Well, I have a separate admin mailbox that all mail for a number of
> admin related addresses goes to (postmaster, hostmaster, abuse and the
> others mentioned by an RFC I don't remember the number of).  I've also
> got a catchall mailbox for last resort delivery - it almost never
> receives mail, but it has come in handy a few times.
>
> Lastly, I use Hobbit (hobbitmon.sf.net) to monitor all my systems,
> including logfile monitoring.  It's the work of a few moments to set
> it to produce an alert when fetchmail generates an error message.
> Just make sure it sends emails to an off-network mailbox as well as to
> a local one, so that if you break your local mailbox you still get
> notified (and visit the web page so you can eyeball the status in case
> you completely break your email)
Thanks for the advice. I'll check into it.

Greets
Johan Vandeweerd

Re: [fetchmail-users] Recipient address rejected: User unknown in local recipient table

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

On 8/15/07, Johan Vandeweerd <fet...@bo...> wrote:
>
> You're right. It runs as a daemon at startup but as user fetchmail.

:)

> How have you configured it or how would you do it?

Well, I have a separate admin mailbox that all mail for a number of
admin related addresses goes to (postmaster, hostmaster, abuse and the
others mentioned by an RFC I don't remember the number of).  I've also
got a catchall mailbox for last resort delivery - it almost never
receives mail, but it has come in handy a few times.

Lastly, I use Hobbit (hobbitmon.sf.net) to monitor all my systems,
including logfile monitoring.  It's the work of a few moments to set
it to produce an alert when fetchmail generates an error message.
Just make sure it sends emails to an off-network mailbox as well as to
a local one, so that if you break your local mailbox you still get
notified (and visit the web page so you can eyeball the status in case
you completely break your email).

> Thanks for all the advice and help btw ;-)

I'm happy to help those who're willing to work towards a solution and
provide the information asked for :)

-- 
                 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] Recipient address rejected: User unknown in local recipient table

[Johan V. <fet...@bo...>]

> Which is a bad idea and if you were running a vaguely recent version
> it would be warning you about this.  However your logs suggest that
> it's being run as the user fetchmail - either that or the fetchmailrc
> file you provided isn't the one you're using.
>   
You're right. It runs as a daemon at startup but as user fetchmail.

> Ah, the old game of shooting yourself in the foot with a rocket
> launcher :)  I'm afraid there's nothing fetchmail can do to protect
> you from this.
How have you configured it or how would you do it?

Thanks for all the advice and help btw ;-)

Greetings
Johan Vandeweerd

Re: [fetchmail-users] Recipient address rejected: User unknown in local recipient table

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

On 8/15/07, Johan Vandeweerd <fet...@bo...> wrote:
>
> > The default antispam list is empty - I'm not sure what you're thinking
> > to achieve with this.
> >
> I let my local mailclient handle the spam (move to spamfolder) so I have
> more control over my spam.

Yes, but you're replacing the empty list with a list containing the
value "-1".  I'm not sure what fetchmail will do with this internally
("fetchmail --configdump" will tell you), but it may just bite you
later.

> Fetchmail is run systemwide as root.

Which is a bad idea and if you were running a vaguely recent version
it would be warning you about this.  However your logs suggest that
it's being run as the user fetchmail - either that or the fetchmailrc
file you provided isn't the one you're using.

> In /etc/aliases everything is
> aliased to root and the final statement is an alias from root to the old
> username that doesn't exist anymore.

Ah, the old game of shooting yourself in the foot with a rocket
launcher :)  I'm afraid there's nothing fetchmail can do to protect
you from this.

-- 
                 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] Recipient address rejected: User unknown in local recipient table

[Johan V. <fet...@bo...>]

> The default antispam list is empty - I'm not sure what you're thinking
> to achieve with this.
>   
I let my local mailclient handle the spam (move to spamfolder) so I have 
more control over my spam.

> So, if you're running as root bounced mail will be directed to
> postmaster, otherwise the user running fetchmail (as detailed in the
> man page).
>   
Fetchmail is run systemwide as root. In /etc/aliases everything is 
aliased to root and the final statement is an alias from root to the old 
username that doesn't exist anymore.
Normally I recieve all message on my mailbox, but I forgot to change the 
alias :-S

Greetings
Johan Vandeweerd

Re: [fetchmail-users] Recipient address rejected: User unknown in local recipient table

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

On 8/15/07, Johan Vandeweerd <fet...@bo...> wrote:
>
> My fetchmailrc looks like this:
>
>     set no bouncemail

So, if you're running as root bounced mail will be directed to
postmaster, otherwise the user running fetchmail (as detailed in the
man page).

>    set daemon 600
>    defaults:
>      antispam -1

The default antispam list is empty - I'm not sure what you're thinking
to achieve with this.

> In the logs I find things like this:
>
<---SNIP--->
>     Aug 12 06:12:01 cyclops postfix/smtpd[19251]: connect from
>     localhost[127.0.0.1]
>     Aug 12 06:12:01 cyclops postfix/smtpd[19251]: EBAE7214DF2:
>     client=localhost[127.0.0.1]

Fetchmail starts the process of sending the bounce message

>     Aug 12 06:12:01 cyclops fetchmail[3067]: mail from
>     MAILER-DAEMON@localserver bounced to fetchmail
>     Aug 12 06:12:02 cyclops postfix/cleanup[19252]: EBAE7214DF2:
>     message-id=<20070812041201.EBAE7214DF2@localserver>
>     Aug 12 06:12:02 cyclops postfix/smtpd[19251]: disconnect from
>     localhost[127.0.0.1]
>     Aug 12 06:12:02 cyclops postfix/qmgr[2967]: EBAE7214DF2: from=<>,
>     size=2340, nrcpt=1 (queue active)
>     Aug 12 06:12:02 cyclops postfix/smtpd[19248]: 0B354214DF4:
>     client=localhost[127.0.0.1]
>     Aug 12 06:12:02 cyclops postfix/cleanup[19252]: 0B354214DF4:
>     message-id=<be1a01c7dca5$f0d405d0$0fff6d29@fredcoxaaxue>
>     Aug 12 06:12:02 cyclops postfix/local[19253]: EBAE7214DF2:
>     to=<fetchmail@localserver>, orig_to=<fetchmail>, relay=local,
>     delay=0.13, delays=0.1/0.01/0/0.02, dsn=2.0.0, status=sent
>     (delivered to maildir)

Bounce message delivered to the account "fetchmail"

> Where are those bouncemessage sent to? Or how could I have noticed this
> earlier?

They're delivered to the "fetchmail" user (the one running fetchmail).
 You could have noticed this earlier by monitoring that account's
email :)  Easiest approach is probably to alias that to the postmaster
address, which you should also be monitoring.

> The old mails are lost, I presume?

Depends on what was in the bounce - I haven't seen a fetchmail bounce
so I can't say.  If fetchmail is only providing the minimal "Your
message titled X could not be delivered" then you're out of luck.

-- 
                 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] Recipient address rejected: User unknown in local recipient table

[Johan V. <fet...@bo...>]

Rob MacGregor wrote:
> On 8/15/07, Johan Vandeweerd <fet...@bo...> wrote:
>   
>> Hello all,
>>
>> At the beginning of this month I changed the username of one of my users
>> but I forgot to change the corresponding username in the fetchmailrc
>> config (so the username in the fetchmailrc config didn't exist anymore).
>> For the last month fetchmail has been fetching my mails but didn't found
>> a  user on the local system (errormsg see title).
>> What did fetchmail do with these mails (they are not on the server)? Are
>> they stored somewhere or did I loose all the mails?
>>     
>
> It depends on a lot of things you haven't told us, not least of which
> is the configuration of fetchmail and whatever SMTP server you are
> running.
>
> I would expect that, by default, your SMTP server returned a "no such
> user" type error and fetchmail generated bounce message (as detailed
> in the FAQ), deleting the message from the remote POP/IMAP server.  If
> you consult your mail log it should tell you.
>
>   
I use postfix and courier.

My fetchmailrc looks like this:

    set no bouncemail
    set daemon 600
    defaults:
      antispam -1
      batchlimit 100

    poll pluto.sygmanet.be with protocol pop3 user "myemail" there with
    password "mypassword" is myusername here

In the logs I find things like this:

    Aug 12 06:12:01 cyclops fetchmail[3067]: awakened at Sun 12 Aug 2007
    06:12:01 AM CEST
    Aug 12 06:12:01 cyclops fetchmail[3067]: Server certificate
    verification error: self signed certificate
    Aug 12 06:12:01 cyclops fetchmail[3067]: Server certificate
    verification error: certificate has expired
    Aug 12 06:12:01 cyclops fetchmail[3067]: 1 message for
    myemailaddress at remoteserver (20949 octets).
    Aug 12 06:12:01 cyclops postfix/smtpd[19248]: connect from
    localhost[127.0.0.1]
    Aug 12 06:12:01 cyclops postfix/smtpd[19248]: NOQUEUE: reject: RCPT
    from localhost[127.0.0.1]: 550 5.1.1 <oldusername@localhost>:
    Recipient address rejected: User unknown in local recipient table;
    from=<fre...@uc...> to=<oldusername@localhost>
    proto=ESMTP helo=<localserver>
    Aug 12 06:12:01 cyclops fetchmail[3067]: reading message
    remoteusername@remoteserver:1 of 1 (20949 octets) (log message
    incomplete)
    Aug 12 06:12:01 cyclops fetchmail[3067]: SMTP error: 550 5.1.1
    <oldusername@localhost>: Recipient address rejected: User unknown in
    local recipient table
    Aug 12 06:12:01 cyclops postfix/smtpd[19251]: connect from
    localhost[127.0.0.1]
    Aug 12 06:12:01 cyclops postfix/smtpd[19251]: EBAE7214DF2:
    client=localhost[127.0.0.1]
    Aug 12 06:12:01 cyclops fetchmail[3067]: mail from
    MAILER-DAEMON@localserver bounced to fetchmail
    Aug 12 06:12:02 cyclops postfix/cleanup[19252]: EBAE7214DF2:
    message-id=<20070812041201.EBAE7214DF2@localserver>
    Aug 12 06:12:02 cyclops postfix/smtpd[19251]: disconnect from
    localhost[127.0.0.1]
    Aug 12 06:12:02 cyclops postfix/qmgr[2967]: EBAE7214DF2: from=<>,
    size=2340, nrcpt=1 (queue active)
    Aug 12 06:12:02 cyclops postfix/smtpd[19248]: 0B354214DF4:
    client=localhost[127.0.0.1]
    Aug 12 06:12:02 cyclops postfix/cleanup[19252]: 0B354214DF4:
    message-id=<be1a01c7dca5$f0d405d0$0fff6d29@fredcoxaaxue>
    Aug 12 06:12:02 cyclops postfix/local[19253]: EBAE7214DF2:
    to=<fetchmail@localserver>, orig_to=<fetchmail>, relay=local,
    delay=0.13, delays=0.1/0.01/0/0.02, dsn=2.0.0, status=sent
    (delivered to maildir)
    Aug 12 06:12:02 cyclops postfix/qmgr[2967]: EBAE7214DF2: removed
    Aug 12 06:12:02 cyclops postfix/qmgr[2967]: 0B354214DF4:
    from=<fre...@uc...>, size=21319, nrcpt=1 (queue active)
    Aug 12 06:12:02 cyclops fetchmail[3067]:  flushed
    Aug 12 06:12:02 cyclops postfix/local[19253]: 0B354214DF4:
    to=<fetchmail@localhost>, relay=local, delay=0.17,
    delays=0.17/0/0/0, dsn=2.0.0, status=sent (delivered to maildir)
    Aug 12 06:12:02 cyclops postfix/qmgr[2967]: 0B354214DF4: removed

Where are those bouncemessage sent to? Or how could I have noticed this 
earlier? The old mails are lost, I presume?

Thanks
Johan Vandeweerd

Re: [fetchmail-users] Recipient address rejected: User unknown in local recipient table

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

On 8/15/07, Johan Vandeweerd <fet...@bo...> wrote:
> Hello all,
>
> At the beginning of this month I changed the username of one of my users
> but I forgot to change the corresponding username in the fetchmailrc
> config (so the username in the fetchmailrc config didn't exist anymore).
> For the last month fetchmail has been fetching my mails but didn't found
> a  user on the local system (errormsg see title).
> What did fetchmail do with these mails (they are not on the server)? Are
> they stored somewhere or did I loose all the mails?

It depends on a lot of things you haven't told us, not least of which
is the configuration of fetchmail and whatever SMTP server you are
running.

I would expect that, by default, your SMTP server returned a "no such
user" type error and fetchmail generated bounce message (as detailed
in the FAQ), deleting the message from the remote POP/IMAP server.  If
you consult your mail log it should tell you.

-- 
                 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] Recipient address rejected: User unknown in local recipient table

[Johan V. <fet...@bo...>]

Hello all,

At the beginning of this month I changed the username of one of my users 
but I forgot to change the corresponding username in the fetchmailrc 
config (so the username in the fetchmailrc config didn't exist anymore). 
For the last month fetchmail has been fetching my mails but didn't found 
a  user on the local system (errormsg see title).
What did fetchmail do with these mails (they are not on the server)? Are 
they stored somewhere or did I loose all the mails?

Thanks in advance,
Johan Vandeweerd

Re: [fetchmail-users] Problem Plz solve it

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

Please contact the fetchmail-users mailing list (CCd) if you want free
assistance.  Personal direct help is charged at £100/email - PayPal
accepted :)

On 8/11/07, Ritesh Yeole <rit...@gm...> wrote:
> Dear Sir ,
>    I fetch the following problem ,I use fedora core  4,
> Please see it
>
> fetchmail: POP3> CAPA
> fetchmail: POP3< +OK Capability list follows:
> fetchmail: POP3< TOP
> fetchmail: POP3< LOGIN-DELAY 180
> fetchmail: POP3< UIDL
> fetchmail: POP3< USER
> fetchmail: POP3< SASL PLAIN LOGIN
> fetchmail: POP3< .
> fetchmail: POP3> USER su...@th...
> fetchmail: POP3< +OK User name accepted, password please
> fetchmail: POP3> PASS *
> fetchmail: POP3< +OK Mailbox open, 75 messages
> fetchmail: POP3> STAT
> fetchmail: POP3< +OK 75 2129188
> fetchmail: POP3> LAST
> fetchmail: POP3< +OK 75
> fetchmail: 75 messages (75 seen) for su...@th... at
> mail.thenetworkelements.com (2129188 octets).
> fetchmail: skipping message
> su...@th...@mail.thenetworkelements.com:1
> not flushed
> fetchmail: skipping message
> su...@th...@mail.thenetworkelements.com:2
> not flushed
> fetchmail: skipping message
> su...@th...@mail.thenetworkelements.com:3
> not flushed

And when you do contact the list, you'll want to provide the
information specified in the FAQ as well as mention what you think the
problem is.

-- 
                 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] daemon not cycling as expected.

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

On 8/8/07, Joe acquisto <jo...@j4...> wrote:
>
> I think I get that.  But, I tend not to do anything on the command line, (I forget various syntax, etc).  About all I would do is fetchmail --quit and then restart.
>
> So, if I do that, assuming I have not touched anything since last cold start, anything in the config file should be in effect?.

Yes - in order of increasing preference the arguments used are:

1) Defaults
2) Config file
3) Command line

If you don't specify anything on the command line then the contents of
the config file will be used.

> My startup script is in (being SUSE) /etc/init.d/rc5.d/S97fetcmail (and /etc/init.d/rc3.d/S97etchmnail, symbolic links, actually).
>
> Is there any way to make those (that) read the config file, instead of using what is entered there?  Without a major re-write.  Or should I just be content with having hacked about to make them have the same values?  As far as I can tell.

No.  If it's specified on the command line it over-rides the
configuration file.  The only way to avoid this is to not specify it
on the command line - in this case by editing the startup script.

-- 
                 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] daemon not cycling as expected.

[Joe a. <jo...@j4...>]

>>> On 8/8/2007 at 4:40 PM, "Rob MacGregor" <rob...@gm...> wrote:
> On 8/8/07, Joe acquisto <jo...@j4...> wrote:
>> Never mind, I think.  I found that my init script (startup scripts) said 600 
> seconds.  I guess I forgot that it does not read fetchmailrc when started 
> that way.
>>
>> Is that correct?
> 
> Not quite - anything you put on the command line over-rules the same
> setting in the config file.

I think I get that.  But, I tend not to do anything on the command line, (I forget various syntax, etc).  About all I would do is fetchmail --quit and then restart.

So, if I do that, assuming I have not touched anything since last cold start, anything in the config file should be in effect?.

My startup script is in (being SUSE) /etc/init.d/rc5.d/S97fetcmail (and /etc/init.d/rc3.d/S97etchmnail, symbolic links, actually).

Is there any way to make those (that) read the config file, instead of using what is entered there?  Without a major re-write.  Or should I just be content with having hacked about to make them have the same values?  As far as I can tell.

joe a.

Re: [fetchmail-users] daemon not cycling as expected.

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

On 8/8/07, Joe acquisto <jo...@j4...> wrote:
> Never mind, I think.  I found that my init script (startup scripts) said 600 seconds.  I guess I forgot that it does not read fetchmailrc when started that way.
>
> Is that correct?

Not quite - anything you put on the command line over-rules the same
setting in the 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

Re: [fetchmail-users] daemon not cycling as expected.

[Joe a. <jo...@j4...>]

Never mind, I think.  I found that my init script (startup scripts) said 600 seconds.  I guess I forgot that it does not read fetchmailrc when started that way.

Is that correct?

joe a.

>>> On 8/8/2007 at 4:20 PM, Joe acquisto wrote:
> Running in daemon mode, awakens every 10 minutes rather than every two as I 
> had intended.
> 
> fetchmailrc says "set daemon 120".  Is that not where I set the awaken time?
> 
> joe a.
> 

[fetchmail-users] daemon not cycling as expected.

[Joe a. <jo...@j4...>]

Running in daemon mode, awakens every 10 minutes rather than every two as I had intended.

fetchmailrc says "set daemon 120".  Is that not where I set the awaken time?

joe a.

Re: [fetchmail-users] Problem using fetchmail in combination with procmail!

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

On 8/6/07, Josef.Fuchs <jos...@j-...> wrote:
> Hello!
>
> I'm using fetchmail to retrieve mails from a pop3 account which until now is
> used with an alias address by two persons. Now I've tried to use fetchmail
> for user A and use procmail to distribute the mails which got sent to the
> alias address to user B on my mailserver.
>
> It seems that procmail isn't active during insertion of mails using
> fetchmail.

That depends on your configuration, which you haven't given - not even
the version of fetchmail you're using.

> Have you any hints what to do to get this working.

Well, you could look at the fetchmail man page under the section
"Multidrop" :)  Of course, this assumes that your ISP provides the
required headers.

If you want any more help you'll need to:

1) Ensure you're running fetchmail 6.3.8
2) Provide a copy of your .fetchmailrc
3) Provide a copy of the headers for a 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

[fetchmail-users] Problem using fetchmail in combination with procmail!

[Josef.Fuchs <jos...@j-...>]

Hello!

I'm using fetchmail to retrieve mails from a pop3 account which until now is
used with an alias address by two persons. Now I've tried to use fetchmail
for user A and use procmail to distribute the mails which got sent to the
alias address to user B on my mailserver.

It seems that procmail isn't active during insertion of mails using
fetchmail. 

Have you any hints what to do to get this working.

Kind regards
Josef