Re: [Mailman-Users] Relaying issues with Mailman and Postfix

2016-10-04 Thread Mark Sapiro 
On 10/03/2016 01:01 PM, Fongaboo wrote:
> 
> However I think I'm not even getting that far yet. I'm running into a
> roadblock that I believe is strictly Postfix. So I take it that messages
> aren't even touching the new Mailman daemon yet.
> 
> No matter what I do, I am getting relay errors when I send a message
> with the Subject 'help' to -requ...@lists.domain.tld, as such:
> 
> Oct  3 14:12:20  postfix/smtpd[67338]: connect from
> mail.outsidedomain.tld[x.x.x.x]
> Oct  3 14:12:20  postfix/smtpd[67338]: NOQUEUE: reject: RCPT
> frommail.outsidedomain.tld[x.x.x.x]: 454 4.7.1
> : Relay access denied;
> from=
> to= proto=ESMTP
> helo=


I'm not sure about the above, but the below says


> But then additionally I'm noticing these entries as well:
> 
> Oct  3 14:09:13  postfix/qmgr[49782]: warning: connect to
> transport private/mailman: No such file or directory
> Oct  3 14:09:14  postfix/error[67292]: E587C642A5F:
> to=, relay=none, delay=4801,
> delays=4801/0.02/0/0.03, dsn=4.3.0, status=deferred (mail transport
> unavailable)


you have an incomplete postfix_to_mailman.py configuration.

See  and be sure to read all of the
linked



> I tried adding the following, but to no avail:
> 
> main.cf:
> 
> relay_recipient_maps = hash:/usr/local/etc/postfix/relay_recipients
> 
> transport_maps = hash:/usr/local/etc/postfix/transport
> 
> 
> relay_recipients:
> 
> (for each list)
> listn...@lists.domain.tld OK
> listname-listn...@lists.domain.tld OK
> listname-boun...@lists.domain.tld OK
> listname-conf...@lists.domain.tld OK
> listname-j...@lists.domain.tld OK
> listname-le...@lists.domain.tld OK
> listname-ow...@lists.domain.tld OK
> listname-requ...@lists.domain.tld OK
> listname-subscr...@lists.domain.tld OK
> listname-unsubscr...@lists.domain.tld OK
> 
> 
> transport:
> 
> lists.domain.tld mailman:


This says use the 'mailman' transport for ALL mail to the
lists.domain.tld domain. Per the above logs, this transport is probably
not completely defined in master.cf[1]. If this is a Debian/Ubuntu
Mailman package, read all the Debian documentation about the choice of
delivering to Mailman via aliases or via postfix_to_mailman.py and keep
in mind everything in the above referenced wiki article and the things
linked therefrom.

In case you haven't figured it out yet, postfix_to_mailman.py is a hot
button issue for me. Debian distributes it; people fail to comprehend
the Debian documentation and mis-configure it and then come here for
help. Read what I said 4 years ago. I don't really blame you. You're
certainly not alone, but if Debian had to deal with all the
postfix_to_mailman.py issues I've been dealing with for years, I suspect
they'd stop distributing it.

[1] This is what you should have in master.cf it you really insist on
using postfix_to_mailman.py

mailman   unix  -   n   n   -   -   pipe
  flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py
  ${nexthop} ${user}

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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

Re: [Mailman-Users] Personalised mails, content very depending on mail client

2016-10-04 Thread Mark Sapiro 
On 10/03/2016 07:06 AM, Henrik Rasmussen wrote:
> 
> Is there something I, as site admin, or the list-admins can do, to get 
> personalized HTML mails, even to Outlook users?


You can set Non-digest options -> personalize to Full Personalization
which will cause delivered non-digest messages to be addressed To: the
recipient, and not try to use msg_header for this purpose.

As far as brain dead MUAs not properly rendering multipart messages with
msg_header and or msg_footer added, see .

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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

