[BlueOnyx:26495] Re: POP sent to IMAP sent

[Michael Stauber via Blueonyx]

Hi Meaulnes,


okaaay, me old man will comply and use the /en vogue/ IMAP 


That's the spirit! :o)

--
With best regards

Michael Stauber
___
Blueonyx mailing list
Blueonyx@mail.blueonyx.it
http://mail.blueonyx.it/mailman/listinfo/blueonyx

[BlueOnyx:26494] Re: POP sent to IMAP sent

[Meaulnes Legler @ MailList via Blueonyx]

thank you all

okaaay, me old man will comply and use the /en vogue/ IMAP 

best regards

で⊃ Meaulnes Legler
Zurich, Switzerland
+41¦0 44 260-1660

On 19.09.23 06:14, Michael Stauber via Blueonyx wrote:

Hi Meaulnes,


I guess all of you guys use IMAP on all of your computers, so you don't have 
this problem... I was looking for a solution for fetching my Sent folder 
contents automatically from my office desktop computer to the remote Sent 
folder on the server.


Like Taco and Chris have already mentioned: This day and age IMAP is really the 
best choice if you want to use the same account on multiple devices AND have 
all emails (sent and received) accessible everywhere.

I was in the same boat many years ago and was still using POP3 on an important 
account. Eventually it really became too much of an hassle when using multiple 
devices for checking emails.

Here is what I did: In Thunderbird I disabled the account that was still using POP3 and 
excluded it from being checked. I also renamed it to "usern...@server.com 
(POP3)" to make it really obvious: That's one old one.

Then I recreated the account in Thunderbird (using the same server, username 
and password), but configured it to use IMAP instead.

That way I now had two configurations in the email client for the very same 
account: An active one using IMAP, and a disabled one that used to use POP3 
before it got disabled and was now excluded from regular email checks.

Now there were a few recent messages (and replies of mine) that I wanted to be 
present on the server and accessible via IMAP. So in Thunderbird I selected 
those messages and copied them from the disabled POP3 account to the now active 
IMAP account. Which then uploaded the messages via IMAP to the server. Then I 
set up a sensible folder structure and sorted the messages into the right 
folders.

If there were still a message older than that which I needed? I still had the 
old POP3 account data in Thunderbird and could fetch 'em from there.

So it's really not too much hassle to switch from POP3 to IMAP in the 
email-client. To the contrary: That little discomfort during the switch is 
repaid tenfold from there on.

Also, when you do this: Email clients usually also allow you to configure how 
long they keep messages on the server before deleting them there, or what to do 
with messages after that expiry date. Especially with IMAP (which usually 
leaves emails on the server) you should set up some sensible expunging or 
archiving.

Depending on the accounts typical usage I leave emails on the server for a few 
days or so and then archive them into either an IMAP folder on the server, or a 
local folder on my PC.



___
Blueonyx mailing list
Blueonyx@mail.blueonyx.it
http://mail.blueonyx.it/mailman/listinfo/blueonyx

[BlueOnyx:26493] Re: The Postfix learning curve continues

[Michael Stauber via Blueonyx]

Hi Chad,

I'm resurfacing an issue from about a month ago, on my transition to 
Postfix.  I've simply not had the time to worry about my internal stuff 
not working, until now.


Your original recommendation was:

"Change your "mynetworks" line in /etc/postfix/main.cf to something like
this if you want to allow the whole 192.168.0.0/16 network to be able to
relay through it:

mynetworks = 127.0.0.0/8 [::1]/128 192.168.0.0/16

Then restart Postfix and see if that helps:

systemctl restart postfix"

I did this, but find that, when I execute the postfix restart, them 
main.cf gets rewritten


Unfortunately that seems correct. I just checked this part of that 
mechanism and it's not entirely working as intended for that particular 
purpose:


In /etc/postfix/main.cf the line "mynetworks" is reserved and you cannot 
edit it. It will get overwritten on Postfix restarts with the IP 
addresses that you have bound to your server.


The *intended* mechanism for allowing to relay is under "Server 
Management" / "Network Services" / "Email" in the "Advanced" tab.


The idea is to allow all hosts listed in "Relay Email From 
Hosts/Domains/IP Addresses" to relay through your server.


However: In our current Postfix implementation that adds entries to 
/etc/postfix/access like this:


test.smd.net   RELAY

But if "Enable SMTP Auth" is active, that then trips Saslauthd and 
relaying is denied, because the sender didn't authenticate.


You're right: In practical terms the IPs of allowed senders would need 
to go into "mynetworks" instead of stuffing them into 
/etc/postfix/access. The issue here is that we've sort of ported the 
Sendmail config to the Postfix config and in Sendmail you can use the 
access file to allow relaying w/o tripping SMTP-Auth. In Postfix it's a 
different story.


The complication is that the GUI field "Relay Email From 
Hosts/Domains/IP Addresses" accepts both IPs and domain names, but the 
"mynetworks" line in Postfix just accepts IPs. So I'll have to throw in 
some extra cogs and wheels to make sure that only IPs end up in the 
"mynetworks" line. But this is doable.


I'll play around with it tomorrow and will see if I can work this out 
and then we'll have a YUM update ready to fix this in the next few days.


--
With best regards

Michael Stauber
___
Blueonyx mailing list
Blueonyx@mail.blueonyx.it
http://mail.blueonyx.it/mailman/listinfo/blueonyx

[BlueOnyx:26492] Re: The Postfix learning curve continues

[Chad Bersche via Blueonyx]

