fetchmail-users — User questions and discussion

Re: [fetchmail-users] Fetchmail Socket error on a satellite connection

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

Once more, with feeling - keep the traffic on the list so that others
can benefit from this in the future and provide assistance.  I'm not
here to personally support you...

On 4/12/07, Ben Jsh <be...@po...> wrote:
>
> OK.
> I am running a Linux what other ways or something else I can do to tune the network.

Which version, what kernel?  If you're having to ask then you need the
help of somebody who really knows what they're doing, and has access
to your systems.  You/they will need to look at the various reported
stats and errors from netstat.  A quick indicator would be from:

    netstat -s | egrep -i "retrans|error"

A high number of errors or retransmissions (particularly if they keep
growing rapidly) indicate probable network problems.

Keep in mind that there are 2 parties in all of this - it may well be
that the real problem is at the other end, over which you have no
control.

> There is a constant ping on the line between 650-1500 MS when I ping google and on the adsl it is 40 ms all the time !?!

Ping stats aren't a good measure of anything beyond, at best, latency.
 The difference is because with the satellite link you're travelling a
*lot* further (about 45,000 miles from ground to satellite and back -
almost twice the circumference of the earth).

> They also told me another error they had from the windows system.
>
> Why do the fetchmail not silently reconnect like outlook if it solves problems?

Maybe it solves the problem, maybe it doesn't.  General unix
philosophy is to not hide details from the end user.  If it's
intermittent then the next poll will solve it.  If it isn't, you
probably want to know when it really started.

> On the windows box they sometimes get
>  mail box contains 85 messages with a total size of 18980048
> receiving message no 27 (6755b)
> connection error (winsock: returned by WSARecv or WSARecvFrom to indicate
> the remote party has initiated a graceful shutdown sequence)
>
> So it seems their windows also got problems?

Well, it seems your satellite link has the problem, which both myself
and Matthias have been saying from the start...

-- 
                 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 Socket error on a satellite connection

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

[ Keep it on the list please ]

On 4/12/07, Ben Jsh <be...@po...> wrote:
> Dear Rob,
>
> On the adsl line the same box works fine.

So we've ruled out fetchmail as the cause/source, again.

> And if they use outlook on the satellite it works fine so they say it is the fetchmail.

A sign of people not willing to look into the problem :)

It could be:

1) Windows network tuning is different, so it handles the asymmetry better
2) Outlook silently reconnects and you never know there was a problem
3) Something else

> The -vvv
> gives me:
>
<---SNIP--->
> fetchmail: socket error while fetching from

