Re: PCRE on Received Header

2017-11-09 Thread Michael B Allen
On Thu, Nov 9, 2017 at 10:09 AM, Ralph Seichter wrote: > I don't know what you mean by "protocol correct" re trace information. > In any case, https://tools.ietf.org/html/rfc5321#section-4.4 states: The RFC states that Received headers must be inserted and that they must not be altered. Spam filt

Re: PCRE on Received Header

2017-11-08 Thread Michael B Allen
On Wed, Nov 8, 2017 at 6:03 PM, Ralph Seichter wrote: > On 08.11.17 23:45, Michael B Allen wrote: > >> many folks are apparently removing this header entirely. That seems >> sloppy to me but if you think otherwise, please tell me about it. > > 'Received' header

PCRE on Received Header

2017-11-08 Thread Michael B Allen
Hi, I would like to re-write the Received header on some messages being sent using ESMTPSA through my mail server. Specifically the header I would like to re-write currently looks like the following (names have been changed to protect the guilty): " Received: from workstation.busihome.local (pool

Re: Very Basic SPF Record

2015-06-09 Thread Michael B Allen
On Tue, Jun 9, 2015 at 4:55 AM, Peter wrote: > Hi Mike, > > ~all denotes "soft fail". In other words that means that if you forget > to add an IP address of your new server to SPF it is not going to be a > total failure :) Soft fail allows to undertake other steps in case it > happens (say i.e. yo

Re: Very Basic SPF Record

2015-06-08 Thread Michael B Allen
On Tue, Jun 9, 2015 at 12:42 AM, DTNX Postmaster wrote: > On 09 Jun 2015, at 05:20, Michael B Allen wrote: > >> I have never setup SPF records before. I have one server doing >> everything although it has two names www.busicorp.com and >> mail.busicorp.com. >&

Very Basic SPF Record

2015-06-08 Thread Michael B Allen
I have never setup SPF records before. I have one server doing everything although it has two names www.busicorp.com and mail.busicorp.com. My understanding is the following is probably what I want: v=spf1 mx ~all Would you agree? Mike

Re: 454 Relay access denied

2015-06-06 Thread Michael B Allen
On Sat, Jun 6, 2015 at 11:29 PM, Michael B Allen wrote: > Jun 6 23:21:06 www postfix/smtpd[2228]: NOQUEUE: reject: RCPT from > mail-la0-f44.google.com[209.85.215.44]: 454 4.7.1 > : Relay access denied; from= > to= proto=ESMTP helo= > mydestination = $myhostname, localhost.$mydo

454 Relay access denied

2015-06-06 Thread Michael B Allen
I just moved over to my new server and I can't receive mail. I can send mail and do IMAP stuff authenticated. I just cannot receive mail. The server is just a single all-in-one smtpd / submission / imap server for a handful of users. I just copied my old config pretty much verbatim but I must admit

General SPAM Strategy

2015-06-04 Thread Michael B Allen
Hi, I need a better spam setup. Right now I'm using spamd to mark spam and then procmail to put spam in Maildir/.Spam and then run bayes on Maildir/.LearnAsSpam once in a while manually and then I have to delete stuff once in a while manually and so on and so on ad nausium. Can someone give me a

Re: Disabling SSLv2 does not work as expected

2011-09-05 Thread Michael B Allen
On Mon, Sep 5, 2011 at 12:32 PM, Noel Jones wrote: > On 9/5/2011 11:19 AM, Michael B Allen wrote: >> On Mon, Sep 5, 2011 at 12:07 PM, Noel Jones wrote: >>> Or separate your mail and https servers to different IP addresses so >>> it's "not the same serv

Re: Disabling SSLv2 does not work as expected

2011-09-05 Thread Michael B Allen
On Mon, Sep 5, 2011 at 12:07 PM, Noel Jones wrote: > On 9/5/2011 10:50 AM, Michael B Allen wrote: >> On Fri, Sep 2, 2011 at 10:19 PM, Noel Jones wrote: >>> On 9/2/2011 2:17 PM, Michael B Allen wrote: >>>> My objectives are not driven by or based on logic. They are

Re: Disabling SSLv2 does not work as expected

2011-09-05 Thread Michael B Allen
On Fri, Sep 2, 2011 at 10:19 PM, Noel Jones wrote: > On 9/2/2011 2:17 PM, Michael B Allen wrote: >> My objectives are not driven by or based on logic. They are based on >> the requirements of a consortium of credit card companies and banks. > > Do they require you to offe

Re: Disabling SSLv2 does not work as expected

2011-09-02 Thread Michael B Allen
On Fri, Sep 2, 2011 at 1:51 PM, Wietse Venema wrote: > Michael B Allen: >> On Fri, Sep 2, 2011 at 12:41 PM, Wietse Venema wrote: >> > Michael B Allen: >> >> Hello, >> >> >> >> I am using postfix 2.3 on CentOS and I wo

Re: Disabling SSLv2 does not work as expected

2011-09-02 Thread Michael B Allen
On Fri, Sep 2, 2011 at 12:41 PM, Wietse Venema wrote: > Michael B Allen: >> Hello, >> >> I am using postfix 2.3 on CentOS and I would like to disable SSLv2. If >> I do the following: >> >> smtpd_tls_mandatory_protocols = SSLv3, TLSv1 >> smtpd_tls_man

Disabling SSLv2 does not work as expected

2011-09-02 Thread Michael B Allen
Hello, I am using postfix 2.3 on CentOS and I would like to disable SSLv2. If I do the following: smtpd_tls_mandatory_protocols = SSLv3, TLSv1 smtpd_tls_mandatory_ciphers = medium, high but despite the fact that this configuration has been posted and reposted about the WWW, it does not actually

Re: Re-write Received Header to Exclude Home Dynamic IP?

2011-05-01 Thread Michael B Allen
53-84.ph.ph.cox.net >    wsip-98-190-153-84.ph.ph.cox.net has address 98.190.153.84 > > There is no mention of 'pool-' anything above. Is it Cox or Verizon? > From this angle, it's Cox. > > This does not resolve: > >    [duane@fc58] ~> host pool-98-190-153-84.n

Re: Re-write Received Header to Exclude Home Dynamic IP?

2011-04-30 Thread Michael B Allen
08:43 -0400 (EDT) User-Agent: SquirrelMail/1.4.8-5.el5.centos.10 So apparently whatever filtering they're doing isn't as simple as doing an RBL lookup on any IP found in Received headers. Maybe the filter is picking up on some part of the "pool-98-190-153-84.nwrknj.fios.verizon.net" like the "pool-" bit. Mike -- Michael B Allen Java Active Directory Integration http://www.ioplex.com/

Re-write Received Header to Exclude Home Dynamic IP?

2011-04-27 Thread Michael B Allen
Hi, When I send email from home through my Postfix server my home dynamic IP is included in the Received header: Received: from nano.foo.net (pool-98-190-153-84.nwrknj.fios.verizon.net [98.190.153.84]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate re