fetchmail-users — User questions and discussion

Re: [fetchmail-users] message...was not the expected length...not flushed

[Otto R. (AP-SGP) <ot...@ap...>]

Hi Matthias,

Thanks for your reply. From your reply, it would imply that fetchmail 
would flush or delete these email - however it doesn't. After about a 
month, I'll have quite a number of these mails on the ISP's server and 
on each fetchmail run (it runs ever 10 minutes in cron) i would see a 
lot of these SAME unflushed emails (as per the log on on first email). 
Am I using the wrong parameter or am I missing a parameter? I am willing 
to take the risk and consequences if there is a parameter in fetchmail 
that will FORCE-DELETE or FLUSH these emails.

I ran my fetchmail manually and it download 58 emails of which 9 were 
faulty and not flushed (as per the log).
I then ran fetchmail again within seconds of the first on finishing and 
indeed there were only 9 messages on the server and again it did not flush.
I then ran fetchmail again for a third time within seconds of the second 
run, and the same 9 messages were still on the server - i just couldn't 
get fetchmail to "flush" or delete these emails.

Any help is much appreciated. Rgds. Otto.

Matthias Andree wrote:
> Otto Rodusek schrieb am 2007-02-02:
>
>   
>> I am doing a fetchmail from my ISP to my local server with the following 
>> command: 
>>
>> fetchmail -K -F -f /menu/fetchmailrc  where fetchmailrc is 
>>
>> poll mail.sg.gs protocol pop3 username ro...@aa... password SECRET to 
>> ro...@aa... 
>>
>> My ISP's email server is using QMAIL. 
>>     
>
> The qmail pop server has been known for a while to miscalculate message
> lenghts, violating RFC-1939, but you can't bother DJB to fix this...
> http://home.pages.de/~mandree/qmail-bugs.html section 3.4
>
>   
>> Fetchmail works just fine, however often times it DOES NOT delete the read 
>> message on the ISP's side (in each case it is definitely a JUNK mails) as 
>> per the log file below. I understand the problem and I have read the part 
>> about fetchmail/qmail however - 
>>     
>
> Tell the ISP not to accept junk mail.
>
>   
>> IS ther ANY WAY for have fetchmail FORCE-DELETE these emails of the ISP 
>> server?? 
>>     
>
> Yes, but as Rob correctly states, that way would endanger your
> legitimate mail.
>
>   
>> fetchmail: SMTP> MAIL FROM:<egt...@sc...>
>> fetchmail: SMTP< 451 DNS temporary failure (#4.3.0)
>>     
>
> DNS problem or the upstream should not accept messages from unresolvable
> domains. This prevents flushing your messages.
>
>   
>> fetchmail: SMTP> RSET
>> fetchmail: SMTP< 250 flushed
>> fetchmail: message ro...@aa....@mail.sg.gs:3 was not the expected length 
>> (17967 actual != 17679 expected)
>>     
>
> Not related to your problem (fetchmail only reports this for your
> information, but it's nothing more; fetchmail pretends this problem
> hadn't existed after it's reported it.)
>
>   

Re: [fetchmail-users] message...was not the expected length...not flushed

[Otto R. (AP-SGP) <ot...@ap...>]

Hi Rob,

Thanks for the reply. I agree about the 451 error and other things about 
fetchmail being conservative. I have been monitoring the situation for 
quite some time and in EACH case it happens that the faulty emails are 
spam. So the question again is - is there ANY WAY at all to get 
fetchmail to FORCE-DELETE these emails. I'm willing to take the risk and 
have tried various parameters but to no avail (I use the -F to flush but 
as you can see from the log it doesn't. Any ideas are welcome. Thanks. 
Rgds. Otto.

Rob MacGregor wrote:
> On 2/2/07, Otto Rodusek <ot...@ap...> wrote:
>   
>> Hi,
>>
>> I am using fetchmail 6.3.5-13 under Suse 10.2 (kernel  2.6.18.2-34-default).
>>     
>
> 6.3.6 came out recently, though it won't help here you should upgrade.
>
>   
>> Fetchmail works just fine, however often times it DOES NOT delete the read
>> message on the ISP's side (in each case it is definitely a JUNK mails) as
>> per the log file below. I understand the problem and I have read the part
>> about fetchmail/qmail however -
>>
>> IS ther ANY WAY for have fetchmail FORCE-DELETE these emails of the ISP
>> server??
>>     
> <---SNIP--->
>   
>> fetchmail: SMTP< 451 DNS temporary failure (#4.3.0)
>>     
>
> That is the actual problem I suspect - a temporary DNS failure.  You
> could risk using the 451 code as an anti-spam code to flush the
> emails, but if you do that you risk also dropping valid email.
>
> Fetchmail is always conservative about these things for good reason :)
>
>   

Re: [fetchmail-users] message...was not the expected length...not flushed

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

Otto Rodusek schrieb am 2007-02-02:

> I am doing a fetchmail from my ISP to my local server with the following 
> command: 
> 
> fetchmail -K -F -f /menu/fetchmailrc  where fetchmailrc is 
> 
> poll mail.sg.gs protocol pop3 username ro...@aa... password SECRET to 
> ro...@aa... 
> 
> My ISP's email server is using QMAIL. 

The qmail pop server has been known for a while to miscalculate message
lenghts, violating RFC-1939, but you can't bother DJB to fix this...
http://home.pages.de/~mandree/qmail-bugs.html section 3.4

> Fetchmail works just fine, however often times it DOES NOT delete the read 
> message on the ISP's side (in each case it is definitely a JUNK mails) as 
> per the log file below. I understand the problem and I have read the part 
> about fetchmail/qmail however - 

Tell the ISP not to accept junk mail.

> IS ther ANY WAY for have fetchmail FORCE-DELETE these emails of the ISP 
> server?? 

Yes, but as Rob correctly states, that way would endanger your
legitimate mail.

> fetchmail: SMTP> MAIL FROM:<egt...@sc...>
> fetchmail: SMTP< 451 DNS temporary failure (#4.3.0)

DNS problem or the upstream should not accept messages from unresolvable
domains. This prevents flushing your messages.

> fetchmail: SMTP> RSET
> fetchmail: SMTP< 250 flushed
> fetchmail: message ro...@aa....@mail.sg.gs:3 was not the expected length 
> (17967 actual != 17679 expected)

Not related to your problem (fetchmail only reports this for your
information, but it's nothing more; fetchmail pretends this problem
hadn't existed after it's reported it.)

-- 
Matthias Andree

Re: [fetchmail-users] message...was not the expected length...not flushed

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

On 2/2/07, Otto Rodusek <ot...@ap...> wrote:
> Hi,
>
> I am using fetchmail 6.3.5-13 under Suse 10.2 (kernel  2.6.18.2-34-default).

6.3.6 came out recently, though it won't help here you should upgrade.

> Fetchmail works just fine, however often times it DOES NOT delete the read
> message on the ISP's side (in each case it is definitely a JUNK mails) as
> per the log file below. I understand the problem and I have read the part
> about fetchmail/qmail however -
>
> IS ther ANY WAY for have fetchmail FORCE-DELETE these emails of the ISP
> server??
<---SNIP--->
> fetchmail: SMTP< 451 DNS temporary failure (#4.3.0)

That is the actual problem I suspect - a temporary DNS failure.  You
could risk using the 451 code as an anti-spam code to flush the
emails, but if you do that you risk also dropping valid email.

Fetchmail is always conservative about these things for good reason :)

-- 
                 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] message...was not the expected length...not flushed

[Otto R. <ot...@ap...>]

Hi, 

I'm new to this list so if this topic was previously covered - I do 
apologize in advance. 

I am using fetchmail 6.3.5-13 under Suse 10.2 (kernel  2.6.18.2-34-default). 

I am doing a fetchmail from my ISP to my local server with the following 
command: 

fetchmail -K -F -f /menu/fetchmailrc  where fetchmailrc is 

poll mail.sg.gs protocol pop3 username ro...@aa... password SECRET to 
ro...@aa... 

My ISP's email server is using QMAIL. 

Fetchmail works just fine, however often times it DOES NOT delete the read 
message on the ISP's side (in each case it is definitely a JUNK mails) as 
per the log file below. I understand the problem and I have read the part 
about fetchmail/qmail however - 

IS ther ANY WAY for have fetchmail FORCE-DELETE these emails of the ISP 
server?? 

Thanks and rgds. Otto. 

Fetchmail log: (I have blanked out some fields)
============== 

<snip>...
fetchmail: POP3> RETR 3
fetchmail: POP3< +OK
reading message ro...@aa...@mail.sg.gs:3 of 13 (17679 octets)
About to rewrite Return-Path: <egt...@sc...>
Rewritten version is Return-Path: <egt...@sc...> 

About to rewrite From: patch to <egt...@sc...>
Rewritten version is From: patch to <egt...@sc...> 

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

fetchmail: forwarding to localhost
fetchmail: SMTP> MAIL FROM:<egt...@sc...>
fetchmail: SMTP< 451 DNS temporary failure (#4.3.0)
fetchmail: SMTP> RSET
fetchmail: SMTP< 250 flushed
fetchmail: message ro...@aa....@mail.sg.gs:3 was not the expected length 
(17967 actual != 17679 expected)
not flushed 

Re: [fetchmail-users] suppress email warnings

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

On 1/28/07, jason farnon <jas...@ya...> wrote:
> I had a quick question that I can't find an answer to in the faq/man--how do
> I suppress email notification of the warning,
>
> fetchmail: Avertissement: appeler fetchmail avec privilèges root est
> déconseille.
>
> which is given for running fetchmail as root? I've run it in debian as a
> scheduled task with "fetchmail -sak" in my crontab. So I get a warning msg
> every 10 minutes. Maybe the answer to this question will answer my next
> one--any idea what I could have done to start this, I didn't think I changed
> anything relevant to my fetchmail setup when the issue started (though as
> you can see I tend to hang around as root a lot so I easily could've dont it
> inadvertantly). Thanks.

Easy, don't start it as root (newer versions of fetchmail warn about
this, future versions may simply refuse to run).

There is absolutely no need to run fetchmail as root - nothing in it
requires it.  Create an unpriviledged user and run it as that user.

-- 
                 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] suppress email warnings

[jason f. <jas...@ya...>]

I had a quick question that I can't find an answer to in the faq/man--how do I suppress email notification of the warning,

fetchmail: Avertissement: appeler fetchmail avec privilèges root est déconseille.

which is given for running fetchmail as root? I've run it in debian as a scheduled task with "fetchmail -sak" in my crontab. So I get a warning msg every 10 minutes. Maybe the answer to this question will answer my next one--any idea what I could have done to start this, I didn't think I changed anything relevant to my fetchmail setup when the issue started (though as you can see I tend to hang around as root a lot so I easily could've dont it inadvertantly). Thanks.

 		
---------------------------------
 Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses.

Re: [fetchmail-users] Fetchmail in Singledrop-mode trying to send mail

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

On 1/25/07, Eddie <st...@at...> wrote:
>
> OK, I guess it was my misunderstanding of exactly how sendmail works.  :-(
>
> I'd assumed that fetchmail would direct all mail, regardless, to my inbox,
> which I now realise it is.

Fetchmail directs all email to your SMTP server, not your inbox (to be picky).

> What I didn't know, was that even though sendmail
> *is* trying to deliver it locally, it still validates the sender domain.  So,
> it was a validation that failed, not an attempt at sending that failed.

You can disable that check (see cf/README -
accept_unresolvable_domains), however given that almost all mail with
an unresolvable sender domain is spam, you're not likely to benefit
from it.

-- 
                 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 in Singledrop-mode trying to send mail

[Eddie <st...@at...>]

On Thursday 25 January 2007 12:28, Rob MacGregor wrote:
> On 1/25/07, Eddie <st...@at...> wrote:
> > I've been running some tests, for about 3 days now, using fetchmail, in
> > daemon mode, to pull my mail down from a POP server every 10 minutes, and
> > then pass it off to procmail.  As far as I can make out, reading the man
> > pages, I am running in singledrop-mode.  This appears to work fine,
> > except on one or two e-mails, I got the following error:
> >
> > Jan 24 11:51:23 The-Tardis sm-mta[22324]: l0OJpNXo022324:
> > ruleset=check_mail, arg1=<ke...@la...""chantelfisher"
> > ame...@sh...">,
> > relay=localhost [127.0.0.1], reject=553 5.1.8
> > <ke...@la...""chantelfisher" ame...@sh...">... Domain of
> > sender address ke...@la...chantelfisher ame...@sh... does
> > not exist
>
> Sendmail generates a permanent failure as the sender's address doesn't
> resolve.
>
> > Jan 24 11:51:23 The-Tardis fetchmail[22142]: SMTP error: 553 5.1.8
> > <ke...@la...""chantelfisher" ame...@sh...">... Domain of
> > sender address ke...@la...chantelfisher ame...@sh... does
> > not exist Jan 24 11:51:23 The-Tardis sm-mta[22324]: l0OJpNXo022324:
> > from=<ke...@la...""chantelfisher" ame...@sh...">,
> > size=2187, class=0, nrcpts=0, proto=ESMTP, daemon=MTA, relay=localhost
> > [127.0.0.1] Jan 24 11:51:23 The-Tardis fetchmail[22142]:  flushed
>
> Fetchmail drops it on the floor, as per the man page (see SMTP/ESMTP
> ERROR HANDLING).
>
> > In this snippet, 2 messages were retrieved from the server.  For the
> > first one, it looks like sendmail tried to deliver the mail, and failed,
> > instead of putting it into the mailbox for eddie.
>
> I fail to see the problem.  Sendmail is doing what you've told it to -
> rejecting emails with a sender domain that doesn't resolve.  Fetchmail
> is doing what it's supposed to - dropping emails that the SMTP server
> rejects with an error code of 553.

OK, I guess it was my misunderstanding of exactly how sendmail works.  :-(

I'd assumed that fetchmail would direct all mail, regardless, to my inbox, 
which I now realise it is.  What I didn't know, was that even though sendmail 
*is* trying to deliver it locally, it still validates the sender domain.  So, 
it was a validation that failed, not an attempt at sending that failed.

Thanks for the explanation.

--
Cheers

Re: [fetchmail-users] Fetchmail in Singledrop-mode trying to send mail

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

On 1/25/07, Eddie <st...@at...> wrote:
> I've been running some tests, for about 3 days now, using fetchmail, in daemon
> mode, to pull my mail down from a POP server every 10 minutes, and then pass
> it off to procmail.  As far as I can make out, reading the man pages, I am
> running in singledrop-mode.  This appears to work fine, except on one or two
> e-mails, I got the following error:
>
> Jan 24 11:51:23 The-Tardis sm-mta[22324]: l0OJpNXo022324: ruleset=check_mail,
> arg1=<ke...@la...""chantelfisher" ame...@sh...">,
> relay=localhost [127.0.0.1], reject=553 5.1.8
> <ke...@la...""chantelfisher" ame...@sh...">... Domain of sender
> address ke...@la...chantelfisher ame...@sh... does not exist

Sendmail generates a permanent failure as the sender's address doesn't resolve.

> Jan 24 11:51:23 The-Tardis fetchmail[22142]: SMTP error: 553 5.1.8
> <ke...@la...""chantelfisher" ame...@sh...">... Domain of sender
> address ke...@la...chantelfisher ame...@sh... does not exist
> Jan 24 11:51:23 The-Tardis sm-mta[22324]: l0OJpNXo022324:
> from=<ke...@la...""chantelfisher" ame...@sh...">, size=2187,
> class=0, nrcpts=0, proto=ESMTP, daemon=MTA, relay=localhost [127.0.0.1]
> Jan 24 11:51:23 The-Tardis fetchmail[22142]:  flushed

Fetchmail drops it on the floor, as per the man page (see SMTP/ESMTP
ERROR HANDLING).

> In this snippet, 2 messages were retrieved from the server.  For the first
> one, it looks like sendmail tried to deliver the mail, and failed, instead of
> putting it into the mailbox for eddie.

I fail to see the problem.  Sendmail is doing what you've told it to -
rejecting emails with a sender domain that doesn't resolve.  Fetchmail
is doing what it's supposed to - dropping emails that the SMTP server
rejects with an error code of 553.

-- 
                 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 in Singledrop-mode trying to send mail

[Eddie <st...@at...>]

I've been running some tests, for about 3 days now, using fetchmail, in daemon 
mode, to pull my mail down from a POP server every 10 minutes, and then pass 
it off to procmail.  As far as I can make out, reading the man pages, I am 
running in singledrop-mode.  This appears to work fine, except on one or two 
e-mails, I got the following error:

Jan 24 11:51:22 The-Tardis fetchmail[22142]: awakened at Wed 24 Jan 2007 
11:51:22 AM PST
Jan 24 11:51:23 The-Tardis fetchmail[22142]: 2 messages for xxxxxxxx at 
pop5.xxxxxxxx.net (3345 octets).
Jan 24 11:51:23 The-Tardis fetchmail[22142]: reading message 
xxx...@po...:1 of 2 (2187 octets)
Jan 24 11:51:23 The-Tardis sm-mta[22324]: l0OJpNXo022324: ruleset=check_mail, 
arg1=<ke...@la...""chantelfisher" ame...@sh...">, 
relay=localhost [127.0.0.1], reject=553 5.1.8 
<ke...@la...""chantelfisher" ame...@sh...">... Domain of sender 
address ke...@la...chantelfisher ame...@sh... does not exist
Jan 24 11:51:23 The-Tardis fetchmail[22142]: SMTP error: 553 5.1.8 
<ke...@la...""chantelfisher" ame...@sh...">... Domain of sender 
address ke...@la...chantelfisher ame...@sh... does not exist
Jan 24 11:51:23 The-Tardis sm-mta[22324]: l0OJpNXo022324: 
from=<ke...@la...""chantelfisher" ame...@sh...">, size=2187, 
class=0, nrcpts=0, proto=ESMTP, daemon=MTA, relay=localhost [127.0.0.1]
Jan 24 11:51:23 The-Tardis fetchmail[22142]:  flushed
Jan 24 11:51:23 The-Tardis fetchmail[22142]: reading message 
xxx...@po...:2 of 2 (1158 octets)
Jan 24 11:51:24 The-Tardis sm-mta[22324]: l0OJpNXp022324: 
from=<To...@li...>, size=1309, class=0, nrcpts=1, 
msgid=<200...@Th...>, bodytype=7BIT, 
proto=ESMTP, daemon=MTA, relay=localhost [127.0.0.1]
Jan 24 11:51:24 The-Tardis fetchmail[22142]:  flushed
Jan 24 11:51:24 The-Tardis fetchmail[22142]: sleeping at Wed 24 Jan 2007 
11:51:24 AM PST
Jan 24 11:51:42 The-Tardis sm-mta[22325]: l0OJpNXp022324: 
to=<eddie@localhost>, delay=00:00:19, xdelay=00:00:18, mailer=local, 
pri=31584, dsn=2.0.0, stat=Sent

In this snippet, 2 messages were retrieved from the server.  For the first 
one, it looks like sendmail tried to deliver the mail, and failed, instead of 
putting it into the mailbox for eddie.

The 2nd message was hadled correctly, in the same way every other message has 
been.

Here's the .fetchmailrc contents:

set daemon 600
set syslog
poll pop5.xxxxxxxx.net proto pop3 user "xxxxxxxx" pass xxxxxxxx

The user in .fetchmailrc is *not* the same as the user, eddie, that runs this 
process.

So, why, if I'm running in singledrop-mode was that one message treated as if 
I am running multidrop-mode, and should I be concerned about this.

Incoming port 25 is blocked by my firewall, so not "outside" smtp servers can 
talk to my sendmail.  

Cheers.

Re: [fetchmail-users] Fetchmail to Postfix

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

"Support @ Smart Networking" <su...@ma...> writes:

> Im finding it hard to decide which is the best solution to use. 
> It looks like copies of emails could potentially either disapear into the etha or even worse be delivered to a user which should not even receive them
> eg. Bcc
> What is the best solution ?

Not using catchall mailboxes, and using an ISP who has a clue about
setting up catchall mailboxes properly, i. e. in a way that DOES NOT
lose Bcc recipients. Details in the URL I posted earlier.

Oh, and do fix your quoting and do not post junk - it's awful to read,
threading is broken, unreadable and everything. I'm not going too look
at this thread any more. Sorry.

<URL:http://www.netmeister.org/news/learn2quote.html>
<URL:http://www.expita.com/nomime.html>

-- 
Matthias Andree

Re: [fetchmail-users] Fetchmail to Postfix

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

On 1/7/07, Support @ Smart Networking <su...@ma...> wrote:
> Fetchmail Version        ----------------------------------------
>
> Fetchmail version 6.2.5+POP2+RPA+NTLM+SDPS+SSL+OPIE+NLS  (SLES 9)

Ok, stop, upgrade to the current version (6.3.6) and repeat the run of
fetchmail.

> poll pop3.mailforyou.co.uk
>      proto pop3
>     envelope "Delivered-To"
>     user remoteusername with password remotepassword to * here

Should be fine.

> fetchmail: SMTP> MAIL FROM:<su...@ma...> SIZE=1721
> fetchmail: SMTP< 250 Ok
> fetchmail: SMTP> RCPT TO:<postmaster@localhost>
> fetchmail: SMTP< 250 Ok

Need to see the email headers for that 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

Re: [fetchmail-users] Fetchmail to Postfix

[Support @ S. N. <su...@ma...>]

Fetchmail Version        ----------------------------------------

Fetchmail version 6.2.5+POP2+RPA+NTLM+SDPS+SSL+OPIE+NLS  (SLES 9)

.fetchmail                     ----------------------------------------

poll pop3.mailforyou.co.uk
     proto pop3
    envelope "Delivered-To"
    user remoteusername with password remotepassword to * here

Output                            ----------------------------------------

fetchmail: 6.2.5 querying pop3.mailforyou.co.uk (protocol POP3) at Sun Jan 
7 11 
:02:08 2007: poll started
fetchmail: POP3< +OK barracuda Cyrus POP3 v2.2.3 server ready 
<43452629314471556 
53.1168167727@barracuda>
fetchmail: POP3> CAPA
fetchmail: POP3< +OK List of capabilities follows
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.3
fetchmail: POP3< .
fetchmail: POP3> USER username
fetchmail: POP3< +OK Name is a valid mailbox
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Mailbox locked and ready
fetchmail: POP3> STAT
fetchmail: POP3< +OK 1 1721
fetchmail: POP3> LAST
fetchmail: POP3< -ERR Unrecognized command  <-------------------this dosent 
look good lol!
fetchmail: Unrecognized command
fetchmail: POP3> UIDL
fetchmail: POP3< +OK unique-id listing follows
fetchmail: POP3< 1 1168033347.4
fetchmail: POP3< .
1 message for cladceil at pop3.mailforyou.co.uk (1721 octets).
fetchmail: POP3> LIST 1
fetchmail: POP3< +OK 1 1721
fetchmail: POP3> TOP 1 99999999
fetchmail: POP3< +OK Message follows
reading message us...@po...:1 of 1 (1721 octets)
fetchmail: SMTP< 220 server.fqdomainnameofserver
fetchmail: SMTP> EHLO localhost
fetchmail: SMTP< 250-server.fqdomainnameofserver
fetchmail: SMTP< 250-PIPELINING
fetchmail: SMTP< 250-SIZE 83886080
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: SMTP> MAIL FROM:<su...@ma...> SIZE=1721
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: SMTP>. (EOM)
fetchmail: SMTP< 250 Ok: queued as 005DC62E02
 flushed
fetchmail: POP3> DELE 1
fetchmail: POP3< +OK message deleted
fetchmail: POP3> QUIT
fetchmail: POP3< +OK
fetchmail: 6.2.5 querying pop3.mailforyou.co.uk (protocol POP3) at Sun Jan 
7 11 
:02:12 2007: poll completed
fetchmail: SMTP> QUIT
fetchmail: SMTP< 221 Bye
fetchmail: normal termination, status 0


----- Original Message ----- 
From: "Rob MacGregor" <rob...@gm...>
To: <fet...@li...>
Sent: Sunday, January 07, 2007 11:11 AM
Subject: Re: [fetchmail-users] Fetchmail to Postfix


> On 1/7/07, Support @ Smart Networking <su...@ma...> wrote:
>> Thank you for your quick response.
>>
>> It still dosent seem to work quite right. Fetchmail downloads the emails 
>> but
>> then tries to deliver them to postmaster@localhost.fqdomain instead of 
>> the
>> corresponding user/email address :(
>
> Right, so how about some of the info the FAQ tells you to provide.  At
> an absolute minimum:
>
> 1) Version of fetchmail
>
> 2) Contents of .fetchmailrc
>
> 3) Output of "fetchmail -v -v -v" showing the problem
>
> -- 
>                 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
>
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>
> 


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Re: [fetchmail-users] Fetchmail to Postfix

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

On 1/7/07, Support @ Smart Networking <su...@ma...> wrote:
> Thank you for your quick response.
>
> It still dosent seem to work quite right. Fetchmail downloads the emails but
> then tries to deliver them to postmaster@localhost.fqdomain instead of the
> corresponding user/email address :(

Right, so how about some of the info the FAQ tells you to provide.  At
an absolute minimum:

1) Version of fetchmail

2) Contents of .fetchmailrc

3) Output of "fetchmail -v -v -v" showing the problem

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

