On 8/28/2014 1:58 AM, Alan Meyer wrote:
Hi,
I recently set up a Ubuntu 14.04 server with Mailman 2.1.16. It took a while
for me to configure because I needed to modify the setup procedure from
Ubuntu's instructions to what the mailman documentation suggested (no use of
the postfix-to-mailman.py script).
At any rate, my main goal has been to use mailman for an Indian Guides group,
which for years has just been an email list of about 50 people. Mailman seemed
like a great option to help ensure that all of the members are accounted for in
each email and to have archives available.
The problem that I'm having is that for some people on the list, they don't reliably get
their emails. Mostly, this is from members that are on gmail.com or hotmail.com or in
some cases ymail.com. The "lost" emails get stuck in their spam filter, and in
some cases hotmail users don't get their emails at all.
I did some testing with a practice list I created (sending to my own set of yahoo, gmail
accounts), where my yahoo account was sending to members on a gmail account. I found no issue
sending directly from yahoo to gmail, but from yahoo->mail list->gmail got caught in the
gmail's spam filter. The gmail account spam folder would flag it and give me a note something
to the effect of "The sender's yahoo.com address could not be confirmed".
Furthermore, in the gmail account, I can mark the email as "Not SPAM" but that
doesn't help on subsequent emails.
As an experiment, I changed a few settings (from default Yes to No), but these
didn't seem to make a difference:
- Should messages from this mailing list include the RFC 2369 (i.e. List-*)
headers? Yes is highly recommended.
- Should postings include the List-Post: header?
- Should the Sender header be rewritten for this mailing list to avoid stray
bounces? Yes is recommended.
My search for SPAM hasn't helped (most SPAM issues are related to actual SPAM
getting in from user accounts).
Have others encountered this type of issue? Are there any settings I can use
or steps I can take to help resolve this?
Thanks in advance.
Sincerely,
-Alan
Alan, I think that you are experiencing DMARC problems. You need the
latest Mailman (2.1.18-1) to handle DMARC issues. See the archives
of this list from this past April onward to read about DMARC and
Mailman.
--Barry Finkel
------------------------------------------------------
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
