james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Closed: (JAMES-127) Need an optional SMTP AUTH
Date Sat, 05 Jun 2004 20:11:53 GMT

   The following issue has been closed.

View the issue:

Here is an overview of the issue:
        Key: JAMES-127
    Summary: Need an optional SMTP AUTH
       Type: Bug

     Status: Closed
 Resolution: FIXED

    Project: James
             James Core

   Reporter: Gili

    Created: Fri, 3 Oct 2003 5:19 AM
    Updated: Sat, 5 Jun 2004 1:10 PM
Environment: Operating System: Windows XP
Platform: PC

The SMTP server should support "optional SMTP AUTH mode" which acts as follows:

- When client connects, server will prompt for AUTH.
- Even if client failed to properly authentication, SMTP server continues
transaction (but remembers the failure)
- During the rest of the transaction it should be possible to check if the
client is authenticated or not.


Say I get an incoming message which gets flaged as SPAM. I always want to inform
the sender of what happened just in case there has been a mistake and he needs
to know I did *not* receive his mail. The problem is that often spammers relay
messages from <my address> to <some remote address> which I bounce as SPAM and
as a result I get 100s of notifications daily that "my" mail bounced.

If optional SMTP auth were implemented I'd configure James to do the following:

- If mail is bounced as SPAM and the FROM address is local and the client is
authenticated, send a notification; otherwise
- Only send a notification if the FROM address is non-local

    Please let me know what you think.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message