[Support @ S. N. <su...@ma...>]

Thank you for your quick response.

It still dosent seem to work quite right. Fetchmail downloads the emails but 
then tries to deliver them to postmaster@localhost.fqdomain instead of the 
corresponding user/email address :(

Kind Regards

Phil


----- Original Message ----- 
From: "Rob MacGregor" <rob...@gm...>
To: <fet...@li...>
Sent: Sunday, January 07, 2007 9:41 AM
Subject: Re: [fetchmail-users] Fetchmail to Postfix


> On 1/6/07, Support @ Smart Networking <su...@ma...> wrote:
>>
>>
>> Thanks for the help here's my raw email including headers :
>>
> <---SNIP--->
>> X-Original-To: su...@ma...
>>
>> Delivered-To: MFY...@ba...
> <---SNIP--->
>
> The "Delivered-To" header is the one you're looking for.  You'll want
> to read the section titled "The Use and Abuse of Multidrop Mailboxes"
> and look at the qvirtual keyword for stripping out the "MFY" part.
>
> So, something like:
>
> poll pop.isp.net
>    qvirtual "MFY"
>    envelope "Delivered-To"
>    user remote with password secure to * here
>
> Should do what you're after, assuming that your local SMTP server is
> correctly configured :)
>
> -- 
>                 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
>
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>
> 


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Re: [fetchmail-users] Fetchmail to Postfix

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

