fetchmail-users — User questions and discussion

[fetchmail-users] fetchmail 6.3.8-rc1 release candidate

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

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

Greetings,

I have uploaded the first fetchmail 6.3.8 release candidate to the usual
download location: <http://home.pages.de/~mandree/fetchmail/>.

One more workaround was added to support repolling after failure of
opportunistic TLS upgrade - this time when the server refused
authentication.

Several parts of the documentation have been corrected and the Received:
format that fetchmail expects was documented. There is also a new
contrib/ script, delete-later.

Details:

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
fetchmail 6.3.8 changes since 6.3.7:

# BUG FIXES:
* Fix pluralization of oversized-message warning mails.
* Fix manual page: --sslcheck -> --sslcertck, and do not set trailing 
  "recommended:" in bold. Fixes Debian Bug #413059, reported by Rafal Czlonka.
* Repoll immediately if a protocol error happens during the authentication 
  attempt after a failed opportunistic TLS upgrade.
  Fixes comment #9 in Gentoo Bug #163782, reported by Takuto Matsuu.
* Fix rendering of the "24 - 26, 28, 29" paragraph in the exit codes section. 
  Reported by Nico Golde.

# DOCUMENTATION:
* Extend --mda documentation, discourage use of qmail-inject.
  Based on a patch by Rob MacGregor.
* Document SOCKS configuration facility (SOCKS_CONF environment variable).
  Thanks to Jochen Hayek, Michael Shuldman and Rob MacGregor.
* Use envelope option in multidrop example. Patch by Rob MacGregor.
* Document expected Received: line format when parsing for envelope addressees.
* Stripped option documentation from sample.rcfile, since this is bound to go
  out of synch with the manual page, which is the only reference on options.

# CONTRIB:
* Add delete-later and delete-later.README, a script and documentation for
  a MySQL/Tcl-based client-side "delete-after" feature.
  Kindly donated by Yoo GmbH, Großvoigtsberg, Germany (Carsten Ralle).

# KNOWN BUGS AND WORKAROUNDS:
  (this section floats upwards through the NEWS file so it stays with the
  current release information)
* fetchmail does not handle messages without Message-ID header well
  (See sourceforge.net bug #780933)
* Sun Workshop 6 (SPARC) is known to miscompile the configuration file lexer in
  64-bit mode.  Either compile 32-bit code or use GCC to compile 64-bit
  fetchmail.  Note that fetchmail doesn't take advantage of 64-bit code,
  so compiling 32-bit SPARC code should not cause any difficulties.
* fetchmail does not track pending deletes over crashes
* the command line interface is a bit narrow-minded sometimes, for instance,
  fetchmail -s doesn't work with a running daemon
* some of the logging output is not very helpful
* some of the documentation is still not up to date
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

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)

iD8DBQFF/Fq4vmGDOQUufZURAh5CAJ9eVxplbQV1HJmEo1cIFFMrPIn+bACeJPm/
0dtsJenupmlzyECQ4KNmYEI=
=qutF
-----END PGP SIGNATURE-----

Re: [fetchmail-users] fetchmail and socks5

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

Jochen Hayek schrieb:

> Now that we (the fetchmail community) know this, fetchmail can also get an internal
> 
>     putenv("SOCKS_CONF=/dev/null")
> 
> somewhere around its
> 
>     SOCKSinit("fetchmail");
> 
> and than a command line switch (e.g. --socks_conf=/etc/socks.conf )
> in order to change it back,
> so that somebody, who really wants to employ socks, actually makes use of it:
> 
>     putenv("SOCKS_CONF=/etc/socks.conf")
> 
> But there are dozens of alternatives ...

But why would fetchmail then need its own command line switch at all?
I mean - if the SOCKS library reads the environment, we can just
document this. I'll do that now.

I'm not going to change the default behaviour in 6.3.X releases anyways:
incompatibilities do not belong in patchlevel update releases. So no
putenvs without options.

Adding even more code to handle yet another option however doesn't seem
justified in this case -- this new option would just be one different
formulation for exactly the same purpose - and we already have env(1)
and shells to handle this. It's not the putenv, but the dozens of code
lines in the fetchmail dump, option parser, rcfile parser, fetchmailconf
and everywhere else I've forgotten.

I hope that's acceptable.

If it's not, please find some good excuses for me for duplicating the
environment modification code that is already in env(1) - and please one
that keeps compatibility with 6.3.7. :-)

Best,
MA

Re: [fetchmail-users] fetchmail and socks5

[Jochen H. <Joc...@Ha...>]

>>>>> "MA" == Matthias Andree writes:

    MA> Well - Dante doesn't have run-time switches, it redirects all
    MA> the network-related functions to itself, 
    MA> fetchmail has not means to circumvent SOCKS if linked against it.
    MA> Such run-time configuration would have to happen by means of socks.conf.

