06:
> to=, relay=spamassassin, delay=0.17,
> delays=0.06/0/0/0.11, dsn=2.0.0, status=sent (delivered via spamassassin
> service)
> May 5 06:42:21 smtp2 postfix/bounce[31734]: C89BB80006: sender delivery
> status notification: E513380009
> May 5 06:42:21 smtp2 postfix/qmgr
Matus UHLAR - fantomas via Postfix-users:
> >Josef Karliak via Postfix-users:
> >>what could cause that Postfix do not send DSN of the mail that is
> >> recieved over another server ?
>
> On 05.05.25 08:16, Wietse Venema via Postfix-users wrote:
> >1) As specified in RFC 3461, the remote SMTP
Josef Karliak via Postfix-users:
what could cause that Postfix do not send DSN of the mail that is
recieved over another server ?
On 05.05.25 08:16, Wietse Venema via Postfix-users wrote:
1) As specified in RFC 3461, the remote SMTP client may disable
delivery status notifications with:
Josef Karliak via Postfix-users:
>Good morning,
>
>what could cause that Postfix do not send DSN of the mail that is
> recieved over another server ?
1) As specified in RFC 3461, the remote SMTP client may disable
delivery status notifications with:
RCPT TO: NOTIFY=none
2) The loca
Good morning,
what could cause that Postfix do not send DSN of the mail that is
recieved over another server ? If I set a email client directly to the
the server with Postfix, DSN is generated:
No DSN : client->smtp1->smtp2
DSN : client->smtp2
Both smtp's IP is in "mynetworks" in
Le 11/13/23 à 14:45, Stephen Satchell via Postfix-users a écrit :
[...]
3. Thunderbird sends out the delivery status return receipt request. I must
emphasize, REQUEST. Mail recipients are free to ignore such requests. For
example, I have my all my instances of Thunderbird set to ignore such
Subject: [Thunderbird email client] Composing email: Clicking Options
Delivery Status Notification Does Not Work At All!!!
Good day from Singapore,
Today is 13 November 2023 Monday Singapore Time 7 PM.
Recently I have installed Thunderbird email client version 115.4.1
(64-bit) SUPERNOVA in Window
Subject: [Thunderbird email client] Composing email: Clicking Options
> Delivery Status Notification Does Not Work At All!!!
Good day from Singapore,
Today is 13 November 2023 Monday Singapore Time 7 PM.
Recently I have installed Thunderbird email client version 115.4.1
(64-bit) SUPERNOVA
On Tue, Oct 19, 2021 at 10:40:12PM -0400, Viktor Dukhovni
wrote:
> On Tue, Oct 19, 2021 at 10:35:41PM -0400, post...@ptld.com wrote:
>
> > >> $ postconf smtpd_discard_ehlo_keywords
> > >> smtpd_discard_ehlo_keywords = pipelining, chunking,
> > >> silent-discard, DSN, ETRN
> > >
> > >
On Tue, Oct 19, 2021 at 10:35:41PM -0400, post...@ptld.com wrote:
> >> $ postconf smtpd_discard_ehlo_keywords
> >> smtpd_discard_ehlo_keywords = pipelining, chunking,
> >> silent-discard, DSN, ETRN
> >
> > Why did you decide to turn off PIPELINING and CHUNKING?
>
> Based on the last par
$ postconf smtpd_discard_ehlo_keywords
smtpd_discard_ehlo_keywords = pipelining, chunking,
silent-discard, DSN, ETRN
Why did you decide to turn off PIPELINING and CHUNKING?
Based on the last paragraph of BDAT_README.html I do not see any benefit
of offering it and I assume disabling
On Tue, Oct 19, 2021 at 08:53:27PM -0400, post...@ptld.com wrote:
> $ postconf smtpd_discard_ehlo_keywords
> smtpd_discard_ehlo_keywords = pipelining, chunking, silent-discard, DSN,
> ETRN
Why did you decide to turn off PIPELINING and CHUNKING?
--
Viktor.
I would like for my postfix to send a DSN back to me (locally), for an
email I'm sending
out to the internet via submission port 587 as an authenticated user.
Never mind, I figured it out.
main.cf:
smtpd_discard_ehlo_keywords = pipelining, chunking, silent-discard,
ETRN, DSN
master.cf:
I generally disable the 'DSN' EHLO keyword on the inbound SMTP port.
$ postconf -P smtp/inet/smtpd_discard_ehlo_keywords
smtp/inet/smtpd_discard_ehlo_keywords = silent-discard,DSN,ETRN
$ postconf -P smtpd_discard_ehlo_keywords
postconf: warning: unmatched request: "smtpd_discard_e
On Tue, Oct 19, 2021 at 06:55:15PM -0400, post...@ptld.com wrote:
> Is there a setting for disabling delivery status notification reports
> being emailed back to the sender address by MAILER-DAEMON? I could not
> find one searching in postconf.5.html
I generally disable the 'DSN
Is there a setting for disabling delivery status notification reports
being emailed back to the sender address by MAILER-DAEMON? I could not
find one searching in postconf.5.html
Is there any negative effects from disabling this?
I feel like it could be abused as a type of back scatter.
Wietse Venema wrote in
<4g0fnm4hyszj...@spike.porcupine.org>:
|Steffen Nurpmeso:
|> Ciao from Germany to the big Apple!
|> (Or maybe .. peanuts?? Or Sunflower seeds? :)
|
|All of the above? I haven't been in the city for more than a year,
Oh .. yes. And potatoes! Potatoes are good.
|bu
Steffen Nurpmeso:
> Ciao from Germany to the big Apple!
> (Or maybe .. peanuts?? Or Sunflower seeds? :)
All of the above? I haven't been in the city for more than a year,
but things are very slowly returning to normal in the Northeast US
with vaccination levels around 70 percent.
Wietse
Wietse Venema wrote in
<4g0bbj3dlnzj...@spike.porcupine.org>:
|Steffen Nurpmeso:
|>|Then Postfix sends a delivery status notification.
|...
|>|Again, Postfix opens the mailbox file, does an lseek() to the end
|>|of the file, writes the message, flushes the output with fsync(),
Steffen Nurpmeso:
> |Then Postfix sends a delivery status notification.
...
> |Again, Postfix opens the mailbox file, does an lseek() to the end
> |of the file, writes the message, flushes the output with fsync(),
> |and closes the mailbox file before claiming successful delivery.
Steffen Nurpmeso wrote in
<20210609165007.rc_ih%stef...@sdaoden.eu>:
...
||> Jun 9 01:38:06 postfix/smtpd[17007]: B713116056: client=unknown[45.13\
||> 7\
||> .22.84]
| ...
||> status=sent (delivered to mailbox)
||
||Postfix delivers an email message with message-id
||<2021060816
c(), and
|closes the mailbox file before claiming successful delivery.
(Mind you i struggled with your words in the release that client
certificates via SASL cannot be supported, since dovecot uses the
very same mechanism for its own client certificate via SASL.)
|Then Postfix sends a deliver
On Wed, Jun 09, 2021 at 11:48:45AM -0400, Wietse Venema wrote:
> > Jun 9 01:38:07 postfix/local[17012]: B713116056:
> > to=, relay=local, delay=2.1, delays=1.3/0.01/0/0.83,
> > dsn=2.0.0, status=sent (delivered to mailbox)
>
> Postfix opens the mailbox file, does an lseek() to the end of the
s the mailbox file before claiming successful delivery.
Then Postfix sends a delivery status notification.
> Jun 9 01:38:07 postfix/cleanup[17011]: A5B3516059:
> message-id=<20210608233807.a5b3516...@sdaoden.eu>
> Jun 9 01:38:07 postfix/qmgr[2581]: A5B3516059: from=<>, size=
=1
(queue active)
Jun 9 01:38:07 postfix/bounce[17013]: B713116056: sender delivery status
notification: A5B3516059
So here a delivery status is generated, and i do not know why or
how i could disable this.
Jun 9 01:38:07 postfix/qmgr[2581]: B713116056: removed
Jun 9 01:38:07 postfix/
On 02/16/2016 03:39 PM, Wietse Venema wrote:
Epiontis IT:
Hi,
does postfix offer a way to explicitly route undeliverable notifications
for alias addresses to the postmaster instead of the mail sender.
With /etc/aliases, use the owner- prefix to redirect bounces for a
specific recipient address
Epiontis IT:
> Hi,
>
> does postfix offer a way to explicitly route undeliverable notifications
> for alias addresses to the postmaster instead of the mail sender.
With /etc/aliases, use the owner- prefix to redirect bounces for a
specific recipient address.
Quote from Posfix aliases(5):
Hi,
does postfix offer a way to explicitly route undeliverable notifications
for alias addresses to the postmaster instead of the mail sender. We use
some aliases that map to external mail addresses. When these are not
available the sender will get notified and may be confused about why his
m
@Ansgar Wiechars,
I am struggling to reply to you as you replied off-list and my last
attempt on the list failed. I think you've fixed the first issue but
there may be another one, perhaps with my settings or the settings you
expect from me as I now get the following bounce:
"This is the mai
Hi Ansgar,
Sorry but the same issue still exists.
If it helps I am relaying via my ISP's mailserver, smtp.ntlworld.com:465
(62.254.26.221) as I am in a dynamic IP block of addresses.
I am having to reply via the postfix list as the direct e-mail does not
work.
Regards,
Nick
On 17/04/2015
@Ansgar Wiechars
I tried to reply to your e-mail earlier today about HTML formatted
e-mails out of courtesy but received the bounce below. I don't think I
am mis-configured but if I am I'd love some help. I had a look at the
rhsbl.ahbl.org list and it seems that this list is no longer active a
Pol Hallen:
> > Do you have a AV scanner or some other after queue content filter? If
> > yes postfix is maybe telling you that the message has been transfered
> > to this next hop. IMHO you should ditch DSN because no one is
> > using/allowing it anyway, so trying to get it right is a fruitless
>
> Do you have a AV scanner or some other after queue content filter? If
> yes postfix is maybe telling you that the message has been transfered
> to this next hop. IMHO you should ditch DSN because no one is
> using/allowing it anyway, so trying to get it right is a fruitless
> effort.
Hello and t
scard
0.0.0.0/0 silent-discard, dsn
::/0silent-discard, dsn
I've small lan on 192.168.1.0 and all clients uses a single smtp postfix
server.
On clients, send the emails with "delivery status notification" option.
After sent, postfix send me a delivery
1.0/24 silent-discard
> 0.0.0.0/0 silent-discard, dsn
> ::/0silent-discard, dsn
>
>
> I've small lan on 192.168.1.0 and all clients uses a single smtp postfix
> server.
>
> On clients, send the emails with "delivery status notif
ilent-discard, dsn
::/0silent-discard, dsn
I've small lan on 192.168.1.0 and all clients uses a single smtp postfix
server.
On clients, send the emails with "delivery status notification" option.
After sent, postfix send me a delivery status notification:
Succ
* Yep the mistake i did was that i was grepping for smtp_discard instead of
smtpd_discard
postconf | grep smtp_disc
smtp_discard_ehlo_keyword_address_maps =
smtp_discard_ehlo_keywords =
postconf | grep smtpd_disc
postscreen_discard_ehlo_keyword_address_maps =
$smtpd_discard_ehlo_keyword_address
erefore, the mail client will not
request delivery status notification.
DSN support is available with Postfix 2.3 and later. To view
Postfix settings use:
$ postconf | grep smtpd_discard_ehlo
$ grep smtpd_discard_ehlo /etc/postfix/master.cf
Wietse
entering state: 0
> 0[a2b140]: SMTP Response: 250 2.1.0 Ok
> 0[a2b140]: SMTP entering state: 5
> 0[a2b140]: SMTP Send: RCPT TO:
> NOTIFY=SUCCESS,FAILURE,DELAY ORCPT=rfc822;mailhostingser...@gmail.com
> -------
>
> TI
On Fri, Dec 30, 2011 at 8:50 PM, Wietse Venema wrote:
> pritam raote:
> > Hello,
> >
> > * DSN(sender delivery status notification) does not work on my box
> running
> > postfix.
> > * the version of postfix on the non working box is postfix-2.8.7-1
>
> DS
pritam raote:
> Hello,
>
> * DSN(sender delivery status notification) does not work on my box running
> postfix.
> * the version of postfix on the non working box is postfix-2.8.7-1
DSN works only if:
1 - The POSTFIX SMTP server sends the DSN announcement to the REMOTE
SMTP c
Hello,
* DSN(sender delivery status notification) does not work on my box running
postfix.
* the version of postfix on the non working box is postfix-2.8.7-1
In Mozilla Thunderebird
write message --> options --> Delivery Status Notification
* Read this didnt help much http://www.postf
4f9nBIuLH7XYppw9r5X86tRuSjZ15KyHdRGo8=
In-Reply-To: <001636e0a98b22ec89049fcaa...@google.com>
Date: Thu, 31 Mar 2011 11:35:29 -0600
Subject: Fwd: Delivery Status Notification (Failure)
From: user
To: "Me"
X-Sanitizer: This message has been sanitized!
X-Sanitizer-URL: http://mailtools.anomy.
...@postfix.org [mailto:owner-postfix-us...@postfix.org]
On Behalf Of lst_ho...@kwsoft.de
Sent: Friday, April 09, 2010 7:37 PM
To: postfix-users@postfix.org
Subject: RE: amavis Delivery status notification(DSN) failing
Zitat von "Sharma, Ashish" :
> Wietse,
>
> Thanks for your sugg
Zitat von "Sharma, Ashish" :
Wietse,
Thanks for your suggestion.
Since I am new in this can you suggest some java based deployments
that I can use. I too looked for what you have suggested but maybe I
didn't looked hard enough.
Thanks in advance
Ashish Sharma
http://james.apache.org/
Sharma, Ashish:
> Mark,
>
> Accepted your point, but I am actually doing what you have suggested already.
>
> Maybe the proof lies in the fact that my custom content filter is
> working fine when amavisd is not used and postfix is directly
> communicating with my component. I am not receiving suc
Ashish,
>> Your java filter sent a greeting: "220 Hello\n"
>> instead of: "220 Hello\r\n". Amavisd waited 30 seconds but
>> end of line (CR LF) never arrived, so the session was aborted.
>> RFC 5321 (and RFC 2821 and RFC 821) requires that SMTP commands
>> and replies are terminated by a CRLF, not
@postfix.org
Subject: Re: amavis Delivery status notification(DSN) failing
Ashish,
> Attached is the full level 5 log for your reference.
Thank you!
Apr 9 07:17:31 ip-10-194-99-63 amavis[18885]: (18885-05)
(about to connect to [127.0.0.1]:10030) FWD via SMTP:
->
Apr 9 07:17:31 ip-10-194
ix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org]
On Behalf Of Wietse Venema
Sent: Friday, April 09, 2010 6:18 PM
To: Postfix users
Subject: Re: amavis Delivery status notification(DSN) failing
Sharma, Ashish:
> Wietse,
>
> Executed the command you sent, getting the following error messa
23 PM
> To: Postfix users
> Subject: Re: amavis Delivery status notification(DSN) failing
>
> Sharma, Ashish:
> > Wietse,
> >
> > Following is the requested result:
> >
> > $telnet 10.194.99.63 10030
> > Trying 10.194.99.63...
> > Connecte
: Friday, April 09, 2010 4:23 PM
To: Postfix users
Subject: Re: amavis Delivery status notification(DSN) failing
Sharma, Ashish:
> Wietse,
>
> Following is the requested result:
>
> $telnet 10.194.99.63 10030
> Trying 10.194.99.63...
> Connected to ip-10-194-99-63.ec2.i
Ashish,
> Attached is the full level 5 log for your reference.
Thank you!
Apr 9 07:17:31 ip-10-194-99-63 amavis[18885]: (18885-05)
(about to connect to [127.0.0.1]:10030) FWD via SMTP:
->
Apr 9 07:17:31 ip-10-194-99-63 amavis[18885]: (18885-05)
smtp session: setting up a new session
Ap
Sharma, Ashish:
> Wietse,
>
> Following is the requested result:
>
> $telnet 10.194.99.63 10030
> Trying 10.194.99.63...
> Connected to ip-10-194-99-63.ec2.internal (10.194.99.63).
> Escape character is '^]'.
> 220 Hello
> Mail From:ashiish.sha...@gmail.com
> 503 5.5.1 Error: need EHLO command
>
g [mailto:owner-postfix-us...@postfix.org]
On Behalf Of Mark Martinec
Sent: Thursday, April 08, 2010 10:04 PM
To: postfix-users@postfix.org
Subject: Re: amavis Delivery status notification(DSN) failing
Ashish,
> I have a postfix mail server over which I have deployed a custom content
> f
ilto:owner-postfix-us...@postfix.org]
On Behalf Of Wietse Venema
Sent: Thursday, April 08, 2010 9:37 PM
To: Postfix users
Subject: Re: amavis Delivery status notification(DSN) failing
Sharma, Ashish:
> Apr 7 11:36:54 ip-10-194-99-63 postfix/lmtp[3594]: BABCC100191:
> to=,
> relay=127.0.0
Ashish,
> I have a postfix mail server over which I have deployed a custom content
> filter written in java.
>
> Now I introduced amavisd (containing clamav and spamassassin) as content
> filter such that the mail is passing in following manner:
>
> ===>mail from outside ===> Postfix > ama
Sharma, Ashish:
> Apr 7 11:36:54 ip-10-194-99-63 postfix/lmtp[3594]: BABCC100191:
> to=,
> relay=127.0.0.1[127.0.0.1]:10024, delay=40, delays=0.54/0.01/0/40, dsn=4.5.0,
> status=deferred (host 127.0.0.1[127.0.0.1] said: 451 4.5.0 Error in
> processing, id=03264-02, delivery-notification FAILED
Hi,
I have a postfix mail server over which I have deployed a custom content filter
written in java.
Now I introduced amavisd (containing clamav and spamassassin) as content filter
such that the mail is passing in following manner:
===>mail from outside ===> Postfix > amavisd ===> custom c
58 matches
Mail list logo