On 1/6/07, Support @ Smart Networking <su...@ma...> wrote:
>
>
> Thanks for the help here's my raw email including headers :
>
<---SNIP--->
> X-Original-To: su...@ma...
>
> Delivered-To: MFY...@ba...
<---SNIP--->

The "Delivered-To" header is the one you're looking for.  You'll want
to read the section titled "The Use and Abuse of Multidrop Mailboxes"
and look at the qvirtual keyword for stripping out the "MFY" part.

So, something like:

poll pop.isp.net
    qvirtual "MFY"
    envelope "Delivered-To"
    user remote with password secure to * here

Should do what you're after, assuming that your local SMTP server is
correctly configured :)

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

[Support @ S. N. <su...@ma...>]

Thanks for the help here's my raw email including headers :

Return-Path: <MFYsupport@barracuda>

Received: from barracuda ([unix socket]) (authenticated user=mailadmin bits=0)

by barracuda (Cyrus v2.2.3) with LMTP; Sat, 06 Jan 2007 20:41:06 +0000

X-Sieve: CMU Sieve 2.2

Return-Path: <su...@ma...>

X-Original-To: su...@ma...

Delivered-To: MFY...@ba...

Received: from mx1.mailforyou.co.uk (mx1.mailforyou.co.uk [82.151.249.74])