Network/communication failure, nothing fetchmail can do (assuming
you've not snipped too much - it would be better if you were to
replace what you're cutting out with, say, xxxx so we know where
you've removed stuff).

Somebody probably needs to look at the network settings of your (I'm
guessing) Linux box, (you haven't said) vs those of the Windows box.
They also want to do lots of packet capture and see what happens
when/if the connection dies on Outlook.

-- 
                 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 Socket error on a satellite connection

[Ben J. <be...@po...>]

Dear Rob,

On the adsl line the same box works fine.
And if they use outlook on the satellite it works fine so they say it is the fetchmail.

The -vvv
gives me:


Remember it happens on random messages and if I go in via webmail and delete this one it can happen again in the future on another one.

fetchmail: POP3> LIST 12
fetchmail: POP3< +OK 12 3073
fetchmail: POP3> TOP 12 99999999
fetchmail: POP3< +OK
reading message :12 of 126 (3073 octets)
About to rewrite Return-Path: <>
Rewritten version is Return-Path: <>

About to rewrite From: =?windows-1251?B?wujq8u7wIMLg6+Xt8ujt7uLo9w==?= <a
Rewritten version is From: =?windows-1251?B?wujq8u7wIMLg6+Xt8ujt7uLo9w==?= <

About to rewrite Reply-To: 
Rewritten version is Reply-To: 

About to rewrite To: Bt 
Rewritten version is To: Bt 

fetchmail: socket error while fetching from 
fetchmail: 6.3.8 querying (protocol POP3) at Thu Apr 12 14:28:25 2007: poll completed
fetchmail: discarding new UID list
fetchmail: Query status=2 (SOCKET)
fetchmail: Writing fetchids file.
fetchmail: normal termination, status 2
fetchmail: Writing fetchids file.

> ----- Original Message -----
> From: "Rob MacGregor" <rob...@gm...>
> To: fet...@li...
> Subject: Re: [fetchmail-users] Fetchmail Socket error on a satellite	connection
> Date: Thu, 12 Apr 2007 13:26:04 +0100
> 
> 
> On 4/12/07, Ben Jsh <be...@po...> wrote:
> > Dear All,
> > I am having trouble downloading mail via POP3 with the latest 
> > 6.3.8 and all versions.
> >
> > I tried popping the same account from a adsl line and it worked 
> > but when I do it over the satellite connection it fails.
> 
> Which says that you have a comms problem and that it isn't software
> related (on the assumption that you're talking about the same system
> running fetchmail).  At a rough guess it is probably due to the highly
> asymmetric nature of the link.  There isn't going to be anything you
> can do to fetchmail to fix this.
> 
> You *may* be able to tune the network settings on your OS (whatever it
> is) to compensate.
> 
> <---SNIP--->
> > fetchmail: Query status=2 (SOCKET)
> > fetchmail: Deleting fetchids file.
> > fetchmail: normal termination, status 2
> > fetchmail: Deleting fetchids file.
> 
> Socket errors are almost always down to your network connection, though
> sometimes due to the remote system (see the FAQ).  I've never yet seen
> them being caused by fetchmail.
> 
> --
>                   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 Socket error on a satellite connection

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

On 4/12/07, Ben Jsh <be...@po...> wrote:
> Dear All,
> I am having trouble downloading mail via POP3 with the latest 6.3.8 and all versions.
>
> I tried popping the same account from a adsl line and it worked but when I do it over the satellite connection it fails.

Which says that you have a comms problem and that it isn't software
related (on the assumption that you're talking about the same system
running fetchmail).  At a rough guess it is probably due to the highly
asymmetric nature of the link.  There isn't going to be anything you
can do to fetchmail to fix this.

You *may* be able to tune the network settings on your OS (whatever it
is) to compensate.

<---SNIP--->
> fetchmail: Query status=2 (SOCKET)
> fetchmail: Deleting fetchids file.
> fetchmail: normal termination, status 2
> fetchmail: Deleting fetchids file.

Socket errors are almost always down to your network connection, though
sometimes due to the remote system (see the FAQ).  I've never yet seen
them being caused by fetchmail.

-- 
                 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 Socket error on a satellite connection

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

Ben Jsh schrieb:

> I am having trouble downloading mail via POP3 with the latest 6.3.8 and all versions.
> 
> I tried popping the same account from a adsl line and it worked but when I do it over the satellite connection it fails.

So the satellite link is the first suspect, no? :-)

> When I connect to the pop3 server some mails are downloaded but with some it is stopping.
> Not sure what is causing it.

How does the satellite connection differ from the ADSL?

...

> I tried everything also setting timeouts and other stuff but it keeps crashing.
> Please help!
> I also tried other pop3 servers and accounts and I just keep getting on random messages

You quoted the SMTP dialog, but your problem is apparently POP3.
It shows the error, but not the preceding events.

Perhaps there's something obvious in the POP3 logging, but if not, sorry
- check http://www.fetchmail.info/fetchmail-FAQ.html#G3 for information
lacking from your report (beyond the differences sat/dsl above) and run
fetchmail -vvv to see if you get POP3 logging.

I can't promise there's anything fetchmail could do about the issue though.

HTH
MA

[fetchmail-users] Fetchmail Socket error on a satellite connection

[Ben J. <be...@po...>]

Dear All,
I am having trouble downloading mail via POP3 with the latest 6.3.8 and all versions.

I tried popping the same account from a adsl line and it worked but when I do it over the satellite connection it fails.

When I connect to the pop3 server some mails are downloaded but with some it is stopping.
Not sure what is causing it.

Trying to connect to 127.0.0.1/25...connected.
fetchmail: SMTP< 220 xxx
fetchmail: SMTP> EHLO xxx
fetchmail: SMTP< 250-p pleased to meet you
fetchmail: SMTP< 250-ENHANCEDSTATUSCODES
fetchmail: SMTP< 250-PIPELINING
fetchmail: SMTP< 250-8BITMIME
fetchmail: SMTP< 250-SIZE
fetchmail: SMTP< 250-DSN
fetchmail: SMTP< 250-DELIVERBY
fetchmail: SMTP< 250 HELP
fetchmail: forwarding to localhost
fetchmail: SMTP> MAIL FROM: BODY=8BITMIME SIZE=100083
fetchmail: SMTP< 250 2.1.0 ... Sender ok
fetchmail: SMTP> RCPT TO:<
fetchmail: SMTP< 250 2.1.5 <>... Recipient ok
fetchmail: SMTP> DATA
fetchmail: SMTP< 354 Enter mail, end with "." on a line by itself
#****************************.*fetchmail: socket error while fetching from 
fetchmail: 6.3.8 querying (protocol POP3) at Mon Apr 9 07:57:48 2007: poll completed
fetchmail: Query status=2 (SOCKET)
fetchmail: Deleting fetchids file.
fetchmail: normal termination, status 2
fetchmail: Deleting fetchids file.

I tried everything also setting timeouts and other stuff but it keeps crashing.
Please help!
I also tried other pop3 servers and accounts and I just keep getting on random messages

reading message 12 of 60 (3073 octets).fetchmail: socket error while fetching from 
fetchmail: Query status=2 (SOCKET)



=

Re: [fetchmail-users] Exchange Server 2003 IMAP NTLM - can someone offer me a test account?

[Ben R. <Be...@mu...>]

Matthias Andree wrote:
> Ben Russo schrieb:
>   
>> Help?
>>
>> I can open Outlook or use a browser to log into my account
>> So I know that my username and password are correct.
>> (I have tried to modify some of the info like password hashes and 
>> usernames/hostnames to maintain some security for my company)
>>
>> Username:  user1
>> Domain:    win2k
>>
>> This works fine.
>>
>>
>> When I try to login to the server it fails?
>>
>> [root@linuxdesktop ~]# /usr/local/bin/fetchmail -v -v -v -c  -p IMAP -L 
>> Fetchlog --auth ntlm -u "user1@win2k" mailserver.win2k.domain.com
>>
>>     
>   
Thanks for your reply!  What a great user community.
And thanks to Mr. MacGregor too.

With a little help from the Exchange Server admin I got squared away.
He had to turn on logging on the server, and then checked the log.
We found error 0x80040920 every time I tried to authenticate.
    http://support.microsoft.com/kb/296387

He opened up my account in the Windows Directory server (or Exchange server)
and changed the mailbox alias so that it matched my Windows Login name
"user1"
The mailbox alias was  "User.1"  (where User is my first name and "1" 
was my last name"
He also adjusted the primary and secondary SMTP alias, but I don't know 
if that was necessary.
It was primary SMTP Us...@do...
and secondary smtp  us...@do...
He swapped the two.

Immediately after that it works fine.
So I am all set.

BTW, it can also fetch other folders in *my* mailbox.
with

      -r "INBOX,Spam/Spam - Quarantine"

on the command line.

My .fetchmailrc looks like this:

set postmaster "linuxuser"
set bouncemail
set no spambounce
set properties ""
set logfile /home/linuxuser/.fetchmaillog
set no syslog
poll mailserver.win2k.domain.com with proto IMAP, auth ntlm user 
"user1@win2k" with pass 'MyPassWord' is linuxuser here options fetchall

My crontab looks like:

*       *       *       *       *        /usr/local/bin/fetchmail -L 
/home/linuxuser/.fetchmaillog -t 10 -B 10 -r "INBOX,Spam/Spam - 
Quarantine" > /dev/null


Seems to work GREAT!

Thanks again.

Re: [fetchmail-users] Exchange Server 2003 IMAP NTLM - can someone offer me a test account?

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

Ben Russo schrieb:
> Help?
> 
> I can open Outlook or use a browser to log into my account
> So I know that my username and password are correct.
> (I have tried to modify some of the info like password hashes and 
> usernames/hostnames to maintain some security for my company)
> 
> Username:  user1
> Domain:    win2k
> 
> This works fine.
> 
> 
> When I try to login to the server it fails?
> 
> [root@linuxdesktop ~]# /usr/local/bin/fetchmail -v -v -v -c  -p IMAP -L 
> Fetchlog --auth ntlm -u "user1@win2k" mailserver.win2k.domain.com
> fetchmail: WARNING: Running as root is discouraged.
> Enter password for user1@wi...@ma...:
> fetchmail: 6.3.8 querying mailserver.win2k.domain.com (protocol IMAP) at 
> Tue 10 Apr 2007 01:54:03 PM EDT: poll started
> fetchmail: Trying to connect to 172.17.7.217/143...connected.
> fetchmail: IMAP< * OK Microsoft Exchange Server 2003 IMAP4rev1 server 
> version 6.5.7638.1 (mailserver.win2k.domain.com) ready.
> fetchmail: IMAP> A0001 CAPABILITY
> fetchmail: IMAP< * CAPABILITY IMAP4 IMAP4rev1 IDLE LOGIN-REFERRALS 
> MAILBOX-REFERRALS NAMESPACE LITERAL+ UIDPLUS CHILDREN AUTH=NTLM
> fetchmail: IMAP< A0001 OK CAPABILITY completed.
> fetchmail: Protocol identified as IMAP4 rev 1
> fetchmail: IMAP> A0002 AUTHENTICATE NTLM
> fetchmail: IMAP< +
> NTLM Request:
>        Ident = NTLMSSP
>        mType = 1
>        Flags = 0000b207
>         User = user1
>       Domain = win2k
> fetchmail: IMAP> BIGxLONGxHASHxOFxCHARS
> fetchmail: IMAP< + BIGGERxLONGERxHASHxOFxCHARSxREALLYxLONG
> NTLM Challenge:
>        Ident = NTLMSSP
>        mType = 2
>       Domain = WIN2K
>        Flags = 02818205
>    Challenge = 63 47 0c 69 22 98 58 37
> NTLM Response:
>        Ident = NTLMSSP
>        mType = 3
>       LmResp = b6 b6 34 22 cd 1e 80 b1 23 d8 3f db aa be c3 45 9e e4 78 
> 6b f9 ac c4 aa
>       NTResp = 95 5a 76 22 71 12 fb b4 8e 26 0a 8a 22 eb 57 ec 49 ce d0 
> 45 ac 48 32 51
>       Domain = win2k
>         User = user1
>          Wks = user1
>         sKey =
>        Flags = 02818205
> fetchmail: IMAP> ANOTHERxBIGxLONGxHASHxOFxCHARSxREALLYxLONGxTOO
> fetchmail: IMAP< A0002 NO Logon failure: unknown user name or bad password.
> fetchmail: IMAP> A0003 *
> fetchmail: Authorization failure on user1@wi...@ma...
> fetchmail: IMAP> A0004 LOGOUT
> fetchmail: IMAP< A0003 BAD Protocol Error: "Unknown command found".
> fetchmail: IMAP< * BYE Microsoft Exchange Server 2003 IMAP4rev1 server 
> version 6.5.7638.1 signing off.
> fetchmail: IMAP< A0004 OK LOGOUT completed.
> fetchmail: 6.3.8 querying mailserver.win2k.domain.com (protocol IMAP) at 
> Tue 10 Apr 2007 01:54:03 PM EDT: poll completed
> fetchmail: normal termination, status 3

Ben,

sorry to hear of authentication troubles - apparently there's something
wrong in fetchmail. To my excuse, I have contradictory information as to
what goes into the Wks=... field and no authoritative reference on the
NTLM authentication dialogue.

Anyone: Can someone provide me a test account for IMAP access to an
Exchange 2003 server or point me to /authoritative/ documentation as to
the NTLM authentication in IMAP?
I only need IMAP access and a valid mailbox with perhaps a test message.
If you can offer that, please contact me off-list.
I can tunnel with OpenVPN, SSH or Cisco VPN if needed and perhaps also
IPSec.

My only NTLM-enabled servers I can test on are Cyrus IMAPd which are
apparently more forgiving than Exchange 2003.

Ben, if you could capture your Outlook's authentication procedure (DO
NOT USE SAVED PASSWORDS AND DO ENTER SOME BOGUS DATA INSTEAD SUCH AS
foobar- DO NOT USE YOUR REAL PASSWORD) with Wireshark (or Windump or
tcpdump - try windump -w output.dump -s 2000) zip the output file and
mail to me offlist.

Thanks.

Best regards,
Matthias Andree

Re: [fetchmail-users] Exchange Server 2003 IMAP NTLM

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

On 4/10/07, Ben Russo <be...@mu...> wrote:
> Help?
>
> I can open Outlook or use a browser to log into my account
> So I know that my username and password are correct.
> (I have tried to modify some of the info like password hashes and
> usernames/hostnames to maintain some security for my company)
>
> Username:  user1
> Domain:    win2k
>
> This works fine.
>
>
> When I try to login to the server it fails?
>
> [root@linuxdesktop ~]# /usr/local/bin/fetchmail -v -v -v -c  -p IMAP -L Fetchlog --auth ntlm -u "user1@win2k" mailserver.win2k.domain.com

Have you tried simple "user1" or "win2k\user1" (assuming that "win2k"
is the domain)?  It looks like you're not providing the username in an
expected format.

-- 
                 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] Exchange Server 2003 IMAP NTLM

