103301 - Like to see bounce feature implemented

Status: RESOLVED DUPLICATE of bug 109930

(SeaMonkey :: MailNews: Message Display, enhancement)

Description

[Frank Furter]

I read through the exisiting bugs, but it looks like this issue has kinda 
gone nowhere.

Has anyone used the Mail.app in Mac OSX? It has a 'bounce' feature that 
works great. I'm not technical enough to supply the details, but I've tried it 
a few times with friends and the email is definitely bounced back saying 
the recipient was unknown.

I'm not personally interested in this being a filter. When you receive some 
spam or whatever, you can simply right-click the message and say 
bounce.

Thoughts?

Comment 1

[R.K.Aa.]

dup of bug 12916?

Comment 2

[riscky]

I don't think this is a dup of 12916

the "bounce" in mail.app is like pine's bounce and produces something like:

"This Message was undeliverable due to the following reason:

Each of the following recipients was rejected by a remote mail server.
The reasons given by the server are included to help you determine why
each recipient was rejected.

    Recipient: <[e-mail]>
    Reason:    Invalid recipient: <[e-mail]>"

Esentally mail.app tells your pop or IMAP server to send the email back to the
orginal source telling the orginal source that it is unable to deliver email...

From my reading of bug 12916 several users reply to email from a
[e-mail] and the email is routed to different techsupport
people to work with the msq... i know i am a tad off on this but thats a general
idea why i think this isn't a dup...

Oh I use mail.app all the time to bounce spam from my main email account... so
it can be a nice thing.

Comment 3

[riscky]

opps... sorry for the spam... I wasn't thinking... where i typed
[e-mail] replace that with some_user@dont_want_spam.net

Comment 4

[Steve K]

This probably ought to be OS:ALL, not OS: MacOS X.  

Comment 5

[Greg K.]

It is definitely a duplicate of bug 12916, in that it requests a bounce feature be added to 
Messenger. The nature of that feature should be debated under that bug and in the applicable 
newsgroup.

*** This bug has been marked as a duplicate of 12916 ***

Comment 6

[laurel]

Marking verified as a duplicate.

Comment 7

[FZiegler]

*** This bug has been marked as a duplicate of 109930 ***