by barracuda.mailforyou.co.uk (Postfix) with ESMTP id ECE1A880368

for <su...@ma...>; Sat, 6 Jan 2007 20:41:05 +0000 (GMT)

Received-SPF: none (mx1.mailforyou.co.uk: domain of su...@ma... does not designate permitted sender hosts)

Received: from mtaout01-winn.ispmail.ntl.com (mtaout01-winn.ispmail.ntl.com [81.103.221.47])

by mx1.mailforyou.co.uk (Postfix) with ESMTP id 8F6D91C7A25

for <su...@ma...>; Sat, 6 Jan 2007 20:42:56 +0000 (GMT)

Received: from aamtaout02-winn.ispmail.ntl.com ([81.103.221.35])

by mtaout01-winn.ispmail.ntl.com with ESMTP

id <200...@aa...>

for <su...@ma...>; Sat, 6 Jan 2007 20:40:06 +0000

Received: from computer ([82.5.58.19]) by aamtaout02-winn.ispmail.ntl.com

with SMTP

id <20070106204006.XCHO17393.aamtaout02-winn.ispmail.ntl.com@computer>

for <su...@ma...>; Sat, 6 Jan 2007 20:40:06 +0000

Message-ID: <002001c731d2$d7659380$0a01a8c0@computer>

