On Wed, Jan 12, 2022 at 10:44:18AM -0500, Wietse Venema wrote:
> Wietse Venema:
> > Wietse:
> > > I think it is a mistake to enforce Spamhaus for clients that connect
> > > to port 578. Clients on port 25 must authenticate.
>
> Sorry, 25 should have been 578.
how to control rules for 587? Is
Hello
I like postfix and dovecot for setting up mail systems.
But I don't like roundcube or rainloop webmail.
How can I make a webmail system like gmail? it would have gmail's
primary features such as grouping, filtering, labeling. is there any
opensource one?
Thank you.
Frank
Chris Green:
> If I add a second line to .forward, e.g. make it something like:-
>
> | /home/chris/.mutt/bin/filter.py
> | /home/chris/dev/bin/filter.py
>
> Then, if (as is likely) there are errors in /home/chris/dev/bin/filter.py
> the message sender will see an error returned even
On Tue, Jan 18, 2022 at 07:52:23AM -0500, Wietse Venema wrote:
> Chris Green:
> > If I add a second line to .forward, e.g. make it something like:-
> >
> > | /home/chris/.mutt/bin/filter.py
> > | /home/chris/dev/bin/filter.py
> >
> > Then, if (as is likely) there are errors in
Hi
Thenx all :) for test i change to 300 for default_process_limit and change 190 to 300
Wysłano z mojego Mi MIX 2Wietse Venema 17 sty 2022 18:34 napisał(a):natan:
> W dniu 17.01.2022 o?15:58, Wietse Venema pisze:
> > natan:
> >> W dniu 14.01.2022 o 22:18, Wietse Venema pisze:
> >>> natan:
On 2022-01-18 12:58, Frank Hwa wrote:
I like postfix and dovecot for setting up mail systems.
But I don't like roundcube or rainloop webmail.
How can I make a webmail system like gmail? it would have gmail's
primary features such as grouping, filtering, labeling. is there any
opensource one?
This is a possibly naive question.
Currently I deliver local mail to myself on my linux (xubuntu 21.10)
system using a ~/.forward file as follows:-
| /home/chris/.mutt/bin/filter.py
I'm looking for a simple way to test new versions of filter.py and I'm
not coming up with easy answers.
If I
I am sorry, that is wrong. I am getting main and master confused.
This is in main
www2:/etc/postfix # grep "^smtpd" main.cf
smtpd_helo_required = yes
smtpd_helo_restrictions = permit_mynetworks, reject_invalid_hostname,
regexp:/etc/postfix/helo.regexp, permit
smtpd_sender_restrictions =
Wietse Venema:
> Ruben Safir:
> > UNDER main.cf I have this:
> >
> > smtpd_data_restrictions = reject_unauth_pipelining, permit
> >
> >
> > # SASL stuff
> >
> ...
> >
On Tue, Jan 18, 2022 at 10:47:05AM -0500, Wietse Venema wrote:
> Ruben Safir:
> > UNDER main.cf I have this:
> >
> > smtpd_data_restrictions = reject_unauth_pipelining, permit
> >
> >
> > # SASL stuff
> >
On Tue, Jan 18, 2022 at 04:50:11PM +0100, Matus UHLAR - fantomas wrote:
> On 18.01.22 10:32, Ruben Safir wrote:
> >I am sorry, that is wrong. I am getting main and master confused.
> [...]
>
> >THIS is in Master
> >www2:/etc/postfix # grep "smtpd" master.cf|grep -v "#"
>
> don't use grep for
On Tue, 18 Jan 2022, Chris Green wrote:
[...]
Currently I deliver local mail to myself on my linux (xubuntu 21.10)
system using a ~/.forward file as follows:-
| /home/chris/.mutt/bin/filter.py
I'm looking for a simple way to test new versions of filter.py and I'm
not coming up with easy
Ruben Safir:
> On Wed, Jan 12, 2022 at 10:44:18AM -0500, Wietse Venema wrote:
> > Wietse Venema:
> > > Wietse:
> > > > I think it is a mistake to enforce Spamhaus for clients that connect
> > > > to port 578. Clients on port 25 must authenticate.
> >
> > Sorry, 25 should have been 578.
>
> how
On Wed, Jan 12, 2022 at 10:43:11AM -0500, Wietse Venema wrote:
> Wietse:
> > I think it is a mistake to enforce Spamhaus for clients that connect
> > to port 578. Clients on port 25 must authenticate.
>
> Ruben Safir:
> > I agree, but I don't know how to control rules for 587?
> > How do I tell
> -o milter_macro_daemon_name=ORIGINATING
>
I don't need the milter I assume?
> Wietse
--
So many immigrant groups have swept through our town
that Brooklyn, like Atlantis, reaches mythological
proportions in the mind of the world - RI Safir 1998
http://www.mrbrklyn.com
DRM is
Ruben Safir:
> UNDER main.cf I have this:
>
> smtpd_data_restrictions = reject_unauth_pipelining, permit
>
>
> # SASL stuff
>
...
> smtpd_sasl_auth_enable = yes
Note, SASL
W dniu 18.01.2022 o 16:53, natan pisze:
> W dniu 18.01.2022 o 16:17, Wietse Venema pisze:
>> natan:
>>> Hi
>>> My happiness did not last long
>>>
>>> Jan 18 13:33:22? postfix/master[3581]: warning:
>>> master_wakeup_timer_event: service qmgr(public/qmgr): Resource
>>> temporarily unavailable
>>>
Hi
My happiness did not last long
Jan 18 13:33:22 postfix/master[3581]: warning:
master_wakeup_timer_event: service qmgr(public/qmgr): Resource
temporarily unavailable
I'm so confused beacuse I cannot resolv thats problem and I dont known
where is realy problem
W dniu 18.01.2022 o 10:34,
natan:
> Hi
> My happiness did not last long
>
> Jan 18 13:33:22? postfix/master[3581]: warning:
> master_wakeup_timer_event: service qmgr(public/qmgr): Resource
> temporarily unavailable
>
> I'm so confused beacuse I cannot resolv thats problem and I dont known
> where is realy problem
Repeat:
On 18.01.22 10:32, Ruben Safir wrote:
I am sorry, that is wrong. I am getting main and master confused.
[...]
THIS is in Master
www2:/etc/postfix # grep "smtpd" master.cf|grep -v "#"
don't use grep for master.cf, there are usuallu options on next lines
smtp inet n - n
Ruben Safir:
> > -o milter_macro_daemon_name=ORIGINATING
>
> I don't need the milter I assume?
You can comment it out and leave it as a reminder. If you ever want
to add a signing milter, then this may be needed.
Wietse
W dniu 18.01.2022 o 16:17, Wietse Venema pisze:
> natan:
>> Hi
>> My happiness did not last long
>>
>> Jan 18 13:33:22? postfix/master[3581]: warning:
>> master_wakeup_timer_event: service qmgr(public/qmgr): Resource
>> temporarily unavailable
>>
>> I'm so confused beacuse I cannot resolv thats
natan:
> W dniu 18.01.2022 o 16:17, Wietse Venema pisze:
> > natan:
> >> Hi
> >> My happiness did not last long
> >>
> >> Jan 18 13:33:22? postfix/master[3581]: warning:
> >> master_wakeup_timer_event: service qmgr(public/qmgr): Resource
> >> temporarily unavailable
> >>
> >> I'm so confused
On Tue, Jan 18, 2022 at 10:36:34AM -0500, Ruben Safir wrote:
> > -o milter_macro_daemon_name=ORIGINATING
> >
>
> I don't need the milter I assume?
>
I have this line as well, which I think might be wrong
smtp inet n - n - - smtpd <<==
As for specifying
[An on-line version of this announcement will be available at
http://www.postfix.org/announcements/postfix-3.6.4.html]
Fixed in Postfix 3.6.4, 3.5.14, 3.4.24, 3.3.21:
* Bug introduced in bugfix 20210708: duplicate bounce_notice_recipient
entries in postconf output. This was caused by an
GhettoForge has a repo for Postfix3, it is not clear to me if Postfix3 is
another beast entirely or if it is just a normal Postfix version 3 and higher.
Can someone explain what is the purpose of "Postfix3"?
Are there other options (repos) for getting current versions of Postfix using
dnf on a
On Tue, Jan 18, 2022 at 04:50:11PM +0100, Matus UHLAR - fantomas wrote:
don't use grep for master.cf, there are usuallu options on next lines
# postconf -M smtps submission
submission inet n - y - - smtpd -o
syslog_name=postfix/submission -o
Are there other options (repos) for getting current versions of Postfix using
dnf on a RHEL system?
fwiw,
use existing pkgs from https://src.fedoraproject.org/rpms/postfix for 'Fedora
ELN, if that fits your needs
or rebuild & package from those sources, or your own tweaked/modified .spec,
post...@ptld.com:
> GhettoForge has a repo for Postfix3, it is not clear to me if
> Postfix3 is another beast entirely or if it is just a normal Postfix
> version 3 and higher. Can someone explain what is the purpose of
> "Postfix3"?
According to http://ghettoforge.org/index.php/Postfix3 it's the
> According to http://ghettoforge.org/index.php/Postfix3 it's the
> latest (presumably stable) release. They appear to have Postfix
> 3.6 at this time.
Yes, I see that. But why "Postfix3"? How is that different from normal Postfix?
If it's a repo providing the same Postfix as every other repo
. . .
> OK, here goes -
>
> Using version 3.4.7 packaged by Suse. I use "fetchmail" to retrieve email
> via imap one of which is gmail. The fetched mail is all sent to a local "off
> box" machine, via postfix, spamassassin and clamav, all on the same server.
> The off box machine let's
For version 3.7.4, is there a means of disabling for smtp per user, per domain,
per IP, when "smtp_sender_dependent_authentication = yes"?
Docs/supplements seem say some roughly analogous settings were available pre V
3.x, but are now deprecated. I've not found any current setting while
It's "postfix3" so it does not conflict with the RHEL/CentOS system "postfix"
package.
RobertC
From: owner-postfix-us...@postfix.org on
behalf of post...@ptld.com
Sent: Tuesday, January 18, 2022 14:39
To: Postfix users
Subject: Re: GhettoForge Postfix3
This
* Frank Hwa:
> I like postfix and dovecot for setting up mail systems. But I don't
> like roundcube or rainloop webmail.
You might give SOGo (https://www.sogo.nu) a shot.
-Ralph
Joe Acquisto-j4:
> For version 3.7.4, is there a means of disabling for smtp per user,
> per domain, per IP, when "smtp_sender_dependent_authentication =
> yes"?
Postfix will search smtp_sasl_password_maps by sender first, and
if that is not found, then by destination.
If you don't want Postfix
On Tue, 18 Jan 2022 15:39:24 -0500
post...@ptld.com wrote:
> > According to http://ghettoforge.org/index.php/Postfix3 it's the
> > latest (presumably stable) release. They appear to have Postfix
> > 3.6 at this time.
>
>
> Yes, I see that. But why "Postfix3"? How is that different from
>
> Wietse Venema:
>> Joe Acquisto-j4:
>> > For version 3.7.4, is there a means of disabling for smtp per user,
>> > per domain, per IP, when "smtp_sender_dependent_authentication =
>> > yes"?
>>
>> Postfix will search smtp_sasl_password_maps by sender first, and
>> if that is not found, then by
. . .
> I would imagine that Postfix can only authenticate to
> servers that have entries in /etc/postfix/sasl_passwd.
>
> smtp_sasl_password_maps (default: empty)
>
> Optional Postfix SMTP client lookup tables with one
> username:password entry per sender, remote hostname
> or
> likely at least a minimal attempt to avoid naming conflicts. renaming
> forked the code (hopefully) helps avoid blaming Wietse for whatever gets
> broken in that fork.
Wait, so its a fork of Postfix?
And not the same code as what Wietse releases for the same version?
Wietse Venema:
> Joe Acquisto-j4:
> > For version 3.7.4, is there a means of disabling for smtp per user,
> > per domain, per IP, when "smtp_sender_dependent_authentication =
> > yes"?
>
> Postfix will search smtp_sasl_password_maps by sender first, and
> if that is not found, then by
On Mon, Jan 17, 2022 at 10:04:13PM -0500, Joe Acquisto-j4
wrote:
> > On 2022-01-17 at 20:09:55 UTC-0500 (Mon, 17 Jan 2022 20:09:55 -0500)
> > Joe Acquisto-j4
> > is rumored to have said:
> >
> >
> >> Sorry for the garbled message. Looking for the config files, etc that
> >> are normally
> Wietse Venema:
>> Joe Acquisto-j4:
>> > For version 3.7.4, is there a means of disabling for smtp per user,
>> > per domain, per IP, when "smtp_sender_dependent_authentication =
>> > yes"?
>>
>> Postfix will search smtp_sasl_password_maps by sender first, and
>> if that is not found, then by
On Tue, 18 Jan 2022 17:13:32 -0500
post...@ptld.com wrote:
> Wait, so its a fork of Postfix?
> And not the same code as what Wietse releases for the same version?
It's whatever the maintainer of that code wants, intends, etc.
Why not ask the maintainer?
--
jd
43 matches
Mail list logo