>>>>> On Sat, 17 Mar 2007 15:18:02 +0100,
>>>>> Michael Shuldman
>>>>> (whose comments are cited below with "    MS> "),
>>>>> had this to say in article <200...@ba...>
>>>>> in newsgroups gmane.network.socks.dante.general
>>>>> concerning the subject of "Re: 2007-03-16 / how to tell socks enabled application to not go via the socks server"

> Jochen Hayek wrote,

    >> But how can a socks enabled (compiled, linked, ...) application
    >> instruct the socks5 library to not go via the socks5 server
    >> other than by removing /etc/socks.conf ?

    MS> Maybe you could set the environmentvariable SOCKS_CONF.  
    MS> What happens if you do "SOCKS_CONF=/dev/null application"?

That does exactly what you and I expect.

Thanks a lot!



Now that we (the fetchmail community) know this, fetchmail can also get an internal

    putenv("SOCKS_CONF=/dev/null")

somewhere around its

    SOCKSinit("fetchmail");

and than a command line switch (e.g. --socks_conf=/etc/socks.conf )
in order to change it back,
so that somebody, who really wants to employ socks, actually makes use of it:

    putenv("SOCKS_CONF=/etc/socks.conf")

But there are dozens of alternatives ...

Re: [fetchmail-users] fetchmail and socks5

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

On 3/16/07, Jochen Hayek <Joc...@ha...> wrote:
>
> I don't want to appear picky (although I probably am),
> but if a usual DAU (and I myself have grown out of that state during some 25 years in IT),
> who certainly has the right to use a Linux, BSD or whatever distro instead of compiling everything himself from scratch
> and who esp. has the right to use a fetchmail, that comes with that distro,
> and such a distro may provide him with a socks enabled fetchmail,
> and if he experiments in one corner (socks),
> then he does not necessarily need to expect impact in a slightly different corner (fetchmail).

I'm with you on that one.  Sadly the problem is that whoever created
the binary package didn't understand the impact of what they were
doing when they compiled in SOCKS support.

> So ... it would be nice to have a socks enabled fetchmail
> defaulting to "do *not* use socks until I tell you via command line or via RC option".

If you're able to supply patches to make this happen then I suspect
the developers would be interested (not a dig, just a suggestion).
I've also submitted a patch for the man page (which should make it
into 6.3.8 with luck) to document this behaviour.

-- 
                 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 multidrop problem

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

On 3/16/07, jay shi <jay...@ya...> wrote:
> Hi Rob & friends,
>                Sorry for my long mail, i just put for understanding purpose only.Plz don't ignore my mail, i am in trouble .
>                well i use ur specified option "envelope 1 Delivered-To"  but still getting no  effect. The user foo & bar getting double mails.
>               what should i do next ?

Right, please go back and read the FAQ.  It tells you what you're
supposed to be providing.

1) Version of fetchmail.  Until that's (at least) 6.3.7 don't bother
going any further.

2) Contents of .fetchmailrc

3) Command line arguments

4) Output of "--nosyslog --nodetach -vvv" (yes, that's three -v
options, enabling debug mode) for a problem email

5) Matching entries from the log of your SMTP server (and what it is)

See also the FAQ:

http://www.fetchmail.info/fetchmail-FAQ.html#M8

-- 
                 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 and socks5

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

Jochen Hayek schrieb:
>>>>>> "MA" == Matthias Andree <mat...@gm...> writes:
> 
>     MA> Well - Dante doesn't have run-time switches, 
>     MA> it redirects all the network-related functions to itself,
>     MA> fetchmail has not means to
>     MA> circumvent SOCKS if linked against it.
> 
>     MA> Such run-time configuration would have to happen by means of socks.conf.
> 
>     MA> I am not sure if that's possible with "via: direct" statements
>     MA> somehow for your configuration.
> 
> I asked the dante people for help (-> news.gmane.org:gmane.network.socks.dante.general : "how to tell socks enabled application to not go via the socks server"),
> and I will come back to you, if there will be a viable solution..

Thank you.

Re: [fetchmail-users] fetchmail and socks5

[Jochen H. <Joc...@Ha...>]