[Mailman-Users] Personalised mails, content very depending on mail client

2016-10-04 Thread Henrik Rasmussen 
As I am testing personalized mails from Mailman (2.1.12) I was wondering why 
various email clients display the content different.


* If I send an HTML mail containing only text, both Gmail and Outlook 
includes personalization in msg_header "Hello %(user_name)s . This is a test"

* If I send an HTML mail containing an image, Gmail shows "Hello 
[member's name]. This is a test" on top and the rest of the mail, including 
image, but Outlook only show the e-mail (including the image), NOT the 
msg_header not msg_footer.

* If I use Outlook to email received on Gmail, using IMAP connection, 
"Hello [member's name]. This is a test" is displayed at the top of the received 
mail, but the content from the sender and the image is attached.

My content filtering -> pass_mime_types are
multipart/mixed
multipart/alternative
text/plain
text/html

but pass_mime_types shouldn't affect the mail as content filtering -> 
filter_content if off. Also collapse_alternatives or convert_html_to_plaintext 
doesn't change a thing (as content filtering -> filter_content if off).

Is there something I, as site admin, or the list-admins can do, to get 
personalized HTML mails, even to Outlook users?

Henrik Rasmussen
--
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

[Mailman-Users] Relaying issues with Mailman and Postfix

2016-10-04 Thread Fongaboo 


Running Postfix 2.11.7 on FreeBSD 10.2-RELEASE. I am migrating a listserv 
on an older box to this one, running newly-installed Mailman 2.1.20.


I found a one-pager that showed me what to tar up and move over to migrate 
my lists to the new instance of Mailman. Hostname is not changing, so that 
made this part fairly painless.


However I think I'm not even getting that far yet. I'm running into a roadblock 
that I believe is strictly Postfix. So I take it that messages aren't even 
touching the new Mailman daemon yet.


No matter what I do, I am getting relay errors when I send a message with the 
Subject 'help' to -requ...@lists.domain.tld, as such:


Oct  3 14:12:20  postfix/smtpd[67338]: connect from 
mail.outsidedomain.tld[x.x.x.x]
Oct  3 14:12:20  postfix/smtpd[67338]: NOQUEUE: reject: RCPT 
frommail.outsidedomain.tld[x.x.x.x]: 454 4.7.1 : Relay access 
denied; from= to= proto=ESMTP 
helo=

But then additionally I'm noticing these entries as well:

Oct  3 14:09:13  postfix/qmgr[49782]: warning: connect to transport 
private/mailman: No such file or directory
Oct  3 14:09:14  postfix/error[67292]: E587C642A5F: 
to=, relay=none, delay=4801, 
delays=4801/0.02/0/0.03, dsn=4.3.0, status=deferred (mail transport unavailable)


I tried adding the following, but to no avail:

main.cf:

relay_recipient_maps = hash:/usr/local/etc/postfix/relay_recipients

transport_maps = hash:/usr/local/etc/postfix/transport


relay_recipients:

(for each list)
listn...@lists.domain.tld OK
listname-listn...@lists.domain.tld OK
listname-boun...@lists.domain.tld OK
listname-conf...@lists.domain.tld OK
listname-j...@lists.domain.tld OK
listname-le...@lists.domain.tld OK
listname-ow...@lists.domain.tld OK
listname-requ...@lists.domain.tld OK
listname-subscr...@lists.domain.tld OK
listname-unsubscr...@lists.domain.tld OK


transport:

lists.domain.tld mailman:


I then postmap'ed relay_recipients and transport and restarted postfix. Even 
restarted mailman for good measure. But no such luck.



My only suspicion is that maybe in Postfix 2.11.7, I need to do something in 
MySQL/PostfixAdmin concerning this line in main.cf?:


relay_domains = proxy:mysql:/usr/local/etc/postfix/mysql_relay_domains_maps.cf



Any assistance or advice, as always, would be greatly appreciated!



Thanx
--
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