fetchmail-users — User questions and discussion

Re: [Fetchmail-users] 2 feature requests for 7.x

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

Am 15.09.2014 um 04:17 schrieb grarpamp:

> I already proposed, with syntax, separating 'user definitions' at
> 'server definitions'
> abstractions years ago for 7.x. I think I split out three classes of
> things, brought
> them to the config file and command line, redfined what 'poll' meant, etc.
> It (and a bunch of fingerprint and TLS handling stuff) is in some tickets that I
> think got destroyed when the ticket system got destroyed/moved, or maybe
> on this list, or something like that, I don't remember. The idea is worthwhile
> and needed.

Dear grarpamp,

thank you for the reminder.  I downloaded the ticket data from BerliOS
but have not yet found a way to recreate Sourceforge tickets from them
authentically, the instructions that were given on sf.net in May were a
bit vague and not at all turnkey solutions, quite on the contrary.

Best,
Matthias

Re: [Fetchmail-users] 2 feature requests for 7.x

[grarpamp <gra...@gm...>]

On Wed, Sep 10, 2014 at 4:47 AM, Martin Koeppe <mk...@gm...> wrote:
> (2) Looking at the new features of 7.x shows that ssl options were
> changed. So maybe another change could be done, if it already changed
> anyway:
>
> With fetchmail 6.3 I see a limitation because --ssl is not
> a server option but a user option. When e.g. 2 of the 5 servers in my
> example above need a different ssl configuration, as they may not
> support ssl at all or have a self signed certificate, I currently must
> add this to _every_ user definition:
>
> defaults:
>         proto pop3 timeout 300 sslproto 'TLS1' ssl
>         sslcertfile /usr/ssl/certs/ca-bundle.trust.crt
>         # sslcertck
>         # sslfingerprint "82:5F:*"
> poll fully-ssl-compatible-server:
>         user "s1a" there with pass "*" is "s1a@domain.local" here
>         sslcertck
>         nokeep fetchall
> poll self-signed-certificate-server:
>         user "s2a" there with pass "*" is "s2a@domain.local" here
>         sslfingerprint "82:5F:*"
>         nokeep fetchall
>
> So "sslcertck" and "sslfingerprint" must be repeated over and over.
> Also if one server doesn't support ssl at all, it's even worse. I
> can't specify "ssl" in defaults section, because there is no (or at
> least not to my knowledge) no-ssl keyword, which I could apply to all
> user accounts on that server. So instead I added "ssl" to every user
> account on every other server, just because one server doesn't support
> it. "sslcertck" is the same.
>
> IMO all these SSL related options should be server options, not user
> options, as they apply before any user name is transmitted to the
> server, so there should be no need have it configured differently for
> every user. Ok, the server could behave diferently after user logon
> depending on the previously negotiated connection. But then I could
> have 2 different poll sections for the same server.

I already proposed, with syntax, separating 'user definitions' at
'server definitions'
abstractions years ago for 7.x. I think I split out three classes of
things, brought
them to the config file and command line, redfined what 'poll' meant, etc.
It (and a bunch of fingerprint and TLS handling stuff) is in some tickets that I
think got destroyed when the ticket system got destroyed/moved, or maybe
on this list, or something like that, I don't remember. The idea is worthwhile
and needed.

Re: [Fetchmail-users] Working around "Bad sender address syntax" error?

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

Am 10.09.2014 um 17:53 schrieb Daniel Barrett:
> 
> Thanks to Matthias and Rob for your suggestions to use the
> nosoftbounce and antispam features!
> 
> Looks like the antispam feature can set "501" as a spam code (-Z 501),
> but it does not accept the full "501 5.1.7" code reported in my error
> message. Is this correct, and do you think this would be a worthwhile
> enhancement request for fetchmail?

Thank you for the suggestion.  For now fetchmail only looks at the
actual SMTP/LMTP response code, rather than the RFC3463 extended status
code, and I wonder how broad we would need to make the RFC3463 stuff to
make it useful, rather than create user confusion because only some
parts of fetchmail might be looking at it.

If you have a use case where you need the 5.1.7 code or similar ones to
make a distinction beyond just the "501" in your case (or more
generally), then please file the use case along with the feature request
and include a reference to RFC3463.

> FYI, I asked my original question on StackOverflow last week and got
> no responses. Feel free to add your answers and win some reputation
> points! :-)

Certainly not.  While Stackoverflow is one of the forums that is getting
near the brink of being actually useful and halfway concise, I do not
believe in dispersing such knowledge outside the official and publicly
archived support channels, and SO is certainly way too late to the game.
By how many years does fetchmail predate it?

Re: [Fetchmail-users] Working around "Bad sender address syntax" error?

[Daniel B. <dba...@bl...>]

Thanks to Matthias and Rob for your suggestions to use the
nosoftbounce and antispam features!

