Recent changes to patches

Patch for JES 1.6.1 - wildcard in domain name

2009-03-17T16:47:19Z

I've found the requirement to specify a full domain name in
the local domains list too limiting as the program I was testing can
generate mails for users in any of many subdomains of a domain. Therefore
I've modified the code slightly to accept also wildcards, like
*.mydomain.com which will accept both me@test.mydomain.com and
you@there.mydomain.com as local mails and deliver them to the default
user.

--- Modifications in mail.conf:
# You can specify either full domain name or use the wildcard *, which
# will match any nonempty string.

# ex: domains=mydomain1.com,mydomain2.com,*.mydomain2.com

domains=mydomain.com
--- Modifications in ConfigurationManager.java:
public boolean isLocalDomain( String domain )
...
if( localDomains[index].equals( domain ) )

{

return true;

}
// JH: Add wildcard support
{
final String localDomainPattern =
localDomains[index].replaceAll("\\.","\\\\.").replaceAll("\\*","\\.\\+");
return domain.matches( localDomainPattern );
}

Various issues addressed

2008-02-07T11:35:37Z

Hey there,
I like your server, really nice work. There were a few annoying quirks here and there so I took it up :)

I worked on the 1.6.1 version.

There are no new classes or methods.

I added a few synchronizations, no big deal.

And now the good stuff.

I have dropped the throw new RuntimeException() approach to disconnections in favor of simple null/boolean checks. There should be no slow downs.

Values (the ones that are meant to be changed while the server is running) can now be altered, while the server is active, in mail.conf and user.conf without issues. There are no file locks anymore.

Affected files:

ConfigurationManager.java
Pop3Processor.java
SMTPProcessor.java

Cheers,
Andreas

Patch for retrieval of partially spooled message

2005-10-10T06:10:30Z

A mail is in the process of being spooled into the user
directory by the SMTPSender. At the same time, a
POP3 client queries the server to retrieve mail. It sees
the mail message currently being spooled and attempts
to retrieve details of that message (for example, its
content or content type). As the message has only
partially been spooled, the POP3 client sometimes sees
spurious results.

This patch addresses the problem by spooling to a
temporary file and then renaming it to the correct file
name once the whole file has been spooled. The POP3
client code picks up only files with correct file names
and does not see temporary files. The POP3 client will
either see no message or the whole message.

This is a patch for version 1.4 of JES.

Patch for handling null reverse-path messages

2004-01-25T11:04:32Z

An "undeliverable mail" notification message from
another mail server will often use a null reverse-path.
This means that no from address is provided with the
message (namely MAIL FROM:<>). When the
SMTPMessage was saved, the from-address line is
blank, but when the SMTPMessage was loaded, a blank
from-address line would cause an exception when
creating the EmailAddress object. Thus the message
would never be delivered, and would forever remain in
the smtp directory causing more attempts to be
delivered.

This patch checks for blank from-address lines. If the
from-address line is blank, an empty EmailAddress object
is created without causing an exception, thereby
allowing the message to be delivered.