[Ben R. <be...@mu...>]

Help?

I can open Outlook or use a browser to log into my account
So I know that my username and password are correct.
(I have tried to modify some of the info like password hashes and 
usernames/hostnames to maintain some security for my company)

Username:  user1
Domain:    win2k

This works fine.


When I try to login to the server it fails?

[root@linuxdesktop ~]# /usr/local/bin/fetchmail -v -v -v -c  -p IMAP -L 
Fetchlog --auth ntlm -u "user1@win2k" mailserver.win2k.domain.com
fetchmail: WARNING: Running as root is discouraged.
Enter password for user1@wi...@ma...:
fetchmail: 6.3.8 querying mailserver.win2k.domain.com (protocol IMAP) at 
Tue 10 Apr 2007 01:54:03 PM EDT: poll started
fetchmail: Trying to connect to 172.17.7.217/143...connected.
fetchmail: IMAP< * OK Microsoft Exchange Server 2003 IMAP4rev1 server 
version 6.5.7638.1 (mailserver.win2k.domain.com) ready.
fetchmail: IMAP> A0001 CAPABILITY
fetchmail: IMAP< * CAPABILITY IMAP4 IMAP4rev1 IDLE LOGIN-REFERRALS 
MAILBOX-REFERRALS NAMESPACE LITERAL+ UIDPLUS CHILDREN AUTH=NTLM
fetchmail: IMAP< A0001 OK CAPABILITY completed.
fetchmail: Protocol identified as IMAP4 rev 1
fetchmail: IMAP> A0002 AUTHENTICATE NTLM
fetchmail: IMAP< +
NTLM Request:
       Ident = NTLMSSP
       mType = 1
       Flags = 0000b207
        User = user1
      Domain = win2k
