mlmmj.mlmmj.org archive mirror
 help / color / mirror / Atom feed
From: "Christian Gleerup" <cromozon@swn.nu>
To: mlmmj@mlmmj.org
Subject: Re[3]: [mlmmj] Configuration problems using mlmmj+postfix
Date: Wed, 25 Nov 2015 09:59:38 +0000	[thread overview]
Message-ID: <db178b5cd12436fb253fe745e57f0310@swn.nu> (raw)

Hi again list,

There still seems to be a problem,
Now I have a doubt if the server receives the mail at all and the errors was all from old mailqueue that I copied from the old server?

any hint on what I should look at besided DNS/MX-records?


-----Original Message----- 
> From: "Christian Gleerup" <cromozon@swn.nu> 
> To: mlmmj@mlmmj.org, "Morten Shearman Kirkegaard" <moki@fabletech.com> 
> Date: 24/11/2015 14:48 
> Subject: Re[2]: [mlmmj] Configuration problems using mlmmj+postfix 
> 
> Morten and Piotr
> 
> I have updated and deleted the emails, now the 'editor' just need to write a new newsletter and see if it is send out.
> 
> thank you both for you help.
> 
> Kind Regards
> Christian Gleerup
> 
> 
> -----Original Message----- 
> > From: "Morten Shearman Kirkegaard" <moki@fabletech.com> 
> > To: mlmmj@mlmmj.org 
> > Date: 24/11/2015 13:48 
> > Subject: Re: [mlmmj] Configuration problems using mlmmj+postfix 
> > 
> > On 2015-11-24 at 08:45:07 +0100, Christian Gleerup wrote:
> > > you are right, the port is overridden in
> > > 
> > > /etc/mlmmj/nyhedsbrev/control/smtpport
> > > 
> > > the old server must have listened to port 10025.
> > > would you recomend me just changing it to 25?
> > 
> > Yes, and you can do that by just removing the "smtpport" file.
> > 
> > > should I just empty the /var/spool/mlmmj/nyhedsbrev/queue using the
> > > commandline or should i use some mlmmj command?
> > 
> > The command line is fine.
> > 
> > Kind regards,
> > Morten
> > 
> > 
> > 
> >



                 reply	other threads:[~2015-11-25  9:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=db178b5cd12436fb253fe745e57f0310@swn.nu \
    --to=cromozon@swn.nu \
    --cc=mlmmj@mlmmj.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).