Jonathan Buschmann | 2 Feb 2011 14:57
Picon
Favicon

Return receipts generated by Exchange

Hi,
When messages are fetched from my Exchange server it sends a read 
receipt. I believe that this has not always been the behavior, although 
for obvious reasons I didn't realize when the behavior began (in terms 
of fetchmail release). It might also have started after an update of the 
Exchange server. I've verified that the receipt is sent at the moment 
the mail is fetched. Via Outlook return receipts are disabled on Exchange.

I'm using 6.3.17+NTLM+SSL on a SUN with Solaris 10.
My fetchmailrc:
set daemon 10
set syslog
set postmaster "postmaster"
set no bouncemail
set no spambounce
set properties ""
poll mail.<snip> with proto IMAP with auth password
        user '<snip>' there with password '<snip>' is '<snip>' here 
options fetchall no mimedecode ssl idle

--

-- 

Picture (Device Independent Bitmap)

*JONATHAN BUSCHMANN
Customer Solution Sales *

Ericsson Telecomunicazioni S.p.A.
Business Segment Services, Market Unit South East Europe
Strada 2, Palazzo C
(Continue reading)

Matthias Andree | 2 Feb 2011 18:00
Picon
Picon

Re: Return receipts generated by Exchange

Am 02.02.2011 14:57, schrieb Jonathan Buschmann:

> When messages are fetched from my Exchange server it sends a read
> receipt. I believe that this has not always been the behavior, although
> for obvious reasons I didn't realize when the behavior began (in terms
> of fetchmail release). It might also have started after an update of the
> Exchange server. I've verified that the receipt is sent at the moment
> the mail is fetched. Via Outlook return receipts are disabled on Exchange.

I don't think this is related to fetchmail -- at least fetchmail doesn't
do more than setting the \Seen flag.  However, I don't know off-hand how
fetchall changes IMAP behaviour WRT this flag; certainly \Deleted gets
set because you're not using "keep" or thereabouts.

I also suspect that Outlook doesn't talk IMAP to Exchange, but MAPI.
Could you check your Outlook configuration?

HTH

--

-- 
Matthias Andree
Matthias Andree | 2 Feb 2011 19:44
Picon
Picon

Re: Fetchmail's bounce behavior - "can't even send to postmaster"

Am 24.01.2011 11:46, schrieb Sunil Shetye:
> [Correcting point 2]
> 
> Matthias, please check if these points should be implemented:
> 
> - Stop redirecting rejected mails to postmaster as a last-resort address.

Possible for protocols that allow leaving messages on the server (POP3,
IMAP). Unsure for ODMR/ETRN/... because I'm not sure if we can reject
messages in a way that the server keeps them and will re-try delivery later.

Only suitable for 7.X.

> - If 'softbounce' and 'no bouncemail', do not send any bounce mail to the postmaster. (as suggested by
Martin Koeppe)

Yes, makes perfect sense. Suitable for 6.3.X and 7.X.

> - Undo documentation on setting postmaster to empty string. Ignore 'set postmaster ""' silently (for compatibility).

Hm. I understand you've introduced a feature but not thoroughly
documented it. I'm not sure I understand what you're proposing.  So 'set
postmaster ""' was an overloaded feature to suppress postmaster mail,
and you propose to silently ignore this setting? What would fetchmail
use instead?  This reads as though the user would be pulled in for nasty
surprises though. :-/

> - Add a failsafe mode to fetchmail. It should be activated when the fetchmailrc is new (say, less than 1 week
old). In failsafe mode, fetchmail will essentially activate softbounce. In daemon mode, after a week of
running time, switch off the failsafe mode.
(Continue reading)

Sunil Shetye | 3 Feb 2011 08:40
Picon
Favicon

Re: Fetchmail's bounce behavior - "can't even send to postmaster"

--- On Thu, 3/2/11, Matthias Andree <matthias.andree <at> gmx.de> wrote:
> > - Stop redirecting rejected mails to postmaster as a
> last-resort address.
> 
> Possible for protocols that allow leaving messages on the
> server (POP3,
> IMAP). Unsure for ODMR/ETRN/... because I'm not sure if we
> can reject
> messages in a way that the server keeps them and will
> re-try delivery later.
> 
> Only suitable for 7.X.

In ETRN, fetchmail is not involved in delivery at all. In ODMR, fetchmail is only acting like a pipe. In both
cases, fetchmail is not involved in sending bounces. send_bouncemail() is indirectly called from
fetch_messages() which is not invoked for ODMR and ETRN (count == -1).

