fetchmail-users — User questions and discussion

Re: [fetchmail-users] Question about mailing lists

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

> if I want to check 20 pop accounts, should I run fetchmail in daemon
> mode or via a cron.

I'd generally recommend daemon mode.

> Is there a way to get it to pause for a time
> between each poll?

That's the way daemon mode works - to start it in daemon mode you MUST
give it an interval (in seconds) between polls.

The man page does tell you about 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] Question about mailing lists

[Andrew N. G. <an...@gr...>]

I would say working great, when compared to the pop3 connector for  
exchange which is a complete PITA.

It also allows me to forward the mail via SMTP into the exchange  
server so the exchange will respect the spam headers from Spam  
Assassin.  I have the exchange box firewalled off and only accepting  
traffic from the internal linux box running fetchmail

I guess the Microsoft pop connector does not let you filter the mail  
in exchange because the "Intelligent Message Filter" in exchange only  
works on SMTP traffic not pop connector traffic.

Over all using fetchmail is a huge improvement and I can have it  
check my mail box once every 5 minutes instead of every 15 minutes  
which is the min for exchange.  I probably will end up creating a  
mail box for each user on the mail server and dropping the catch all.

I would eliminate exchange completely if our CRM would work with  
IMAP.  Don't get started on the CRM though. :)

A couple more questions:

if I want to check 20 pop accounts, should I run fetchmail in daemon  
mode or via a cron.  Is there a way to get it to pause for a time  
between each poll?

Thanks for all the help with everything,

Andrew


On Feb 9, 2007, at 9:27 PM, Matthias Andree wrote:

> "Andrew N. Gray" <an...@gr...> writes:
>
>> I have fetchmail configured and working great.  It fetches the mail
>> from a pop catch all and sends it out via SMTP to our exchange server
>>
>> The issue I have is with a couple of mailing lists that are delivered
>> via BCC
>
> So you call that "working great"?  I wouldn't.
>
> fetchmail can only handle this if the catchall account conforms to
> http://home.pages.de/~mandree/mail/multidrop - else you need to  
> take any
> "mailbox fetching" (thus, fetchmail) out of the loop and do direct
> SMTP. That's beyond this list's scope, pointers are Postfix and  
> perhaps
> Exim.
>
> -- 
> Matthias Andree

Re: [fetchmail-users] Question about mailing lists

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

"Andrew N. Gray" <an...@gr...> writes:

> I have fetchmail configured and working great.  It fetches the mail  
> from a pop catch all and sends it out via SMTP to our exchange server
>
> The issue I have is with a couple of mailing lists that are delivered  
> via BCC

So you call that "working great"?  I wouldn't.

fetchmail can only handle this if the catchall account conforms to
http://home.pages.de/~mandree/mail/multidrop - else you need to take any
"mailbox fetching" (thus, fetchmail) out of the loop and do direct
SMTP. That's beyond this list's scope, pointers are Postfix and perhaps
Exim.

-- 
Matthias Andree

Re: [fetchmail-users] A question about the envelope option

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

On 2/9/07, Andrew N. Gray <an...@gr...> wrote:
> I am trying to figure out the envelope options for fetchmail and
> found this passage in the man page
>
> > In the .fetchmailrc file, the 'envelope' string argument  may  be
> > preceded  by a whitespace-separated number.  This number, if
> > specified, is the number of such headers to skip over (that  is,
> > an  argument  of  1 selects  the second header of the given type).
>
> At the bottom of this email is an example header from an email I am
> trying to direct to the correct box and my fetchmailrc file.
>
> Can I use the option "1 envelope" to solve this problem and deliver
> the following email to es...@po..., which is the second line
> of the Received header

In theory, maybe.  However the correct approach is to get your ISP to
put the correct value in the Envelope-to header :)

> Also, where does this option go in my fetchmail.rc file?

As documented, it's a server option, so you'd put it after the poll
line, but before the 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

Re: [fetchmail-users] Question about mailing lists, now running as unprivile

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

Keep the traffic on the list.

On 2/9/07, Andrew N. Gray <an...@gr...> wrote:
> thanks for the info about the unprivileged user.
>
> I am running the service as a daemon on gentoo,  is there are
> preferred way to start fetchmail as an unprivileged user using the
> init.d/fetchmail script.

Well, that's a Gentoo issue, not a Fetchmail one :)

However, a few seconds on the Gentoo site suggest you need to look at
"start-stop-daemon".  The option is probably going to be "--user
<myuser>".

-- 
                 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] Question about mailing lists

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

On 2/8/07, Andrew N. Gray <an...@gr...> wrote:
> I have fetchmail configured and working great.  It fetches the mail
> from a pop catch all and sends it out via SMTP to our exchange server
>
> The issue I have is with a couple of mailing lists that are delivered
> via BCC
>
> I would like anything sent to "nca...@li..." to be
> delivered to user ES...@po....  I also would like to not have
> to set up another pop account.

You'll probably have to configure your SMTP server to handle this, I
don't think you can do this with fetchmail.

> Also, I am new to fetchmail.  does anyone see any glarring problems
> with my set up.  poissonlaw.com and poissonpoissonbower.com are the
> same DNS entry.   I am using Keep until I finish testing and getting
> everything to work.

One warning - your config seems to suggest you're running it as root.
Recent versions of fetchmail will warn you about doing this and future
versions may refuse to run as root.  Create an unpriviledged user for
fetchmail and run it under this account instead.

-- 
                 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] Question about mailing lists

[Andrew N. G. <an...@gr...>]

I have fetchmail configured and working great.  It fetches the mail  
from a pop catch all and sends it out via SMTP to our exchange server

