Topic: Problem with email

[Oosterheert]

We have a SME 7.0 server running at one of our clients which uses the email server of SME. We pop the provider and SME sends the mails to the right users. This mostly works, but every now and then SME decides to route the email not to the user, but to the postmaster, being us.

This seems to happen mostly(/only?) when the sender uses a mailinglist and not when they give the exact mailadres.

This morning someone send an email to 2 users at our client. Both those emails were send by SME to 'postmaster'. I called up the sender and she confirms she send the email to the 2 users using her adress book. Her adressbook has the right email adresses :dewit@something.nl and blaauw@something.nl (it's our problem so the clients name doesn't need to be known in this). According to the headers SME seems to think the adress is 235-dewit@something, so were does this number come from and what can i do about it?

(tedocweb is the provider of our cliënt)

Return-Path: <F.jonkers@sender.com>
X-Envelope-To: support@oosterheert.net, archievering@oosterheert.nl
X-Spam-Status: No, hits=0.0 required=2.0
   tests=AWL: 0.063,BAYES_00: -1.665,FORGED_RCVD_HELO: 0.135,
   HTML_50_60: 0.134,HTML_MESSAGE: 0.001,SUBJ_ALL_CAPS: 0.997,
   TO_CC_NONE: 0.131,UNPARSEABLE_RELAY: 0.001,TOTAL_SCORE: -0.203
X-Spam-Level:
Received: from oosterheert.nl ([193.138.157.226])
   by postadres.net
   (using TLSv1/SSLv3 with cipher AES256-SHA (256 bits))
   for support@oosterheert.net;
   Mon, 23 Oct 2006 09:55:53 +0200
Received: from res1.digitalus.nl (root@localhost)
   by oosterheert.nl (8.12.10/8.12.10) with ESMTP id k9N7taM5014780
   for <support@oosterheert.nl>; Mon, 23 Oct 2006 09:55:36 +0200
X-ClientAddr: 195.35.136.106
Received: from ns5.tedocweb.net (wc-106.r-195-35-136.essentkabel.com [195.35.136.106])
   by res1.digitalus.nl (8.12.10/8.12.10) with ESMTP id k9N7tWim014755
   for <support@oosterheert.nl>; Mon, 23 Oct 2006 09:55:32 +0200
Received: (qmail 6587 invoked from network); 23 Oct 2006 09:55:27 +0200
Received: from unknown (HELO something) (217.166.196.33)
  by duikschoolbrabant.nl with SMTP; 23 Oct 2006 09:55:27 +0200
Received: (qmail 2714 invoked by uid 101); 23 Oct 2006 07:55:26 -0000
Delivered-To: postmaster@os11.something
Received: (qmail 2712 invoked by alias); 23 Oct 2006 07:55:26 -0000
Delivered-To: alias-localdelivery-postmaster@something
Received: (qmail 2709 invoked by uid 453); 23 Oct 2006 07:55:26 -0000
X-Spam-Status: No, hits=0.7 required=7.0
   tests=HTML_50_60,HTML_FONT_BIG,HTML_MESSAGE,SUBJ_ALL_CAPS
X-Spam-Check-By: something
Received: from localhost (HELO localhost) (127.0.0.1)
    by something (qpsmtpd/0.31.1) with ESMTP; Mon, 23 Oct 2006 09:55:16 +0200
Delivered-To: 235-info@something.nl
Received: from mail3.tedocweb.net
   by localhost with POP3 (fetchmail-6.2.5)
   for postmaster@something (multi-drop); Mon, 23 Oct 2006 09:55:16 +0200 (CEST)
Received: (qmail 6188 invoked by uid 110); 23 Oct 2006 09:54:22 +0200
Delivered-To: 235-blaauw@something.nl
Received: (qmail 6179 invoked from network); 23 Oct 2006 09:54:22 +0200
Received: from senderh1.sender.com (HELO senderH3.sender.com) (62.58.200.170)
  by duikschoolbrabant.nl with SMTP; 23 Oct 2006 09:54:22 +0200
Content-Transfer-Encoding: 7bit
Importance: normal
Priority: normal
Received: from sender.com ([192.168.1.17]) by senderH3.sender.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 23 Oct 2006 09:53:48 +0200
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2757
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
   boundary="----_=_NextPart_001_01C6F678.5F3E5976"
Subject: 26-10-2006 GEEN LEVERINGEN
Date: Mon, 23 Oct 2006 09:53:48 +0200
Message-ID: <903239AB0C6CE845AE1D2D6434AA861A0C255F24@senderh1.sender.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: 26-10-2006 GEEN LEVERINGEN
Thread-Index: Acb2eF8lps0XDNkzSnqN+ilse636Ng==
From: "Fonny Jonkers" <F.jonkers@sender.com>
Bcc:
X-OriginalArrivalTime: 23 Oct 2006 07:53:48.0360 (UTC) FILETIME=[5F64FC80:01C6F678]
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on ns5.tedocweb.net
X-Spam-Level: *
X-Fetchmail-Warning: no recipient addresses matched declared local names
X-Old-Spam-Status: No, hits=2.0 required=7.0 tests=EXCUSE_16,HTML_30_40,
   HTML_FONTCOLOR_BLUE,HTML_FONTCOLOR_RED,HTML_FONT_BIG,HTML_MESSAGE,
   LINES_OF_YELLING,LINES_OF_YELLING_2,SUBJ_ALL_CAPS autolearn=no
   version=2.63
X---MailScanner-Information: Please contact the ISP for more information
X---MailScanner: Found to be clean
X-MailScanner-From: f.jonkers@sender.com

This is a multi-part message in MIME format.

......
their mailcontent etc.
......
------_=_NextPart_001_01C6F678.5F3E5976--

[mmccarn]

This is a known issue when using fetchmail to retrieve email that was Bcc'd to multiple users that both use the same maildrop mailbox.

From the point of view of the off-site server - it received a single message and was told to deliver it to the same recipient (your single POP3 off-site mailbox) twice.

If you control the mailbox with the off-site pop3 mailbox it may be possible to tell that server to insert "X-Original-To:..." headers containing the actual recipient address so that Fetchmail can route it properly when it finally joins the dance.

Here's a link to the Fetchmail manual describing this:
http://www.fetchmail.info/fetchmail-man.html#35

[rulle_mus]

Hello,

I have the same problem at several sites.

Have you been able to work arround this?

Regards Mus

[mmccarn]

The problem I described CANNOT be fixed on any server running fetchmail to collect email from a POP3 mailbox - the routing information needed to prevent the duplicates has already been completely removed from the incoming messages before they were placed in the off-site POP mailbox.

Your choices are to try to modify the POP server to add "X-Original-To" headers, to reconfigure the off-site server (and fetchmail) to have fetchmail use ETRN or ODMR (I can't help you here...), or to have your email delivered directly to your SME server.

I use the last method, even with a dynamic IP:

- I use DynDNS to give a domain name to my SME
- I have my mx record pointing to the DynDNS domain name
- I send outgoing emails through my ISP

[CharlieBrady]

Your choices are to try to modify the POP server to add "X-Original-To" headers, to reconfigure the off-site server (and fetchmail) to have fetchmail use ETRN or ODMR (I can't help you here...), or to have your email delivered directly to your SME server.

I use the last method, even with a dynamic IP:

- I use DynDNS to give a domain name to my SME
- I have my mx record pointing to the DynDNS domain name
- I send outgoing emails through my ISP

That is the best solution. Multi-drop mail is fundamentally broken. It cannot be done simply and reliably. Avoid it if at all possible.