>>>>> "RMG2" == Rob MacGregor writes:

    >> [2007-03-15 14:11:49] johayek@HayekJ $ fetchmail --version
    >> This is fetchmail release 6.3.2+POP2+IMAP-GSS+RPA+NTLM+SDPS+SSL+OPIE+SOCKS+NLS.

    RMG2> Yeah that looks like it was configured with socks support.  Having
    RMG2> myself dug through the documentation and FAQ it appears that there is
    RMG2> socks support after all (it's not documented anywhere except the FAQ):

    RMG2> http://www.fetchmail.info/fetchmail-FAQ.html#K1

    RMG2> Rebuild fetchmail without the socks support.  

    RMG2> It looks like fetchmail will automatically use socks
    RMG2> if you build it with socks support

... resp. e.g. if your ready-made Linux distribution provides you with a fetchmail configured like that.

    RMG2> - there's no runtime switch.
    RMG2> (At least that's what a read of the source tells me)

    RMG2> So, in short, while you didn't intend to configure fetchmail
    RMG2> to use your socks server, 
    RMG2> you did by configuring socks support into fetchmail

I don't want to appear picky (although I probably am),
but if a usual DAU (and I myself have grown out of that state during some 25 years in IT),
who certainly has the right to use a Linux, BSD or whatever distro instead of compiling everything himself from scratch
and who esp. has the right to use a fetchmail, that comes with that distro,
and such a distro may provide him with a socks enabled fetchmail,
and if he experiments in one corner (socks),
then he does not necessarily need to expect impact in a slightly different corner (fetchmail).

Although addmittedly both corners are "a little" associated "through" TCP/IP resp. a substitute aka socks library.

So ... it would be nice to have a socks enabled fetchmail 
defaulting to "do *not* use socks until I tell you via command line or via RC option".

And that's where I started "a while ago":

    JH> I would actually prefer a command line option and an entry in the RC file.

    JH> Is there already a feature of fetchmail, that this could be made similar to?

Having a look at the sources myself, too,
I hoped, that the call to SOCKSinit would be an appropriate location to include such a switch,
but that hope sadly did not fulfill.



Alright, I think, I just admit,
that my idea of a fetchmail has not yet been implemented and is also not so easy to implement.



I asked the dante people for the help (-> news.gmane.org:gmane.network.socks.dante.general : "how to tell socks enabled application to not go via the socks server"),
and I will come back to you, if there will be a viable solution..

    RMG2> (and I'm guessing defining some
    RMG2> environment variables or putting entries in socks.conf).

I "just" made my socks.conf to point to a real socks5 server.
Before that, that socks.conf just waited to be taken care of ...




Cheers,
Jochen

Re: [fetchmail-users] fetchmail and socks5

[Jochen H. <Joc...@Ha...>]

>>>>> "MA" == Matthias Andree <mat...@gm...> writes:

    MA> Well - Dante doesn't have run-time switches, 
    MA> it redirects all the network-related functions to itself,
    MA> fetchmail has not means to
    MA> circumvent SOCKS if linked against it.

    MA> Such run-time configuration would have to happen by means of socks.conf.

    MA> I am not sure if that's possible with "via: direct" statements
    MA> somehow for your configuration.

I asked the dante people for help (-> news.gmane.org:gmane.network.socks.dante.general : "how to tell socks enabled application to not go via the socks server"),
and I will come back to you, if there will be a viable solution..


Cheers,
Jochen

Re: [fetchmail-users] fetchmail multidrop problem

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

Hi Rob & friends,
               Sorry for my long mail, i just put for understanding purpose only.Plz don't ignore my mail, i am in trouble .
               well i use ur specified option "envelope 1 Delivered-To"  but still getting no  effect. The user foo & bar getting double mails.
              what should i do next ?

Thanks & Regards
Jayesh
               

Rob MacGregor <rob...@gm...> wrote: Keep the traffic on the list.  If you don't then I'll simply ignore
any email from you...

On 3/15/07, jay shi  wrote:
> Hi Rob
>             Thanks For ur quick response
>             Now i ugrade the fetchmail to fetchmail 6.3.7 but still i am
> strugling
>
>             I used the option "envelope Delivered-To 1" in .fetchmailrc file
>
>             But while running the getmail it giving me the sysntax error

And what error would that be?  My crystal ball is broken today.

>             In man fetchmail  i got the following option
>
> -E 
 | --envelope 

>               (Keyword: envelope; Multidrop only)
>               In the configuration file, an enhanced syntax is used:
>               envelope [] 

>
>             what could be the  correct option ? for skipping lines

Ah, maybe it's "envelope 1 Delivered-To".  I've never come across a
mail system that's broken enough to insert multiple delivered to
headers before :)

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


 
---------------------------------
Expecting? Get great news right away with email Auto-Check.
Try the Yahoo! Mail Beta.

Re: [fetchmail-users] fetchmail header (undisclosed recipients)

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

On 3/15/07, Sylvain Le Torrec <syl...@ad...> wrote:
> First, thank you for your quick answer

As I said before - you need to provide the headers from a sample email
so we can point out which header you should be using for the enevelope
header.  Blindly putting in values won't help you.

You also haven't provide any of the other diagnostic information that
the FAQ tells you to provide, except for the contents of your
fetchmailrc and version of fetchmail.  If you really want help then
please provide 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] fetchmail header (undisclosed recipients)

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

Sylvain Le Torrec schrieb:
> First, thank you for your quick answer