fetchmail: IMAP> BIGxLONGxHASHxOFxCHARS
fetchmail: IMAP< + BIGGERxLONGERxHASHxOFxCHARSxREALLYxLONG
NTLM Challenge:
       Ident = NTLMSSP
       mType = 2
      Domain = WIN2K
       Flags = 02818205
   Challenge = 63 47 0c 69 22 98 58 37
NTLM Response:
       Ident = NTLMSSP
       mType = 3
      LmResp = b6 b6 34 22 cd 1e 80 b1 23 d8 3f db aa be c3 45 9e e4 78 
6b f9 ac c4 aa
      NTResp = 95 5a 76 22 71 12 fb b4 8e 26 0a 8a 22 eb 57 ec 49 ce d0 
45 ac 48 32 51
      Domain = win2k
        User = user1
         Wks = user1
        sKey =
       Flags = 02818205
fetchmail: IMAP> ANOTHERxBIGxLONGxHASHxOFxCHARSxREALLYxLONGxTOO
fetchmail: IMAP< A0002 NO Logon failure: unknown user name or bad password.
fetchmail: IMAP> A0003 *
fetchmail: Authorization failure on user1@wi...@ma...
fetchmail: IMAP> A0004 LOGOUT
fetchmail: IMAP< A0003 BAD Protocol Error: "Unknown command found".
fetchmail: IMAP< * BYE Microsoft Exchange Server 2003 IMAP4rev1 server 
version 6.5.7638.1 signing off.
fetchmail: IMAP< A0004 OK LOGOUT completed.
fetchmail: 6.3.8 querying mailserver.win2k.domain.com (protocol IMAP) at 
Tue 10 Apr 2007 01:54:03 PM EDT: poll completed
fetchmail: normal termination, status 3

[fetchmail-users] fetchmail 6.3.8 security fix release

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

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

Greetings,

I am announcing the release of fetchmail 6.3.8. This new stable version
of fetchmail strengthens the APOP validator to make the
man-in-the-middle attack to be presented as CVE-2007-1558 more
difficult. It also fixes a regression from the 6.3.6 security patches
and further long-standing bugs.

Note that 6.3.8 is the last planned release on the 6.3 branch, further
planned fetchmail releases will take some time to appear and contain
larger changes.

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 in 6.3.8 since 6.3.7;
unless otherwise noted, changes to this release were made by Matthias Andree:

# ADVANCE WARNING OF FEATURES TO BE REMOVED OR CHANGED IN FUTURE VERSIONS
(There are no plans to remove these features from a 6.3.X release, but they may
be removed from a 6.4.0 or newer release.)
* The MX and host alias DNS lookups that fetchmail performs in multidrop mode
  are based on assumptions that are rarely met in practice, somewhat defective,
  deprecated and may be removed from a future fetchmail version.  They have
  never supported IPv6 (including IPv6-mapped IPv4).
  Non-DNS based alias keywords such as "aka" will remain in fetchmail.
* The monitor and interface options may be removed from a future fetchmail
  version as they are not reasonably portable.
* POP2 is obsolete, support will be removed from a future fetchmail version.
* RPOP is obsolete, support will be removed from a future fetchmail release.
* --sslcertck will become a default setting in a future fetchmail version.
* The multidrop To/Cc guessing code along with the fragile duplicate suppressor
  is deprecated and may be removed from a future release.
* The "envelope Received" option may be removed from a future release, because
  the Received header was never meant to be machine-readable, the format varies
  widely, and various other differences in behavior make parsing Received an
  unreliable undertaking. The envelope option as such will remain though, in
  order to support Delivered-To, X-Envelope-To, X-Original-To and similar.
  See also <http://home.pages.de/~mandree/mail/multidrop>.
* The --enable-fallback (fall back to MDA if MTA unavailable) will be removed
  from a future fetchmail release, because it makes fetchmail's behavior
  inconsistent and confusing.
* The "protocol auto" default inside fetchmail may be removed from a future
  fetchmail release. Explicit configuration of the protocol is recommended.
* Kerberos IV support may be removed from a future fetchmail release.
* SIGHUP wakeup support may be removed from a future fetchmail release and
  cause fetchmail to terminate - it was broken for many years.
* Support for operating systems that are not sufficiently POSIX compliant may be
  removed or operation on such systems may be suboptimal for future releases.

# SECURITY STRENGTHENING:
* Make the APOP challenge parser more distrustful and have it reject challenges
  that do not conform to RFC-822 msg-id format, in the hope to make mounting
  man-in-the-middle attacks (MITM) against APOP a bit more difficult.
  (CVE-2007-1558, reported by Gaëtan Leurent, published 2007-04-02 on Bugtraq)

  APOP is claimed insecure by Gaëtan Leurent for MITM scenarios for typical
  setups: based on MD5 collisions, it is purportedly possible to recover the
  first three characters of the shared secret (password), which would then make
  recovery of the shared secret a matter of hours or minutes; this would then
  enable the attacker to impersonate the client vis-à-vis the server.

  For further details, check
  * Gaëtan Leurent, "Message Freedom in MD4 and MD5 Collisions: Application
  to APOP", Fast Software Encryption 2007, Luxembourg. (Proceedings to appear in
  Springer's Lecture Notes on Computer Science.)
  * The mailing list discussion thread at
  <http://lists.berlios.de/pipermail/fetchmail-devel/2007-March/000887.html>