> > - If 'softbounce' and 'no bouncemail', do not send any
> bounce mail to the postmaster. (as suggested by Martin
> Koeppe)
> 
> Yes, makes perfect sense. Suitable for 6.3.X and 7.X.

Okay.

> > - Undo documentation on setting postmaster to empty
> string. Ignore 'set postmaster ""' silently (for
> compatibility).
> 
> Hm. I understand you've introduced a feature but not
(Continue reading)

Jonathan Buschmann | 3 Feb 2011 09:14
Picon
Favicon

Re: Return receipts generated by Exchange

My Outlook config seems OK. As I said I have the sending of return 
receipts turned off.
As you say, Outlook doesn't use IMAP.
I'll take a look at the code to try to understand what fetchall does.

At precisely 02/02/2011 18.00, with renowned erudition Matthias Andree 
eloquently scribed:
> Am 02.02.2011 14:57, schrieb Jonathan Buschmann:
>
>> When messages are fetched from my Exchange server it sends a read
>> receipt. I believe that this has not always been the behavior, although
>> for obvious reasons I didn't realize when the behavior began (in terms
>> of fetchmail release). It might also have started after an update of the
>> Exchange server. I've verified that the receipt is sent at the moment
>> the mail is fetched. Via Outlook return receipts are disabled on Exchange.
> I don't think this is related to fetchmail -- at least fetchmail doesn't
> do more than setting the \Seen flag.  However, I don't know off-hand how
> fetchall changes IMAP behaviour WRT this flag; certainly \Deleted gets
> set because you're not using "keep" or thereabouts.
>
> I also suspect that Outlook doesn't talk IMAP to Exchange, but MAPI.
> Could you check your Outlook configuration?
>
> HTH
>

--

-- 

Picture (Device Independent Bitmap)

(Continue reading)

Jerry | 3 Feb 2011 12:30
Face
Favicon

Re: Return receipts generated by Exchange

On Thu, 3 Feb 2011 09:14:57 +0100
Jonathan Buschmann <jonathan.buschmann <at> ericsson.com> articulated:

> At precisely 02/02/2011 18.00, with renowned erudition Matthias
> Andree eloquently scribed:
> > Am 02.02.2011 14:57, schrieb Jonathan Buschmann:
> >
> >> When messages are fetched from my Exchange server it sends a read
> >> receipt. I believe that this has not always been the behavior,
> >> although for obvious reasons I didn't realize when the behavior
> >> began (in terms of fetchmail release). It might also have started
> >> after an update of the Exchange server. I've verified that the
> >> receipt is sent at the moment the mail is fetched. Via Outlook
> >> return receipts are disabled on Exchange.
> > I don't think this is related to fetchmail -- at least fetchmail
> > doesn't do more than setting the \Seen flag.  However, I don't know
> > off-hand how fetchall changes IMAP behaviour WRT this flag;
> > certainly \Deleted gets set because you're not using "keep" or
> > thereabouts.
> >
> > I also suspect that Outlook doesn't talk IMAP to Exchange, but MAPI.
> > Could you check your Outlook configuration?
> > 
> My Outlook config seems OK. As I said I have the sending of return 
> receipts turned off.
> As you say, Outlook doesn't use IMAP.
> I'll take a look at the code to try to understand what fetchall does.

Could you please post the version number for of MS Outlook, and if
possible the Exchange server?
(Continue reading)

Jonathan Buschmann | 4 Feb 2011 16:28
Picon
Favicon

Re: Return receipts generated by Exchange

Outlook is 11.8206.8202 SP3.
I used to see the Exchange version when connecting to the server 
verbosely, but now it no longer reports its version!
Th best I can offer is the capability set: CAPABILITY IMAP4 IMAP4rev1 
AUTH=NTLM AUTH=GSSAPI AUTH=PLAIN IDLE NAMESPACE LITERAL+
unless someone can suggest how to get the version info.

At precisely 03/02/2011 12.30, with renowned erudition Jerry eloquently 
scribed:
> On Thu, 3 Feb 2011 09:14:57 +0100
> Jonathan Buschmann<jonathan.buschmann <at> ericsson.com>  articulated:
>
>> At precisely 02/02/2011 18.00, with renowned erudition Matthias
>> Andree eloquently scribed:
>>> Am 02.02.2011 14:57, schrieb Jonathan Buschmann:
>>>
>>>> When messages are fetched from my Exchange server it sends a read
>>>> receipt. I believe that this has not always been the behavior,
>>>> although for obvious reasons I didn't realize when the behavior
>>>> began (in terms of fetchmail release). It might also have started
>>>> after an update of the Exchange server. I've verified that the
>>>> receipt is sent at the moment the mail is fetched. Via Outlook
>>>> return receipts are disabled on Exchange.
>>> I don't think this is related to fetchmail -- at least fetchmail
>>> doesn't do more than setting the \Seen flag.  However, I don't know
>>> off-hand how fetchall changes IMAP behaviour WRT this flag;
>>> certainly \Deleted gets set because you're not using "keep" or
>>> thereabouts.
>>>
>>> I also suspect that Outlook doesn't talk IMAP to Exchange, but MAPI.
(Continue reading)

Mike Clarke | 5 Feb 2011 11:19
Picon

SMTP error: 501: domain missing or malformed


Recently I've been getting spam arriving with malformed From addresses, 
like <leslie <at> >. Instead of collecting these messages fetchmail just 
leaves them on the POP3 server and logs an error message which gets 
repeated every 10 minutes when it tries to collect mail. The only way I 
can get stop this is to use a webmail interface to delete the offending 
messages.

Leaving these messages on the server indefinitely does not appear to be 
the right approach. Is there any way to configure fetchmail to either 
delete or accept them. If fetchmail were to accept them they could then 
be dealt with by my spam filters. 

--

-- 
Mike Clarke
Rob MacGregor | 5 Feb 2011 19:17
Picon
Gravatar

Re: SMTP error: 501: domain missing or malformed

On Sat, Feb 5, 2011 at 10:19, Mike Clarke <jmc-fetchmail <at> milibyte.co.uk> wrote:
>
> Recently I've been getting spam arriving with malformed From addresses,
> like <leslie <at> >. Instead of collecting these messages fetchmail just
> leaves them on the POP3 server and logs an error message which gets
> repeated every 10 minutes when it tries to collect mail. The only way I
> can get stop this is to use a webmail interface to delete the offending
> messages.
>
> Leaving these messages on the server indefinitely does not appear to be
> the right approach. Is there any way to configure fetchmail to either
> delete or accept them. If fetchmail were to accept them they could then
> be dealt with by my spam filters.

Please read the FAQ (http://fetchmail.berlios.de/fetchmail-FAQ.html)
which details the bug reporting process. This can be summarised as:

1. Ensure you're running the current release (6.3.19 at this time)
2. Provide the details of:
 a. Your operating system.
 b. Your compiler version, if you built from source; otherwise, the
name and origin of the RPM or other binary package you installed.
 c. The name and version of the SMTP listener or MDA you are forwarding to.
 d. Any command-line options you used.
 e. The output of env LC_ALL=C fetchmail -V called with whatever other
command-line options you used.
 f. The output of env LC_ALL=C fetchmail --nodetach -vvv --nosyslog
with whatever other command-line options you use routinely.

--

-- 
(Continue reading)

Mike Clarke | 5 Feb 2011 22:48
Picon

Re: SMTP error: 501: domain missing or malformed

On Saturday 05 February 2011, Rob MacGregor wrote:

> On Sat, Feb 5, 2011 at 10:19, Mike Clarke 
<jmc-fetchmail <at> milibyte.co.uk> wrote:
> > Recently I've been getting spam arriving with malformed From
> > addresses, like <leslie <at> >. Instead of collecting these messages
> > fetchmail just leaves them on the POP3 server and logs an error
> > message which gets repeated every 10 minutes when it tries to
> > collect mail. The only way I can get stop this is to use a webmail
> > interface to delete the offending messages.
> >
> > Leaving these messages on the server indefinitely does not appear
> > to be the right approach. Is there any way to configure fetchmail
> > to either delete or accept them. If fetchmail were to accept them
> > they could then be dealt with by my spam filters.
>
> Please read the FAQ (http://fetchmail.berlios.de/fetchmail-FAQ.html)
> which details the bug reporting process. This can be summarised as:
>
> 1. Ensure you're running the current release (6.3.19 at this time)
> 2. Provide the details of:
>  a. Your operating system.
>  b. Your compiler version, if you built from source; otherwise, the
> name and origin of the RPM or other binary package you installed.
>  c. The name and version of the SMTP listener or MDA you are
> forwarding to. d. Any command-line options you used.
>  e. The output of env LC_ALL=C fetchmail -V called with whatever
> other command-line options you used.
>  f. The output of env LC_ALL=C fetchmail --nodetach -vvv --nosyslog
> with whatever other command-line options you use routinely.
(Continue reading)


Gmane