Blocking Invalid Addresses

Hello,

We are running the following version:

iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003)

libimta.so 5.2 HotFix 1.16 (built 12:32:17, May 14 2003)

SunOS angel 5.8 Generic_117350-21 sun4u sparc SUNW,Sun-Fire-V440

We are starting to see e-mails coming into the message store with a From: address that contains no domain. Example: yetdhfoep@

Is there something in the mappings file that we could put it to block this type of e-mail.

Thanks in advance

[512 byte] By [869863panthers99a] at [2007-11-26 12:19:06]
# 1

Hi,

can you post full headers of e-mail in question? Logs?

Also, may not be bad to look at this http://docs.sun.com/app/docs/doc/819-2650/6n4u4dtsb?a=view#bgava

It is posible to configure e-mail server to reject e-mail's with invalid domain in from field (we do this on firewall. Please note that you must allow blank sender <>)

445320gljivaa at 2007-7-7 14:59:43 > top of Java-index,Archived Forums,Socket Programming...
# 2

Hi,

Please note that if the email has a From: address in the body of the email (as opposed to the envelope from address), then you will need to use something like a system sieve filter to block any such emails.

A full copy of the email (all headers) would be useful as noted already.

Regards,

Shane.

450819shane_hjortha at 2007-7-7 14:59:43 > top of Java-index,Archived Forums,Socket Programming...
# 3

Noticing that 5.2hf1.16 is extremely OLD. . .

If I were running this server, I'd download and install 5.2p2 IMMEDIATELY, and if I had a support contract, I'd get the current bits.

I'd also be looking at upgrading to 6.2. . .

If the server is not a large one, and can handle some DNS performance hit, you might want to try the "mailfromdns" keyword. That checks that the "from" part is a valid domain, before accepting a message.

584685jay_plesseta at 2007-7-7 14:59:43 > top of Java-index,Archived Forums,Socket Programming...
# 4
Whoops. meanmailfromdnsverifysorry
584685jay_plesseta at 2007-7-7 14:59:43 > top of Java-index,Archived Forums,Socket Programming...
# 5

We found a workaround. What we did was in the ORIG_SEND_ACCESS mapping table, we added an entry of:

tcp_local|*@|*|*$N (Space is in front of tcp_local)

We have tested and this appears to be working.

Thanks for the help.

On another note, we are in the process of installing/migrating to 2005Q4. That is why we are not running the latest patch. We don't want to have to run testing in 2 environments.

Message was edited by:

panthers99

869863panthers99a at 2007-7-7 14:59:43 > top of Java-index,Archived Forums,Socket Programming...