Re: [Mailman-Users] FetchMail feed into Mailman

[Dimitri Maziuk via Mailman-Users]

On 3/26/19 4:12 PM, Grant Taylor via Mailman-Users wrote:

> Sure, FetchMail can pull email from the ISP and inject it into the local
> server.  But what advantage does that gain you?  Is said advantage worth
> the complexity?

Apparently lennartwware-infested linux distros no longer require MTA,
presumably because smtp is implemented inside systemd now. I'm not sure
the "extra complexity" argument holds, though.

Before this, cron needed an MTA and stock maintenance stuff like log
rotation ran from crontab. So there was more complexity in getting one
set up without a local MTA, than in setting up postfix.

-- 
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu



signature.asc
Description: OpenPGP digital signature
--
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] FetchMail feed into Mailman

[Grant Taylor via Mailman-Users]

On 3/26/19 12:36 AM, Jim Ziobro wrote:
You won't know how important until you start getting duplicate messages 
like RFC 1047 .


How would having a local MTA change the behavior in the face of a 
duplicate message?


I've seen symptoms of duplicate messages where multiple servers up 
stream are the source of duplication.


Are you implying that local MTA alters this behavior?  Or that it 
provides additional tracing / diagnostic information?


I'm not aware of Mailman having any Message-ID deduplication 
functionality.  Nor have I really seen it as a need.




--
Grant. . . .
unix || die



smime.p7s
Description: S/MIME Cryptographic Signature
--
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] FetchMail feed into Mailman

[Grant Taylor via Mailman-Users]

On 3/26/19 12:36 AM, Jim Ziobro wrote:
why not setup standard Mailman under your favorite mail system and let 
FetchMail do what it does best?


The unneeded complexity of a local mail system.

FetchMail & SMTP Auth would work against an ISP's email server over 
dynamic / dial up connections.


Sure, FetchMail can pull email from the ISP and inject it into the local 
server.  But what advantage does that gain you?  Is said advantage worth 
the complexity?


Especially if the ISP aliases testlist & testlist-* into one mailbox.



--
Grant. . . .
unix || die



smime.p7s
Description: S/MIME Cryptographic Signature
--
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] FetchMail feed into Mailman

[Jim Ziobro]

FetchMail injects messages into the local mail system via SMTP.   I see 
it also supports LMTP.  So I guess you would not need a local mail 
system with Mailman3.  But why not setup standard Mailman under your 
favorite mail system and let FetchMail do what it does best?  It is a 
widely supported configuration.


Your favorite mail system would handle queues for you as well as support 
all the tools (milters, etc) surrounding your mailman deployment.  
Reliably handling the queue is important.  You won't know how important 
until you start getting duplicate messages like RFC 1047 
.


Just checking... when using fetchmail (for example "testlist" on Gmail) 
then you'd be fetching mail for: testl...@gmail.com as well as


testlist-ad...@gmail.com
testlist-boun...@gmail.com
testlist-conf...@gmail.com
testlist-j...@gmail.com
testlist-le...@gmail.com
testlist-ow...@gmail.com
testlist-requ...@gmail.com
testlist-subscr...@gmail.com
testlist-unsubscr...@gmail.com
owner-testl...@gmail.com

My fetchmail test is giving me reasonable Sender info.

Ciao,
//Z\\


On 3/25/2019 12:45 PM, Mark Sapiro wrote:

On 3/25/19 8:21 AM, Grant Taylor via Mailman-Users wrote:

Noted.  I think it would be possible to interject a shim between
fetchmail that would extract what's necessary to speak LMTP to Mailman.


Yes, it would be possible.



Is the LMTP still STDIN / STDOUT or something else (possibly a Unix
socket)?


The shim could receive a message on stdin from fetchmail, but it would
have to deliver the message via LMTP (a subset of SMTP) to Mailman's
lmtp runner which listens on a tcp socket, typically localhost:8024.



I'm trying to understand if I could drive Mailman 3 via Expect.  Not
that I would.  I'm just wondering if I could.


You probably could if you created an Expect script to speak LMTP. I
think the major issue in this is that fetchmail does not provide the
envelope, so you don't know the actual envelope sender to use in the
LMTP MAIL FROM command. If the MDA that delivered the mail to the remote
mailbox was compliant, it will be in a Return-Path: header in the
message, but otherwise you'd have to fake it by using a Sender: or From:
header. Also, you don't directly know the original recipient, although
you can infer it based on the mailbox you fetched from.



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