Please trim your quotes. Only quote necessary material and delete the
rest. (Outlook makes people misbehave, that's just incredible.)

> I'm using fetchmail 6.2.4 (I know I have to upgrade it) with qmail

Newer versions have better documentation, too...

> -----------------------------------------
> See my fetchmailrc
> -----------------------------------------
> defaults
> set no bouncemail
> poll domain.mydomain.org protocol POP3
> localdomains mylocaldomain
> tracepolls
> envelope "Delivered-To:"
> qvirtual "Delivered-To:"

This is bogus, you need to specify the prefix that the UPSTREAM qmail
adds to Delivered-To headers (what they have in their virtualdomains
table on their right hand side), if for instance all headers looked like:

Delivered-To: let...@ba...

You could use qvirtual "letorrec-".

> username myusername
> password mypasswd
> is *
> fetchall
> mda "sed 1,2d | /var/qmail/bin/qmail-inject"

Make that

mda "sed 1,2d | /usr/sbin/sendmail -i -f %F -- %T"

That should work with qmail (you MAY have to use /usr/lib/sendmail
instead) and prevent forwarding loops (by making recipients explicit -
the %T is it).

Also, will people *please* stop using this ghastly qmail-inject? It
offers no advantage, only the disadvantage of a nonstandard command line
interface. (qmail's sendmail compatibility wrapper even understands
qmail-inject's environment variables.)

HTH,
MA

[fetchmail-users] TR: fetchmail header (undisclosed recipients)

[Sylvain Le T. <syl...@ad...>]

First, thank you for your quick answer

I'm using fetchmail 6.2.4 (I know I have to upgrade it) with qmail
-----------------------------------------
See my fetchmailrc
-----------------------------------------
defaults
set no bouncemail
poll domain.mydomain.org protocol POP3
localdomains mylocaldomain
tracepolls
envelope "Delivered-To:"
qvirtual "Delivered-To:"
username myusername
password mypasswd
is *
fetchall
mda "sed 1,2d | /var/qmail/bin/qmail-inject"

# the last line allowed to not receiving 2 copies of a mail.        
-----------------------------------------

I found your mail in my postier account...

Reporting-MTA: dns; mail.berlios.de
X-Postfix-Queue-ID: 3666CC4720
X-Postfix-Sender: rfc822; root@mydomain
Arrival-Date: Thu, 15 Mar 2007 22:13:38 +0100 (CET)

Final-Recipient: rfc822; fet...@li...
Action: failed
Status: 5.0.0
Diagnostic-Code: X-Postfix; mail forwarding loop for
    fet...@li...

my fetchmail doesn't know what to do with.... 
------------------------------------------

When there's a mail with "undisclosed recipients", my fetchmail dies and
it's blocked.

Thank you.

Sylvain Le Torrec
Informaticien - Agence de Santé des îles
Wallis et Futuna
BP 4G MATA UTU 98600 WALLIS
Tel : (681) 72 07 25 ou Poste 349
 

-----Message d'origine-----
De : fet...@li...
[mailto:fet...@li...] De la part de Rob
MacGregor
Envoyé : vendredi 16 mars 2007 09:10
À : fet...@li...
Objet : Re: [fetchmail-users] fetchmail header (undisclosed recipients)

Please, no HTML.

On 3/15/07, Sylvain Le Torrec <syl...@ad...> wrote:
>
> I don't find answers of my last questions in your FAQ.
>
> 1- On my server, I've got some mails where there is
"undisclosed-recipients"
> in the mail. Fecthmail doesn't know how to retrieve it, what can I do?

Read the FAQ and provide the information requested.  We'll also need
mail headers from one of the emails so we can point out which envelope
header you should be using (see the man page).

> 2- When an external user of my network sends a mail on my network, I
receive
> 2 copies of this mail.
>
> 3- If an external user sends a mail to 2 or more users, fetchmail
re-inject
> the mail in my qmail and this one sent the mail to other recipient. What I
> do to make fetchmail look only the mail address of my network.
>
> 4* – if an external user (from @domain.com) send a mail to my network
> (@mydomain.org) and to one or more user on domain.com, each user will
> receive 2 or more same mails.

These are all the same problem and related to your using multidrop
without defining the envelope header.

As Gerard said, please provide your fetchmail version.  You also need
to provide your fetchmailrc and any command line arguments you're
using - as per the FAQ you read :)

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

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

Re: [fetchmail-users] fetchmail header (undisclosed recipients)

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

Sylvain Le Torrec schrieb:

> I don’t find answers of my last questions in your FAQ.

Are you sure?

> 1- On my server, I’ve got some mails where there is
> “undisclosed-recipients” in the mail. Fecthmail doesn’t know how to
> retrieve it, what can I do?

Fix your upstream and your configuration - this should address items #1
to #4. Make sure to meet the requirements at
http://home.pages.de/~mandree/mail/multidrop

> What can I do to make fetchmail not look the “to:” and look the right
> header?

man fetchmail
/envelope
/qvirtual

> How can I do to make fetchmail work nice with qmail (not reinject to
> make qmail send again mails)

I don't understand this question. See if whatever problem you have in
mind persists if you've fixed the other issues.

HTH,
MA

Re: [fetchmail-users] fetchmail header (undisclosed recipients)

[Sylvain Le T. <syl...@ad...>]

First, thank you for your quick answer

I'm using fetchmail 6.2.4 (I know I have to upgrade it) with qmail
-----------------------------------------
See my fetchmailrc
-----------------------------------------
defaults
set no bouncemail
poll domain.mydomain.org protocol POP3
localdomains mylocaldomain
tracepolls
envelope "Delivered-To:"
qvirtual "Delivered-To:"
username myusername
password mypasswd
is *
fetchall
mda "sed 1,2d | /var/qmail/bin/qmail-inject"

# the last line allowed to not receiving 2 copies of a mail.        
-----------------------------------------

I found your mail in my postier account...

Reporting-MTA: dns; mail.berlios.de
X-Postfix-Queue-ID: 3666CC4720
X-Postfix-Sender: rfc822; root@mydomain
Arrival-Date: Thu, 15 Mar 2007 22:13:38 +0100 (CET)

Final-Recipient: rfc822; fet...@li...
Action: failed
Status: 5.0.0
Diagnostic-Code: X-Postfix; mail forwarding loop for
    fet...@li...

my fetchmail doesn't know what to do with.... 
------------------------------------------

When there's a mail with "undisclosed recipients", my fetchmail dies and
it's blocked.

Thank you.

Sylvain Le Torrec
Informaticien - Agence de Santé des îles
Wallis et Futuna
BP 4G MATA UTU 98600 WALLIS
Tel : (681) 72 07 25 ou Poste 349
 

-----Message d'origine-----
De : fet...@li...
[mailto:fet...@li...] De la part de Rob
MacGregor
Envoyé : vendredi 16 mars 2007 09:10
À : fet...@li...
Objet : Re: [fetchmail-users] fetchmail header (undisclosed recipients)

Please, no HTML.

On 3/15/07, Sylvain Le Torrec <syl...@ad...> wrote:
>
> I don't find answers of my last questions in your FAQ.
>
> 1- On my server, I've got some mails where there is
"undisclosed-recipients"
> in the mail. Fecthmail doesn't know how to retrieve it, what can I do?

Read the FAQ and provide the information requested.  We'll also need
mail headers from one of the emails so we can point out which envelope
header you should be using (see the man page).

> 2- When an external user of my network sends a mail on my network, I
receive
> 2 copies of this mail.
>
> 3- If an external user sends a mail to 2 or more users, fetchmail
re-inject
> the mail in my qmail and this one sent the mail to other recipient. What I
> do to make fetchmail look only the mail address of my network.
>
> 4* – if an external user (from @domain.com) send a mail to my network
> (@mydomain.org) and to one or more user on domain.com, each user will
> receive 2 or more same mails.

These are all the same problem and related to your using multidrop
without defining the envelope header.

As Gerard said, please provide your fetchmail version.  You also need
to provide your fetchmailrc and any command line arguments you're
using - as per the FAQ you read :)

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

