On 04/02/2011 07:17 AM, Alex wrote:
Hi,
I have a fedora14 box that I'm trying to configure for use with
postfix with dovecot and TLS, permitting only TLS connections after
authenticating with sasl.
What do you mean, *after* ?
It appears to mostly be working now, but
mail is rejected due to
Am 02.04.2011 07:17, schrieb Alex:
> I have a fedora14 box that I'm trying to configure for use with
> postfix with dovecot and TLS, permitting only TLS connections after
> authenticating with sasl.
send account-information unencrypted and after that
encrypt data? who wants such bad things and
On Thu, 31 Mar 2011 14:53:11 -0400, Victor Duchovni
wrote:
> > /etc/postfix/master.cf
> > slow unix - - - - - smtp
> > -o syslog_name=postfix-slow
> > -o smtp_connection_reuse_time_limit=30s
> > EOT
> >
> > /etc/postfix/main.cf
> > slow_initial_destination
Hi,
>> I have a fedora14 box that I'm trying to configure for use with
>> postfix with dovecot and TLS, permitting only TLS connections after
>> authenticating with sasl.
>
> What do you mean, *after* ?
Oops. I'm still learning this, and think I got confused writing this
so late last night.
>> A
Am 02.04.2011 21:00, schrieb Alex:
>> Fix your client to properly use TLS AND THEN SASL.
>
> I'm using the K9 client for Android. Using this method with TLS and
> SASL I need port 25 open for SMTP and TLS, and 587 for submission and
> SASL, correct?
i believe you need some clarify
SASL-Auth and
On 04/02/2011 09:00 PM, Alex wrote:
I'm using the K9 client for Android. Using this method with TLS and
SASL I need port 25 open for SMTP and TLS, and 587 for submission and
SASL, correct?
Um.. no.
Submission can be done over port 25 or 587, and can use TLS or SASL, or
both, or neither.
Hi,
>>> Apr 2 01:03:55 fc14 postfix/smtpd[10284]: NOQUEUE: reject: RCPT from
>>> unknown[184.XXX.XX.223]: 553 5.7.1: Sender
>>> address rejected: not owned by user alex; from=
>>> to= proto=ESMTP
>>> helo=<184-XXX-XXX-223.pools.mycellphone.net>
>>
>> You're not authenticated.
Okay, I think I ha
On 04/02/2011 09:50 PM, Alex wrote:
Okay, I think I have it working correctly now. I believe my mistake
was with using the incorrect ports for authentication.
Authentication doesn't have a "port" - it is an integral part of the
SMTP protocol.
I think I may
not fully understand the logic be
Am 02.04.2011 21:58, schrieb Jeroen Geilman:
> On 04/02/2011 09:50 PM, Alex wrote:
>
>> Okay, I think I have it working correctly now. I believe my mistake
>> was with using the incorrect ports for authentication.
>
> Authentication doesn't have a "port" - it is an integral part of the SMTP
>
On 04/02/2011 10:11 PM, Reindl Harald wrote:
Am 02.04.2011 21:58, schrieb Jeroen Geilman:
On 04/02/2011 09:50 PM, Alex wrote:
Okay, I think I have it working correctly now. I believe my mistake
was with using the incorrect ports for authentication.
Authentication doesn't ha
Am 02.04.2011 23:17, schrieb Jeroen Geilman:
> I see Mr Reindl is butting his big mouth in again
is your toilet broken or why is your neck so big?
> I "should" do nothing.
YOU can do waht you want, but do not recommend others wrong things
> If the OP is running normal SMTP on port 25, then TL
Mark Alan:
> We will now try the following transport settings (based on a
> recent Wietse sugestion):
>
> slow unix - - - - - smtp
> -o syslog_name=postfix-slow
> -o default_destination_rate_delay=1s
> -o default_destination_recipient_limit=20
> -o smtp_
1)What are the types of emails in postfix queue that would be set to
MAILER-DAEMON? Is it all undeliverable mails? Or we can add
in extra criteria to set incoming mails to MAILER-DAEMON (& how)?
2)I think it takes several hours currently to set undeliverable mails to
MAILER-DAEMON. Wher
On 4/2/2011 10:13 PM, Roger Goh wrote:
1)What are the types of emails in postfix queue that would be set to
MAILER-DAEMON? Is it all undeliverable mails? Or we can add
in extra criteria to set incoming mails to MAILER-DAEMON (& how)?
2)I think it takes several hours currently to set u
14 matches
Mail list logo
