On Mon, Aug 04, 2008, Peter Hardy wrote:
I for one think it's perfectly cromulent. If the sender MX utilises
greylisting then it'll send back a transient failure message as distinct
from a permanent 550 failure. At that point, the receiving MX can either
assume a transient failure means it's
Voytek Eymont [EMAIL PROTECTED] writes:
I have some web generated emails being sent as 'apache@' [as the
default web user] (which perhaps I should change, but it never really
caused problems in the past)
now, an isp appears to be doing a user lookup as below and bounces
emails, claiming my
On Mon, August 4, 2008 2:19 pm, Scott Ragen wrote:
[EMAIL PROTECTED] wrote on 29/07/2008 07:15:47 AM:
One could argue that either server is incorrectly configured. I suspect
the receiving email server is checking if the sending email is valid in an
attempt to stop spam. You could just alias
I have some web generated emails being sent as 'apache@' [as the default
web user] (which perhaps I should change, but it never really caused
problems in the past)
now, an isp appears to be doing a user lookup as below and bounces emails,
claiming my server is mis-configured:
is there any req on
[EMAIL PROTECTED] wrote on 29/07/2008 07:15:47 AM:
I have some web generated emails being sent as 'apache@' [as the default
web user] (which perhaps I should change, but it never really caused
problems in the past)
now, an isp appears to be doing a user lookup as below and bounces
emails,
On Mon, 2008-08-04 at 14:10 +1000, Mary Gardiner wrote:
On Tue, Jul 29, 2008, Voytek Eymont wrote:
is there any req on me having an 'apache@' address if I'm sending
emails as such ?
(i.e., who misconfigured their server ?)
Sender address verification is a fairly common anti-spam