Re: [fetchmail-users] fetchmail and socks5

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

Joc...@Ha... schrieb:
>>>>>> "RMG" == Rob MacGregor writes:
> 
> On 3/8/07, Jochen Hayek wrote:
> 
>     >> A while ago I started experiments with socks5 (-> dante)
>     >> and created a /etc/socks.conf on my local host and I set up a socks5 proxy server on a neighbour box.
>     >> 
>     >> I did not instruct my local fetchmail to make use of my socks5 proxy
>     >> and I also wasn't aware, that my local fetchmail actually does us it,
>     >> but in a situation, when that proxy server on the neighbour box temporarily did not run,
>     >> I finally noticed (using "strace"), that fetchmail contacted my socks5 proxy.
>     >> 
>     >> 
>     >> I did some rtfm-ing,
>     >> but I did not find a way to instruct fetchmail to *not* attempt contacting my socks5 proxy.
> 
>     RMG> Fetchmail has *no* native socks support.  
> 
> Currently I am convinced, your statement is incorrect.
> 
> But I rather have some sympathy for your suspicion,
> as this magical and undescribed feature of fetchmail is certainly rather weird,
> and fetchmail shouldn't behave like that.

Well - Dante doesn't have run-time switches, it redirects all the
network-related functions to itself, fetchmail has not means to
circumvent SOCKS if linked against it.
Such run-time configuration would have to happen by means of socks.conf.

I am not sure if that's possible with "via: direct" statements somehow
for your configuration.

HTH
MA

Re: [fetchmail-users] fetchmail multidrop problem

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

Rob MacGregor schrieb:
> Ah, maybe it's "envelope 1 Delivered-To".  I've never come across a
> mail system that's broken enough to insert multiple delivered to
> headers before :)

You mean internal forwarding chains that use useless rewritten
addresses? IOW, those need not necessarily broken.

But I agree, inaccurate messages won't help debugging in any way.

MA

Re: [fetchmail-users] fetchmail header (undisclosed recipients)

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

Please, no HTML.

On 3/15/07, Sylvain Le Torrec <syl...@ad...> wrote:
>
> I don't find answers of my last questions in your FAQ.
>
> 1- On my server, I've got some mails where there is "undisclosed-recipients"
> in the mail. Fecthmail doesn't know how to retrieve it, what can I do?

Read the FAQ and provide the information requested.  We'll also need
mail headers from one of the emails so we can point out which envelope
header you should be using (see the man page).

