Am 14.08.2018 um 08:38 schrieb Poliman - Serwis:
> Hi people!
>
> I have a problem with sending emails and I of course try dig. The problem
> in logs:
> Aug 14 07:13:30 s1 postfix/smtpd[8804]: NOQUEUE: filter: RCPT from
> ip6-localhost[127.0.0.1]: : Sender address
> triggers FILTER amavis:[127.0.0
I did a typo. Of course there is colonel.com.pl. Remote address
marc...@colonel.com.pl is enabled and works (google hosting). How do you
know that postfix is thinking colonel.com.pl belongs to himself and what is
that mean [honestly, I am still learning, so maybe it's quite newbie
question]? Output
Can't see any obvious reason.
Try /usr/sbin/sendmail -v marc...@colonel.com.pl on serverconsole.
(Answer will be mailed to loginname.)
Willi
Am 14.08.2018 um 09:12 schrieb Poliman - Serwis:
> I did a typo. Of course there is colonel.com.pl. Remote address
> marc...@colonel.com.pl is enabled a
In console it looks like it hangs:
root@s1:/etc/postfix# /usr/sbin/sendmail -v marc...@colonel.com.pl
[under command is blank screen - should it be?]
I have interrupted it, because from 4 mins it hang and nothing shows at
marc...@colonel.com.pl
--
*Pozdrawiam / Best Regards*
*Piotr Bracha*
Am 14.08.2018 um 10:30 schrieb Poliman - Serwis:
> In console it looks like it hangs:
> root@s1:/etc/postfix# /usr/sbin/sendmail -v marc...@colonel.com.pl
>
> [under command is blank screen - should it be?]
>
> I have interrupted it, because from 4 mins it hang and nothing shows at
> marc...@col
On 13.08.18 21:36, Danny Horne wrote:
I'm trying out Postscreen after having used Postgrey for some time. The
reason for the switch is that Postgrey can cause emails from Google etc.
to take a long time to come through due to the large number of IP
addresses they use (and I don't want to whiteli
On 14.08.18 08:38, Poliman - Serwis wrote:
I have a problem with sending emails and I of course try dig. The problem
in logs:
Aug 14 07:13:30 s1 postfix/smtpd[8804]: NOQUEUE: filter: RCPT from
ip6-localhost[127.0.0.1]: : Sender address
triggers FILTER amavis:[127.0.0.1]:10026; from=
to= proto=
On 14/08/18 10:36, Matus UHLAR - fantomas wrote:
>
> so, what is the problem?
>
None as far as I'm aware, but this is my first time using Postscreen, so
wanted to check that I hadn't messed anything up
On 14/08/18 10:36, Matus UHLAR - fantomas wrote:
so, what is the problem?
On 14.08.18 11:22, Danny Horne wrote:
None as far as I'm aware, but this is my first time using Postscreen, so
wanted to check that I hadn't messed anything up
aha. You'll find that from:
"postfix/postscreen[...]: NOQ
I interrupt this by press on ctrl+c:
root@s1:/etc/postfix# /usr/sbin/sendmail -v marc...@colonel.com.pl
^C
root@s1:/etc/postfix#
Should I execute above command and then click ctrl+d?
Hosted means that record A points to ip of my server - s1.poliman.net [here
is also dns zone] but in dns zone of c
I noticed a mail that broke logging syntax:
Aug 14 15:29:57 X postfix/cleanup[11962]: 41qYP05TZCz5xY9:
message-id==?utf-8?Q?=3CE1F7DC2C-82B5-4927-B0DB-0179227E665C=40aalborgf?=?
=?utf-8?Q?=C3=B8rstehj=C3=A6lp=2Edk=3E?=
I guess the message-id contains non-ascii chars that break logging, or
so
On Tue, 14 Aug 2018 at 15:22, Tom Sommer wrote:
> I noticed a mail that broke logging syntax:
>
> Aug 14 15:29:57 X postfix/cleanup[11962]: 41qYP05TZCz5xY9:
> message-id==?utf-8?Q?=3CE1F7DC2C-82B5-4927-B0DB-0179227E665C=40aalborgf?=?
> =?utf-8?Q?=C3=B8rstehj=C3=A6lp=2Edk=3E?=
>
> I guess the mess
Please avoid top-posting.
On 14.08.18 08:38, Poliman - Serwis wrote:
I have a problem with sending emails and I of course try dig. The problem
in logs:
Aug 14 07:13:30 s1 postfix/smtpd[8804]: NOQUEUE: filter: RCPT from
ip6-localhost[127.0.0.1]: : Sender address
triggers FILTER amavis:[127.0
> On Aug 14, 2018, at 10:21 AM, Tom Sommer wrote:
>
> Aug 14 15:29:57 X postfix/cleanup[11962]: 41qYP05TZCz5xY9:
> message-id==?utf-8?Q?=3CE1F7DC2C-82B5-4927-B0DB-0179227E665C=40aalborgf?=?
> =?utf-8?Q?=C3=B8rstehj=C3=A6lp=2Edk=3E?=
>
> I guess the message-id contains non-ascii chars that b
The message-id is not contained within <> in the log message but maybe that is
correct, it just breaks logstash parsing but perhaps the parser is to blame.
--
Tom Sommer
> On 14 Aug 2018, at 16.34, Dominic Raferd wrote:
>
>
>
>> On Tue, 14 Aug 2018 at 15:22, Tom Sommer wrote:
>> I noticed
> On Aug 14, 2018, at 10:50 AM, Tom Sommer wrote:
>
> The message-id is not contained within <> in the log message but maybe that
> is correct, it just breaks logstash parsing but perhaps the parser is to
> blame.
The "<" and ">" characters are not added by Postfix, they are normally part
o
> On 14 Aug 2018, at 16.57, Viktor Dukhovni wrote:
>
>
>
>> On Aug 14, 2018, at 10:50 AM, Tom Sommer wrote:
>>
>> The message-id is not contained within <> in the log message but maybe that
>> is correct, it just breaks logstash parsing but perhaps the parser is to
>> blame.
>
> The "<"
Hello,
I'm starting the process of moving my mail from a hosted service to my own.
It'll include a Postfix server.
I got a test server running locally and 'sending & receiving' mail inside my
lan.
Now I'm doing my reading on security issues, authentication, and the like.
I've got stacks of a
> On Aug 14, 2018, at 11:05 PM, robac...@fastmail.us wrote:
>
> (2)
>
> Is it time -- in the real-world -- to force STARTTLS yet?
Google reports ~90% of email (volume) inbound/outbound to Gmail uses TLS.
That 10% by volume is probably a larger fraction by count of destination
domains. STARTT
> On Aug 14, 2018, at 11:53 PM, Viktor Dukhovni
> wrote:
>
> DANE is ready for adoption, with multiple fielded implementations and many
> (312 thousand inbound plus some large ones still outbound only) live domains.
>
> Outbound DANE is simple. Make sure you have a DNSSEC-validating resolve
20 matches
Mail list logo
