Our mailserver says:

Out: 220 [ourmailserver] ESMTP Postfix (Debian/GNU)
In: EHLO relay0.transip.nl
Out: 250-[ourmailserver]
Out: 250-PIPELINING
Out: 250-SIZE 52428800
Out: 250-VRFY
Out: 250-ETRN
Out: 250-STARTTLS
Out: 250-AUTH LOGIN CRAM-MD5 DIGEST-MD5 PLAIN
Out: 250-ENHANCEDSTATUSCODES
Out: 250-8BITMIME
Out: 250 DSN
In: MAIL FROM: SIZE=2814 BODY=8BITMIME
Out: 250 2.1.0 Ok
In: RCPT TO:
ORCPT=rfc822;
Out: 450 4.1.7 : Sender address rejected: undeliverable
address: host smtp2.osuosl.org[140.211.166.133] said: 554 5.7.1
: Recipient address rejected: Access denied (in reply
to RCPT TO command)
In: DATA
Out: 554 5.5.1 Error: no valid recipients
In: RSET
Out: 250 2.0.0 Ok
In: QUIT
Out: 221 2.0.0 Bye

Is this bad? Shouldn't apache@drupal.org be a real existing address??

Comments

AjK’s picture

Status: Active » Fixed

No, why should it? It doesn't appear here:- http://www.ietf.org/rfc/rfc2142.txt

klokop’s picture

Various Internet documents have specified mailbox names to be used
when reaching the operators of the new service; for example, [RFC822
6.3, C.6] requires the presence of a mailbox name
on all hosts that have an SMTP server. Other protocols have defacto
standards for well known mailbox names, such as for
NNTP (see [RFC977]), and for HTTP (see [HTTP]).
Defacto standards also exist for well known mailbox names which have
nothing to do with a particular protocol, e.g., and
.

So you're saying the drupal email shouldn't be sent from 'apache@drupal.org', but from 'webmaster@drupal.org', en this address should be in existance. Right?

klokop’s picture

Status: Fixed » Postponed (maintainer needs more info)

Bit quick to close this issue, innit?

AjK’s picture

It was ok to close because it had a valid answer to teh question.

You never said you were replying to an email sent from apache@drupal.org. Was that the case? If so the issue is warrented as a "sender address" probably needs fixing here somewhere. If not, the issue can be closed.

morbus iff’s picture

Note that some mailservers, as a spam prevention tool, attempt to connect to the sending server to verify that the address is correct (by issuing a RCPT TO command and checking the response). In cases like this, mail could be denied by the receiving mail server, long before the user has a chance to see it. This is called "callback verification":

http://en.wikipedia.org/wiki/Callback_verification

michelle’s picture

Charter has an issue with the spam protection, too. I had to switch to Gmail to be able to email the Drupal mailing lists.

Michelle

klokop’s picture

Oh, yeah, sorry, that was teh case. I was indeed replying to an email from apache@drupal.org.

nnewton’s picture

Assigned: Unassigned » nnewton
Status: Postponed (maintainer needs more info) » Active

Hi,

Thanks for pointing this out. I don't want these addresses to deliver, but we will change apache@drupal.org to noreply@drupal.org as this is more of a standard.

Thanks for the report.

silverwing’s picture

Status: Active » Fixed

Queue Cleanup - I'm assuming that this is considered fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.