Michael Welch wrote:
Right, that must be because this list's Sender: header does not look like a
real email address. I wonder why ours are different.
This thread has been well covered. I just want to add a couple of
things:
As mentioned in other replies, the difference in the 'bounces'
Thanks to all, lots of info in there.
I see now that it is probably not user error that is causing this, but that
some users have a version of Outlook that may inadvertently picking up the
address from the Sender: header.
So, I have a feature suggestion: Add an autoreply option for -bounces
Michael Welch writes:
So, I have a feature suggestion: Add an autoreply option for
-bounces incoming emails.
Executive summary: not likely to help, not likely to happen.
This is just going to annoy people who can't easily help themselves
(Outlook and Blackberry users, apparently). You
Michael Welch wrote:
That means I end up having to do personal contact with way too many
people to let them know that they did not use the correct address, so
they need to resend.
I notice that this list does not show me the real address in those
headers, but rather something like:
Sender:
Brad Knowles [EMAIL PROTECTED] wrote in reply, in part:
Over the several years I've been acting as one of the co-owners of this
list, I don't recall getting any messages being sent by users to
mailman-users-bounces.
I have some Mailman lists, and if a recipient does a reply-all
from a BlackBerry
Brad Knowles wrote at 09:09 AM 11/17/2008:
Michael Welch wrote:
That means I end up having to do personal contact with way too many
people to let them know that they did not use the correct address, so
they need to resend.
I notice that this list does not show me the real address in those
Michael Welch wrote:
That does not work, I assume because the message to -owner is coming from
-bounces and not from the original list member. So an autoresponder would
be sent back to -bounces, which might actually create an endless loop
(though I imagine Mailman traps for that).
You are
Hi Brad. I did test it, hence That does not work.
But I do appreciate the reminder, because I had intended to populate that
particular autoresponder.
Brad Knowles wrote at 11:09 AM 11/17/2008:
Michael Welch wrote:
That does not work, I assume because the message to -owner is coming from
Michael Welch wrote:
Hi Brad. I did test it, hence That does not work.
Ahh, sorry. It wasn't clear to me that you had actually tested it or not.
My bad.
But I do appreciate the reminder, because I had intended to populate that
particular autoresponder.
And thanks to your note, I have
Michael Welch writes:
Right, that must be because this list's Sender: header does not
look like a real email address. I wonder why ours are different.
It's one of the VERP settings. While true VERP is done by the
MTA, not by agents like Mailman, the basic idea is the same: to
personalize
Stephen J. Turnbull wrote:
The downside is performance, which is why VERP off is the default.
That and the fact that not all MTAs support VERP at all, and some of the
ones that do support VERP don't support it by default. So, we leave this
option turned off by default.
I'm still on
Stephen J. Turnbull wrote:
It's one of the VERP settings. While true VERP is done by the
MTA, not by agents like Mailman, the basic idea is the same: to
personalize various fields in the message so that the original that
elicited a reply (including a bounce) can be identified.
Um... Please
Brad Knowles writes:
VERP is available on Mailman 2.1.5, but it does have to be enabled in the
configuration file, before you can actually see the option in the web admin
UI for your list(s).
OK, so that probably was a deliberate decision and won't fly on his ISP.
Which is actually
13 matches
Mail list logo