The issue I have is with a couple of mailing lists that are delivered  
via BCC

I would like anything sent to "nca...@li..." to be  
delivered to user ES...@po....  I also would like to not have  
to set up another pop account.

Also, I am new to fetchmail.  does anyone see any glarring problems  
with my set up.  poissonlaw.com and poissonpoissonbower.com are the  
same DNS entry.   I am using Keep until I finish testing and getting  
everything to work.


thanks for your help,

Andrew


Here is my fetchmailrc

set postmaster AN...@po...
set no bouncemail

poll mail.poissonlaw.com with proto pop3 localdomains poissonlaw.com  
poissonpoissonbower.com:
         user ********** pass ********* to * smtphost 10.5.*.*  
smtpaddress poissonlaw.com keep
         set logfile /root/fetchmaillog

Re: [fetchmail-users] fetchmail: incorrect header ?

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

On 2/7/07, jay shi <jay...@ya...> wrote:
> Hi ,
>         Can any one help me, what  the following error want to say  and what
> option i should use in fetchmailrc file to overcome this. I am getting the
> following error atleast 2 -3 times in a day.
>          I observe that normaly these mails are spam mails.So i normly
> delete these mail and then every thing start normal.
>         Is there any option by which i can download these type of incorrect
> header mail?
>         I am using fetchmail-6.2.0-8 + fedora core 1

That's a *very* old version - upgrade to 6.3.6 and retest.

-- 
                 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: incorrect header ?

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

Hi ,
        Can any one help me, what  the following error want to say  and what option i should use in fetchmailrc file to overcome this. I am getting the following error atleast 2 -3 times in a day.
         I observe that normaly these mails are spam mails.So i normly delete these mail and then every thing start normal.
        Is there any option by which i can download these type of incorrect header mail?
        I am using fetchmail-6.2.0-8 + fedora core 1

log o/p :--
=====
fetchmail: reading message ab...@te...@10.20.30.40:1 of 2 (63761 octets)
fetchmail: incorrect header line found while scanning headers
fetchmail: incorrect header line found while scanning headers
.............................................................fetchmail:  retained
fetchmail: POP3> RETR 2
fetchmail: POP3< +OK
fetchmail: reading message ab...@te...@10.20.30.40:2 of 2 (694 octets)
fetchmail: incorrect header line found while scanning headers
fetchmail:  retained
fetchmail: POP3> QUIT
fetchmail: POP3< +OK


Thanks & Regards
Jayesh


 
---------------------------------
Never miss an email again!
Yahoo! Toolbar alerts you the instant new Mail arrives. Check it out.

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

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

Please don't top post.

On 2/3/07, Otto Rodusek (AP-SGP) <ot...@ap...> wrote:
>
>  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.

The problem is that YOUR local SMTP server is returning a temporary
delivery failure so fetchmail is keeping the email.  You can either:

a) Get your ISP to not accept email from unresolvable domains (which
no ISP ever should)
b) Switch ISP to one with a clue
c) Configure your local SMTP server to provide a permanent delivery
failure on DNS lookup failures, which risks losing email
d) Configure fetchmail with the 451 code as an anti-spam code, and
risk losing 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] message...was not the expected length...not flushed

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

Otto Rodusek (AP-SGP) schrieb am 2007-02-03:

> 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 

No, it wouldn't, and your upstream ISP shouldn't accept them in the
first place. Talk to them. There is a vast choice of qmail front-ends
that perform various additional checks before accepting a message.

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

Check the antispam configuration option, but that's a bad solution - if
you are 100% sure it's not a local issue, you should really talk to the
ISP instead and have them refuse messages from nonexistent or
nonresolvable domains.

> I ran my fetchmail manually and it download 58 emails of which 9 were 
> faulty and not flushed (as per the log).

fetchmail hasn't downloaded them and seen a "temporary" error code, so
it assumes the download will work in the future.


Please do trim your quotes next time, and do not top-post.

-- 
Matthias Andree

[fetchmail-users] fetchmail 6.3.7-rc1 release candidate

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

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

Greetings,

The security fixes in 6.3.6 also had side effects, and broke these two
features:
- - KPOP authentication
- - repolling without TLS if opportunistic upgrade to TLS failed for POP3

I have uploaded the fetchmail 6.3.7 release candidate to the usual download location:
<http://home.pages.de/~mandree/fetchmail/> - this should become the
final 6.3.7 release quite soon - unless further regressions or critical
bugs are reported.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
fetchmail 6.3.7 changes since 6.3.6:

# FIXES FOR REGRESSIONS IN 6.3.6
* Fix KPOP. Patch by Miloslav Trmac.
* Fix repoll when server disconnects after opportunistic TLS failed for POP3.
  Berlios Bug #10133, reported by Andrej Kacian.

# TRANSLATION UPDATES
* Japanese (Takeshi Hamasaki), Polish (Jakub Bogusz)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

WARNING: This message sets the Reply-To: header.
When replying to me personally, you need to edit the To: header!

Thank you.

Happy fetching,
Matthias Andree
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFw9f2vmGDOQUufZURAvhJAKCNcHhCUFf2aZ+yj3zDjomHgyGK1ACeO9DN
y4oyx3Dl4EHy/3vvSKE4prs=
=QH4/
-----END PGP SIGNATURE-----

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.......@ma...: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.......@ma...: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.......@ma...: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 ken@langelands.comchantelfisher 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 ken@langelands.comchantelfisher 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 ken@langelands.comchantelfisher 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 ken@langelands.comchantelfisher 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 ken@langelands.comchantelfisher 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 ken@langelands.comchantelfisher 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