Looks like the antispam feature can set "501" as a spam code (-Z 501),
but it does not accept the full "501 5.1.7" code reported in my error
message. Is this correct, and do you think this would be a worthwhile
enhancement request for fetchmail?

FYI, I asked my original question on StackOverflow last week and got
no responses. Feel free to add your answers and win some reputation
points! :-)

  http://stackoverflow.com/questions/25705002/postfix-bad-sender-address-syntax-causes-fetchmail-to-re-fetch-the-same-email

--
Dan Barrett
dba...@bl...

Re: [Fetchmail-users] fetchmail ssl cipher

[Martin K. <mk...@gm...>]

On Sat, 27 Jul 2013, Martin Koeppe wrote:


> when using fetchmail 6.3.21/cygwin with --sslproto 'SSL3' or --sslproto 
> 'TLS1', is it possible to see which SSL cipher has been chosen for a 
> connection?
>
> Or is it possible to show all supported server ciphers for SSL connections? 
> With -vvv it shows the certificate, but apparently not the cipher.
>
> Would it also be possible to limit the list of client supported ciphers 
> offered to the server?

Hi,

just another 2 wishlist item related to SSL in fetchmail 7.x.

(1) Configuring to-be-used ciphers / tls version

(2) logging actually used cipher
In between I saw that exim can log the cipher in the Received: line.
Maybe fetchmail could do so, too:

Received: from [x.x.x.x] (helo=xyz)
     by frontend.clustermail.de with esmtpsa (TLSv1:AES128-SHA:128)
     (Exim 4.63)


Thanks for consideration

Martin

[Fetchmail-users] 2 feature requests for 7.x

[Martin K. <mk...@gm...>]

Hi,

in my configuration I use fetchmail to fetch mails for several users 
from several servers in one rcfile. So lets say one rcfile has e.g. 50 
users and 5 servers, so 10 users per server. (I have several of those 
configurations.)

As I just read the message:

   Working around "Bad sender address syntax" error?

I would like to add 2 wishlist items for fetchmail 7.x:


(1) When it will be possible to repack broken messages into a new mail 
as an attachment (I like this idea, and I also encountered broken 
headers/addresses several times), I wish to be able to inform users in 
that same way, when a message has not been fetched because of size 
limit.


(2) Looking at the new features of 7.x shows that ssl options were 
changed. So maybe another change could be done, if it already changed 
anyway:

With fetchmail 6.3 I see a limitation because --ssl is not 
a server option but a user option. When e.g. 2 of the 5 servers in my 
example above need a different ssl configuration, as they may not 
support ssl at all or have a self signed certificate, I currently must 
add this to _every_ user definition:


defaults:
 	proto pop3 timeout 300 sslproto 'TLS1' ssl
 	sslcertfile /usr/ssl/certs/ca-bundle.trust.crt
 	# sslcertck
 	# sslfingerprint "82:5F:*"


poll fully-ssl-compatible-server:
 	user "s1a" there with pass "*" is "s1a@domain.local" here
 	sslcertck
 	nokeep fetchall

 	user "s1b" there with pass "*" is "s1b@domain.local" here
 	sslcertck
 	nokeep fetchall


poll self-signed-certificate-server:
 	user "s2a" there with pass "*" is "s2a@domain.local" here
 	sslfingerprint "82:5F:*"
 	nokeep fetchall

 	user "s2b" there with pass "*" is "s2b@domain.local" here
 	sslfingerprint "82:5F:*"
 	nokeep fetchall



So "sslcertck" and "sslfingerprint" must be repeated over and over. 
Also if one server doesn't support ssl at all, it's even worse. I 
can't specify "ssl" in defaults section, because there is no (or at 
least not to my knowledge) no-ssl keyword, which I could apply to all 
user accounts on that server. So instead I added "ssl" to every user 
account on every other server, just because one server doesn't support 
it. "sslcertck" is the same.


IMO all these SSL related options should be server options, not user 
options, as they apply before any user name is transmitted to the 
server, so there should be no need have it configured differently for 
every user. Ok, the server could behave diferently after user logon 
depending on the previously negotiated connection. But then I could 
have 2 different poll sections for the same server.


Martin

Re: [Fetchmail-users] Working around "Bad sender address syntax" error?

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

Am 10.09.2014 um 08:22 schrieb J. Roeleveld:

> I have not looked into the code yet, but if I were to provide a patch making 
> this possible, would you be willing to work with me to get it included?
> 
> One other option I was thinking off would be to move the entire email into the 
> body of a "new" email and add headers to have it delivered to the user as 
> such. That should avoid any security issues.

Hi Joost,

The second proposal seems OK with me, but I would not enable it by
default.  I am planning to switch off the softbounce feature, so that
fetchmail would delete such nondeliverable mail by default, in fetchmail 7.