Reply-To: "Support @ Smart Networking" <su...@ma...>

From: "Support @ Smart Networking" <su...@ma...>

To: "Support @ Smart Networking" <su...@ma...>

Cc: "Support @ Smart Networking" <su...@ma...>

Subject: Subject Header

Date: Sat, 6 Jan 2007 20:40:00 -0000

Organization: Smart Networking

MIME-Version: 1.0

Content-Type: multipart/alternative;

boundary="----=_NextPart_000_001D_01C731D2.D5B39DC0"

X-Priority: 3

X-MSMail-Priority: Normal

X-Mailer: Microsoft Outlook Express 6.00.2900.3028

X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028

X-mx1.mailforyou.co.uk-MailScanner-Information: Please contact the ISP for more information

X-mx1.mailforyou.co.uk-MailScanner: Found to be clean

X-mx1.mailforyou.co.uk-MailScanner-From: su...@ma...

hope this helps 

Phil

Re: [fetchmail-users] Fetchmail to Postfix

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

On 1/6/07, Support @ Smart Networking <su...@ma...> wrote:
> Im finding it hard to decide which is the best solution to use.
> It looks like copies of emails could potentially either disapear into the
> etha

Only if you've managed to completely break your postfix setup.
Fetchmail doesn't lose emails (though see the section on Spam
Filtering - fetchmail *will* drop emails with the same message ID if
it's already seen them).