Hi Michael.

I'm resurfacing an issue from about a month ago, on my transition to 
Postfix.  I've simply not had the time to worry about my internal stuff 
not working, until now.


Your original recommendation was:

"Change your "mynetworks" line in /etc/postfix/main.cf to something like
this if you want to allow the whole 192.168.0.0/16 network to be able to
relay through it:

mynetworks = 127.0.0.0/8 [::1]/128 192.168.0.0/16

Then restart Postfix and see if that helps:

systemctl restart postfix"


I did this, but find that, when I execute the postfix restart, them 
main.cf gets rewritten, and mynetworks is updated to:


mynetworks = 127.0.0.0/8 127.0.0.1/32 [::1]/128 192.168.0.212/32 
192.168.0.213/32 192.168.0.214/32


the 192*/32 address correlate to the vSites that I have configured.  I'm 
not sure how I can prevent this from getting overwritten, as when I did 
add the 192.168.0.0/16, it was removed, and replaced as I showed above.


Hoping to get this all working, now that I have a bit more time to 
dedicate to it.


Thanks!

  -- Chad


___
Blueonyx mailing list
Blueonyx@mail.blueonyx.it
http://mail.blueonyx.it/mailman/listinfo/blueonyx

[BlueOnyx:26491] Re: Postfix stopping and starting - and trying to run Sendmail

[Michael Stauber via Blueonyx]

Hi Neil,

Having seen the other thread about mail problems, I've done the yum 
re-update that you recommended.


However, I'm seeing

  server1 postfix/master[103392]: terminating on signal 15

every 2 minutes then a little while later:

server1 postfix/postfix-script[103598]: starting the Postfix mail system

Sep 20 20:34:04 server1 systemd[1]: sendmail.service: start
operation timed out. Terminating.

Sep 20 20:34:19 server1 systemd[1]: Starting Sendmail Mail Transport
Agent...


Your server seems to be unsure if it has Sendmail of Postfix enabled. 
Only one of them should be running. Please go to "Server Management" / 
"Network Services" / "Email" in your BlueOnyx GUI and see what you have 
configured as "SMTP Server". Change it to the MTA you want to use and 
hit save.


That should then stop and disable the MTA that ought to be off and will 
enable and start the MTA that should be running. I recommend using Postfix.


(PS Sorry if this arrives multiple times: I'm seeing a "Soft Bounce" 550 
5.7.1 Rejected: 185.41.28.109 listed at rbl.solarspeed.info 
 from my mail server waterend.net 
!)


rbl.solarspeed.info is my own RBL server into which I feed IPs and IP 
address ranges that sent me SPAM, or which have other observed bad 
behaviour such as brute force attacks. Most of my servers are using it - 
including this list-server. I just checked and for one reason or other I 
had the whole 185.41.28.0/22 (AS200484) address range blocked.


I just removed that block, although it might take a moment until it has 
propagated to all my DNS servers.


If you need any further help with your MTA issue, please file a "Support 
Request" via the BlueOnyx GUI and tick the checkbox "Allow access", so 
that I can take a look.


--
With best regards

Michael Stauber
___
Blueonyx mailing list
Blueonyx@mail.blueonyx.it
http://mail.blueonyx.it/mailman/listinfo/blueonyx

[BlueOnyx:26490] Postfix stopping and starting - and trying to run Sendmail

[Neil Watson via Blueonyx]

Hi (trying again now I've joined the mailing list as this email)

Having seen the other thread about mail problems, I've done the yum
re-update that you recommended.

However, I'm seeing

 server1 postfix/master[103392]: terminating on signal 15


every 2 minutes then a little while later:

server1 postfix/postfix-script[103598]: starting the Postfix mail system

server1 postfix/master[103600]: daemon started -- version 3.5.2,
configuration /etc/postfix

Also, despite being set for using Postfix, it seems to be trying to start
Sendmail - which fails

 server1 systemd[1]: Starting Sendmail Mail
Transport Agent...

Sep 20 20:32:34 server1 systemd[1]: sendmail.service: Can't open PID file
/run/sendmail.pid (yet?) after start: No such file or directory

Sep 20 20:34:04 server1 systemd[1]: sendmail.service: start operation timed
out. Terminating.

Sep 20 20:34:04 server1 systemd[1]: sendmail.service: Failed with result
'timeout'.

Sep 20 20:34:04 server1 systemd[1]: Failed to start Sendmail Mail Transport
Agent.

Sep 20 20:34:04 server1 systemd[1]: Dependency failed for Sendmail Mail
Transport Client.

Sep 20 20:34:04 server1 systemd[1]: sm-client.service: Job
sm-client.service/start failed with result 'dependency'.

Sep 20 20:34:04 server1 sauce_serviced[1137]: Daemon.pm: /usr/bin/systemctl
restart sendmail.service: Transaction failed with exit code 256

Sep 20 20:34:19 server1 systemd[1]: Starting Sendmail Mail Transport
Agent...

Sep 20 20:34:19 server1 systemd[1]: sendmail.service: Can't open PID file
/run/sendmail.pid (yet?) after start: No such file or directory


It is looking very confused!

BO 3210R

Best regards

Neil.

(PS Sorry if this arrives multiple times: I'm seeing a "Soft Bounce" 550
5.7.1 Rejected: 185.41.28.109 listed at rbl.solarspeed.info from my mail
server waterend.net!)
___
Blueonyx mailing list
Blueonyx@mail.blueonyx.it
http://mail.blueonyx.it/mailman/listinfo/blueonyx