We can discuss integration, code, and thereabouts on the -devel@ mailing
list, and I will not add features to the legacy_63 branch - please make
sure you work against the master branch, which is currently a
7.0.0-alpha version.

Best,
Matthias

Re: [Fetchmail-users] Working around "Bad sender address syntax" error?

[J. R. <jo...@an...>]

On Wednesday, September 10, 2014 08:04:04 AM Matthias Andree wrote:
> Am 10.09.2014 um 07:55 schrieb J. Roeleveld:
> > I would prefer to see a 4th option:
> > Save the email as a TXT file in a configurable location to allow us to at
> > least confirm it is spam and not a misconfigured email client. (I've
> > encountered that particular situation not too long ago)
> 
> Thanks for the feedback.
> 
> I do not think I will go for such features.
> 
> I want fetchmail to behave in a consistent and easily determined way,
> rather than along many ifs and buts, meaning in particular I want it to
> only ever use the one specific delivery path that is configured.
> 
> Another instance, disabling the "fallback" from SMTP to MDA was
> something that happened at my insisting already before I became a
> maintainer because it's just hard to track and tends to trigger false
> reports about misfiled/lost mail.
> 
> Feel free to file a feature request on the sourceforge.net project page
> (you need to be a registered user so I can ask questions and avoid
> hit-and-run reports) so this does not get lost, but it is very low
> priority for me and unlikely to happen in the next year.

Thank you for your reply. I will put this as a feature request.

I have not looked into the code yet, but if I were to provide a patch making 
this possible, would you be willing to work with me to get it included?

One other option I was thinking off would be to move the entire email into the 
body of a "new" email and add headers to have it delivered to the user as 
such. That should avoid any security issues.

If that is more acceptable, then please let me know and I will try to 
implement it like that.

Kind regards,

Joost

PS. Expect the feature request later today (if I can get a user account 
sorted)

Re: [Fetchmail-users] Working around "Bad sender address syntax" error?

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

Am 10.09.2014 um 07:55 schrieb J. Roeleveld:

> I would prefer to see a 4th option:
> Save the email as a TXT file in a configurable location to allow us to at 
> least confirm it is spam and not a misconfigured email client. (I've 
> encountered that particular situation not too long ago)

Thanks for the feedback.

I do not think I will go for such features.

I want fetchmail to behave in a consistent and easily determined way,
rather than along many ifs and buts, meaning in particular I want it to
only ever use the one specific delivery path that is configured.

Another instance, disabling the "fallback" from SMTP to MDA was
something that happened at my insisting already before I became a
maintainer because it's just hard to track and tends to trigger false
reports about misfiled/lost mail.

Feel free to file a feature request on the sourceforge.net project page
(you need to be a registered user so I can ask questions and avoid
hit-and-run reports) so this does not get lost, but it is very low
priority for me and unlikely to happen in the next year.

Re: [Fetchmail-users] Working around "Bad sender address syntax" error?

[J. R. <jo...@an...>]

On Tuesday, September 09, 2014 10:59:51 PM Matthias Andree wrote:
> Am 09.09.2014 um 15:17 schrieb Daniel Barrett:
> > I use fetchmail to retrieve email from an IMAP server every five
> > minutes, passing it to a local postfix process on my home Linux box
> > for delivery. The problem: sometimes an email has an invalid "From"
> > 
> > line (usually spam), like this one with leading hyphens:
> >   From: "- Some Dumb Spammer" <-Du...@ex...>
> > 
> > In this case, when fetchmail retrieves the email, the local postfix
> > 
> > process raises an error:
> >   fetchmail: SMTP error: 501 5.1.7 Bad sender address syntax
> > 
> > This error causes fetchmail to leave the bad email sitting on the IMAP
> > server, even when my .fetchmailrc file specifies "nokeep". As a
> > result, fetchmail re-downloads it every five minutes. Repeat
> > forever... or until I manually delete the bad email from the IMAP
> > server.
> 
> Daniel,
> 
> Older fetchmail versions promised to never delete mail from the server
> that was not reported as delivered by its SMTP/LMTP server or MDA, and
> since v6.3.10, fetchmail lives up to this promise.
> 
> > What's the best way to break these loops automatically, either
> > deleting or delivering the bad email, without opening a security hole
> > (e.g., permitting leading hyphens)?
> 
> I see at least three options:
> 
> 1. Leading hyphens are only a security risk if you are using scripts
> that would feed them to utilities that do not understand "--" to mark
> the end of options, or without these "--".  If you're sure you're safe,
> you can permit them.
> 
> 2. If you prefer to delete permanently undeliverable messages (those
> that elicit error codes 500 and above), use --nosoftbounce on the
> command line, or "set no softbounce" in the rcfile.  Details in the
> manual page.
> 
> 3. If you prefer to delete messages with particular error codes, see the
> manual page about the antispam option, see Rob MacGregor's message for a
> reference.