> 2- When an external user of my network sends a mail on my network, I receive
> 2 copies of this mail.
>
> 3- If an external user sends a mail to 2 or more users, fetchmail re-inject
> the mail in my qmail and this one sent the mail to other recipient. What I
> do to make fetchmail look only the mail address of my network.
>
> 4* – if an external user (from @domain.com) send a mail to my network
> (@mydomain.org) and to one or more user on domain.com, each user will
> receive 2 or more same mails.

These are all the same problem and related to your using multidrop
without defining the envelope header.

As Gerard said, please provide your fetchmail version.  You also need
to provide your fetchmailrc and any command line arguments you're
using - as per the FAQ you read :)

-- 
                 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 header (undisclosed recipients)

[Gerard S. <ge...@se...>]

On Thursday March 15, 2007 at 04:31:13 (PM) Sylvain Le Torrec wrote:

> 1- On my server, I've got some mails where there is "undisclosed-recipients"
> in the mail. Fecthmail doesn't know how to retrieve it, what can I do?
> 
> 2- When an external user of my network sends a mail on my network, I receive
> 2 copies of this mail.
> 
> 3- If an external user sends a mail to 2 or more users, fetchmail re-inject
> the mail in my qmail and this one sent the mail to other recipient. What I
> do to make fetchmail look only the mail address of my network. 
> 
> 4* -  if an external user (from @domain.com) send a mail to my network
> (@mydomain.org) and to one or more user on domain.com, each user will
> receive 2 or more same mails.

1) Please do not use HTML for posting to a mail forum. I know you are
employing MS Outlook; however, that can be configured to send plain text
messages. In addition, sending it as a 'HIGH' or 'HIGHEST' priority has
no effect on a mail list either.

2) What version of 'fetchmail' are you using?

3) What MTA are you using?

It sounds like you have something seriously configured incorrectly.

-- 
Gerard

[fetchmail-users] fetchmail header (undisclosed recipients)

[Sylvain Le T. <syl...@ad...>]

Hello,

 

I don’t find answers of my last questions in your FAQ.

 

1- On my server, I’ve got some mails where there is “undisclosed-recipients”
in the mail. Fecthmail doesn’t know how to retrieve it, what can I do?

2- When an external user of my network sends a mail on my network, I receive
2 copies of this mail.

3- If an external user sends a mail to 2 or more users, fetchmail re-inject
the mail in my qmail and this one sent the mail to other recipient. What I
do to make fetchmail look only the mail address of my network. 

4* – if an external user (from @domain.com) send a mail to my network
(@mydomain.org) and to one or more user on domain.com, each user will
receive 2 or more same mails.

 

*an account from domain.com receives all mails to mydomain.org. Fetchmail
pop it to retrieve mails.

 

What can I do to make fetchmail not look the “to:” and look the right
header?

How can I do to make fetchmail work nice with qmail (not reinject to make
qmail send again mails)

 

Thank you very much.

 

I hope someone can help me 

 

 

 

Sylvain Le Torrec

Informaticien - Agence de Santé des îles

Wallis et Futuna

BP 4G MATA UTU 98600 WALLIS

Tel : (681) 72 07 25 ou Poste 349

 

 

Re: [fetchmail-users] fetchmail and socks5

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

On 3/15/07, Joc...@ha...
<Joc...@ha...> wrote:
> >>>>> "RMG" == Rob MacGregor writes:
>
> Currently I am convinced, your statement is incorrect.

