Re: Forward to gmail and DMARC

On 14 Jul 2017, at 09:41, Dominic Raferd wrote: > Me: >> Automated? Or is that something you do manually? > > Yes I have it automated Oh, we'll that would be nifty to see what you've done if it's not too much trouble. -- Apple broke AppleScripting signatures in

Re: Mailing list manager recommendation?

On Fri, Jul 14, 2017 at 14:32 Miles Fidelman wrote: > I've had very good luck with Sympa > ... There's also groupserver, which does a good job of combining lists with web-based forum-style access - and is particularly good if your users are going to be setting up and

Re: Mailing list manager recommendation?

On Fri, Jul 14, 2017 at 14:01 Geert Stappers wrote: > On Fri, Jul 14, 2017 at 02:41:07PM +, Tom Browder wrote: > > I need an mailing list manager (MLM) and plan to eventually use GNU > Mailman > 3 (MM3). Until its installation process is easier, I would like to use an

Re: Mailing list manager recommendation?

I've had very good luck with Sympa - which is about the only industrial strength open source list manager. It was developed, and is maintained by a consortium of French universities, and aimed at large installations (e.g., universities). It's probably overkill for small lists, and small

Re: Mailing list manager recommendation?

On Fri, Jul 14, 2017 at 02:41:07PM +, Tom Browder wrote: > I need an mailing list manager (MLM) and plan to eventually use GNU Mailman > 3 (MM3). Until its installation process is easier, I would like to use an > interim MLM that is easiest to install. Ideally I would be able to import >

Re: Forward to gmail and DMARC

On 14 July 2017 at 16:21, @lbutlr wrote: > On 13 Jul 2017, at 15:05, Dominic Raferd wrote: > > On 13 July 2017 at 21:06, @lbutlr wrote: > > > > I forward mail to a gmail user, but there are a lot of bounces from > gmail. I don't

Re: Postfix 3.2.0 - Sending to all MX records

> On Jul 14, 2017, at 11:29 AM, @lbutlr wrote: > > Does it occur to you that there might possibly be a reason the default is > 18000 and that reducing it by a couple of orders of magnitude is not > something you should just do without knowing the ramifications? > > Do you

Re: Postfix 3.2.0 - Sending to all MX records

On 14 Jul 2017, at 06:40, Tom Hudson wrote: > Just to let you know, the problem appears to have been caused by the > "daemon_timeout" being set far too low during our initial configuration. I > know the default in postfix is 18000s but ours had been set to 60s! > Increasing

Re: postfix mail parsing

> On Jul 14, 2017, at 4:16 AM, hyndavirap...@bel.co.in wrote: > > In cleanup process, i'm able to parse all the custom headers. but in qmgr > process i'm not able to do that. The queue manager is not the place for complex message content processing. Your best bet is to write a milter or SMTP

Re: Forward to gmail and DMARC

On 13 Jul 2017, at 15:05, Dominic Raferd wrote: > On 13 July 2017 at 21:06, @lbutlr wrote: > > I forward mail to a gmail user, but there are a lot of bounces from gmail. I > don't honestly care about the ones that google says are spam, but recently

Mailing list manager recommendation?

I need an mailing list manager (MLM) and plan to eventually use GNU Mailman 3 (MM3). Until its installation process is easier, I would like to use an interim MLM that is easiest to install. Ideally I would be able to import mail from the interim MLM into MM3. Note: I have installed MM2 in the

Re: Postfix 3.2.0 - Sending to all MX records

> On Jul 14, 2017, at 8:40 AM, Tom Hudson wrote: > > Thank you for all of your help so far with this issue. > > Just to let you know, the problem appears to have been caused by the > "daemon_timeout" being set far too low during our initial configuration. I > know the

Re: postfix mail parsing

On 2017-07-14 13:46:15 (+0530), hyndavirap...@bel.co.in wrote: i have installed postfix 2.10 from source code. That's getting a little long in the tooth. we are sending mail to postfix server with custom headers. Based on those headers, some actions need to be

Re: Postfix 3.2.0 - Sending to all MX records

Hi, Thank you for all of your help so far with this issue. Just to let you know, the problem appears to have been caused by the "daemon_timeout" being set far too low during our initial configuration. I know the default in postfix is 18000s but ours had been set to 60s! Increasing this to 600s

Re: Block forged addresses

On 14/07/17 10:28, Abi Askushi wrote: > Hi all, > > I was wondering what choices are there to block forged sender email > addresses. > > I was thinking SPF could assist. > The other option I saw is reject_sender_login_mismatch in postfix. * > * > Do you have any other suggestion? > > Many thanx

Re: Block forged addresses

Abi Askushi skrev den 2017-07-14 11:28: Do you have any other suggestion? i do it with reject_sender_access from virtual alias maps after permit_sasl_authenticated real users can still use there sender alias without any issue, but no forged is now possible tested it with postfixadmin as

Block forged addresses

Hi all, I was wondering what choices are there to block forged sender email addresses. I was thinking SPF could assist. The other option I saw is reject_sender_login_mismatch in postfix. Do you have any other suggestion? Many thanx Abi

postfix mail parsing

Hi, i have installed postfix 2.10 from source code. we are sending mail to postfix server with custom headers. Based on those headers, some actions need to be taken at mail server. For that purpose i'm customizing postfix source code. In cleanup process, i'm able to parse all the custom