> or even worse be delivered to a user which should not even receive them
> eg. Bcc

Depends on whether your ISP provides the required headers.  If the
email contains no details as to the user it was intended for then
you're out of luck.  This is documented in the man page under
"multi-drop".

> What is the best solution ?

Depends on the message headers you have to work with.

> Could you show me the location of a .fetchmailrc script that I could look
> at?

They're in the man page :)

If you could provide a sample header from an email (ideally one BCCd)
then I'm sure somebody can provide something a little more.

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

[Support @ S. N. <su...@ma...>]

Im finding it hard to decide which is the best solution to use.  
It looks like copies of emails could potentially either disapear into the etha or even worse be delivered to a user which should not even receive them eg. Bcc
What is the best solution ?
Could you show me the location of a .fetchmailrc script that I could look at?

Thanks Phil
  ----- Original Message ----- 
  From: Support @ Smart Networking 
  To: fet...@li... 
  Sent: Friday, January 05, 2007 11:24 PM
  Subject: [fetchmail-users] Fetchmail to Postfix


  Is it possible to use fetchmail to download from a catch all pop account and then place the downloaded email into postfix for local delivery

  ISP  ------> FETCHMAIL -------> POSTFIX -----------> USERMAIL BOX

  At present to achieve this I have to download the emails from the ISP to a catch all user account on my local server, then filter them using .forward and a procmail recipe.  
  Is there an easier way to make fetchmail download the emails directly to the local server's mail queue so that postfix can the email to the corresponding local user. (I am running postfix and cyrus)

  Many thanks in advance.

  Kind Regards

  Phil Brooks

  -- 
  This message has been scanned for viruses and 
  dangerous content by MailScanner, and is 
  believed to be clean. 