(And eventually so am I - it's nice to learn something new :>)

> But I rather have some sympathy for your suspicion,
> as this magical and undescribed feature of fetchmail is certainly rather weird,
> and fetchmail shouldn't behave like that.
>
> Have you ever run fetchmail in a socks5 ready environment?
> Give yourself a try and let's continue discussing the matter than!

I have, and have never seen this before.

>     RMG> You're either running it
>     RMG> with a socks wrapper (runsock/socksify)
>     RMG> or have added this yourself (eg via ld.so.preload).
>
> No, I don't, nothing like that.
> (No socks wrapper, no LD_PRELOAD, no /etc/ld.so.preload, no ...)
> I told you above: "I did not instruct my local fetchmail to make use of my socks5 proxy"
> I mean, what I write.
> And you read my statement, didn't you?!?

If you're going to take that attitude I'll simply stop trying to help you :/

That you didn't (mean to) explicitly configure fetchmail itself to use
socks doesn't it isn't.

And, frankly, your original email contained no data at all, just your
words.  Without data showing what's actually going on I have to make
assumptions.

> Can you see "SOCKS" here:
>
>     [2007-03-15 14:11:49] johayek@HayekJ $ fetchmail --version
>     This is fetchmail release 6.3.2+POP2+IMAP-GSS+RPA+NTLM+SDPS+SSL+OPIE+SOCKS+NLS.

Yeah that looks like it was configured with socks support.  Having
myself dug through the documentation and FAQ it appears that there is
socks support after all (it's not documented anywhere except the FAQ):

http://www.fetchmail.info/fetchmail-FAQ.html#K1

Rebuild fetchmail without the socks support.  It looks like fetchmail
will automatically use socks if you build it with socks support -
there's no runtime switch.  (At least that's what a read of the source
tells me)

So, in short, while you didn't intend to configure fetchmail to use
your socks server, you did by configuring socks support into fetchmail
(and I'm guessing defining some environment variables or putting
entries in socks.conf).

-- 
                 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 and socks5

[<Joc...@Ha...>]

>>>>> "RMG" == Rob MacGregor writes:

On 3/8/07, Jochen Hayek wrote:

    >> A while ago I started experiments with socks5 (-> dante)
    >> and created a /etc/socks.conf on my local host and I set up a socks5 proxy server on a neighbour box.
    >> 
    >> I did not instruct my local fetchmail to make use of my socks5 proxy
    >> and I also wasn't aware, that my local fetchmail actually does us it,
    >> but in a situation, when that proxy server on the neighbour box temporarily did not run,
    >> I finally noticed (using "strace"), that fetchmail contacted my socks5 proxy.
    >> 
    >> 
    >> I did some rtfm-ing,
    >> but I did not find a way to instruct fetchmail to *not* attempt contacting my socks5 proxy.

    RMG> Fetchmail has *no* native socks support.  

Currently I am convinced, your statement is incorrect.

But I rather have some sympathy for your suspicion,
as this magical and undescribed feature of fetchmail is certainly rather weird,
and fetchmail shouldn't behave like that.

Have you ever run fetchmail in a socks5 ready environment?
Give yourself a try and let's continue discussing the matter than!

    RMG> You're either running it
    RMG> with a socks wrapper (runsock/socksify)
    RMG> or have added this yourself (eg via ld.so.preload).

No, I don't, nothing like that.
(No socks wrapper, no LD_PRELOAD, no /etc/ld.so.preload, no ...)
I told you above: "I did not instruct my local fetchmail to make use of my socks5 proxy"
I mean, what I write.
And you read my statement, didn't you?!?

    RMG> It's hard to say though as you've provided no
    RMG> real information (version numbers, contents of configuration files,
    RMG> command lines used, anything really).

Alright, alright, yet another doubting Thomas ;-)

Can you see "SOCKS" here:

    [2007-03-15 14:11:49] johayek@HayekJ $ fetchmail --version
    This is fetchmail release 6.3.2+POP2+IMAP-GSS+RPA+NTLM+SDPS+SSL+OPIE+SOCKS+NLS.

    Copyright (C) 2002, 2003 Eric S. Raymond
    Copyright (C) 2004 Matthias Andree, Eric S. Raymond, Rob F. Funk, Graham Wilson
    Copyright (C) 2005 Matthias Andree, Sunil Shetye
    Copyright (C) 2006 Matthias Andree
    Fetchmail comes with ABSOLUTELY NO WARRANTY. This is free software, and you
    are welcome to redistribute it under certain conditions. For details,
    please see the file COPYING in the source or documentation directory.

    Fallback MDA: (none)
    Linux HayekJ 2.6.16.21-0.13-default #1 Mon Jul 17 17:22:44 UTC 2006 i686 i686 i386 GNU/Linux
    Taking options from command line and /home/jochen_hayek/.fetchmailrc
    Idfile is /home/jochen_hayek/.fetchids
    Fetchmail will show progress dots even in logfiles.
    Fetchmail will forward misaddressed multidrop messages to johayek.
    Fetchmail will direct error mail to the postmaster.


    close(3)                                = 0
    [...]
    open("/etc/socks.conf", O_RDONLY)       = 4
    [...]



And here we have some config file extract:

      skip shuttle.de
        via   "blablabla.shuttle.de" with proto IMAP and no dns tracepolls
        user "jh9999" there with password "PASSWORD" is johayek here
        options
        ssl
          sslproto tls1
          sslfingerprint "D9:83:30:EA:3B:A5:02:A2:D6:72:1D:B7:AB:C3:30:CB"
        fetchall
        stripcr
        dropstatus
        dropdelivered
        warnings 3600
        expunge 20
        folders imap/folder-misc/_to-be-downloaded,imap/folder/prio-4
        properties "'mailbox_from':'INBOX','mailbox_dir':'imap','mailbox_dir_separator':'/'"
        antispam 571
        no rewrite
        pass8bits