I would prefer to see a 4th option:
Save the email as a TXT file in a configurable location to allow us to at 
least confirm it is spam and not a misconfigured email client. (I've 
encountered that particular situation not too long ago)

--
Joost

Re: [Fetchmail-users] Working around "Bad sender address syntax" error?

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

Am 09.09.2014 um 15:17 schrieb Daniel Barrett:
> 
> I use fetchmail to retrieve email from an IMAP server every five
> minutes, passing it to a local postfix process on my home Linux box
> for delivery. The problem: sometimes an email has an invalid "From"
> line (usually spam), like this one with leading hyphens:
> 
>   From: "- Some Dumb Spammer" <-Du...@ex...>
> 
> In this case, when fetchmail retrieves the email, the local postfix
> process raises an error:
> 
>   fetchmail: SMTP error: 501 5.1.7 Bad sender address syntax
> 
> This error causes fetchmail to leave the bad email sitting on the IMAP
> server, even when my .fetchmailrc file specifies "nokeep". As a
> result, fetchmail re-downloads it every five minutes. Repeat
> forever... or until I manually delete the bad email from the IMAP
> server.

Daniel,

Older fetchmail versions promised to never delete mail from the server
that was not reported as delivered by its SMTP/LMTP server or MDA, and
since v6.3.10, fetchmail lives up to this promise.

> What's the best way to break these loops automatically, either
> deleting or delivering the bad email, without opening a security hole
> (e.g., permitting leading hyphens)?

I see at least three options:

1. Leading hyphens are only a security risk if you are using scripts
that would feed them to utilities that do not understand "--" to mark
the end of options, or without these "--".  If you're sure you're safe,
you can permit them.

2. If you prefer to delete permanently undeliverable messages (those
that elicit error codes 500 and above), use --nosoftbounce on the
command line, or "set no softbounce" in the rcfile.  Details in the
manual page.

3. If you prefer to delete messages with particular error codes, see the
manual page about the antispam option, see Rob MacGregor's message for a
reference.

Best,
Matthias

Re: [Fetchmail-users] Working around "Bad sender address syntax" error?

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

On 9 September 2014 14:17, Daniel Barrett <dba...@bl...> wrote:
>
> I use fetchmail to retrieve email from an IMAP server every five
> minutes, passing it to a local postfix process on my home Linux box
> for delivery. The problem: sometimes an email has an invalid "From"
> line (usually spam), like this one with leading hyphens:
>
>   From: "- Some Dumb Spammer" <-Du...@ex...>
>
> In this case, when fetchmail retrieves the email, the local postfix
> process raises an error:
>
>   fetchmail: SMTP error: 501 5.1.7 Bad sender address syntax
>
> This error causes fetchmail to leave the bad email sitting on the IMAP
> server, even when my .fetchmailrc file specifies "nokeep". As a
> result, fetchmail re-downloads it every five minutes. Repeat
> forever... or until I manually delete the bad email from the IMAP
> server.
>
> What's the best way to break these loops automatically, either
> deleting or delivering the bad email, without opening a security hole
> (e.g., permitting leading hyphens)?

Check the anti-spam option:

http://www.fetchmail.info/fetchmail-man.html#29

If you set 501 as a spam code fetchmail will delete any email your
Postfix server returns that code for.

-- 
                 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] Working around "Bad sender address syntax" error?

[Daniel B. <dba...@bl...>]

I use fetchmail to retrieve email from an IMAP server every five
minutes, passing it to a local postfix process on my home Linux box
for delivery. The problem: sometimes an email has an invalid "From"
line (usually spam), like this one with leading hyphens:

  From: "- Some Dumb Spammer" <-Du...@ex...>

In this case, when fetchmail retrieves the email, the local postfix
process raises an error:

  fetchmail: SMTP error: 501 5.1.7 Bad sender address syntax

This error causes fetchmail to leave the bad email sitting on the IMAP
server, even when my .fetchmailrc file specifies "nokeep". As a
result, fetchmail re-downloads it every five minutes. Repeat
forever... or until I manually delete the bad email from the IMAP
server.

What's the best way to break these loops automatically, either
deleting or delivering the bad email, without opening a security hole
(e.g., permitting leading hyphens)?

Thank you very much.

--
Dan Barrett
dba...@bl...

Re: [Fetchmail-users] fetchmail with same email address

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

Am 14.08.2014 um 04:55 schrieb Ronald Artos:
> I've have this mail server host which I fetch messages and store it in our
> local mail server, my setup is like this:
> 
> poll mail.example.com protocol POP3 user "sy...@ex..." there with
> password "webhostpass" is "sy...@ex..." here;
> 
> 
> running fetchmail will fetch messages from mail.example.com but I no
> message came to my local mail server. But replacing the target
> email address like "web...@ex..." it can deliver the message.
> 
> How can I fetch email from remote server to local server using same email
> address / username ?
> 
> local mail server, I am using iRedmail with virtual user and virtual domain.
> 
> -=ronald
> ------------------------------------------------------------------------------