------------------------------------------------------------------------------


  _______________________________________________
  fetchmail-users mailing list
  fet...@li...
  https://lists.berlios.de/mailman/listinfo/fetchmail-users

Re: [fetchmail-users] Fetchmail to Postfix

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

One posting is enough.

Support @ Smart Networking schrieb am 2007-01-05:

> Is there an easier way to make fetchmail download the emails directly
> to the local server's mail queue so that postfix can the email to the
> corresponding local user. (I am running postfix and cyrus)

yes

check the manpage, http://home.pages.de/~mandree/mail/multidrop
and fetchmail's envelope option.

-- 
Matthias Andree

[fetchmail-users] Fetchmail to Postfix

[Support @ S. N. <su...@ma...>]

Is it possible to use fetchmail to download from a catch all pop account and then place the downloaded email into postfix for local delivery

ISP  ------> FETCHMAIL -------> POSTFIX -----------> USERMAIL BOX

At present to achieve this I have to download the emails from the ISP to a catch all user account on my local server, then filter them using .forward and a procmail recipe.  
Is there an easier way to make fetchmail download the emails directly to the local server's mail queue so that postfix can the email to the corresponding local user. (I am running postfix and cyrus)

Many thanks in advance.

Kind Regards

Phil Brooks

[fetchmail-users] Fetchmail to Postfix

[Support @ S. N. <su...@ma...>]

Is it possible to use fetchmail to download from a catch all pop account and then place the downloaded email into postfix for local delivery

ISP  ------> FETCHMAIL -------> POSTFIX -----------> USERMAIL BOX

At present to achieve this I have to download the emails from the ISP to a catch all user account on my local server, then filter them using .forward and a procmail recipe.  
Is there an easier way to make fetchmail download the emails directly to the local server's mail queue so that postfix can the email to the corresponding local user. (I am running postfix and cyrus)

Many thanks in advance.

Kind Regards

Phil Brooks
-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

[fetchmail-users] fetchmail security announcement 2006-02 (CVE-2006-5867)

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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

fetchmail-SA-2006-02: TLS enforcement problem/MITM attack/password exposure

Topics:		fetchmail cannot enforce TLS

Author:		Matthias Andree
Version:	1.0
Announced:	2007-01-04
Type:		secret information disclosure
Impact:		fetchmail can expose cleartext password over unsecure link
		fetchmail may not detect man in the middle attacks
Danger:		medium
Credits:	Isaac Wilcox (bug report, testing, collaboration on fix)
CVE Name:	CVE-2006-5867
URL:		http://fetchmail.berlios.de/fetchmail-SA-2006-02.txt
Project URL:	http://fetchmail.berlios.de/

Affects:	fetchmail releases <= 6.3.5
		fetchmail release candidates 6.3.6-rc1, -rc2, -rc3

Not affected:	fetchmail release candidates 6.3.6-rc4, -rc5
		fetchmail release 6.3.6

Corrected:	2006-11-26 fetchmail 6.3.6-rc4


0. Release history
==================

2006-11-16	v0.01 internal review draft
2006-11-26	v0.02 revise failure cases, workaround, add acknowledgments
2006-11-27	v0.03 add more vulnerabilities
2006-01-04	v1.0  ready for release


1. Background
=============

fetchmail is a software package to retrieve mail from remote POP2, POP3,
IMAP, ETRN or ODMR servers and forward it to local SMTP, LMTP servers or
message delivery agents.

fetchmail ships with a graphical, Python/Tkinter based configuration
utility named "fetchmailconf" to help the user create configuration (run
control) files for fetchmail.


2. Problem description and Impact
=================================

Fetchmail has had several nasty password disclosure vulnerabilities for
a long time. It was only recently that these have been found.