# 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.
* If SOCKS support was compiled in, add 'socks' to the feature_options Python
  list emitted in --configdump. Reported by Rob MacGregor.
* Do not crash with a null pointer dereference when opening the BSMTP file 
  fails. Improve error checking and reporting. Reported by Reto Schüttel,
  Debian Bug#416625. Fix based on a patch by Nico Golde.
* Make BSMTP output actually work, it would persistently fail with SOCKET error
  after writing the first header. Bug independently found and reported in
  excellent detail by Reto Schüttel, Debian Bug#416812.

# DOCUMENTATION:
* Add fetchmail-SA-2007-01.txt
* 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.
* Mention that --limit default is 0 bytes, which is special for "no limit".
* Corrected Robert M. Funk's name that I misspelled. My sincere apologies
  -- Matthias Andree.

# 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)
* BSMTP is mostly untested and errors can cause corrupt output.
* 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

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

iD8DBQFGFq68vmGDOQUufZURAidjAKCG9+TAjmMz7l/9KWFROKBqhyBLPgCg9hbo
KAMMlF17J1XRbB/rGR9uiSA=
=orbA
-----END PGP SIGNATURE-----

Re: [fetchmail-users] Bug#416282: Fetchmail oversized-messages warning could say more

[Michelle K. <lin...@fr...>]

Hello Nico and Dan,

a copy of this message goes directly to the <fetchmail> list
since I find, it is a realy good thing to have it availlable.

Am 2007-03-26 19:43:28, schrieb Nico Golde:
> Hi,
> * Dan Jacobson <ji...@ji...> [2007-03-26 19:03]:
> > Package: fetchmail
> > Version: 6.3.6-1
> > Severity: wishlist
> > 
> > Can't it give some hint about the sender, subject or something? Else
> > one often has to dialup one's modem another time just to find out.
> 
> You also have to if you want to download it.
> I don't see a real need for it. Let's assume you expect an 
> important mail by someone and you want to download it if you 
> get it. So with the sender address you can see it's the 
> important mail. Another user wants different information and 
> another a different information again. To make everyone 
> happy you can just download it...
> Kind regards
> Nico

Good E-Mail programs under Windows (YES), like Eudora, have a size-limit
function too.  If a Mail is bigger as the given value, the E-Mail-Program
download ONLY the Header and Add a text to it which telle the usr that
the Message had exceeded the fetchsize limit and show the real size.

So in fetchmail they can add something like:

----8<-----------------------------------------------------------------
From: Michelle Konzack <lin...@fr...>
To: Nico Golde <ni...@ng...>, 41...@bu...
Subject: Re: Bug#416282: Fetchmail oversized-messages warning could say more
Date: ....

!!! FETCHMAIL SIZE LIMIT WARNING !!!

The original messages exceeded the configured fetch size of
10 kBytes and was not downloaded.  If you want to download it,
please use fetchmail manualy with the option "--limit 0".

----8<-----------------------------------------------------------------


Thanks, Greetings and nice Day
    Michelle Konzack
    Systemadministrator
    Tamay Dogan Network
    Debian GNU/Linux Consultant


-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/
##################### Debian GNU/Linux Consultant #####################
Michelle Konzack   Apt. 917                  ICQ #328449886
                   50, rue de Soultz         MSN LinuxMichi
0033/6/61925193    67100 Strasbourg/France   IRC #Debian (irc.icq.com)

Re: [fetchmail-users] Fetchmail/Multiple Local Users/Multiple Email Accounts

[Lovell M. <lov...@gm...>]

On Apr 2, 2007, at 4:22 PM, Matthias Andree wrote:

