On Tue, Oct 13, 2015 at 10:15:27PM -0500, John Griessen wrote:
> I want to use my server and postfix now for smtp sending, since my isp is
> limiting sends.
>
> All the contents of main.cf, master.cf and some of the server logs during
> tests with thunderbird are in a paste site with no ads here
I want to use my server and postfix now for smtp sending, since my isp is
limiting sends.
All the contents of main.cf, master.cf and some of the server logs during
tests with thunderbird are in a paste site with no ads here:
https://pastee.org/pr7p7
Thanks for any hints...
John Griessen
On Tue, Oct 13, 2015 at 10:53:47PM +, Kevin Miller wrote:
> I need to set up a server so that any mail to/from a specific domain
> (Alaska.gov - external to us) is using mandatory TLS. The server is a
> mail gateway - it doesn't have any local mailboxes and acts as a virus/spam
> filter relay
I need to set up a server so that any mail to/from a specific domain
(Alaska.gov - external to us) is using mandatory TLS. The server is a mail
gateway - it doesn't have any local mailboxes and acts as a virus/spam filter
relay to internal mail servers.
In main.cf,
smtpd_use_tls=yes
smtpd_tl
I've been using postfix to serve emails, but sending via my isp for a long time
and want to
use my server and postfix now since the isp is limiting sends.
Is there any better tool than using thunderbird and the server logs?
I've put all the contents of main.cf, master.cf and some of the server
(I've wrestled with subscribing to the group, apologies in advance if
four different versions of this message all appear together...)
I'm using spamassassin together with postfix, as a milter. This is
Ubuntu 14.04, standard packages.
I was keeping a single Bayesian database for all users, but wou
On Mon, October 12, 2015 7:07 am, @lbutlr wrote:
> On Oct 11, 2015, at 5:51 AM, Voytek wrote:
> I’m guessing not.
> Please do not try to obfuscate your domains by using other people’s
> domains.
>
> Example.com, example.net, and example.org exist precisely for this
> purpose.
sorry, my bad. goin
On 10/13/15 14:26, Noel Jones wrote:
> On 10/13/2015 10:43 AM, Phil Stracchino wrote:
>> Of *course*, it figures that right now there are no false positives in
>> my quarantine that I can test with, only valid spam hits that I don't
>> want to retrain as FPs... so I can't retest until a new FP com
Phil Stracchino:
> On 10/13/15 12:04, Viktor Dukhovni wrote:
> >
> > The local(8) delivery agent is processing a message with an invalid
> > (non-printable) recipient.
>
> Could it be the case that the recipient is unprintable because it was
> originally processed and quarantined by dspam when sm
On 10/13/2015 10:43 AM, Phil Stracchino wrote:
> On 10/13/15 11:29, Phil Stracchino wrote:
>> On 10/13/15 11:10, Wietse Venema wrote:
>>> k...@rice.edu:
Hi Phil,
You are running postfix v3 and it appears that its UTF-8 support has a
problem with how DSPAM delivers messages. Can
On 10/13/15 12:40, Viktor Dukhovni wrote:
> Keep in mind that wildcard virtual(5) aliases can also break
> recipient validation. Any "@domain" keys in the tables for alias_maps
> or virtual_alias_maps?
Nope, none. There are @domain keys in relay-recipients, but they are
all for domains I do not
On Tue, Oct 13, 2015 at 12:29:54PM -0400, Phil Stracchino wrote:
> > Yes, but the question is why your MTA would have accepted such a
> > recipient. Recipient validation would normally reject non-existent
> > users whether UTF-8 or ASCII. Have you disabled recipient validation,
> > or created a
On 10/13/15 12:10, Viktor Dukhovni wrote:
> On Tue, Oct 13, 2015 at 12:07:44PM -0400, Phil Stracchino wrote:
>
>> On 10/13/15 12:04, Viktor Dukhovni wrote:
>>>
>>> The local(8) delivery agent is processing a message with an invalid
>>> (non-printable) recipient.
>>
>> Could it be the case that the
On Tue, Oct 13, 2015 at 12:07:44PM -0400, Phil Stracchino wrote:
> On 10/13/15 12:04, Viktor Dukhovni wrote:
> >
> > The local(8) delivery agent is processing a message with an invalid
> > (non-printable) recipient.
>
> Could it be the case that the recipient is unprintable because it was
> orig
On 10/13/15 12:04, Viktor Dukhovni wrote:
>
> The local(8) delivery agent is processing a message with an invalid
> (non-printable) recipient.
Could it be the case that the recipient is unprintable because it was
originally processed and quarantined by dspam when smtputf8 was active?
--
Phil
On Tue, Oct 13, 2015 at 11:55:16AM -0400, Phil Stracchino wrote:
> > That release also has no smtputf8 support, so it is difficult to
> > see why that might be better than 3.0.x with smtputf8 disabled.
>
> You make a good, but mystifying, point if smtputf8 was not
> supported in 2.11, and re
On Tue, Oct 13, 2015 at 11:51:50AM -0400, Phil Stracchino wrote:
> Oct 3 14:48:23 epsilon3 postfix/smtpd[7639]: connect from
> localhost[127.0.0.1]
> Oct 3 14:48:23 epsilon3 dspam[7638]: Got error 500 in response to RCPT
> TO: 500 5.5.2 Error: bad UTF-8 syntax^M
> Oct 3 14:48:23 epsilon3 postfi
On 10/13/15 11:33, Viktor Dukhovni wrote:
> On Tue, Oct 13, 2015 at 11:29:03AM -0400, Phil Stracchino wrote:
>> I'll try downgrading the main mail server to 2.x and see if that works.
>
> That release also has no smtputf8 support, so it is difficult to
> see why that might be better than 3.0.x wit
On 10/13/15 11:34, Wietse Venema wrote:
> Phil Stracchino:
>> On 10/13/15 11:10, Wietse Venema wrote:
>>> k...@rice.edu:
Hi Phil,
You are running postfix v3 and it appears that its UTF-8 support has a
problem with how DSPAM delivers messages. Can you try downgrading to
v2.x
On 10/13/15 11:29, Phil Stracchino wrote:
> On 10/13/15 11:10, Wietse Venema wrote:
>> k...@rice.edu:
>>> Hi Phil,
>>>
>>> You are running postfix v3 and it appears that its UTF-8 support has a
>>> problem with how DSPAM delivers messages. Can you try downgrading to
>>> v2.x and see if you still ha
Phil Stracchino:
> On 10/13/15 11:10, Wietse Venema wrote:
> > k...@rice.edu:
> >> Hi Phil,
> >>
> >> You are running postfix v3 and it appears that its UTF-8 support has a
> >> problem with how DSPAM delivers messages. Can you try downgrading to
> >> v2.x and see if you still have the problem. We
On Tue, Oct 13, 2015 at 11:29:03AM -0400, Phil Stracchino wrote:
> I already tried that, but when I disabled smtputf8, I lost the ability
> to retrain misses. It appears smtputf8 is a requirement.
You must be mistaken. The only plausible issue is smtputf8 messages
already in the queue, I don't
On 10/13/15 11:10, Wietse Venema wrote:
> k...@rice.edu:
>> Hi Phil,
>>
>> You are running postfix v3 and it appears that its UTF-8 support has a
>> problem with how DSPAM delivers messages. Can you try downgrading to
>> v2.x and see if you still have the problem. We are using 2.x here without
>> a
k...@rice.edu:
> Hi Phil,
>
> You are running postfix v3 and it appears that its UTF-8 support has a
> problem with how DSPAM delivers messages. Can you try downgrading to
> v2.x and see if you still have the problem. We are using 2.x here without
> an issue.
Or you could just set
smtputf8_enabl
On Tue, Oct 13, 2015 at 10:12:52AM -0400, Phil Stracchino wrote:
> I use DSpam with Postfix, and it works well ... except that some time
> back, redelivery of false positives stopped working. I'm not precisely
> certain when it stopped working.
>
> This is the error that is logged on a redelive
On 10/13/2015 1:01 AM, Christian Kivalo wrote:
> Hi,
>
> On 2015-10-13 05:22, Richard B. Pyne wrote:
>> I am running postfix 2.10.1, dovecot 2.2.10, with postfixadmin and
>> maia mailguard.
>>
>> I am trying to figure out how to disable the HELO/EHLO
>> reject_non_fqdn_hostname on the submission p
I use DSpam with Postfix, and it works well ... except that some time
back, redelivery of false positives stopped working. I'm not precisely
certain when it stopped working.
This is the error that is logged on a redelivery attempt:
==> mail.log <==
Oct 3 14:48:23 epsilon3 postfix/smtpd[7639]
Fredrik Sandstr?m:
[ Charset ISO-8859-1 converted... ]
> What's up with this? The result of the probe is "deliverable", but
> postfix rejects the message with a 450 code.
>
> Oct 13 11:12:52 smtp5 postfix/smtpd[5261]: connect from
> mail-vk0-f43.google.com[209.85.213.43]
> Oct 13 11:12:52 smtp
What's up with this? The result of the probe is "deliverable", but
postfix rejects the message with a 450 code.
Oct 13 11:12:52 smtp5 postfix/smtpd[5261]: connect from
mail-vk0-f43.google.com[209.85.213.43]
Oct 13 11:12:52 smtp5 postfix/cleanup[5012]: AC5E08029F:
message-id=<20151013081252.
On 13/10/15 04:41, Viktor Dukhovni wrote:
> On Tue, Oct 13, 2015 at 02:11:59AM +0100, niya levi wrote:
>
>> I can connect to smtpd and SASL with TLS on port 25,
>> but port 587 only responds with connected, then hangs
>> for a while, then quits without any certificate activity.
>> Is my submissio
30 matches
Mail list logo