Scalix imposes a time limit on messages?

[Nodsu]

One day I tried to restore a bunch of mail from the archive. Since the messages are in a SMTP session format, the most obvious thing to do is to pipe them directly to some SMTP server and have them drop to the user's inbox. It turned out that Scalix wouldn't accept messages with the Date ield too far in the past. Using a quick-and-dirty sed command I filtered out the Date: headers from the messages and they were delivered properly.

Now we are trying to migrate users from a POP3-only mailserver (old FTGate).
Again, the most convenient option would be to funnel all the messages to SMTP daemon and let them be delivered to Scalix. Again, all older messages are accepted by the Scalix server, but then they disappear (the messages are archived, but do not go to the user's inbox). Removing the Date: field from the message makes it all OK again.

Is there a way to disable this sort of date filtering?

[jcaudell]

Hmm, are you running Spamassassin or any other filtering programs on the smtp server? I get spam messages with odd dates all the time on unfiltered mail accounts.

[Nodsu]

No filtering at all. It happens when feeding messages to omsmtpd listening on the external interface.

When giving the message to Sendmail on localhost:25, it gets delivered (with the "now" date set).