headers
Jerry | 5 Apr 2010 14:48
Face
Favicon

Query status=2 (SOCKET)

FreeBSD-7.3 OS

I am continually finding this message in the "fetchmail.log".

fetchmail: Query status=2 (SOCKET)

The following is a snippet of the output when this message occurs. I
included connects from both sides of the message since I am not sure
where it is originating from. The real email address has be obfuscated.

fetchmail: 6.3.15 querying pop.aol.com (protocol POP3) at Mon Apr  5
08:01:45 2010: poll started fetchmail: Trying to connect to
205.188.155.221/110...connected. fetchmail: POP3< +OK POP3 ready
fetchmail: POP3> CAPA
fetchmail: POP3< +OK Capability list follows
fetchmail: POP3< TOP
fetchmail: POP3< USER
fetchmail: POP3< STLS
fetchmail: POP3< .
fetchmail: POP3> STLS
fetchmail: POP3< +OK
fetchmail: Issuer Organization: America Online Inc.
fetchmail: Issuer CommonName: AOL Member CA
fetchmail: Server CommonName: imap.aol.com
fetchmail: Subject Alternative Name: imap.aol.com
fetchmail: Subject Alternative Name: imap.aim.com
fetchmail: Subject Alternative Name: imap.cs.com
fetchmail: Subject Alternative Name: client.imap.aol.com
fetchmail: Subject Alternative Name: imap.au.aol.com
fetchmail: Subject Alternative Name: imap.ar.aol.com
(Continue reading)

Permalink | Reply | 1 comment |
headers
Rob MacGregor | 5 Apr 2010 17:46
Picon
Gravatar

Re: Query status=2 (SOCKET)

On Mon, Apr 5, 2010 at 13:48, Jerry <fetchmail.user <at> seibercom.net> wrote:
> FreeBSD-7.3 OS
>
> I am continually finding this message in the "fetchmail.log".
>
> fetchmail: Query status=2 (SOCKET)

If you haven't already, search the list archive - this type of error
comes up regularly.

<---SNIP--->
> fetchmail: 6.3.15 querying pop.aol.com (protocol POP3) at Mon Apr  5
> 08:01:45 2010: poll started fetchmail: Trying to connect to
> fetchmail: 6.3.15 querying pop.aol.com (protocol POP3) at Mon Apr  5
> 08:01:46 2010: poll completed fetchmail: Query status=2 (SOCKET)
<---SNIP--->

Looks like a temporary network error talking to the remote POP server.
 There's nothing you can do about these if the cause is outside your
local network (which it usually is).

--

-- 
                 Please keep list traffic on the list.

Rob MacGregor
      Whoever fights monsters should see to it that in the process he
        doesn't become a monster.                  Friedrich Nietzsche
_______________________________________________
fetchmail-users mailing list
fetchmail-users <at> lists.berlios.de
(Continue reading)

Permalink | Reply | 0 comments |
headers
Richard Brooksby | 6 Apr 2010 11:43
Favicon
Gravatar

Add response to "SMTP listener refused delivery" message

Hello.

I could not find a place to make a suggestion for an improvement to fetchmail, so I joined this list.  Please
let me know if there is a better place.

Fetchmail will produce a message like this:

  fetchmail: SMTP listener refused delivery

when a sendmail milter blocks a message for some reason.  (We use SpamAssassin Clam-AV milters.)

It would be useful if we could see the SMTP response code and message as part of this message from fetchmail. 
It is visible if you run fetchmail with verbose output, but this would require extra parsing.  It seems like
a good idea to me if the response was always included in this normal message, since I think anyone would want
to know what caused the message to be refused.

In our case, we'd like to be sure that the messages were being dropped are spam rejections.

Thanks.

---
Richard Brooksby <rb <at> ravenbrook.com>  Senior Consultant
Ravenbrook Limited <http://www.ravenbrook.com/>
Voice: +44 777 9996245  Fax: +44 870 1641432
AIM: hothquist  Yahoo: gresque  Jabber: hothquist <at> jabber.org
LinkedIn: <http://www.linkedin.com/in/richardbrooksby>
Permalink | Reply | 1 comment |
headers
Matthias Andree | 6 Apr 2010 21:06
Picon
Picon

