On 10/29/18 4:51 PM, Mark Sapiro wrote:
A simple, but possibly unsatisfactory solution is to put the following
two lines in mm_cfg.py
GLOBAL_PIPELINE.remove('ToDigest')
GLOBAL_PIPELINE.insert(GLOBAL_PIPELINE.index('ToOutgoing'), 'ToDigest')
This will cause the message to not be added to the
On 10/29/18 12:42 PM, David Gibbs wrote:
>
> When MM 2.1.29 sends out a mime encoded digest, the individual messages
> in the digest don't have the reply-to header set so replies go back to
> the list (as with non-digest messages).
>
> Is there any way to have the reply-to header set correctly
Folks:
On my lists, I have reply_goes_to_list set so users reply's default to the list
address.
When MM 2.1.29 sends out a mime encoded digest, the individual messages in the
digest don't have the reply-to header set so replies go back to the list (as
with non-digest messages).
Is there
Thank you for your reply - at your recommendation I have changed the DNS
to a full A record. And now that mailman is our production list
program, I have assigned it the lists host name: lists.bates.edu.
However, I am still seeing the previous behavior as described. When I
have a list with
Karen R McArthur wrote:
Thank you for your reply - at your recommendation I have changed the DNS
to a full A record. And now that mailman is our production list
program, I have assigned it the lists host name: lists.bates.edu.
However, I am still seeing the previous behavior as described.
My host_name *is* set to lists.bates.edu. Following is a snip from my
config_list -o command:
# The host_name is the preferred name for email to mailman-related
# addresses on this host, and generally should be the mail host's
# exchanger address, if any. This setting can be useful for
Karen R McArthur wrote:
My host_name *is* set to lists.bates.edu. Following is a snip from my
config_list -o command:
# The host_name is the preferred name for email to mailman-related
# addresses on this host, and generally should be the mail host's
# exchanger address, if any. This setting
On default setup, I currently have:
first_strip_reply_to = False
reply_goes_to_list = 1
reply_to_address = ''
My list server fqdn: mailman.bates.edu
I would like the reply-to to go to this fqdn
([EMAIL PROTECTED]), but it gets stripped to [EMAIL PROTECTED]
As far as I can tell, sendmail is
Karen R McArthur wrote:
My list server fqdn: mailman.bates.edu
I would like the reply-to to go to this fqdn
([EMAIL PROTECTED]), but it gets stripped to [EMAIL PROTECTED]
For one thing, mailman.bates.edu is a CNAME alias that points to
postoffice03.bates.edu, so all MTAs should be
Karen R McArthur wrote:
On default setup, I currently have:
first_strip_reply_to = False
reply_goes_to_list = 1
reply_to_address = ''
Brad has already posted a very good response. I'm just responding to a
couple of technical issues.
With the above settings, the list posting address will be
Hello all,
I'm using operas mail client.
Every mailing list running mail man does not add a reply-to header, so if
I answer a message my reply goes directly to the person but not to the
list :(
Is there something that can be done?
bye!
Dominik
To: mailman-users@python.org
Subject: [Mailman-Users] reply-to header missing..
Hello all,
I'm using operas mail client.
Every mailing list running mail man does not add a reply-to
header, so if I answer a message my reply goes directly to
the person but not to the list
Hello!
On Tue, Oct 04, 2005 at 01:21:31PM +0200, Dominik Werder wrote:
Hello all,
I'm using operas mail client.
Every mailing list running mail man does not add a reply-to header, so if
I answer a message my reply goes directly to the person but not to the
list :(
Is there something that
Hello,
I have sucessfully set up mailman, but when I try to reply to all the
address for the list is not the address for the list.
Here is an example:
List address: [EMAIL PROTECTED]
But when I reply to all, the address in the email to header is:
[EMAIL PROTECTED]
My email client is MS
14 matches
Mail list logo
