Since V 9.407-3 emails with same to-recipient and cc-recipient will stuck in mail manager in SMTP Corrupt.

Hi Markus,

I don't understand why would someone do that? cc and to for the same email address!

It will be an interesting learning curve if this holds any significance.

Thanks

Yes, adding an email adress in to an cc is bullshit in my opinion, too.

But we have a fleetmanager software that sends emails to the person who booked a car and to the person who drives this car. In allmost all circumstances this is the same person.

Additional explanation:

When an email from extern is send to an recipient (to an cc field) the mail will be forwarded correctly (one time).

But if from our internal network a software (f.e. thunderbird) uses our utm as smtp server and the recipient is in to and cc the mail will  stuck in mail manager smtp corrupt.

The following is being displayed in smtp corrupt:

Message Delivery Log:
Recipient information is missing/incorrect. 2 recipients were expected but found 1

Hi,

you are right. This doesn't make any sense.

But we often receive mails from People who add here own adress at cc:.

So in case of a reply, our mailsystem will answer to all and adding of course the Sender adress also. So we will have the same mailadress in to: and cc:

Worst case is simply to hold this mail in "smtp currupt" without the possibilty to Forward this mail and without a reply to the Sender that we are in trouble with this mail.

Nobody will get any notification that there is an unsend mail!

Regards

Wilfried

Markus S. said:

 

The following is being displayed in smtp corrupt:

Message Delivery Log:
Recipient information is missing/incorrect. 2 recipients were expected but found 1

 

We are seeing EXACTLY this at work on all UTM installations, customers ARE ANGRY - We have done 4 support cases today, and REALLY hope for a snap fix.

Could reproduce this with SMTP test tool, making "to" address andCC adress the same, I get "SMTp Corrupt logged"

looks like 9.407 tried to use RFC5322 smtp compliance.

Hi All,

The issue is reported as NUTM-5599. We are working on a fix to resolve it. No ETA from the developers.

Thanks

Same problem also for us... we'll wait the fix. Thanks

We have the same problem also. Will watch for the fix for this to be released, and hopefully it's soon.

Well have been with Support on this one and have tested things out, so far I have this status on the case (From my point of view):

1) Restore to 9.406

2) !!! NOT Supported by Sophos!!!

CRON this job every minute if you are on 9.407 and cannot revert or wait:

cd /var/storage/chroot-smtp/spool/corrupt/1

mv * /var/storage/chroot-smtp/spool/output/1/input/

This will take all the "corrupted" mail and put them into the input folder on the SMTP agtent and they will be sent out as usual.

!!! Ps. the "SMTP Corrupt" pane in Mail Manager will still show the corrupted mails, as this will not update the mail manager database.  - so be aware of that!!! 

HowTo Cron: https://community.sophos.com/kb/en-us/12176

3) Wait for 9.408, which should be released sometime next month??