Re: Add response to "SMTP listener refused delivery" message

Am 06.04.2010, 11:43 Uhr, schrieb Richard Brooksby:

> Hello.
>
> I could not find a place to make a suggestion for an improvement to  
> fetchmail, so I joined this list.  Please let me know if there is a  
> better place.
>
> Fetchmail will produce a message like this:
>
>   fetchmail: SMTP listener refused delivery
>
> when a sendmail milter blocks a message for some reason.  (We use  
> SpamAssassin Clam-AV milters.)
>
> It would be useful if we could see the SMTP response code and message as  
> part of this message from fetchmail.  It is visible if you run fetchmail  
> with verbose output, but this would require extra parsing.  It seems  
> like a good idea to me if the response was always included in this  
> normal message, since I think anyone would want to know what caused the  
> message to be refused.

Indeed the proposition is useful, but is not trivial to do given how  
information flows inside fetchmail; I doubt I can apply it to a fetchmail  
6.3.X version easily.

I'll note this in TODO.txt, but for a quick fix, somebody would have to  
come up with a patch.

--

--
(Continue reading)

Permalink | Reply | 0 comments |
headers
Matthias Andree | 6 Apr 2010 23:08
Picon
Picon

fetchmail 6.3.16 bugfix release

Greetings,

I am announcing the release of fetchmail 6.3.16.  This new stable
version of fetchmail fixes --interface support broken in 6.3.15 and
improves SSL compatibility with some site; details below.

The software is available from:
<http://developer.berlios.de/project/showfiles.php?group_id=1824>

The fetchmail home pages are:
<http://www.fetchmail.info/>  or  <http://fetchmail.berlios.de/>

These are the relevant changes since the previous release.  Unless
otherwise noted, changes to this release were made by Matthias Andree:

fetchmail-6.3.16 (released 2010-04-06, 25574 LoC):

# BUG FIX
* Fix --interface option, broken in 6.3.15. Reported by Vladmimir Stavrinov.
  Fixes Debian Bug #576717.

# CHANGE
* Call OpenSSL_add_all_algorithms(). This is needed to support non-mandatory
  algorithms in certificates. Sjoerd Simons, to fix Debian Bug #576430.
  OpenSSL 0.9.8* does not load - for instance - the SHA256 digest by default.
  Reported as OpenSSL RT#2224.

By popular demand, diffs from the previous release have been omitted.

--

--
(Continue reading)

Permalink | Reply | 0 comments |
headers
Nicolas RENAULT | 12 Apr 2010 13:40

attached files retrievement

Hello,
i want to retrieve mail body in text file and save attached file. 
Actually i get mail body but fetchmail write the attached file in the text file with mail body.

 text file exemple after fetchmail : 

Content-Type: multipart/alternative;
boundary="_000_EF5BAFE7AB8A3744A1226F270380E4DA5C093FACDBPOBOXUSPHOTOM_"
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

MAIL body 

Content-Type: application/vnd.ms-excel; name="Status-ST-Tours.xls"
Content-Description: Status-ST-Tours.xls
Content-Disposition: attachment; filename="Status-ST-Tours.xls"; size=45056;
creation-date="Wed, 25 Nov 2009 10:38:55 GMT";
modification-date="Tue, 16 Mar 2010 09:51:30 GMT"
Content-Transfer-Encoding: base64

attached file binary code

configuration :
my OS: red hat
sender OS : windows

the problem is : 
How can i retrieve the attached file ?

thank you.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Matthias Andree | 12 Apr 2010 15:09
Picon
Picon

Re: attached files retrievement