V1. sslcertck/sslfingerprint options should have implied "sslproto tls1"
    in order to enforce TLS negotiation, but did not.

V2. Even with "sslproto tls1" in the config, fetches would go ahead
    in plain text if STLS/STARTTLS wasn't available (not advertised,
    or advertised but rejected).

V3. POP3 fetches could completely ignore all TLS options whether
    available or not because it didn't reliably issue CAPA before
    checking for STLS support - but CAPA is a requisite for STLS.
    Whether or not CAPAbilities were probed, depended on the "auth"
    option. (Fetchmail only tried CAPA if the auth option was not set at
    all, was set to gssapi, kerberos, kerberos_v4, otp, or cram-md5.)

V4. POP3 could fall back to using plain text passwords, even if strong
    authentication had been configured.

V5. POP2 would not complain if strong authentication or TLS had been
    requested.

This can cause eavesdroppers to obtain the password, depending on the
authentication scheme that is configured or auto-selected, and
subsequently impersonate somebody else when logging into the upstream
server.


3. Workaround
=============

If your upstream offers SSLv3-wrapped service on a dedicated port,
use   fetchmail --ssl --sslcertck --sslproto ssl3   on the command line,
or equivalent in the run control file.  This encrypts the whole session.


4. Solution
===========

Download and install fetchmail 6.3.6 or a newer stable release from
fetchmail's project site at
<http://developer.berlios.de/project/showfiles.php?group_id=1824>.


5. Acknowledgments
==================

Isaac Wilcox has been a great help with testing the fixes and getting
them right.


A. Copyright, License and Warranty
==================================

(C) Copyright 2007 by Matthias Andree, <mat...@gm...>.
Some rights reserved.

This work is licensed under the Creative Commons
Attribution-NonCommercial-NoDerivs German License. To view a copy of
this license, visit http://creativecommons.org/licenses/by-nc-nd/2.0/de/
or send a letter to Creative Commons; 559 Nathan Abbott Way;
Stanford, California 94305; USA.

THIS WORK IS PROVIDED FREE OF CHARGE AND WITHOUT ANY WARRANTIES.
Use the information herein at your own risk.

END OF fetchmail-SA-2006-02.txt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFntkXvmGDOQUufZURAqVdAKC+UZHUWIZPyp1ZaJdKF4/QUGf/ewCeN8uN
objiIGL0OdrSIPZf1smU2vA=
=faeY
-----END PGP SIGNATURE-----

[fetchmail-users] fetchmail security announcement 2006-03 (CVE-2006-5974)

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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

fetchmail-SA-2006-03: crash when refusing message delivered through MDA

Topics:		fetchmail crashes when refusing a message bound for an MDA

Author:		Matthias Andree
Version:	1.0
Announced:	2007-01-04
Type:		denial of service
Impact:		fetchmail aborts prematurely
Danger:		low
Credits:	Neil Hoggarth (bug report and analysis)
CVE Name:	CVE-2006-5974
URL:		http://fetchmail.berlios.de/fetchmail-SA-2006-03.txt
Project URL:	http://fetchmail.berlios.de/

Affects:	fetchmail release = 6.3.5
		fetchmail release candidates 6.3.6-rc1, -rc2

Not affected:	fetchmail release 6.3.6

Corrected:	2006-11-14 fetchmail SVN


0. Release history
==================

2006-11-19 -	internal review draft
2007-01-04 1.0	 ready for release


1. Background
=============

fetchmail is a software package to retrieve mail from remote POP2, POP3,
IMAP, ETRN or ODMR servers and forward it to local SMTP, LMTP servers or
message delivery agents.

fetchmail ships with a graphical, Python/Tkinter based configuration
utility named "fetchmailconf" to help the user create configuration (run
control) files for fetchmail.


2. Problem description and Impact
=================================

Fetchmail 6.3.5 and early 6.3.6 release candidates, when delivering
messages to a message delivery agent by means of the "mda" option, can
crash (by passing a NULL pointer to ferror() and fflush()) when refusing
a message. SMTP and LMTP delivery modes aren't affected.


3. Workaround
=============

Avoid the mda option and ship to a local SMTP or LMTP server instead.


4. Solution
===========

Download and install fetchmail 6.3.6 or a newer stable release from
fetchmail's project site at
<http://developer.berlios.de/project/showfiles.php?group_id=1824>.



A. Copyright, License and Warranty
==================================

(C) Copyright 2007 by Matthias Andree, <mat...@gm...>.
Some rights reserved.

This work is licensed under the Creative Commons
Attribution-NonCommercial-NoDerivs German License. To view a copy of
this license, visit http://creativecommons.org/licenses/by-nc-nd/2.0/de/
or send a letter to Creative Commons; 559 Nathan Abbott Way;
Stanford, California 94305; USA.

THIS WORK IS PROVIDED FREE OF CHARGE AND WITHOUT ANY WARRANTIES.
Use the information herein at your own risk.

END OF fetchmail-SA-2006-03.txt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFntkCvmGDOQUufZURApmyAKCV50Rs96vyEl8L8oXsMiIam064IwCg08KI
HWQ3SfEpc6WV4bS+xZwWj5g=
=JZIR
-----END PGP SIGNATURE-----