Re: email from comcast.net is bouncing

2013-09-01 Thread Grant
> Grant: >> I'm on Gentoo and I use the etc-update script to update config files >> after upgrading. Should dnsblog be uncommented in a default >> master.cf? If so I may need to file a Gentoo bug. > > As distributed by me, the 'inet' smtpd service is active, and all > postscreen-related services

Re: email from comcast.net is bouncing

2013-09-01 Thread Wietse Venema
Grant: > I'm on Gentoo and I use the etc-update script to update config files > after upgrading. Should dnsblog be uncommented in a default > master.cf? If so I may need to file a Gentoo bug. As distributed by me, the 'inet' smtpd service is active, and all postscreen-related services are commen

Re: email from comcast.net is bouncing

2013-09-01 Thread Grant
>> I grep'ed the mail logs for dnsblog and got a huge number of these: >> >> [postfix/postscreen] warning: psc_dnsbl_request: connect to >> private/dnsblog service: No such file or directory >> >>> >> >>> Looks as if you've found the problem. >> >>> >> >>> Make sure your master.

Re: email from comcast.net is bouncing

2013-09-01 Thread James Griffin
!-- On Sun 1.Sep'13 at 9:52:50 BST, Grant (emailgr...@gmail.com), wrote: > I grep'ed the mail logs for dnsblog and got a huge number of these: > > [postfix/postscreen] warning: psc_dnsbl_request: connect to > private/dnsblog service: No such file or directory > >>> > >>> Look

Re: email from comcast.net is bouncing

2013-09-01 Thread Grant
I grep'ed the mail logs for dnsblog and got a huge number of these: [postfix/postscreen] warning: psc_dnsbl_request: connect to private/dnsblog service: No such file or directory >>> >>> Looks as if you've found the problem. >>> >>> Make sure your master.cf has an entry like: >>

Re: email from comcast.net is bouncing

2013-08-31 Thread James Griffin
!-- On Fri 30.Aug'13 at 20:27:43 BST, Grant (emailgr...@gmail.com), wrote: > >> I grep'ed the mail logs for dnsblog and got a huge number of these: > >> > >> [postfix/postscreen] warning: psc_dnsbl_request: connect to > >> private/dnsblog service: No such file or directory > > > > Looks as if you'

Re: email from comcast.net is bouncing

2013-08-30 Thread Noel Jones
On 8/30/2013 2:27 PM, Grant wrote: >>> I grep'ed the mail logs for dnsblog and got a huge number of these: >>> >>> [postfix/postscreen] warning: psc_dnsbl_request: connect to >>> private/dnsblog service: No such file or directory >> >> Looks as if you've found the problem. >> >> Make sure your mast

Re: email from comcast.net is bouncing

2013-08-30 Thread Grant
>> I grep'ed the mail logs for dnsblog and got a huge number of these: >> >> [postfix/postscreen] warning: psc_dnsbl_request: connect to >> private/dnsblog service: No such file or directory > > Looks as if you've found the problem. > > Make sure your master.cf has an entry like: > > dnsblog unix

Re: email from comcast.net is bouncing