Ronald,

if the target address is the only difference between working and
non-working configurations, then you will need to check your iRedmail
setup and logging.

If fetchmail has trouble delivering mail to iRedmail it will let you
know on the console with your configuration.

If you have trouble discerning what fetchmail does with your message,
add "-v" options to the command line and check options, and if you need
help understanding fetchmail's logging, see Rob MacGregor's response as
of a few hours ago for what you need to provide.

HTH
Matthias

Re: [Fetchmail-users] fetchmail with same email address

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

On Thu, Aug 14, 2014 at 3:55 AM, Ronald Artos <ron...@gm...> wrote:
> I've have this mail server host which I fetch messages and store it in our
> local mail server, my setup is like this:
>
> poll mail.example.com protocol POP3 user "sy...@ex..." there with
> password "webhostpass" is "sy...@ex..." here;
>
>
> running fetchmail will fetch messages from mail.example.com but I no
> message came to my local mail server. But replacing the target
> email address like "web...@ex..." it can deliver the message.
>
> How can I fetch email from remote server to local server using same email
> address / username ?
>
> local mail server, I am using iRedmail with virtual user and virtual domain.

Please read section G3 of the FAQ and provide all the information
requested there.

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

-- 
                 Please keep list traffic on the list.

Rob MacGregor
      Whoever fights monsters should see to it that in the process he
        doesn't become a monster.                  Friedrich Nietzsche

[Fetchmail-users] fetchmail with same email address

[Ronald A. <ron...@gm...>]

I've have this mail server host which I fetch messages and store it in our
local mail server, my setup is like this:

poll mail.example.com protocol POP3 user "sy...@ex..." there with
password "webhostpass" is "sy...@ex..." here;


running fetchmail will fetch messages from mail.example.com but I no
message came to my local mail server. But replacing the target
email address like "web...@ex..." it can deliver the message.

How can I fetch email from remote server to local server using same email
address / username ?

local mail server, I am using iRedmail with virtual user and virtual domain.

-=ronald

[Fetchmail-users] (no subject)

[Harry P. <re...@ne...>]

Re: [Fetchmail-users] Retrieving read messages from IMAP server

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

Am 20.07.2014 20:57, schrieb Jerry:
> On Sun, 20 Jul 2014 18:17:42 +0100, Rob MacGregor stated:
> 
>> On Sun, Jul 20, 2014 at 4:34 PM, Jerry <je...@se...> wrote:
>>> On Sun, 20 Jul 2014 15:57:02 +0100, Rob MacGregor stated:
>>>
>>> Yes, I have. Using MS Outlook 15.0.4631.1002 on my laptop. Outlook is
>>> configured to use IMAP for the account in question. I can go to the
>>> webmail site and confirm that the message is still there; however, it is
>>> marked as read. Fetchmail will not not download it. If I first use
>>> fetchmail to retrieve the email, it is also left on the site and Outlook
>>> will retrieve it. I figure I must have something configured incorrectly.
>>
>> Please see section G3 of the FAQ:
>> http://www.fetchmail.info/fetchmail-FAQ.html#G3
>>
>> It lists the information we need to help you. A transcript that
>> includes a failure to retrieve a message that's on the server would
>> help too.
> 
> env LC_ALL=C fetchmail --nodetach -vvv --nosyslog

Thank you.

Unfortunately the original fetchmail design - and still present with
IMAP - was that it assumed to be the only client polling the mailbox,
and hence can - as of 6.3.X - only be made to operate in either of these
modes:

- do not download mail another client has marked "seen"

- download and flush all mail, but this means the /other/ client only
has a few messages, and only as they accumulate before the next
fetchmail poll.

One workaround is - counter to other recommendations that are valid for
different situations or needs - to use POP3 + UIDL.

Fetchmail's IMAP client, as of 6.3.X, only downloads unseen mail, unless
you set --fetchall - but you cannot usefully combine fetchall and keep
because that would duplicate all mail.

Re: [Fetchmail-users] Retrieving read messages from IMAP server

[Jerry <je...@se...>]

On Sun, 20 Jul 2014 18:17:42 +0100, Rob MacGregor stated:

> On Sun, Jul 20, 2014 at 4:34 PM, Jerry <je...@se...> wrote:
> > On Sun, 20 Jul 2014 15:57:02 +0100, Rob MacGregor stated:
> >
> > Yes, I have. Using MS Outlook 15.0.4631.1002 on my laptop. Outlook is
> > configured to use IMAP for the account in question. I can go to the
> > webmail site and confirm that the message is still there; however, it is
> > marked as read. Fetchmail will not not download it. If I first use
> > fetchmail to retrieve the email, it is also left on the site and Outlook
> > will retrieve it. I figure I must have something configured incorrectly.
> 
> Please see section G3 of the FAQ:
> http://www.fetchmail.info/fetchmail-FAQ.html#G3
> 
> It lists the information we need to help you. A transcript that
> includes a failure to retrieve a message that's on the server would
> help too.

env LC_ALL=C fetchmail --nodetach -vvv --nosyslog

Old UID list from muon.mfg-consulting-llc.com: <empty>
Scratch list of UIDs: <empty>
fetchmail: 6.3.26 querying muon.mfg-consulting-llc.com (protocol IMAP) at Sun Jul 20 14:44:57 2014: poll started
Trying to connect to 69.16.208.160/143...connected.
fetchmail: IMAP< * OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE ACL ACL2=UNION STARTTLS] Courier-IMAP ready. Copyright 1998-2011 Double Precision, Inc.  See COPYING for distribution information.
fetchmail: IMAP> A0001 CAPABILITY
fetchmail: IMAP< * CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE ACL ACL2=UNION STARTTLS
fetchmail: IMAP< A0001 OK CAPABILITY completed
fetchmail: Protocol identified as IMAP4 rev 1
fetchmail: IMAP> A0002 STARTTLS
fetchmail: IMAP< A0002 OK Begin SSL/TLS negotiation now.
fetchmail: Certificate chain, from root to peer, starting at depth 1:
fetchmail: Issuer Organization: GlobalSign nv-sa
fetchmail: Issuer CommonName: GlobalSign Root CA
fetchmail: Subject CommonName: GlobalSign Domain Validation CA - SHA256 - G2
fetchmail: Certificate at depth 1:
fetchmail: Issuer Organization: GlobalSign nv-sa
fetchmail: Issuer CommonName: GlobalSign Root CA
fetchmail: Subject CommonName: GlobalSign Domain Validation CA - SHA256 - G2
fetchmail: Server certificate:
fetchmail: Issuer Organization: GlobalSign nv-sa
fetchmail: Issuer CommonName: GlobalSign Domain Validation CA - SHA256 - G2
fetchmail: Subject CommonName: muon.mfg-consulting-llc.com
fetchmail: Subject Alternative Name: muon.mfg-consulting-llc.com
fetchmail: muon.mfg-consulting-llc.com key fingerprint: 52:83:BD:F4:EB:72:70:1A:AA:3A:F9:13:65:9A:59:2E
fetchmail: muon.mfg-consulting-llc.com fingerprints match.
fetchmail: IMAP> A0003 CAPABILITY
fetchmail: IMAP< * CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE AUTH=PLAIN ACL ACL2=UNION
fetchmail: IMAP< A0003 OK CAPABILITY completed
fetchmail: Protocol identified as IMAP4 rev 1
fetchmail: muon.mfg-consulting-llc.com: upgrade to TLS succeeded.
fetchmail: GSSAPI error gss_inquire_cred:  No credentials were supplied, or the credentials were unavailable or inaccessible.
fetchmail: GSSAPI error gss_inquire_cred: unknown mech-code 0 for mech unknown
fetchmail: No suitable GSSAPI credentials found. Skipping GSSAPI authentication.
fetchmail: If you want to use GSSAPI, you need credentials first, possibly from kinit.
fetchmail: IMAP> A0004 LOGIN "ger...@st..." *
fetchmail: IMAP< A0004 OK LOGIN Ok.
fetchmail: selecting or re-polling default folder
fetchmail: IMAP> A0005 SELECT "INBOX"
fetchmail: IMAP< * FLAGS (\Draft \Answered \Flagged \Deleted \Seen \Recent)
fetchmail: IMAP< * OK [PERMANENTFLAGS (\* \Draft \Answered \Flagged \Deleted \Seen)] Limited
fetchmail: IMAP< * 4 EXISTS
fetchmail: IMAP< * 0 RECENT
fetchmail: IMAP< * OK [UIDVALIDITY 403878125] Ok
fetchmail: IMAP< * OK [MYRIGHTS "acdilrsw"] ACL
fetchmail: IMAP< A0005 OK [READ-WRITE] Ok
fetchmail: 4 messages waiting after first poll
fetchmail: IMAP> A0006 SEARCH UNSEEN UNDELETED
fetchmail: IMAP< * SEARCH
fetchmail: IMAP< A0006 OK SEARCH done.
4 messages (4 seen) for ger...@st... at muon.mfg-consulting-llc.com.
fetchmail: IMAP> A0007 LOGOUT
fetchmail: IMAP< * BYE Courier-IMAP server shutting down
fetchmail: IMAP< A0007 OK LOGOUT completed
fetchmail: 6.3.26 querying muon.mfg-consulting-llc.com (protocol IMAP) at Sun Jul 20 14:44:58 2014: poll completed
New UID list from muon.mfg-consulting-llc.com: <empty>
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: normal termination, status 1


