Considered Spam

Hello,
I have developed a new mail service in which mail flow is:

users send mail to "someuser AT myserver.com". my server process it
(changes the mail body, lets say it "cleans it") - and forwards it to
the real user's email (which he has given me upon registration) -
"sameuser AT yahoo.com".

This acts like bigfoot.com if you're familiar with it, just that it
adds some processing to the message.

any ISP smart enough, like yahoo/hotmail - checks if the originating
sending smtp domain (myserver.com) == recipients domain (yahoo.com),
and there it fails - thus, marking the mails as spam.

I think this is the reason why my mails are considered spam.

With bigfoot it doesn't happen, but it acts EXACTLY the same.
any ideas what i can do?

thx.

Re: Considered Spam

This is a MIME GnuPG-signed message. If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.
The Internet standard for MIME PGP messages, RFC 2015, was published in 1996.
To open this message correctly you will need to install E-mail or Usenet
software that supports modern Internet standards.

--=_mimegpg-commodore.email-scan.com-15671-1157318746-0001
Content-Type: text/plain; format=flowed; charset="US-ASCII"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

yonido@gmail.com writes:

> Hello,
> I have developed a new mail service in which mail flow is:
>
> users send mail to "someuser AT myserver.com". my server process it
> (changes the mail body, lets say it "cleans it") - and forwards it to
> the real user's email (which he has given me upon registration) -
> "sameuser AT yahoo.com".
>
> This acts like bigfoot.com if you're familiar with it, just that it
> adds some processing to the message.
>
> any ISP smart enough, like yahoo/hotmail - checks if the originating
> sending smtp domain (myserver.com) == recipients domain (yahoo.com),
> and there it fails - thus, marking the mails as spam.
>
> I think this is the reason why my mails are considered spam.
>
> With bigfoot it doesn't happen, but it acts EXACTLY the same.
> any ideas what i can do?

Although your description is a bit confusing, as I understand your question:
you are forwarding people's mail, and the recipient's mail server rejects
the forwarded mail because the message's return address does not belong to
you.

There are some defined Internet protocols by which any domain can publish
a list of IP addresses that are authorized to originate any mail naming the
domain as a return address. Verifying whether the message originated from
an authorized IP address is not mandatory, it is optional, but more and more
ISPs are doing it.

There's nothing that you can do. It is unquestionably anyone's prerogative
to publish a list of IP addresses authorized to originate mail with the
domain listed as a return address. It's their domain, they can do whatever
they want. It is also anyone's prerogative to configure their mail servers
any way it pleases them. If they choose to reject all mail that gives a
return address with a domain that publishes a list of authorized IP
addresses, and the mail does not originate from one of those IPs, then it is
their privilege to do so.

Your only option is to change the return address when you forward the mail.
Rather than keep the original return address, replace the original address
with one in your domain.


--=_mimegpg-commodore.email-scan.com-15671-1157318746-0001
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

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

iD8DBQBE+0hax9p3GYHlUOIRAmwOAJ9kYoWe7NRjOLRKY61Ti48a/mnNJwCf cE+2
nlIe1ybe9QPNZaNSZ2/eDYU=
=UVOk
-----END PGP SIGNATURE-----

--=_mimegpg-commodore.email-scan.com-15671-1157318746-0001--

Re: Considered Spam

On comp.mail.misc, in <1157312806.456123.96000@b28g2000cwb.googlegroups.com>, "yonido@gmail.com" wrote: