New install of postfix on a freebsd 12.4 system.
I have milter-greylist installed, set up in main.cf as:
milter_protocol = 6
milter_default_action = accept
smtpd_milters = local:/var/milter-greylist/milter-greylist.sock
The socket to milter-greylist is at:
$ ls -dl /var/milter-greylist/
d
Just got the message
smtp; 552 5.3.4 Message size exceeds fixed limit
when attempting to receive a 7MB file:
$ postconf -d | grep size_limit
body_checks_size_limit = 51200
bounce_size_limit = 5
header_size_limit = 102400
mailbox_size_limit = 5120
message_size_limit = 1024
$ postcon
Your log level is too high.
I believe you :-). Although level 2 was the only way I could see
what was happening using the maps I had set, some of which weren't doing
what I (erroneously) thought they should.
What is the relationship between the -v args in master.cf and
debug_peer_level and deb
If someone can point me at an explanation of log entries it would be much
appreciated.
1)
This is a low traffic server.
Whenever a new entry arrives for processing, I see what looks like tables
getting reloaded, e.g.
dict_cidr_open: add a.b.c.0/17 OK
dict_cidr_open: add d.e.f.0/24 OK
dict_open:
On 2/19/21 1:51 PM, Wietse Venema wrote:
Postfix CIDR maps support CIDR. I don't understand how one
would implement CIDR lookup keys in a hash: map.
me either, thanks and to others who replied also
It would be handy if postmap hash:foo printed a warning if it encountered
CIDR or any other pro
I had the impression a map could contain client addresses in CIDR
notation, but apparently not. Is there a way to make restrictions
using CIDR notation?
Here's what I was trying to do:
smtpd_client_restrictions =
permit_mynetworks
check_client_access hash:/etc/postfix/ok_client
reject
/e
On 2/17/21 2:17 PM, Wietse Venema wrote:
Gary Aitken:
< mail-pf1-f170.google.com[209.85.210.170]: DATA
mail-pf1-f170.google.com[209.85.210.170]:
554 5.5.1 Error: no valid recipients
That is incomplete. There is also an RCPT TO command, plus a response
from Postfix that says why
I'm trying to allow client connections from only two places:
a known ip
a specific domain served at gmail
And delivery only to local recipients.
Relevant parts of main.cf:
mynetworks = 127.0.0.0/8 10.138.0.10/32 [:::127.0.0.0]/104 [::1]/128
postfix-server-domain.com otherdomain.com
smt
On 1/17/21 9:53 AM, Matus UHLAR - fantomas wrote:
On 1/16/21 4:04 PM, Jaroslaw Rafa wrote:
Dnia 16.01.2021 o godz. 15:11:58 Gary Aitken pisze:
1. Why is it attempting to send mail on port 25 and not 587?
Because that's the usual port MTA tries to connect to when sending mail. You
d
On 1/17/21 12:30 AM, Viktor Dukhovni wrote:
On Sat, Jan 16, 2021 at 11:37:50PM -0700, Gary Aitken wrote:
/etc/postfix/master.cf:
#smtp inet n - y - - smtpd
submission inet n - y - - smtpd
This looks like a
On 1/16/21 4:08 PM, Viktor Dukhovni wrote:
On Sat, Jan 16, 2021 at 03:11:58PM -0700, Gary Aitken wrote:
I'm trying to set up a postfix-server on a google-compute-engine vm that works
as follows:
* outgoing mail from local machine (aaa.xxx.com) to a select few specific
addresses an
On 1/16/21 4:04 PM, Jaroslaw Rafa wrote:
Dnia 16.01.2021 o godz. 15:11:58 Gary Aitken pisze:
1. Why is it attempting to send mail on port 25 and not 587?
Because that's the usual port MTA tries to connect to when sending mail. You
didn't specify anywhere in your configuration
I'm trying to set up a postfix-server on a google-compute-engine vm that works
as follows:
outgoing mail from local machine (aaa.xxx.com) to a select few specific
addresses and any address on a specific domain (yyy.com)
incoming mail from a single domain only (yyy.com)
DNS is set with MX
On 6/16/20 10:39 PM, Bob Proulx wrote:
Gary Aitken wrote:
...
For future reference it is also possible to use dpkg to remove
postfix ignoring the dependency and then install it again satisfying
the dependency.
dpkg --purge --force-depends postfix ...verify /etc/postfix/ and
other locations
On 6/16/20 9:49 PM, Scott Kitterman wrote:
On Tuesday, June 16, 2020 11:36:27 PM EDT Gary Aitken wrote:
It is using default mail port, 25; I need port 465 or 587 because
it's my understanding google blocks everything on port 25. During
the setup, I was not (I don't think) given the
On 6/12/20 12:26 PM, Wietse Venema wrote:
Gary Aitken:
I had previously edited main.cf to set
sendmail_path = /usr/sbin/sendmail
setgid_group = postdrop
$ sudo postfix check
postfix: fatal: bad string length 0 < 1: mailq_path =
Not sure what mailq_path should be set to... /var/sp
I apologize for the interruption in this thread, fires to put out so slow
getting back to this.
On Sunday, May 31, 2020 4:31:23 PM EDT Gary Aitken wrote:
On 5/31/20 11:34 AM, Matus UHLAR - fantomas wrote:
I'm new to postfix and trying to administer a debian
google-compute box, also new
On 5/31/20 11:34 AM, Matus UHLAR - fantomas wrote:
I'm new to postfix and trying to administer a debian
google-compute box, also new to me (coming from fbsd). So lots of
opportunities for learning...
I modified /etc/crontable to fire off some backup stuff (a shell
script that does a "gcloud c
Hi all,
I'm new to postfix and trying to administer a debian google-compute
box, also new to me (coming from fbsd). So lots of opportunities
for learning...
I modified /etc/crontable to fire off some backup stuff (a shell
script that does a "gcloud compute disks snapshot ...". Cron logs
attemp
19 matches
Mail list logo
