mailsewer etiquette

2003-03-05 Thread David Cantrell
I run a secondary MX for an ex-colleague's domain, in exchange for him doing the same for me. I have noticed recently that particular messages get stuck in my queue for him, despite his server being up. Judging from the sender addresses, they're spam. Question is - is it polite for him to

Re: mailsewer etiquette

2003-03-05 Thread Jason Clifford
On Wed, 5 Mar 2003, David Cantrell wrote: I run a secondary MX for an ex-colleague's domain, in exchange for him doing the same for me. I have noticed recently that particular messages get stuck in my queue for him, despite his server being up. Judging from the sender addresses, they're

Re: mailsewer etiquette

2003-03-05 Thread David Cantrell
On Wed, Mar 05, 2003 at 09:27:34AM +, Jason Clifford wrote: On Wed, 5 Mar 2003, David Cantrell wrote: especially as he sends a 450, which is SO wrong, as I damned well know that the destination address exists. It's not the recipient address his server is bitching about but rather the

Re: mailsewer etiquette

2003-03-05 Thread Jason Clifford
On Wed, 5 Mar 2003, David Cantrell wrote: especially as he sends a 450, which is SO wrong, as I damned well know that the destination address exists. It's not the recipient address his server is bitching about but rather the sender address. According to RFC 821, a 450 status means