2013-08-30 Thread Wietse Venema
Grant: > >> Aug 26 21:21:35 [postfix/tlsproxy] CONNECT from [209.85.219.51]:41193 > >> Aug 26 21:21:36 [postfix/postscreen] NOQUEUE: reject: RCPT from > >> [209.85.219.51]:41193: 450 4.3.2 Service currently unavailable; > >> from=, to=, proto=ESMTP, > >> helo= > >> Aug 26 21:21:36 [postfix/tlsproxy

Re: email from comcast.net is bouncing

2013-08-30 Thread Noel Jones
On 8/30/2013 3:44 AM, Grant wrote: > > I grep'ed the mail logs for dnsblog and got a huge number of these: > > [postfix/postscreen] warning: psc_dnsbl_request: connect to > private/dnsblog service: No such file or directory Looks as if you've found the problem. Make sure your master.cf has an e

Re: email from comcast.net is bouncing

2013-08-30 Thread Grant
>> > Aug 26 21:21:35 [postfix/tlsproxy] CONNECT from >> > [209.85.219.51]:41193 >> > Aug 26 21:21:36 [postfix/postscreen] NOQUEUE: reject: RCPT from >> > [209.85.219.51]:41193: 450 4.3.2 Service currently unavailable; >> > from=, to=, proto=ESMTP, >> > helo= >> > Aug 26 21:21:36 [postfix/tlsproxy]

Re: email from comcast.net is bouncing

2013-08-30 Thread Grant
>> Aug 26 21:21:35 [postfix/tlsproxy] CONNECT from [209.85.219.51]:41193 >> Aug 26 21:21:36 [postfix/postscreen] NOQUEUE: reject: RCPT from >> [209.85.219.51]:41193: 450 4.3.2 Service currently unavailable; >> from=, to=, proto=ESMTP, >> helo= >> Aug 26 21:21:36 [postfix/tlsproxy] DISCONNECT [209.8

Re: email from comcast.net is bouncing

2013-08-27 Thread Wietse Venema
/dev/rob0: > > Aug 26 21:21:35 [postfix/tlsproxy] CONNECT from > > [209.85.219.51]:41193 > > Aug 26 21:21:36 [postfix/postscreen] NOQUEUE: reject: RCPT from > > [209.85.219.51]:41193: 450 4.3.2 Service currently unavailable; > > from=, to=, proto=ESMTP, > > helo= > > Aug 26 21:21:36 [postfix/tlspr

Re: email from comcast.net is bouncing

2013-08-27 Thread /dev/rob0
On Tue, Aug 27, 2013 at 12:56:42AM -0700, Grant wrote: > >> >> >> SUBJECT: Delivery status notification > >> >> >> This is an automatically generated Delivery Status > >> >> >> Notification. Delivery to the following recipients was > >> >> >> aborted after 7 second(s): mas...@masked.com > >> >> >

Re: email from comcast.net is bouncing

2013-08-27 Thread Wietse Venema
Grant: > Aug 26 21:21:35 [postfix/tlsproxy] CONNECT from [209.85.219.51]:41193 > Aug 26 21:21:36 [postfix/postscreen] NOQUEUE: reject: RCPT from > [209.85.219.51]:41193: 450 4.3.2 Service currently unavailable; > from=, to=, proto=ESMTP, > helo= > Aug 26 21:21:36 [postfix/tlsproxy] DISCONNECT [209.

Re: email from comcast.net is bouncing

2013-08-27 Thread Grant
>> >> >> SUBJECT: Delivery status notification >> >> >> This is an automatically generated Delivery Status Notification. >> >> >> Delivery to the following recipients was aborted after 7 second(s): >> >> >> mas...@masked.com >> >> > >> >> > If you want that mail, whitelist them, >> >> >> >> They sh

Re: email from comcast.net is bouncing

2013-08-26 Thread Wietse Venema
Grant: > >> >> SUBJECT: Delivery status notification > >> >> This is an automatically generated Delivery Status Notification. > >> >> Delivery to the following recipients was aborted after 7 second(s): > >> >> mas...@masked.com > >> > > >> > If you want that mail, whitelist them, > >> > >> They sho

Re: email from comcast.net is bouncing

2013-08-26 Thread Grant
>> >> SUBJECT: Delivery status notification >> >> This is an automatically generated Delivery Status Notification. >> >> Delivery to the following recipients was aborted after 7 second(s): >> >> mas...@masked.com >> > >> > If you want that mail, whitelist them, >> >> They should already be whitelis

Re: email from comcast.net is bouncing

2013-08-26 Thread Grant
>> >> SUBJECT: Delivery status notification >> >> This is an automatically generated Delivery Status Notification. >> >> Delivery to the following recipients was aborted after 7 second(s): >> >> mas...@masked.com >> > >> > If you want that mail, whitelist them, >> >> They should already be whitelis

Re: email from comcast.net is bouncing

2013-08-26 Thread Wietse Venema
Grant: > >> SUBJECT: Delivery status notification > >> This is an automatically generated Delivery Status Notification. > >> Delivery to the following recipients was aborted after 7 second(s): > >> mas...@masked.com > > > > If you want that mail, whitelist them, > > They should already be whitelis

Re: email from comcast.net is bouncing

2013-08-25 Thread Grant
>> SUBJECT: Delivery status notification >> This is an automatically generated Delivery Status Notification. >> Delivery to the following recipients was aborted after 7 second(s): >> mas...@masked.com > > If you want that mail, whitelist them, They should already be whitelisted through my use of l

Re: email from comcast.net is bouncing

2013-08-25 Thread Wietse Venema
Grant: > SUBJECT: Delivery status notification > This is an automatically generated Delivery Status Notification. > Delivery to the following recipients was aborted after 7 second(s): > mas...@masked.com If you want that mail, whitelist them, Wietse

email from comcast.net is bouncing

2013-08-25 Thread Grant
I've had a long-running problem with messages sent from comcast.net addresses bouncing back to the sender. I thought this could be due to the postscreen deep protocol checks I use with postfix-2.11_pre*, but I added the following to main.cf on August 15th and yesterday I received a message from so