> Lovell Mcilwain schrieb:
>
>> Sorry I didn't mean to forget to show that.  Here are the permissions
>> on that directory.
>>
>> [root@Linux ~]$ ls -ldb /var/mail/
>> drwxrwxr-x 2 root mail 4096 Apr  2 04:50 /var/mail/
>
> Might require stuffing user1 and user2 into the "mail" group
> (particularly if user1 is in that group and user2 isn't, although that
> group isn't shown for either of them).

So I have added both users to the mail group and now I am able to  
write to the mail spool for user2.  I guess its a combination of  
things but Im just not sure how it all started.

All in all I got all that I needed to get done done thanks to you guys.

Re: [fetchmail-users] Fetchmail/Multiple Local Users/Multiple Email Accounts

[Lovell M. <lov...@gm...>]

On Apr 2, 2007, at 4:22 PM, Matthias Andree wrote:

> Lovell Mcilwain schrieb:
>
>> Sorry I didn't mean to forget to show that.  Here are the permissions
>> on that directory.
>>
>> [root@Linux ~]$ ls -ldb /var/mail/
>> drwxrwxr-x 2 root mail 4096 Apr  2 04:50 /var/mail/
>
> Might require stuffing user1 and user2 into the "mail" group
> (particularly if user1 is in that group and user2 isn't, although that
> group isn't shown for either of them).

Ok I will check and add them both to the mail group.  I kinda find it  
weird that when I did this for user1 sometime ago, I didni't have to  
muck around with the mail file or permissions at all in t he /var/ 
mail directory , just the .fetchmail file in the ~/ directory.

I wonder if its possible I screwed up something on a larger scale

Re: [fetchmail-users] Fetchmail/Multiple Local Users/Multiple Email Accounts

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

Lovell Mcilwain schrieb:

> Sorry I didn't mean to forget to show that.  Here are the permissions  
> on that directory.
> 
> [root@Linux ~]$ ls -ldb /var/mail/
> drwxrwxr-x 2 root mail 4096 Apr  2 04:50 /var/mail/

Might require stuffing user1 and user2 into the "mail" group
(particularly if user1 is in that group and user2 isn't, although that
group isn't shown for either of them).

Re: [fetchmail-users] Fetchmail/Multiple Local Users/Multiple Email Accounts

[Lovell M. <lov...@gm...>]

On Apr 2, 2007, at 3:42 PM, Matthias Andree wrote:

> Lovell Mcilwain schrieb:
>>> Check the permissions of the procmail executable (is it setuid  
>>> root?)
>> -rwxr-xr-x 1 root mail 92452 Jul 12  2006 /usr/bin/procmail
>>> Check the permissions of /var/mail and /var/mail/user2.
>> user1
>> -rw-rw---- 1 user1 mail 77465038 Apr  2 14:22 /var/mail/user1
>>
>> user2
>> -rw-r--r-- 1 user2 mail 0 Apr  1 18:36 /var/mail/user2 (I had to
>> create this file by hand (touch user2) chown user2 / chgrp mail and
>> that was it for this one) in the comparison I can see that this might
>> be an issue.
>
> Maybe, but this isn't the whole picture.
> Try "chmod 0660 /var/mail/user2" to fix.
>
> Since you didn't show the /var/mail permissions,
> I can't say if that's sufficient though.'
Sorry I didn't mean to forget to show that.  Here are the permissions  
on that directory.

[root@Linux ~]$ ls -ldb /var/mail/
drwxrwxr-x 2 root mail 4096 Apr  2 04:50 /var/mail/

>
> HTH,
> Matthias

Re: [fetchmail-users] Fetchmail/Multiple Local Users/Multiple Email Accounts

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

On 4/2/07, Lovell Mcilwain <lov...@gm...> wrote:
<---SNIP working run--->
> I did turn off my IMAPS client before I tried this last test.

This suggests that your ISP only supports a single connection.  You
may find that it will allow multiple IMAP connections though - worth a
try.

-- 
                 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/Multiple Local Users/Multiple Email Accounts

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

Lovell Mcilwain schrieb:
>> Check the permissions of the procmail executable (is it setuid root?)
> -rwxr-xr-x 1 root mail 92452 Jul 12  2006 /usr/bin/procmail
>> Check the permissions of /var/mail and /var/mail/user2.
> user1
> -rw-rw---- 1 user1 mail 77465038 Apr  2 14:22 /var/mail/user1
> 
> user2
> -rw-r--r-- 1 user2 mail 0 Apr  1 18:36 /var/mail/user2 (I had to  
> create this file by hand (touch user2) chown user2 / chgrp mail and  
> that was it for this one) in the comparison I can see that this might  
> be an issue.

Maybe, but this isn't the whole picture.
Try "chmod 0660 /var/mail/user2" to fix.

Since you didn't show the /var/mail permissions,
I can't say if that's sufficient though.

HTH,
Matthias

Re: [fetchmail-users] Fetchmail/Multiple Local Users/Multiple Email Accounts

[Lovell M. <lov...@gm...>]

On Apr 2, 2007, at 2:30 PM, Rob MacGregor wrote:

> On 4/2/07, Lovell Mcilwain <lov...@gm...> wrote:
>>> 1) The output of "id" as each user
>> user1
>> uid=500(user1) gid=500(user1) groups=500(user1)
>> context=user_u:system_r:unconfined_t
>>
>> user2
>> uid=501(user2) gid=501(user2) groups=501(user2)
>> context=user_u:system_r:unconfined_t
>
> Ok, these really are 2 users (worth checking :>)
>
>> [user2@Linux ~]$ tail -f fetchmail.log
>> fetchmail: Lock-busy error on lmc...@wo...
>> fetchmail: POP3> QUIT
>> fetchmail: POP3< +OK signing off.
>> fetchmail: lock busy on server error while fetching from
>> lmc...@wo...
>> fetchmail: 6.3.6 querying @work.pop.com (protocol POP3) at Mon 02 Apr
>> 2007 02:15:38 PM EDT: poll completed
>> fetchmail: Query status=9 (LOCKBUSY)
>> fetchmail: Deleting fetchids file.
>> fetchmail: sleeping at Mon 02 Apr 2007 02:15:38 PM EDT for 300  
>> seconds
>> fetchmail: terminated with signal 15
>> fetchmail: Deleting fetchids file.
>
> Ok, how about the rest of the log.  Log snippets just waste my time.
>
fetchmail: 6.3.6 querying work.pop.com (protocol POP3) at Mon 02 Apr  
2007 03:18
:00 PM EDT: poll started
fetchmail: Trying to connect to 192.104.65.xx/995...connected.
fetchmail: Issuer Organization: VeriSign, Inc.
fetchmail: Issuer CommonName: VeriSign Class 3 Secure Server CA
fetchmail: Server CommonName: work.pop.com
fetchmail: work.pop.com key fingerprint: 13:7B:A9:9C:09:7F:5A: 
97:AD:D3:1D:71:5F
:E8:FE:C5
fetchmail: Server certificate verification error: unable to get local  
issuer cer
tificate
fetchmail: Server certificate verification error: certificate not  
trusted
fetchmail: Server certificate verification error: unable to verify  
the first cer
tificate
fetchmail: POP3< +OK Mail server is ready.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK Capability list follows
fetchmail: POP3< TOP
fetchmail: POP3< USER
fetchmail: POP3< LOGIN-DELAY 0
fetchmail: POP3< EXPIRE 0
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< AUTH-RESP-CODE
fetchmail: POP3< X-MANGLE
fetchmail: POP3< X-MACRO
fetchmail: POP3< X-LOCALTIME Sat, 31 Mar 2007 19:36:03 -0400
fetchmail: POP3< IMPLEMENTATION Qpopper-version-4.0.5
fetchmail: POP3< .
fetchmail: POP3> USER lmcilwain
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< +OK lmcilwain has 10445 visible messages (1 hidden)  
in 98056903
6 octets.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 10445 980569036
fetchmail: POP3> LAST
fetchmail: POP3< +OK 10446 is the last read message.
fetchmail: 10445 messages for lmcilwain at vip.opnet.com (980569036  
octets).
fetchmail: skipping message lmc...@wo...:1 not flushed
fetchmail: skipping message lmc...@wo...:2 not flushed
fetchmail: skipping message lmc...@wo...:3 not flushed
fetchmail: skipping message lmc...@wo...:4 not flushed
fetchmail: skipping message lmc...@wo...:5 not flushed
fetchmail: skipping message lmc...@wo...:6 not flushed
fetchmail: skipping message lmc...@wo...:7 not flushed
fetchmail: skipping message lmc...@wo...:8 not flushed
fetchmail: skipping message lmc...@wo...:9 not flushed
fetchmail: skipping message lmc...@wo...:10 not flushed
...... Same fetchmail message different ID.....
fetchmail: skipping message lmc...@wo...:10445 not flushed
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Pop server at work.pop.com signing off.
fetchmail: 6.3.6 querying work.pop.com (protocol POP3) at Mon 02 Apr  
2007 03:22:24 PM EDT: poll comp
leted
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: Deleting fetchids file.
fetchmail: sleeping at Mon 02 Apr 2007 03:22:24 PM EDT for 300 seconds
fetchmail: terminated with signal 15
fetchmail: Deleting fetchids file.


> Note that the log does suggest the problem is that you have multiple
> programs connecting to the mailbox and your work's POP server only
> supports one at a time.
I did turn off my IMAPS client before I tried this last test.

>
> -- 
>                  Please keep list traffic on the list.
>
> Rob MacGregor
>       Whoever fights monsters should see to it that in the process he
>         doesn't become a monster.                  Friedrich Nietzsche
> _______________________________________________
> fetchmail-users mailing list
> fet...@li...
> https://lists.berlios.de/mailman/listinfo/fetchmail-users

Re: [fetchmail-users] Fetchmail/Multiple Local Users/Multiple Email Accounts

[Lovell M. <lov...@gm...>]

On Apr 2, 2007, at 2:30 PM, Rob MacGregor wrote:

> On 4/2/07, Lovell Mcilwain <lov...@gm...> wrote:
>>> 1) The output of "id" as each user
>> user1
>> uid=500(user1) gid=500(user1) groups=500(user1)
>> context=user_u:system_r:unconfined_t
>>
>> user2
>> uid=501(user2) gid=501(user2) groups=501(user2)
>> context=user_u:system_r:unconfined_t
>
> Ok, these really are 2 users (worth checking :>)
>
>> [user2@Linux ~]$ tail -f fetchmail.log
>> fetchmail: Lock-busy error on lmc...@wo...
>> fetchmail: POP3> QUIT
>> fetchmail: POP3< +OK signing off.
>> fetchmail: lock busy on server error while fetching from
>> lmc...@wo...
>> fetchmail: 6.3.6 querying @work.pop.com (protocol POP3) at Mon 02 Apr
>> 2007 02:15:38 PM EDT: poll completed
>> fetchmail: Query status=9 (LOCKBUSY)
>> fetchmail: Deleting fetchids file.
>> fetchmail: sleeping at Mon 02 Apr 2007 02:15:38 PM EDT for 300  
>> seconds
>> fetchmail: terminated with signal 15
>> fetchmail: Deleting fetchids file.
>
> Ok, how about the rest of the log.  Log snippets just waste my time.
>
Sorry about that, the log kinda just sat there so I thought it was  
done, I will regenerate.

> Note that the log does suggest the problem is that you have multiple
> programs connecting to the mailbox and your work's POP server only
> supports one at a time.

I was connected to the system via IMAPS.  I am using fetchmail to  
download via POP, I didn't think the two would conflict.  I will shut  
down my client connecting via IMAPS and give it another shot

>
> -- 
>                  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/Multiple Local Users/Multiple Email Accounts

[Lovell M. <lov...@gm...>]

On Apr 2, 2007, at 2:21 PM, Matthias Andree wrote:

> Lovell Mcilwain schrieb:
>
>> I was able to get fetchmail started but I have now run into another
>> problem.  When I checked my log after running in detailed verbose, I
>> get the following error:
>> [lmcilwain@Firewall ~]$ tail -f fetchmail.log
>> procmail: Couldn't create "/var/mail/lmcilwain"
>> procmail: [17952] Sun Apr  1 17:54:43 2007
>> procmail: Assigning "LOGNAME=procmail.log"
>> procmail: Assigning "LOGFILE=procmail.log"
>> procmail: Opening "procmail.log"
>>
>> So now I am not able to get anything into my inbox and everything
>> haults.  I have not been able to find a way to get it to write to /
>> var/mail/user2.
>
> Looks like a procmail issue.
>
> Check the permissions of the procmail executable (is it setuid root?)
-rwxr-xr-x 1 root mail 92452 Jul 12  2006 /usr/bin/procmail
>
> Check the permissions of /var/mail and /var/mail/user2.
user1
-rw-rw---- 1 user1 mail 77465038 Apr  2 14:22 /var/mail/user1

user2
-rw-r--r-- 1 user2 mail 0 Apr  1 18:36 /var/mail/user2 (I had to  
create this file by hand (touch user2) chown user2 / chgrp mail and  
that was it for this one) in the comparison I can see that this might  
be an issue.

> Use: ls -ldb /some/thing
>
> If that doesn't help, check with the procmail mailing lists or replace
> procmail by maildrop.

Re: [fetchmail-users] Fetchmail/Multiple Local Users/Multiple Email Accounts

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

On 4/2/07, Lovell Mcilwain <lov...@gm...> wrote:
> > 1) The output of "id" as each user
> user1
> uid=500(user1) gid=500(user1) groups=500(user1)
> context=user_u:system_r:unconfined_t
>
> user2
> uid=501(user2) gid=501(user2) groups=501(user2)
> context=user_u:system_r:unconfined_t

