Gossamer Forum
Home : Products : Gossamer Mail : Discussion :

Forwarding bug??

Quote Reply
Forwarding bug??
Hi,

I have a client that has enabled forwarding of his mail xxx@domain.com to his Gossamer Mail account! He says that he isn't receiving any mail! He has tried forwarding his mail to another e-mail address and it works!
So the problem must be with GM, is it a bug or can't GM handle forwarded messages??

thanks

:D
Quote Reply
Re: [Surfer2] Forwarding bug?? In reply to
Hi,

Is the message bouncing? Do you have bounces turned on? Basically we need a copy of the message Gossamer Mail is getting in order to see what's going on.

Cheers,

Alex
--
Gossamer Threads Inc.
Quote Reply
Re: [Alex] Forwarding bug?? In reply to
No, let me clarify!

My user has a non GM e-mail account. He sets that e-mail account to farward all e-mails to the GM account. The e-mails that GM receives is the forwarded mails from his other account. Clear now?

There is basically something different in the headers that GM isn't interperting right, since its a forwarded message.

I'll try and get hold of his e-mail.

thanks
Quote Reply
Re: [Surfer2] Forwarding bug?? In reply to
What mail server are you using? You'll need one that can add the appropriate headers to the email (ie. who the mail was delivered to), as the headers probably only contain the user's original email address (the one it got sent to, and not the gossamer mail one).

Qmail automatically adds the "Delivered-To" header, with sendmail you can do this: http://www.sendmail.org/faq/section3.html#3.29, to add a "X-Envelope-To" header. I don't believe we've found a solution for Courier yet Unsure.

This is very similar to Anup's BCC bug. Once the email has been delivered to the catchall, when incoming.pl tries to figure out who the email's been sent to, it can't find out because the recipient isn't anywhere to be found in the headers. But if the mail server helps out and adds who the message was actually delivered to (the mail server knows as it's told when the email was delivered to it), then Gossamer Mail will know who to deliver the email to.

I hope this explaination helps.

Adrian
Quote Reply
Re: [brewt] Forwarding bug?? In reply to
I understand, but I have no control of the mail server that my user is using. I think he is using the mail server at register.com. He has basically registered a domain name and added e-mail forwarding of all e-mails of his new domain to the GM account.

I'll try to get a header of his forwarded e-mails...

Thanks
Quote Reply
Re: [Surfer2] Forwarding bug?? In reply to
In Reply To:
but I have no control of the mail server that my user is using.
No, it's not his mail server that needs to do it. Your mail server needs to add in the appropriate header.

Adrian
Quote Reply
Re: [brewt] Forwarding bug?? In reply to
This is the mail that GM won't accept!
It is sent from ymarks@mac.com to info@simchaguidlines.com where it is forwarded to a GM account xxx@zzz.com
Maybe incoming.pl needs to be modified?

Return-Path: <ymarks@mac.com>
Received: from c001.snv.cp.net (h027.c001.snv.cp.net [209.228.32.110])
by www.zzz.com (8.10.2/8.10.2) with SMTP id g6OLs8006390
for <xxx@zzz.com>; Wed, 24 Jul 2002 16:54:08 -0500
Received: (cpmta 20190 invoked from network); 24 Jul 2002 14:54:01 -0700
Delivered-To: simchaguidelines.com%info@simchaguidelines.com
X-UID: Inbox;1009850047;407
Received: (cpmta 20187 invoked from network); 24 Jul 2002 14:54:00 -0700
Received: from 204.179.120.85 (HELO smtpout.mac.com)
by smtp.c001.snv.cp.net (209.228.32.110) with SMTP; 24 Jul 2002 14:54:00 -0700
X-Received: 24 Jul 2002 21:54:00 GMT
Received: from smtp-relay01.mac.com (smtp-relay01-en1 [10.13.10.224])
by smtpout.mac.com (8.12.1/8.10.2/1.0) with ESMTP id g6OLs02F020277
for <info@simchaguidelines.com>; Wed, 24 Jul 2002 14:54:00 -0700 (PDT)
Received: from asmtp02.mac.com (asmtp02-qfe3 [10.13.10.66])
by smtp-relay01.mac.com (8.12.1/8.12.1/1.0) with ESMTP id g6OLrtWf004379
for <info@simchaguidelines.com>; Wed, 24 Jul 2002 14:53:55 -0700 (PDT)
Received: from localhost ([24.228.69.24]) by asmtp02.mac.com
(Netscape Messaging Server 4.15) with ESMTP id GZRWTU00.OHE for
<info@simchaguidelines.com>; Wed, 24 Jul 2002 14:53:54 -0700
Date: Wed, 24 Jul 2002 17:53:51 -0400
Mime-Version: 1.0 (Apple Message framework v482)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Subject: test to michael
From: ymarks@mac.com
To: info@simchaguidelines.com
Content-Transfer-Encoding: 7bit
Message-Id: <D76FDD07-9F4F-11D6-87B1-000393595528@mac.com>
X-Mailer: Apple Mail (2.482)
X-UIDL: ;o/!!jl&"!X$F"!3W@!!

hello this is a test

Last edited by:

Surfer2: Jul 24, 2002, 3:10 PM
Quote Reply
Re: [brewt] Forwarding bug?? In reply to
Quote:
This is very similar to Anup's BCC bug. Once the email has been delivered to the catchall, when incoming.pl tries to figure out who the email's been sent to, it can't find out because the recipient isn't anywhere to be found in the headers



I tried a test only to see if it was similar to Anup's BCC bug. Two GM Domains involved. user@domain1 set to fwd message to user@domain2

user@domain2 sends a mail to user@domain1 . user@domain2 has the mail fwded by user@domain1 so it works...... May be I 'll have to test where the two domains are one GM the other non GM Or is it that the BCC bug has been taken care of (at leats for Courier ;-))

I'll have to check on the Looping when user@domain2 sets mailfwding to user@domain1.


Anup

Last edited by:

anup123: Jul 24, 2002, 7:43 PM
Quote Reply
Re: [brewt] Forwarding bug?? In reply to
Adrian, can you check if the above header will work with GM?

Thanks
Quote Reply
Re: [Surfer2] Forwarding bug?? In reply to
It should work, but you probably need a newer incoming.pl. I've attached the newest incoming.pl. You'll have to change the "use lib '../admin';" line to where your admin path is (look at your old incoming.pl).

Adrian
Quote Reply
Re: [brewt] Forwarding bug?? In reply to
Thanks Adrian!!!

It seems to work with this new version. I had v1.59, yours was 1.61 I think.

Any idea when we might see 2.1.1??

Also, it would be nice if you had a page somewhere where you would list all the fixed bugs for the new version as you go a long. With a list we could first check it to see if the bug has been fixed before we must contact gossamer.

thanks for your help!