env LC_ALL=C fetchmail -V 

This is fetchmail release 6.3.26+GSS+RPA+NTLM+SDPS+SSL+OPIE+NLS.

Copyright (C) 2002, 2003 Eric S. Raymond
Copyright (C) 2004 Matthias Andree, Eric S. Raymond,
                   Robert M. Funk, Graham Wilson
Copyright (C) 2005 - 2012 Sunil Shetye
Copyright (C) 2005 - 2013 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.
This product includes software developed by the OpenSSL Project
for use in the OpenSSL Toolkit. (http://www.openssl.org/)

Fallback MDA: (none)
FreeBSD scorpio.seibercom.net 10.0-RELEASE-p3 FreeBSD 10.0-RELEASE-p3 #0: Tue May 13 18:31:10 UTC 2014     ro...@am...:/usr/obj/usr/src/sys/GENERIC  amd64
Taking options from command line and /home/gerard/.fetchmailrc
Idfile is /var/tmp/.fetchids
Fetchmail will forward misaddressed multidrop messages to postmaster.
Options for retrieving from ger...@st...@muon.mfg-consulting-llc.com:
  True name of server is muon.mfg-consulting-llc.com.
  Protocol is IMAP.
  All available authentication methods will be tried.
  SSL protocol: TLS1.
  SSL key fingerprint (checked against the server key): 52:83:BD:F4:EB:72:70:1A:AA:3A:F9:13:65:9A:59:2E
  Server nonresponse timeout is 30 seconds.
  Default mailbox selected.
  Only new messages will be retrieved (--all off).
  Fetched messages will be kept on the server (--keep on).
  Old messages will not be flushed before message retrieval (--flush off).
  Oversized messages will not be flushed before message retrieval (--limitflush off).
  Rewrite of server-local addresses is enabled (--norewrite off).
  Carriage-return stripping is disabled (stripcr off).
  Carriage-return forcing is disabled (forcecr off).
  Interpretation of Content-Transfer-Encoding is enabled (pass8bits off).
  MIME decoding is disabled (mimedecode off).
  Idle after poll is disabled (idle off).
  Nonempty Status lines will be kept (dropstatus off)
  Delivered-To lines will be discarded (dropdelivered on)
  Fetch message size limit is 100 (--fetchsizelimit 100).
  Do binary search of UIDs during 3 out of 4 polls (--fastuidl 4).
  Messages will be SMTP-forwarded to: localhost (default)
  Address to be put in RCPT TO lines shipped to SMTP will be st...@st...
  Single-drop mode: 1 local name recognized.
  No UIDs saved from this host.
  Messages with bad headers will be passed on.

I hope this is what you want.

-- 
Jerry

Re: [Fetchmail-users] Retrieving read messages from IMAP server

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

On Sun, Jul 20, 2014 at 4:34 PM, Jerry <je...@se...> wrote:
> On Sun, 20 Jul 2014 15:57:02 +0100, Rob MacGregor stated:
>
> Yes, I have. Using MS Outlook 15.0.4631.1002 on my laptop. Outlook is
> configured to use IMAP for the account in question. I can go to the webmail
> site and confirm that the message is still there; however, it is marked as
> read. Fetchmail will not not download it. If I first use fetchmail to
> retrieve the email, it is also left on the site and Outlook will retrieve it.
> I figure I must have something configured incorrectly.

Please see section G3 of the FAQ:
http://www.fetchmail.info/fetchmail-FAQ.html#G3

It lists the information we need to help you. A transcript that
includes a failure to retrieve a message that's on the server would
help too.

-- 
                 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] Retrieving read messages from IMAP server

[Jerry <je...@se...>]

On Sun, 20 Jul 2014 15:57:02 +0100, Rob MacGregor stated:

> Have you confirmed that the (unspecified) program on your laptop is
> really using IMAP and leaving the messages behind? It sounds more
> likely that it's either using POP3 or it's deleting them.

Yes, I have. Using MS Outlook 15.0.4631.1002 on my laptop. Outlook is
configured to use IMAP for the account in question. I can go to the webmail
site and confirm that the message is still there; however, it is marked as
read. Fetchmail will not not download it. If I first use fetchmail to
retrieve the email, it is also left on the site and Outlook will retrieve it.
I figure I must have something configured incorrectly.

-- 
Jerry

Re: [Fetchmail-users] Retrieving read messages from IMAP server

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

On Sat, Jul 19, 2014 at 6:46 PM, Jerry <je...@se...> wrote:
> I am probably doing something really stupid here, but I am not sure what.

What version (number) of fetchmail and what operating system are you using?