Ok, these really are 2 users (worth checking :>)

> [user2@Linux ~]$ tail -f fetchmail.log
> fetchmail: Lock-busy error on lmc...@wo...
> fetchmail: POP3> QUIT
> fetchmail: POP3< +OK signing off.
> fetchmail: lock busy on server error while fetching from
> lmc...@wo...
> fetchmail: 6.3.6 querying @work.pop.com (protocol POP3) at Mon 02 Apr
> 2007 02:15:38 PM EDT: poll completed
> fetchmail: Query status=9 (LOCKBUSY)
> fetchmail: Deleting fetchids file.
> fetchmail: sleeping at Mon 02 Apr 2007 02:15:38 PM EDT for 300 seconds
> fetchmail: terminated with signal 15
> fetchmail: Deleting fetchids file.

Ok, how about the rest of the log.  Log snippets just waste my time.

Note that the log does suggest the problem is that you have multiple
programs connecting to the mailbox and your work's POP server only
supports one at a time.

-- 
                 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/Multiple Local Users/Multiple Email Accounts

[Lovell M. <lov...@gm...>]

On Apr 2, 2007, at 1:58 PM, Rob MacGregor wrote:

> On 4/2/07, Lovell Mcilwain <lov...@gm...> wrote:
> <---SNIP--->
>> [user1@Linux ~]$ more .fetchmailrc
>> defaults proto pop3 user lmc...@gm... mda "/usr/bin/procmail -
>> d user1"
>> poll pop.gmail.com port 995 pass <pass> ssl is user1 here
>> set daemon 120
>> set syslog
>> set postmaster ""
>> set no bouncemail
>> set no spambounce
>> set properties ""
>> set logfile "fetchmail.log"
>>
>> Second account on Linux
>> [user2@Linux ~]$ more .fetchmailrc
>> defaults proto pop3 user lmcilwain mda "/usr/bin/procmail -d user2"
>> poll work.smtp.com port 995 pass <pass>  ssl is user2 here
>> set daemon 300
>> set syslog
>> set postmaster ""
>> set no bouncemail
>> set no spambounce
>> set properties ""
>> set logfile "fetchmail.log"
>
> Ok, nothing I can see that causes fetchmai to complain.  Can you do
> the following:
>
> 1) The output of "id" as each user
user1
uid=500(user1) gid=500(user1) groups=500(user1)  
context=user_u:system_r:unconfined_t

