@lbutlr wrote:
> Bob Proulx wrote:
> > But so many people use Gmail these days that they have gotten used to
> > the way Gmail does things. And Gmail de-duplicates and saves the
> > first message with any particular message-id that arrives. And then
> > displays a "mailbox" showing a view of the
@lbutlr wrote:
> On 23 Nov 2020, at 15:27, Jaroslaw Rafa wrote:
> > Dnia 23.11.2020 o godz. 11:49:39 D'Arcy Cain pisze:
> >>
> >> If someone replies to a mailing list and copies the sender then that
> >> person gets two copies. The above recipe avoids that.
>
> > Moreover, it breaks the
On 23 Nov 2020, at 15:40, Richard Damon wrote:
> On 11/23/20 5:27 PM, Jaroslaw Rafa wrote:
>> Dnia 23.11.2020 o godz. 11:49:39 D'Arcy Cain pisze:
>>> If someone replies to a mailing list and copies the sender then that
>>> person gets two copies. The above recipe avoids that.
>> If someone gets
On 23 Nov 2020, at 15:27, Jaroslaw Rafa wrote:
> Dnia 23.11.2020 o godz. 11:49:39 D'Arcy Cain pisze:
>>
>> If someone replies to a mailing list and copies the sender then that
>> person gets two copies. The above recipe avoids that.
> Moreover, it breaks the continuity of threads on mailing
On 23 Nov 2020, at 13:24, Bob Proulx wrote:
> Jaroslaw Rafa wrote:
>> Dnia 23.11.2020 o godz. 10:18:39 D'Arcy Cain pisze:
>>> After the first message was accepted all of the rest
>>> were silently dropped as duplicates due to a very standard procmail
>>> recipe:
>>>
>>> :0 Wh: msgid.lock
>>> |
On 23 Nov 2020, at 13:34, Erwan David wrote:
> Le 23/11/2020 à 20:16, @lbutlr a écrit :
>> I would feel comfortable rejecting messages without a Message-ID.
> Maybe on smtp, but not on submission. FOr me policy there is completeley
> different
On submission postfix adds the message ID as is
On 11/23/20 5:27 PM, Jaroslaw Rafa wrote:
> Dnia 23.11.2020 o godz. 11:49:39 D'Arcy Cain pisze:
>> If someone replies to a mailing list and copies the sender then that
>> person gets two copies. The above recipe avoids that.
> If someone gets two copies - a direct one and the mailing list one -
Dnia 23.11.2020 o godz. 11:49:39 D'Arcy Cain pisze:
>
> If someone replies to a mailing list and copies the sender then that
> person gets two copies. The above recipe avoids that.
If someone gets two copies - a direct one and the mailing list one - then
he/she knows that the sender has replied
On 11/23/20 3:34 PM, Erwan David wrote:
> Le 23/11/2020 à 20:16, @lbutlr a écrit :
>> On 23 Nov 2020, at 06:49, maciejm wrote:
>>> "RFC 822 Message-ID is not required"
>> RFC 822 has been obsoleted several times.
>>
>> RFC 5322 states:
>>
>>Though listed as optional in the table in section
Le 23/11/2020 à 20:16, @lbutlr a écrit :
> On 23 Nov 2020, at 06:49, maciejm wrote:
>> "RFC 822 Message-ID is not required"
> RFC 822 has been obsoleted several times.
>
> RFC 5322 states:
>
>Though listed as optional in the table in section 3.6, every message
>SHOULD have a
Jaroslaw Rafa wrote:
> Dnia 23.11.2020 o godz. 10:18:39 D'Arcy Cain pisze:
> > After the first message was accepted all of the rest
> > were silently dropped as duplicates due to a very standard procmail
> > recipe:
> >
> > :0 Wh: msgid.lock
> > | formail -D 65536 $HOME/.msgid.cache
>
> Who uses
On 23 Nov 2020, at 07:44, Jaroslaw Rafa wrote:
> Dnia 23.11.2020 o godz. 10:18:39 D'Arcy Cain pisze:
>>
>> :0 Wh: msgid.lock
>> | formail -D 65536 $HOME/.msgid.cache
>
> Who uses that?
Everyone who ever used procmail? Nearly everyone who ever used procmail?
It's even in the procmail man page.
On 23 Nov 2020, at 06:49, maciejm wrote:
> "RFC 822 Message-ID is not required"
RFC 822 has been obsoleted several times.
RFC 5322 states:
Though listed as optional in the table in section 3.6, every message
SHOULD have a "Message-ID:" field. Furthermore, reply messages
SHOULD have
Benny Pedersen:
> Wietse Venema skrev den 2020-11-23 17:10:
>
> > Postfix 2.6 and later don't add a Message-ID header, unless the
> > message comes from a "local" source. That header is a combination
> > of a time stamp and the Postfix $myhostname value, so it is unique
> > as long as both values
Joe,
> Due to some recent malware (in attachments, obvious stuff) wanted to add AV
> scanning. I gather "Amavis-new" is the hot ticket these days,
> I deal with Sophos products and would like to use their linux product to do
> the scanning. Seems to be precious little on how to do that.
I
Wietse Venema skrev den 2020-11-23 17:10:
Postfix 2.6 and later don't add a Message-ID header, unless the
message comes from a "local" source. That header is a combination
of a time stamp and the Postfix $myhostname value, so it is unique
as long as both values are unique.
okay, what if msgid
On 23/11/2020 16:34, Joe Acquisto-j4 wrote:
Not to waste anyone's time, but I posted this on SA list and a Sophos site, but, came up with zip.
Not even a "do-dah". Beyond "experiences"
any leads to general "how to: guides that work in practice?
SOHO system, on virtual machines. Fairly
Not to waste anyone's time, but I posted this on SA list and a Sophos site,
but, came up with zip. Not even a "do-dah". Beyond "experiences"
any leads to general "how to: guides that work in practice?
>> SOHO system, on virtual machines. Fairly recent versions. Running openSUSE
>> Leap 15.1.
Benny Pedersen:
> D'Arcy Cain skrev den 2020-11-23 15:18:
>
> > :0 Wh: msgid.lock
> > | formail -D 65536 $HOME/.msgid.cache
> >
> > In other words, the message ID "" was considered a duplicate after the
> > first one.
>
> if you use postfix there would be uniq msgid always, eq postfix ensures
D'Arcy Cain skrev den 2020-11-23 15:18:
:0 Wh: msgid.lock
| formail -D 65536 $HOME/.msgid.cache
In other words, the message ID "" was considered a duplicate after the
first one.
if you use postfix there would be uniq msgid always, eq postfix ensures
there is always fqdn in msgid aswell,
On 11/23/20 10:44 AM, Jaroslaw Rafa wrote:
Dnia 23.11.2020 o godz. 10:18:39 D'Arcy Cain pisze:
I used to have a client who was not getting emails from one of his
friends. Turned out that the friend's client/MUA was not adding the
message ID.
Doesn't Postfix automatically add Message-Id:
PGNet Dev:
> On 11/23/20 6:48 AM, Wietse Venema wrote:
> > Note that smtpd does not implement the virtual alias mapping. It
> > merely determines if the recipient address should be accepted or
> > rejected.
> >
> > The virtual alias mapping happens on the other end of the
> > smtpd_proxy_filter
> postfix/smtpd[24986]: warning: hostname server17-ams1.internet-census.org
> does not resolve to address 107.6.163.34: Name or service not known
This is a type 4 error (the name->address mapping does not exist).
> postfix/smtpd[24986]: connect from unknown[107.6.163.34]
> postfix/smtpd[24986]:
Thanks for the reply.
The warning says that "hostname does not resolve to address" (case #4) but
then the log says that connection is rejected because it cannot find a
hostname (case #2).
So which one is the actual rejection reason? Doesn't it feel a bit
confusing?
Regards
On 11/23/20 6:48 AM, Wietse Venema wrote:
Note that smtpd does not implement the virtual alias mapping. It
merely determines if the recipient address should be accepted or
rejected.
The virtual alias mapping happens on the other end of the
smtpd_proxy_filter (presumably, another smtpd process
Jaroslaw Rafa:
> Dnia 23.11.2020 o godz. 10:18:39 D'Arcy Cain pisze:
> >
> > I used to have a client who was not getting emails from one of his
> > friends. Turned out that the friend's client/MUA was not adding the
> > message ID.
>
> Doesn't Postfix automatically add Message-Id: header upon
On 11/23/20 9:18 AM, D'Arcy Cain wrote:
> On 11/23/20 9:49 AM, maciejm wrote:
>> Hi
>> Thanks for replay I found "RFC 822 Message-ID is not required"
>> Probably "problem" is in configurations in some clients.
>
> I used to have a client who was not getting emails from one of his friends.
>
PGNet Dev:
> On 11/22/20 11:58 AM, Wietse Venema wrote:
>
> > This would be good fit for virtual_alias_maps (and maybe adding
> > domains to virtual_alias_domains, see note below). virtual_alias_maps
> > replaces the envelope recipient without replacing header addresses,
> > and it works for
Dnia 23.11.2020 o godz. 10:18:39 D'Arcy Cain pisze:
>
> I used to have a client who was not getting emails from one of his
> friends. Turned out that the friend's client/MUA was not adding the
> message ID.
Doesn't Postfix automatically add Message-Id: header upon sending a message
if none is
Eugene Podshivalov:
> Hi all,
> I have the following config
>
> > smtpd_client_restrictions =
> > reject_unknown_client_hostname
> > smtpd_helo_required = yes
> > smtpd_helo_restrictions =
> > reject_invalid_helo_hostname,
> > reject_non_fqdn_helo_hostname,
> >
On 11/22/20 11:58 AM, Wietse Venema wrote:
This would be good fit for virtual_alias_maps (and maybe adding
domains to virtual_alias_domains, see note below). virtual_alias_maps
replaces the envelope recipient without replacing header addresses,
and it works for single-recipient mail
On 11/23/20 9:49 AM, maciejm wrote:
Hi
Thanks for replay I found "RFC 822 Message-ID is not required"
Probably "problem" is in configurations in some clients.
I used to have a client who was not getting emails from one of his friends.
Turned out that the friend's client/MUA was not adding
Hi
Thanks for replay I found "RFC 822 Message-ID is not required"
Probably "problem" is in configurations in some clients.
On 23.11.2020 14:39, Matus UHLAR - fantomas wrote:
> On 23.11.20 14:35, natan wrote:
>> I have probably to trivial questions about message-ID
>>
>> Why sometimes, some user
On 23.11.20 14:35, natan wrote:
I have probably to trivial questions about message-ID
Why sometimes, some user have empty message-id=<>
example:
Nov 23 13:13:53 smtp1 postfix/submission/smtpd[29867]: 4CfmKF1CSDz5MwK:
.domain.ltd[xxx.xxx.xxx.xxx], sasl_method=login,
Hi
I have probably to trivial questions about message-ID
Why sometimes, some user have empty message-id=<>
example:
Nov 23 13:13:53 smtp1 postfix/submission/smtpd[29867]: 4CfmKF1CSDz5MwK:
.domain.ltd[xxx.xxx.xxx.xxx], sasl_method=login,
sasl_username=bi...@domain2.ltd
Nov 23 13:13:53 smtp1
Hi all,
I have the following config
> smtpd_client_restrictions =
> reject_unknown_client_hostname
> smtpd_helo_required = yes
> smtpd_helo_restrictions =
> reject_invalid_helo_hostname,
> reject_non_fqdn_helo_hostname,
> reject_unknown_helo_hostname
> smtpd_sender_restrictions =
36 matches
Mail list logo