And here we have some "strace" output:

    [2007-03-15 13:30:59] johayek@HayekJ $ strace fetchmail shuttle.de
    execve("/usr/bin/fetchmail", ["fetchmail", "shuttle.de"], [/* 112 vars */]) = 0
    brk(0)                                  = 0x808d000
    mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7fb3000
    access("/etc/ld.so.preload", R_OK)      = -1 ENOENT (No such file or directory)
    open("/usr/local/lib/tls/i686/sse2/libsocks.so.0", O_RDONLY) = -1 ENOENT (No such file or directory)
    open("/usr/local/lib/tls/i686/libsocks.so.0", O_RDONLY) = -1 ENOENT (No such file or directory)
    open("/usr/local/lib/tls/sse2/libsocks.so.0", O_RDONLY) = -1 ENOENT (No such file or directory)
    open("/usr/local/lib/tls/libsocks.so.0", O_RDONLY) = -1 ENOENT (No such file or directory)
    open("/usr/local/lib/i686/sse2/libsocks.so.0", O_RDONLY) = -1 ENOENT (No such file or directory)
    open("/usr/local/lib/i686/libsocks.so.0", O_RDONLY) = -1 ENOENT (No such file or directory)
    open("/usr/local/lib/sse2/libsocks.so.0", O_RDONLY) = -1 ENOENT (No such file or directory)
    open("/usr/local/lib/libsocks.so.0", O_RDONLY) = -1 ENOENT (No such file or directory)
    open("/usr/lib/tls/i686/sse2/libsocks.so.0", O_RDONLY) = -1 ENOENT (No such file or directory)
    open("/usr/lib/tls/i686/libsocks.so.0", O_RDONLY) = -1 ENOENT (No such file or directory)
    open("/usr/lib/tls/sse2/libsocks.so.0", O_RDONLY) = -1 ENOENT (No such file or directory)
    open("/usr/lib/tls/libsocks.so.0", O_RDONLY) = -1 ENOENT (No such file or directory)
    open("/usr/lib/i686/sse2/libsocks.so.0", O_RDONLY) = -1 ENOENT (No such file or directory)
    open("/usr/lib/i686/libsocks.so.0", O_RDONLY) = -1 ENOENT (No such file or directory)
    open("/usr/lib/sse2/libsocks.so.0", O_RDONLY) = -1 ENOENT (No such file or directory)
    open("/usr/lib/libsocks.so.0", O_RDONLY) = 3
    read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0 O\0\000"..., 512) = 512
    [...]
    open("/etc/socks.conf", O_RDONLY)       = 4
    fstat64(4, {st_mode=S_IFREG|0644, st_size=4374, ...}) = 0
    mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7bb3000
    read(4, "# $Id: socks.conf,v 1.28 2001/12"..., 8192) = 4374
    read(4, "", 4096)                       = 0
    [...]

Re: [fetchmail-users] fetchmail multidrop problem

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

Keep the traffic on the list.  If you don't then I'll simply ignore
any email from you...

On 3/15/07, jay shi <jay...@ya...> wrote:
> Hi Rob
>             Thanks For ur quick response
>             Now i ugrade the fetchmail to fetchmail 6.3.7 but still i am
> strugling
>
>             I used the option "envelope Delivered-To 1" in .fetchmailrc file
>
>             But while running the getmail it giving me the sysntax error

And what error would that be?  My crystal ball is broken today.

>             In man fetchmail  i got the following option
>
> -E <line> | --envelope <line>
>               (Keyword: envelope; Multidrop only)
>               In the configuration file, an enhanced syntax is used:
>               envelope [<count>] <line>
>
>             what could be the  correct option ? for skipping lines

Ah, maybe it's "envelope 1 Delivered-To".  I've never come across a
mail system that's broken enough to insert multiple delivered to
headers before :)

-- 
                 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] injecting message and header rewrite

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

Payal Rathod schrieb am 2007-03-14:

> Well, I found it out -D domain is what I need. Thanks anyways.
> And Matthias, qmail rocks ;)

And Earth is a disc and the Moon is made of green cheese.

SCNR

-- 
Matthias Andree

Re: [fetchmail-users] injecting message and header rewrite

[Payal R. <pay...@sc...>]

On Mon, Mar 12, 2007 at 11:42:58PM +0100, Matthias Andree wrote:
> > Any ideas on what is wrong? The rc file is just a simple 2 line test 
> > file like below,
> > poll domain with proto pop3, nodns :
> > user payal with pass word to payal here ......
> 
> ...you aren't forwarding to server Y :-)
> 
> There are several options to change behavior, not the least of which
> one of the --smtp options.

Well, I found it out -D domain is what I need. Thanks anyways.
And Matthias, qmail rocks ;)

With warm regards,
-Payal

Re: [fetchmail-users] fetchmail multidrop problem

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

On 3/14/07, jay shi <jay...@ya...> wrote:

> I am trying to fetch mail on local server of Fedora core 2 fetchmail
> fetchmail-6.2.5-2
> I also tested the same things with Centos 4.4 along with fetchmail
> fetchmail-6.2.5-6.el4.5

Standard advice - upgrade to the latest version (6.3.7 ISTR).

> When i send mail from Out side to this to both user.
> now when i see the header of foo's mail header it
> shows Delivered-To: ex...@ab... alog with
> respecting id.
> that is Delivered-To: fo...@ab....
> how can i remove Delivered-To: ex...@ab... line
> from header while downloading

Fetchmail doesn't do that - however as documented in the manual you
can provide a count of the number of lines to ignore.  In your case
you'd use "Envelope Delivered-To 1"

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