Am 12.04.2010 13:40, schrieb Nicolas RENAULT:
> Hello,
> i want to retrieve mail body in text file and save attached file. 
> Actually i get mail body but fetchmail write the attached file in the text file with mail body.
>  
>  text file exemple after fetchmail : 
>  
> Content-Type: multipart/alternative;
> boundary="_000_EF5BAFE7AB8A3744A1226F270380E4DA5C093FACDBPOBOXUSPHOTOM_"
> Content-Type: text/plain; charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
> 
> MAIL body 
>  
> Content-Type: application/vnd.ms-excel; name="Status-ST-Tours.xls"
> Content-Description: Status-ST-Tours.xls
> Content-Disposition: attachment; filename="Status-ST-Tours.xls"; size=45056;
> creation-date="Wed, 25 Nov 2009 10:38:55 GMT";
> modification-date="Tue, 16 Mar 2010 09:51:30 GMT"
> Content-Transfer-Encoding: base64
> 
> attached file binary code
>  
> configuration :
> my OS: red hat
> sender OS : windows
>  
> the problem is : 
> How can i retrieve the attached file ?
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Robert Holtzman | 13 Apr 2010 01:49
Picon

sperate servers

I'm trying to set up .fetchmailrc to poll 2 mail servers but only route 
one to Procmail, the other going to /var/mail/≤username>. Everything 
I've been able to find online says if no mda is specified the messages 
go to the default mailbox, which is what I want. The problem is that 
even though I only specify the mda for one server messages from both are 
routed through it.

My .fetchmailrc is:

poll "pop.sonic.net"
protocol pop3 
username "xxxxxx" 
password "xxxxxxxx"
mimedecode 
#
#
poll "pop.west.cox.net"
protocol pop3 
username "xxxxxx" 
password "xxxxxxxxxx" 
mimedecode 
mda "/usr/bin/procmail -f -"

One solution would be to specify separate .procmailrc files but
1) that's clumsy and 2) I don't know how. After reading the Procmail man 
page I tried specifying separate files but couldn't make it work.

Any pointers appreciated.

--

--
(Continue reading)

Permalink | Reply | 7 comments |
headers
Rob MacGregor | 13 Apr 2010 10:32
Picon
Gravatar

Re: sperate servers

On Tue, Apr 13, 2010 at 00:49, Robert Holtzman <holtzm <at> cox.net> wrote:
> I'm trying to set up .fetchmailrc to poll 2 mail servers but only route one
> to Procmail, the other going to /var/mail/≤username>. Everything I've been
> able to find online says if no mda is specified the messages go to the
> default mailbox, which is what I want. The problem is that even though I
> only specify the mda for one server messages from both are routed through
> it.
>
> My .fetchmailrc is:
>
> poll "pop.sonic.net"
> protocol pop3 username "xxxxxx" password "xxxxxxxx"
> mimedecode #

Mail delivered to your local SMTP server, which may be using procmail
for delivery.

> poll "pop.west.cox.net"
> protocol pop3 username "xxxxxx" password "xxxxxxxxxx" mimedecode mda
> "/usr/bin/procmail -f -"

Mail delivered to procmail.

> One solution would be to specify separate .procmailrc files but
> 1) that's clumsy and 2) I don't know how. After reading the Procmail man
> page I tried specifying separate files but couldn't make it work.
>
> Any pointers appreciated.

Fetchmail has no control over what happens after it hands the email to
(Continue reading)

Permalink | Reply | 6 comments |
headers
Ewald Jenisch | 13 Apr 2010 13:51
Picon

No pop/ssl since fetchmail 6.3.16

Hi,

I've set up fetchmail with ssl as per
http://bronski.net/data/fetchmail-deu.php and this has worked ever
since.

However following a recent upgrade of my FreeBSD system (7.3)
including fetchmail (-> 6.3.16) and openssl (-> 1.0.0) I've got
problems fetching mail from my pop server via ssl:

Here's what I get when I try to pull mail off my pop server:

------------------------------ < Cut here > ------------------------------

Enter password for eje <at> area51.myco.co.at: 
fetchmail: Server certificate verification error: self signed certificate
34381474120:error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed:s3_clnt.c:1056:
fetchmail: SSL connection failed.
fetchmail: socket error while fetching from eje <at> area51.myco.co.at
fetchmail: Query status=2 (SOCKET)
Error while opening POP-socket

------------------------------ < Cut here > ------------------------------

BTW, on the pop server there have been no changes over the past few
months (I'm sure, because I also administer this server), so I'm
pretty sure that this has something to do with fetchmail. Fetchmail
does *not* run in daemon mode.

I've tried re-installing the server cert on my client several times -
(Continue reading)

Permalink | Reply | 2 comments |

Gmane