You have been perfectly clear. As outlined in DSN_README, the RFC
does not support a way to selectively disable SUCCESS notification.
Postfix is not just a bunch of random hacks thrown together. You
are free to use a different mail system.
Wietse
__
On 23.05.24 20:51, Alexander Kolesnikov via Postfix-users wrote:
23.05.2024 19:06, Wietse Venema via Postfix-users пишет:
Aleksandr Kolesnikov via Postfix-users:
if the user requests a DSN, he receives a delivery message via the
...
how to prohibit the sending of such DSN?
Perhaps: [1
23.05.2024 19:06, Wietse Venema via
Postfix-users пишет:
Aleksandr Kolesnikov via Postfix-users:
if the user requests a DSN, he receives a delivery message via the
...
how to prohibit the sending of such DSN
Aleksandr Kolesnikov via Postfix-users:
> if the user requests a DSN, he receives a delivery message via the
...
> how to prohibit the sending of such DSN?
Perhaps: https://www.postfix.org/DSN_README.html
Wietse
___
Postfix-users m
Hi All,
the resubmit service is configured in master.cf:
resubmit unix - n n - 10 pipe
flags=Rq user=nobody null_sender=
argv=/usr/local/libexec/resubmit_mail.sh -N success --
${recipient}
if the user requests a DSN
ation
after virtual alias expansion of a recipient that has a notify=success
property.
You are using MailScanner which has at least one problem with
propagating DSN notify requests. For example:
Postfix -milter-protocol-> MailScaner -qmqp-protocol-> Postfix
If you can't run Postf
> De: Viktor Dukhovni via Postfix-users
> Enviada: 31 de março de 2023 15:10
>
> On Fri, Mar 31, 2023 at 02:00:49PM +0100, Nuno Pereira via Postfix-users
wrote:
>
> > Logs of message with success DSN sent:
>
> Are you sure you syslog system is not dropping some of th
> De: Wietse Venema via Postfix-users
> Enviada: 31 de março de 2023 15:35
> Para: Postfix users
> Assunto: [pfx] Re: Success DSN for virtual mailboxes not working
>
> Nuno Pereira via Postfix-users:
> > Logs of message with success DSN sent:
> >
> > Ma
> -Mensagem original-
> De: Matus UHLAR - fantomas via Postfix-users
> Enviada: 31 de março de 2023 12:29
> Para: postfix-users@postfix.org
> Assunto: [pfx] Re: Success DSN for virtual mailboxes not working
>
> >> Nuno Pereira via Postfix-users skrev den 2023-
There is a difference in MailScanner logging when a SUCCESS DSN is
created and when it is not created.
Wietse Venema via Postfix-users:
> Nuno Pereira via Postfix-users:
> > Logs of message with success DSN sent:
> >
> > Mar 31 13:26:16 MAIL01 postfix/cleanup[110]: 2106
Nuno Pereira via Postfix-users:
> Logs of message with success DSN sent:
>
> Mar 31 13:26:16 MAIL01 postfix/cleanup[110]: 21069213F:
> message-id= uYAAA4AABB+0ZLW85dyTYzsfdF+fjJNAQA=@otherdomain.com>
> Mar 31 13:26:19 MAIL01 MailScanner[1402982]: Requeue:
On Fri, Mar 31, 2023 at 02:00:49PM +0100, Nuno Pereira via Postfix-users wrote:
> Logs of message with success DSN sent:
Are you sure you syslog system is not dropping some of the log messages?
(A common problem with systemd-based logging).
> Mar 31 13:26:19 MAIL01 postfix/lmtp[1
> -Mensagem original-
> De: Wietse Venema via Postfix-users
> Enviada: 31 de março de 2023 12:54
> Para: Postfix users
> Assunto: [pfx] Re: Success DSN for virtual mailboxes not working
>
> Nuno Pereira via Postfix-users:
> > > De: Wietse Venema via Postf
Nuno Pereira via Postfix-users:
> > De: Wietse Venema via Postfix-users
> > Enviada: 30 de mar?o de 2023 21:25
> > Para: Postfix users
> > Assunto: [pfx] Re: Success DSN for virtual mailboxes not working
> >
> > Nuno Pereira via Postfix-users:
> >
Nuno Pereira via Postfix-users skrev den 2023-03-30 20:29:
> We have tried to figure out why this happens, but haven't found a
> solution until now.
logs ?
On 31.03.23 12:10, Nuno Pereira via Postfix-users wrote:
I don't find anything relevant in logs: just an indication tha
> De: Wietse Venema via Postfix-users
> Enviada: 30 de março de 2023 21:25
> Para: Postfix users
> Assunto: [pfx] Re: Success DSN for virtual mailboxes not working
>
> Nuno Pereira via Postfix-users:
> > Hello.
> >
> > We have a setup where postifix is
> De: Benny Pedersen via Postfix-users
> Enviada: 30 de março de 2023 21:20
> Para: postfix-users@postfix.org
> Assunto: [pfx] Re: Success DSN for virtual mailboxes not working
>
> Nuno Pereira via Postfix-users skrev den 2023-03-30 20:29:
>
> > We have tried to figur
ains = virtualdomain.com
>
> virtual_alias_maps = mysql:/etc/postfix/mysql-virtual-email2email.cf
>
> virtual_mailbox_domains = realdomain.com
...
> The problem is with DSN for success messages: they're not returned for emails
> sent to @virtualdomain.com, but are for ones sent to @realdomain.co
Nuno Pereira via Postfix-users skrev den 2023-03-30 20:29:
We have tried to figure out why this happens, but haven't found a
solution until now.
logs ?
It should be mentioned that failure notifications are sent from
@virtualdomain.com when it's the case.
i don't know yet
note hopefully yo
nt and received correctly.
The problem is with DSN for success messages: they're not returned for emails
sent to @virtualdomain.com, but are for ones sent to @realdomain.com (which
aren't a virtual on it's own).
We have tried to figure out why this happens, but haven't found
Peter:
> On 31/12/22 17:29, Sean Hennessey wrote:
> > I'm doing some testing and am trying to figure out a way to set up
> > postfix so that it won't ever send a DSN.
>
> DSNs are an important part of email but if your server sends out too
> many of them, or
On 31/12/22 17:29, Sean Hennessey wrote:
I'm doing some testing and am trying to figure out a way to set up
postfix so that it won't ever send a DSN.
DSNs are an important part of email but if your server sends out too
many of them, or in two many scenarios it becomes a potential
On 31/12/22 19:43, Matthias Andree wrote:
Am 31.12.22 um 05:29 schrieb Sean Hennessey:
I'm doing some testing and am trying to figure out a way to set up
postfix so that it won't ever send a DSN.
What is the use case for that other than bulk sending of unsolicited
e-mail
Am 31.12.22 um 05:29 schrieb Sean Hennessey:
I'm doing some testing and am trying to figure out a way to set up
postfix so that it won't ever send a DSN.
What is the use case for that other than bulk sending of unsolicited
e-mail?
Normally operators will want to know what addresses
On 31 December 2022 05:29:58 CET, Sean Hennessey
wrote:
>I'm doing some testing and am trying to figure out a way to set up postfix so
>that it won't ever send a DSN.
>
>In googling around I found one option is to change the bounce service in
>master.cf to use the di
I'm doing some testing and am trying to figure out a way to set up postfix so
that it won't ever send a DSN.
In googling around I found one option is to change the bounce service in
master.cf to use the discard service. That seems to stop the DSN for a bounce
to be sent out, but
Hi
I need disallow for just one client IP
I have two servers:
1)for outgoing (smtp)
2)for incomming (MX)
W dniu 04.11.2021 o 20:28, Viktor Dukhovni pisze:
> On Thu, Nov 04, 2021 at 09:35:22AM +0100, natan wrote:
>
>> Is available restrict any DSN sending to one
On Thu, Nov 04, 2021 at 09:35:22AM +0100, natan wrote:
> Is available restrict any DSN sending to one IP for my MX ?
>
>smtp_discard_ehlo_keyword_address_maps = cidr:/etc/postfix/no_access
>
> no_access:
> 217.xxx.xxx.xxx/32 silent-discard, dsn
Is this a question or a
Hi
Is available restrict any DSN sending to one IP for my MX ?
In my MX like:
smtp_discard_ehlo_keyword_address_maps =
cidr:/etc/postfix/no_access
no_access:
217.xxx.xxx.xxx/32 silent-discard, dsn
--
Awesome. Thank you. That did the trick.
Am Di., 15. Jan. 2019 um 13:22 Uhr schrieb Wietse Venema <
wie...@porcupine.org>:
> Stefan Bauer:
> > Hi,
> >
> > i would like that postfix always sends DSN, when requested by client and
> > mail got forwarded to next-hop
Stefan Bauer:
> Hi,
>
> i would like that postfix always sends DSN, when requested by client and
> mail got forwarded to next-hop / final destination.
Postfix implements a published RFC, and according to that RFC,
Postfix will send a 'relayed' DSN if:
1 - The sender requ
Hi,
i would like that postfix always sends DSN, when requested by client and
mail got forwarded to next-hop / final destination.
Thats works on some recipients, but not on all. postfix always sends DSN on
specific destinations (e.g. web.de)
: delivery via mx-ha02.web.de[212.227.17.8]:25: 250
On 17.08.17 11:18, Steven Conrad Bayer wrote:
we are using Debian 8 with Postfix 2.11.3 installed from Debian Repo
and want to disable DSN reports only for success notifications
because we are receiving many backscatter like this in the past days:
"MESSAGE DELIVERED SUCCESSFULLY
Your E
Hello,
we are using Debian 8 with Postfix 2.11.3 installed from Debian Repo and
want to disable DSN reports only for success notifications because we
are receiving many backscatter like this in the past days:
"MESSAGE DELIVERED SUCCESSFULLY
Your E-mail requested a delivery notice/r
Il 17/10/2016 16:40, Wietse Venema ha scritto:
Davide Gmail:
Hi to all, my problem is this:
i have on esmtp headers advertisement DSN enabled; when some domain
request DSN to my system correct response through bounce.cf template is
sent to sender but in r4esponse i receive this
Davide Gmail:
> Hi to all, my problem is this:
>
> i have on esmtp headers advertisement DSN enabled; when some domain
> request DSN to my system correct response through bounce.cf template is
> sent to sender but in r4esponse i receive this:
>
> :
> 213.199.154.106
Hi to all, my problem is this:
i have on esmtp headers advertisement DSN enabled; when some domain
request DSN to my system correct response through bounce.cf template is
sent to sender but in r4esponse i receive this:
:
213.199.154.106 failed after I sent the message.
Remote host said: 550
On Wed, Jul 20, 2016 at 12:09:24PM +0200, Marek Salwerowicz wrote:
> I have disabled globally DSN in my main.cf:
> smtpd_discard_ehlo_keyword_address_maps = cidr:/etc/postfix/dsn_access
>
> /etc/postfix/dsn_access:
>
> # block folllowing
> 0.0.0.0/0 silen
Marek Salwerowicz:
> Hi list,
>
> I have disabled globally DSN in my main.cf:
> smtpd_discard_ehlo_keyword_address_maps = cidr:/etc/postfix/dsn_access
>
> /etc/postfix/dsn_access:
>
> # block folllowing
> 0.0.0.0/0 silent-discard, dsn
> ::/0
Hi list,
I have disabled globally DSN in my main.cf:
smtpd_discard_ehlo_keyword_address_maps = cidr:/etc/postfix/dsn_access
/etc/postfix/dsn_access:
# block folllowing
0.0.0.0/0 silent-discard, dsn
::/0silent-discard, dsn
Would it be possible to allow "out
In Postfix's log I can see something lines like this:
Sep 24 01:54:21 smtp01 postfix/smtp[22577]: 4A38422A536: to=<
some.em...@gmail.com>, relay=gmail-smtp-in.l.google.com[74.125.143.26]:25,
delay=35, delays=33/0/0.85/0.73, dsn=2.0.0, status=sent (250 2.0.0 OK
1443074061 xf5si40
- Original Message -
> From: "Wietse Venema"
> To: "Postfix users"
> Sent: Monday, July 20, 2015 4:57:43 PM
> Subject: Re: Send a DSN report only to one specified email address
> Postfix implements DSN as specified in RFC 3464. The Postfix
>
Ray:
> > DSNs are sent to the envelope sender, VERP changes the envelope
> > sender, therefore VERP has effect for all DSNs.
>
> > Wietse
>
> OK, I will checkout VERP, sounds exactly like what I would need
> indeed. My remaining question would be on how to acti
> DSNs are sent to the envelope sender, VERP changes the envelope
> sender, therefore VERP has effect for all DSNs.
> Wietse
OK, I will checkout VERP, sounds exactly like what I would need indeed. My
remaining question would be on how to activate the Success DSN reports?
Best
Ray
--
ready covered native
> with postfix (notify_class and some recipient parameter). 2Bounce is really
> secondary for me, what I would like is the possibility to also receive the
> Success DSN in some parameter defined email.
>
> VERP would handle the bounces, but not the success delive
ass and some recipient parameter). 2Bounce is really
secondary for me, what I would like is the possibility to also receive the
Success DSN in some parameter defined email.
VERP would handle the bounces, but not the success deliveries, right?
Thanks
Best
Ray
* Ray :
> Hello,
>
> we are a travel agency and have lot's of outbound email (confirmations,
> vouchers, etc.). What I want to integrate now is DSN report information in
> our backend management software. We want the agent in the callcenter be able
> to see an emai
Hello,
we are a travel agency and have lot's of outbound email (confirmations,
vouchers, etc.). What I want to integrate now is DSN report information in our
backend management software. We want the agent in the callcenter be able to see
an email has been sent and the Delivery inform
On Thu, Jul 02, 2015 at 07:36:38PM +0300, Michael Peter wrote:
> for postfix log file /var/log/maillog, we notice that following line
>
> 1198B1E111: to=,
> relay=mail.example.com[XXX.XXX.XXX.XXX]:25, delay=20,
> delays=4.3/0.01/1.8/14, dsn=2.6.0, status=sent (250 2.6.0
meddelande-
From: Michael Peter
Sent: Thursday, July 02, 2015 6:36 PM
To: postfix-users@postfix.org
Subject: Question about DSN
Hi,
for postfix log file /var/log/maillog, we notice that following line
1198B1E111: to=,
relay=mail.example.com[XXX.XXX.XXX.XXX]:25, delay=20,
delays=4.3/0.01/1.8/14,
Hi,
for postfix log file /var/log/maillog, we notice that following line
1198B1E111: to=,
relay=mail.example.com[XXX.XXX.XXX.XXX]:25, delay=20,
delays=4.3/0.01/1.8/14, dsn=2.6.0, status=sent (250 2.6.0 Queued mail for
delivery)
The DSN is 2.6.0 INSTEAD of 2.0.0,
is DSN is 2.6.0 is considered
smtpd[17904]: >
unknown[192.0.2.25]: 250-STARTTLS
Nov 12 17:45:33 mail.example.org postfix/smtpd[17904]: >
unknown[192.0.2.25]: 250-ENHANCEDSTATUSCODES
Nov 12 17:45:33 mail.example.org postfix/smtpd[17904]: >
unknown[192.0.2.25]: 250-8BITMIME
Nov 12 17:45:33 mail.example.org postfix/sm
A. Schulze:
>
> wietse:
> > /^(RCPT\s+TO:<.*>.*\s+NOTIFY=.*)/ $1
> > /^(RCPT\s+TO:<.*>.*)/ $1 NOTIFY=SUCCESS,DELAY,FAILURE
>
> the regex above don't match on 'RCPT TO: ' ( SPACE
> after colon )
That is invalid syntax. What software (other than home-grown
scripts) sends commands like that?
Viktor Dukhovni:
> On Wed, Nov 12, 2014 at 05:56:38PM +0100, A. Schulze wrote:
> >
> > wietse:
> > >/^(RCPT\s+TO:<.*>.*\s+NOTIFY=.*)/ $1
> > >/^(RCPT\s+TO:<.*>.*)/ $1 NOTIFY=SUCCESS,DELAY,FAILURE
> >
> > the regex above don't match on 'RCPT TO: ' ( SPACE after
> > colon )
>
> Note the extra spac
On Wed, Nov 12, 2014 at 05:56:38PM +0100, A. Schulze wrote:
>
> wietse:
> >/^(RCPT\s+TO:<.*>.*\s+NOTIFY=.*)/ $1
> >/^(RCPT\s+TO:<.*>.*)/ $1 NOTIFY=SUCCESS,DELAY,FAILURE
>
> the regex above don't match on 'RCPT TO: ' ( SPACE after
> colon )
Note the extra space violates RFCs 5321, 2821, 821. How
wietse:
/^(RCPT\s+TO:<.*>.*\s+NOTIFY=.*)/ $1
/^(RCPT\s+TO:<.*>.*)/ $1 NOTIFY=SUCCESS,DELAY,FAILURE
the regex above don't match on 'RCPT TO: ' ( SPACE
after colon )
I use now:
/^(RCPT\s+TO:\s*<.*>.*\s+NOTIFY=.*)/ $1
/^(RCPT\s+TO:\s*<.*>.*)/ $1 NOTIFY=SUCCESS,DELAY,FAILURE
Andreas
in bounce.cf for this "new feature"
Try again.
Which notification should Postfix send when delayed mail is "relayed",
and the user specified DSN=DELAY, DSN=SUCCESS, or both? Why should
these notifications be different?
Which notification should Postfix send when delayed mail is
ned here:
> http://marc.info/?l=postfix-users&m=141044783906935
> and the result was exactly as specified.
> Thank you!
>
> Would be still nice if you could spend a new text
> template in bounce.cf for this "new feature"
Which notification should Postfix send when de
wietse:
This is a minimal patch relative to the confirm_delay_cleared patch.
This suppresses the notification when the user requests NOTIFY=FAILURE,
or any NOTIFY features that do not include DELAY.
I checked the cases mentioned here:
http://marc.info/?l=postfix-users&m=141044783906935
and
Wietse Venema:
> > 3) sender did not request "DELAY" notification
> > -> relay should not send a "relayed" (after delay)
>
> I looked at the code, and while the existing "delayed" notifications
> can be suppressed with NOTIFY=FAILURE (i.e. without "DELAY"), it
> looks like the new "relayed" (a
A. Schulze:
>
> wietse:
>
> > First, I think this is somewhat academic because many users will
> > be confused when they receive more than one notification for the
> > same email message, regardless of the content of that notification.
> right. Users tend to not read such messages :-/
>
> > Pres
wietse:
First, I think this is somewhat academic because many users will
be confused when they receive more than one notification for the
same email message, regardless of the content of that notification.
right. Users tend to not read such messages :-/
Presently, we have a new feature to se
s "SUCCESS" notification but the remote SMTP server
does not announce DSN support. Otherwise, Postfix delegates the
responsibility for "SUCCESS" notification to the remote SMTP server.
Presently, we have a new feature to send a "relayed" (after delay)
notification when delayed
al/feature-patches/20140907-confirm_delay_cleared-patch
Hello,
thanks for the patch. I like to use it with postfix-2.11.1. At a first
view it works as expected.
But imagine th following scenario: client <-> relay <-> destination
- client send a message requesting DSN on success a
Wietse Venema:
> Florian Pritz:
> > Hi,
> >
> > I've currently set delay_warning_time = 4h and maximal_queue_lifetime =
> > 5d, which are nice values and all, but if I get a delay DSN I'd like to
> > know sooner than after 5 days if the mail went throu
Florian Pritz:
> Hi,
>
> I've currently set delay_warning_time = 4h and maximal_queue_lifetime =
> 5d, which are nice values and all, but if I get a delay DSN I'd like to
> know sooner than after 5 days if the mail went through.
>
> I can't seem to find an opt
On 18 Aug 2014, at 07:12 , Florian Pritz wrote:
> Thanks for the explanation, but I already know you can request a success
> DSN when sending email. My questions is different in that I only want a
> success DSN if the mail has previously generated a delay DSN and I don't
> want
Florian Pritz:
> On 18.08.2014 13:12, Wietse Venema wrote:
> > Florian Pritz:
> >> I've currently set delay_warning_time = 4h and maximal_queue_lifetime =
> >> 5d, which are nice values and all, but if I get a delay DSN I'd like to
> >> know soo
On 18.08.2014 13:12, Wietse Venema wrote:
> Florian Pritz:
>> I've currently set delay_warning_time = 4h and maximal_queue_lifetime =
>> 5d, which are nice values and all, but if I get a delay DSN I'd like to
>> know sooner than after 5 days if the mail went thr
Florian Pritz:
> I've currently set delay_warning_time = 4h and maximal_queue_lifetime =
> 5d, which are nice values and all, but if I get a delay DSN I'd like to
> know sooner than after 5 days if the mail went through.
By default, Postfix requests a DSN for delayed and faile
Hi,
I've currently set delay_warning_time = 4h and maximal_queue_lifetime =
5d, which are nice values and all, but if I get a delay DSN I'd like to
know sooner than after 5 days if the mail went through.
I can't seem to find an option that sends me a positive DSN for delayed
mai
hyndavirap...@bel.co.in:
> Thanks for the reply. I have only configured the whole setup. I am
> getting DSN from relay server to sender but not from the destination.
Wietse:
> If the relay sends a DSN for success, the remote system won't send one.
>
> If the relay sends a
Thanks Wietse for the help.
By default Postfix server does not send DSN to sender. How can I make it
by default? Is therre any configuration parameter to set this?
---
Hyndavi
> hyndavirap...@bel.co.in:
>> Thanks for the reply. I have only configured the whole setup. I am
>> g
hyndavirap...@bel.co.in:
> Thanks for the reply. I have only configured the whole setup. I am
> getting DSN from relay server to sender but not from the destination.
If the relay sends a DSN for success, the remote system won't send one.
If the relay sends a DSN for failure, the re
Hi,
Thanks for the reply. I have only configured the whole setup. I am
getting DSN from relay server to sender but not from the destination.
I have a basic question.. how to enable DSN by default in postfix?
Thanks and regards
Hyndvai
> hyndavirap...@bel.co.in:
>> getting del
hyndavirap...@bel.co.in:
> getting delivered to sender inbox. when Relay server forwards the mail to
> actual destination, Sender is not getting any notification.
Ask the remote system administrator why they aren't sending DSN.
Wietse
Hi,
I am not getting DSN from receiver to sender. My set up is as follows.
I have two domains, say a.abc.com and b.abc.com and one relay server.
When mail goes from one domain to other domain, mail goes through the
relay server.
I have tried to send mail form a.abc.com to b.abc.com through
Hi,
I would like to redirect all DSN messages to the same bounce complex.
In the case where the recipient's endpoint is SMTP (author's endpoint is
LMTP)
and the recipient address does not accept the mail from this author (or
recip address doesn't exist),
the bounce message i
Charles Orth:
> Hi,
>
> Has there been any thoughts on support for passing recipient DSN
> information to milter protocol (eg rcpt_dsn macro)?
According to the change log you can specify both NOTIFY and
ORCPT parameters.
Wietse
20131123
Feature: support for NOTI
Hi,
Has there been any thoughts on support for passing recipient DSN
information to milter protocol (eg rcpt_dsn macro)?
Charles
On Mon, May 12, 2014 at 04:43:22PM +0200, Erik Logtenberg wrote:
> Okay, so the thing with DSN's is this: if my email client requests a DSN
> on success when sending a mail, my Postfix server will honour that
> request. Postfix does this in one of two possible ways:
The recommended
Hi,
Indeed I was a bit unclear.
Okay, so the thing with DSN's is this: if my email client requests a DSN
on success when sending a mail, my Postfix server will honour that
request. Postfix does this in one of two possible ways:
1. either the remote mail server indicates that it offer
Am 2014-04-23 13:39, schrieb Erik Logtenberg:
Hi,
If I request a (success) DSN from my Postfix server, my server
responds
as expected. Usually my mail server has to deliver the mail remotely
and
I would like Postfix to request a DSN from the remote server as well
if
the user asked for one
Erik Logtenberg:
> If I request a (success) DSN from my Postfix server, my server responds
> as expected. Usually my mail server has to deliver the mail remotely and
> I would like Postfix to request a DSN from the remote server as well if
> the user asked for one. Is that possible?
Hi,
If I request a (success) DSN from my Postfix server, my server responds
as expected. Usually my mail server has to deliver the mail remotely and
I would like Postfix to request a DSN from the remote server as well if
the user asked for one. Is that possible?
Kind regards,
Erik.
Wietse Venema:
> There is a problem with your patch: it turns off forced DSN for all
> SMTP clients that are serviced by the same SMTP daemon process.
Oh, yes, now I see it too. var_force_dsn_on_success is global per process?
My usecases never trigger that situation.
One point more to us
Wietse Venema:
> Andreas Schulze:
> >
> > Hello,
> >
> > DSN for successfully deliveries are not enabled by default. They have
> > to be requested
> > by an smtp client using extra parameter on RFC5321.MAILFROM an
> > RFC5321.RCPTTO
> >
>
Andreas Schulze:
>
> Hello,
>
> DSN for successfully deliveries are not enabled by default. They have
> to be requested
> by an smtp client using extra parameter on RFC5321.MAILFROM an RFC5321.RCPTTO
>
> But not every MUA has the ability to do this. Some years ago I
Hello,
DSN for successfully deliveries are not enabled by default. They have
to be requested
by an smtp client using extra parameter on RFC5321.MAILFROM an RFC5321.RCPTTO
But not every MUA has the ability to do this. Some years ago I had a
requirement to
force DSN on successfully
Kev:
> Hi!
>
> I have an issue, we have DSN enabled by default on postfix, and it works
> great, but we have an issue when sending multiple emails, its difficult to
> see what email got deliver, so is there anyway to include the subject of
> the original email in the DSN not
Hi!
I have an issue, we have DSN enabled by default on postfix, and it works
great, but we have an issue when sending multiple emails, its difficult to
see what email got deliver, so is there anyway to include the subject of
the original email in the DSN notifications ?
rgds
Kev
bitozoid:
> Wietse Venema:
>
> > bitozoid:
> > > Postfix generates DSNs with the following header:
> > >
> > > Content-Type: multipart/report; report-type=delivery-status;
> > > boundary="XX"
> > >
> > > Is there a way for DSNs to be text/plain formatted? Something like:
> > >
Wietse Venema:
> bitozoid:
> > Postfix generates DSNs with the following header:
> >
> > Content-Type: multipart/report; report-type=delivery-status;
> > boundary="XX"
> >
> > Is there a way for DSNs to be text/plain formatted? Something like:
> >
> > Content-Type: text/plain
>
bitozoid:
> Postfix generates DSNs with the following header:
>
> Content-Type: multipart/report; report-type=delivery-status;
> boundary="XX"
>
> Is there a way for DSNs to be text/plain formatted? Something like:
>
> Content-Type: text/plain
Postfix uses the standardized b
Postfix generates DSNs with the following header:
Content-Type: multipart/report; report-type=delivery-status;
boundary="XX"
Is there a way for DSNs to be text/plain formatted? Something like:
Content-Type: text/plain
I need my smarthost to forward these mails but it does no
has no delivery agent), the relay
class with relay_transport, and the local address class with
local_transport.
Indeed I was only responding to the question of how to get error(8)
to generate a sensible DSN status code and error message. Whether
it is wise to route the mail in question to the erro
he "user unknown" error message.
>
> Similar usage is recommended for the other Postfix address classes:
> the virtual alias class (which has no delivery agent), the relay
> class with relay_transport, and the local address class with
> local_transport.
Indeed I was only res
Quanah Gibson-Mount:
> I changed the value for virtual_transport to be:
>
> error: 5.1.1 Mailbox unavailable
>
> And now I see:
>
> Oct 2 11:54:21 zre-ldap002 postfix/error[331]: 897561E37C6:
> to=, relay=none, delay=0.06,
> delays=0.03/0/0/0.02, dsn=5.1.1, stat
t nexthop is optional. ;)
It sounds like at least in the case of "error" it is not.
I changed the value for virtual_transport to be:
error: 5.1.1 Mailbox unavailable
And now I see:
Oct 2 11:54:21 zre-ldap002 postfix/error[331]: 897561E37C6:
to=, relay=none, delay=0.06,
delays=0
On Tue, Oct 02, 2012 at 08:21:54AM -0400, Wietse Venema wrote:
> Quanah Gibson-Mount:
> >
> > virtual_transport = error
>
> [...]
>
> I could speculate that your "virtual_transport = error" causes the
> nexthop to become the recipient domain (zre-ldap002.eng.vmware.com)
> which then is reported
1 - 100 of 223 matches
Mail list logo
