1 (edited by vva 2011-11-28 04:29:48)

Topic: DSN not working ?

==== Provide basic information to help troubleshoot and get quick answer ====
- iRedMail version:
- Linux/BSD distribution name and version:
- Any related log? Log is helpful for troubleshooting.
====

Debian 6.0.2
iRedMail-0.7.3

Hello,

I'm new to iRedMail. I already implemented it on two mail servers and managed to fix all issues I had but I have a problem with Delivery Status Notification (DSN) not working - I want all senders who have that flag in their emails to receive a success DSN.

I read everything in google I found with no luck.

Please help me solve this issue.

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: DSN not working ?

What flag? What kind of email and DSN do you expect?

3

Re: DSN not working ?

==== Provide basic information to help troubleshoot and get quick answer ====
- iRedMail version:
- Linux/BSD distribution name and version:
- Any related log? Log is helpful for troubleshooting.
====

Debian 6.0.2
iRedMail 0.7.3

Thank you for the prompt reply.

As you know there is a delivery status notification flag in every message - the client decides if to raise the flag or not.
Installation of iRedMail makes some configuration changes in Postfix and it returns read request status but doesn't return DSN (delivery status notification) when such flag is raised.

That's what I mean - I need a way to make DSN be sent out to the sender on successful delivery.

4

Re: DSN not working ?

I'm afraid that iRedMail (Postfix) doesn't support this feature. You see this feature in Microsoft Exchange, right?

5

Re: DSN not working ?

DSN is working for me on iRedMail. Are you using Postfix 2.3 or older? (older versions don't support DSN).
It is turned ON by default, and it's working.

6

Re: DSN not working ?

Oops, seems i misunderstood.
Hi @maxie_ro, thanks for your reply. smile

7

Re: DSN not working ?

==== Provide basic information to help troubleshoot and get quick answer ====
- iRedMail version:
- Linux/BSD distribution name and version:
- Any related log? Log is helpful for troubleshooting.
====

Debian 6.0.2
iRedMail 0.7.3
Postfix 2.7.1

I'm using Postfix 2.7.1
I know it's ON by default because I already implemented postfix alone and had no problems with it.

I think the problem is somewhere in the colaboration between postfix, amavisd-new and spamassassin may be ?

Can you help me with this ?

8

Re: DSN not working ?

Did you try finding related log in Postfix/Amavisd/Dovecot log file?

9

Re: DSN not working ?

==== Provide basic information to help troubleshoot and get quick answer ====
- iRedMail version:
- Linux/BSD distribution name and version:
- Any related log? Log is helpful for troubleshooting.
====

I didn't find anything strange in the log files of Postfix, Amavisd and Dovecot.
I think there is some restriction in the configuration of Postfix or Amavisd but I can't find it.
I know for sure that if I install postfix from scratch and configure it myself the DSN is working perfectly.

10

Re: DSN not working ?

vva wrote:

I know for sure that if I install postfix from scratch and configure it myself the DSN is working perfectly.

It's a good idea to compare their configrations to figure out why DSN on iRedMail server doesn't work.

11

Re: DSN not working ?

ZhangHuangbin wrote:
vva wrote:

I know for sure that if I install postfix from scratch and configure it myself the DSN is working perfectly.

It's a good idea to compare their configrations to figure out why DSN on iRedMail server doesn't work.

==== Provide basic information to help troubleshoot and get quick answer ====
- iRedMail version:
- Linux/BSD distribution name and version:
- Any related log? Log is helpful for troubleshooting.
====

I did this and I couldn't find anything wrong - that's why I think that the problem is not in the postfix itself or it's configuration but something to do with the colaboratioon with amavisd and dovecot may be ?!

12

Re: DSN not working ?

DSN are processed by Postfix only and DSN responses are sent only by Postfix. Amavisd and dovecot don't have anything to do with this.

13

Re: DSN not working ?

maxie_ro wrote:

DSN are processed by Postfix only and DSN responses are sent only by Postfix. Amavisd and dovecot don't have anything to do with this.

==== Provide basic information to help troubleshoot and get quick answer ====
- iRedMail version:
- Linux/BSD distribution name and version:
- Any related log? Log is helpful for troubleshooting.
====

Thank you maxie_ro.

This was usefull. There is nothing in the postfix logs about a generated DSN message.
I think there is some configuration parameter which prevents DSN from being generated and sent back.
When I configure postfix by myself everything is working but in iRedMail default postfix configuration there are many more configuration parameters which I've read about and there's nothing about DSN but may be the collaboration between them stops DSN ?

14

Re: DSN not working ?

I don't know about such a parameter. This is what I get in my maillog for example:

Dec 20 07:52:08 mx1 postfix/bounce[9283]: 12D772C88668: sender delivery status notification: 1E6FE2C88658
Dec 20 07:52:27 mx1 postfix/bounce[9283]: 1A37B2C88658: sender delivery status notification: EC03A2C88668
Dec 20 08:22:21 mx1 postfix/bounce[23067]: 540832C88668: sender delivery status notification: C22212C888AA
Dec 20 08:34:28 mx1 postfix/bounce[29077]: BF19C2C88668: sender delivery status notification: 75C012C888AA
Dec 20 08:52:41 mx1 postfix/bounce[6023]: 33C5C2C88658: sender delivery status notification: D92C22C88668
Dec 20 09:16:14 mx1 postfix/bounce[19382]: 8909B2C8863D: sender delivery status notification: 15B6628680A7
Dec 20 09:16:33 mx1 postfix/bounce[19382]: 53F8C2C88658: sender delivery status notification: EC14C28680A7
Dec 20 09:28:06 mx1 postfix/bounce[26464]: 60EED2C888F8: sender delivery status notification: CC0762C888EF
Dec 20 09:28:10 mx1 postfix/bounce[26464]: 5DFA82C888E7: sender delivery status notification: 16E842C888EF
Dec 20 09:32:58 mx1 postfix/bounce[29690]: E94F72C8891B: sender delivery status notification: D21442C88903
Dec 20 09:34:18 mx1 postfix/bounce[29690]: 153862C888EF: sender delivery status notification: 4AC4328680A7
Dec 20 09:34:21 mx1 postfix/bounce[29690]: 28D212C88903: sender delivery status notification: 9363F28680A7
Dec 20 09:38:57 mx1 postfix/bounce[1436]: 574352E6800A: sender delivery status notification: 887712E68002
Dec 20 09:47:49 mx1 postfix/bounce[7182]: DF6032C888E8: sender delivery status notification: 30EE32C88903
Dec 20 10:02:12 mx1 postfix/bounce[16712]: 891242C885A3: sender delivery status notification: D47A32C8862C
Dec 20 10:17:05 mx1 postfix/bounce[26596]: AC32426E801D: sender delivery status notification: 5DB692C88903
Dec 20 10:32:57 mx1 postfix/bounce[4896]: 795A12C8892E: sender delivery status notification: 0A8662C88948
Dec 20 10:34:52 mx1 postfix/bounce[6178]: CB4F52C88948: sender delivery status notification: B8B092C8894C