On Sat, Jun 6, 2015 at 11:29 PM, Michael B Allen wrote:
> Jun 6 23:21:06 www postfix/smtpd[2228]: NOQUEUE: reject: RCPT from
> mail-la0-f44.google.com[209.85.215.44]: 454 4.7.1
> : Relay access denied; from=
> to= proto=ESMTP helo=
> mydestination = $myhostname, localhost.$mydomain, localhost
>
Bill Cole said:
> On 3 Jun 2015, at 9:15, John Allen wrote:
>
> >Is there any way of testing for and refusing un-encrypted email?
>
> The generic answer is "yes" but you need to define what you mean to
> pick a mechanism.
>
> If you mean email must be sent and received over an encrypted
> transp
I just moved over to my new server and I can't receive mail. I can
send mail and do IMAP stuff authenticated. I just cannot receive mail.
The server is just a single all-in-one smtpd / submission / imap
server for a handful of users. I just copied my old config pretty much
verbatim but I must admit
Hi Viktor,
I don't complain, I just want to know what happens, and if it makes
sense at all. ;)
How do you know it's Debian? Yes, it's something between Wheezy and
Jessie. Is that a known issue with Debian?
As far as I can see, there's no cron job or something like that that
could alter Postfix
On Sat, Jun 06, 2015 at 10:25:10PM +0200, Robert Senger wrote:
> Suddenly (whoever did that):
> smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
> myhostname = host-1-2-3-4-provider.net
Complain to your Debian maintainer.
--
Viktor.
Hi all,
I've seen some really strange things happening these days.
Recently I asked my ISP to set the PTR records for my ipv4 address
from the default (something like host-1-2-3-4.provider.net) to my own
domains (mydomain.de and myotherdomain.net). Fine.
Then I changed
myhostname = host-1-2
Wietse Venema:
> The Postfix master daemon opens three sockets per master.cf entry:
> the service endpoint (the first field in master.cf), plus one
> socketpair. This single socketpair is used to receive updates from
> all the child processes that implement the corresponding master.cf
> service.