> I have fetchmail set up to retrieve mail from an IMAP account I have. Now,
> this IMAP account is also accessed from my laptop computer when I am
> traveling. If I retrieve a message directly from the IMAP account onto my
> laptop, fetchmail will no longer download it onto my work station computer.
> However, if fetchmail downloads the email first, it is still available for
> download onto my laptop. I hope this all makes sense.

Have you confirmed that the (unspecified) program on your laptop is
really using IMAP and leaving the messages behind? It sounds more
likely that it's either using POP3 or it's deleting them.

-- 
                 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] Retrieving read messages from IMAP server

[Jerry <je...@se...>]

I am probably doing something really stupid here, but I am not sure what.

I have fetchmail set up to retrieve mail from an IMAP account I have. Now,
this IMAP account is also accessed from my laptop computer when I am
traveling. If I retrieve a message directly from the IMAP account onto my
laptop, fetchmail will no longer download it onto my work station computer.
However, if fetchmail downloads the email first, it is still available for
download onto my laptop. I hope this all makes sense.

This is the config from my fetchmailrc file. Obviously, I have modified the
actual user name and password.

# Configuration created Tue Jul  1 15:56:47 2014 by fetchmailconf 1.57
set idfile "/var/tmp/.fetchids"
set logfile "/var/log/fetchmail"
set postmaster "postmaster"
set bouncemail
set no spambounce
set softbounce
set properties ""

poll muon.mfg-consulting-llc.com proto IMAP timeout 30 and options bad-header accept
user 'US...@IS...' there with password 'SECRET' is 'US...@IS...' here options keep ssl dropdelivered smtpname 'Som...@XX...' sslfingerprint '52:83:BD:F4:EB:72:70:1A:AA:3A:F9:13:65:9A:59:2E'

-- 
Jerry

[Fetchmail-users] Fetchmail mailing lists moved to sourceforge.net

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

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

Greetings,

the previous fetchmail hosting service, berlios.de, has shut down two
months ago, and the easily-transferable data have been moved to
Sourceforge.net. This includes the web space, downloads, project
overview, Git repository, and now the mailing lists.

After a long hiatus of nearly two months, the three fetchmail mailing
lists are apparently back; I requested an import on May 21st and
apparently sourceforge.net just imported them, without closing the
support ticket yet.  Still I will post now to avoid further confusion.


YOU MAY NEED TO CHANGE LIST SETTINGS OR YOUR WORK FLOWS:

1. the list addresses now all end in @lists.sourceforge.net, no longer
in @lists.berlios.de.

2. the only settings we could preserve from former lists are whether you
were receiving a. plain messages, or b. digests, or c. no messages at all.

You may have to adjust your inbound mail filters and aliases or address
books that you use to post to the list, or file messages into folders.

You may have to re-configure personal subscriber customization.
The entry pages to do that latter are:

https://lists.sourceforge.net/lists/listinfo/fetchmail-announce
https://lists.sourceforge.net/lists/listinfo/fetchmail-devel
https://lists.sourceforge.net/lists/listinfo/fetchmail-users


QUICK MAILING LIST OVERVIEW (LIST PURPOSE)

The fetchmail-announce@ list is reserved for the project admins for
release/errata/security and other similarly important announcements, in
order to be a very low traffic list with only a few posts per year.

The fetchmail-users@ list is for general discussion of use, function,
integration with other software from the end user's perspective, support
inquiries, and thereabouts.

The fetchmail-devel@ list is for discussion of the code, development,
and integration with other software from a developer's perspective.


FURTHER SERVICES

The unmaintained Wiki contents were mostly of interest to developers and
have been dropped.

The tracker data could not yet be imported.  I downloaded the data, but
it would take major efforts to import things.

The website contents are more or less unchanged, and I need to update
them to reflect the mailing list migration.

The Git repository has been and continues to be at
<https://gitorious.org/fetchmail/> and gets manually mirrored to
<https://sourceforge.net/p/fetchmail/git/>.

If you have any concerns, troubles, thoughts, let me know, either
through the fetchmail-users@ list, or directly if it's sensitive.

Best,
Matthias
- - fetchmail maintainer -
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAlOzv+UACgkQvmGDOQUufZU1SQCfZZGyFQUA4jj6TAR3RmXMD9E5
Y0wAoOGGB04chmix3Djn+rc+v/SeJv4n
=hfm1
-----END PGP SIGNATURE-----

Re: [fetchmail-users] Fetchmail

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

Am 02.05.2014 15:36, schrieb jader fabiano:
> Hello!
> I am developing a solution that it use fetchmail, and I have a doubt.
> How can I specify to fetchmail uses tls1.1 or tls1.2?
> 
> I did not find how i can do this.

That's because the code has not yet been written, and OpenSSL has gained
TLSv1.1 and 1.2 support only recently.

We should have such code in fetchmail 7.0 once it's ready (and it is not
on any schedule right now), but such code has not yet been written.