user2
uid=501(user2) gid=501(user2) groups=501(user2)  
context=user_u:system_r:unconfined_t

> 2) Start fetchmail as user1, then run "fetchmail --nosyslog -v -v -v"
> as user2, while fetchmail for user1 is running

I actually ran fetchmail --keep --nosyslog -v -v -v (I wanted to keep  
my mail on the server until I get this working right)

[user2@Linux ~]$ tail -f fetchmail.log
fetchmail: Lock-busy error on lmc...@wo...
fetchmail: POP3> QUIT
fetchmail: POP3< +OK signing off.
fetchmail: lock busy on server error while fetching from  
lmc...@wo...
fetchmail: 6.3.6 querying @work.pop.com (protocol POP3) at Mon 02 Apr  
2007 02:15:38 PM EDT: poll completed
fetchmail: Query status=9 (LOCKBUSY)
fetchmail: Deleting fetchids file.
fetchmail: sleeping at Mon 02 Apr 2007 02:15:38 PM EDT for 300 seconds
fetchmail: terminated with signal 15
fetchmail: Deleting fetchids file.



>>> Version of fetchmail?
>> [user2@Linux ~]$ fetchmail -V
>> This is fetchmail release 6.3.6+GSS+RPA+NTLM+SDPS+SSL+HESIOD+NLS+KRB4
>> +KRB5.
>
> Current enough.
>
> I assume that work.smtp.com doesn't resolve to pop.gmail.com?
>
> -- 
>                  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/Multiple Local Users/Multiple Email Accounts

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

Lovell Mcilwain schrieb:

> I was able to get fetchmail started but I have now run into another  
> problem.  When I checked my log after running in detailed verbose, I  
> get the following error:
> [lmcilwain@Firewall ~]$ tail -f fetchmail.log
> procmail: Couldn't create "/var/mail/lmcilwain"
> procmail: [17952] Sun Apr  1 17:54:43 2007
> procmail: Assigning "LOGNAME=procmail.log"
> procmail: Assigning "LOGFILE=procmail.log"
> procmail: Opening "procmail.log"
> 
> So now I am not able to get anything into my inbox and everything  
> haults.  I have not been able to find a way to get it to write to / 
> var/mail/user2.

Looks like a procmail issue.

Check the permissions of the procmail executable (is it setuid root?)

Check the permissions of /var/mail and /var/mail/user2.

Use: ls -ldb /some/thing

If that doesn't help, check with the procmail mailing lists or replace
procmail by maildrop.

Re: [fetchmail-users] Fetchmail/Multiple Local Users/Multiple Email Accounts

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

On 4/2/07, Lovell Mcilwain <lov...@gm...> wrote:
<---SNIP--->
> [user1@Linux ~]$ more .fetchmailrc
> defaults proto pop3 user lmc...@gm... mda "/usr/bin/procmail -
> d user1"
> poll pop.gmail.com port 995 pass <pass> ssl is user1 here
> set daemon 120
> set syslog
> set postmaster ""
> set no bouncemail
> set no spambounce
> set properties ""
> set logfile "fetchmail.log"
>
> Second account on Linux
> [user2@Linux ~]$ more .fetchmailrc
> defaults proto pop3 user lmcilwain mda "/usr/bin/procmail -d user2"
> poll work.smtp.com port 995 pass <pass>  ssl is user2 here
> set daemon 300
> set syslog
> set postmaster ""
> set no bouncemail
> set no spambounce
> set properties ""
> set logfile "fetchmail.log"

Ok, nothing I can see that causes fetchmai to complain.  Can you do
the following:

1) The output of "id" as each user
2) Start fetchmail as user1, then run "fetchmail --nosyslog -v -v -v"
as user2, while fetchmail for user1 is running

> > Version of fetchmail?
> [user2@Linux ~]$ fetchmail -V
> This is fetchmail release 6.3.6+GSS+RPA+NTLM+SDPS+SSL+HESIOD+NLS+KRB4
> +KRB5.

Current enough.

I assume that work.smtp.com doesn't resolve to pop.gmail.com?

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