Re: Inbox and Sent messages in one thread. How To?
On 06Dec13 13:57 +0100, Suvayu Ali wrote: > On Thu, Dec 05, 2013 at 08:21:00PM -0500, Patrick Shanahan wrote: > > * Kirill Tkhai [12-05-13 20:05]: > > > I want to have a posibility to see inbox and sent messages together in > > > one thread. Is this possible without copying content of Sent folder to > > > Inbox? > > > > Leave the "sent" msgs in the inbox > > > > or insteadof "saving" outgoing post, copy them to the "Sent" directory and > > the original will remain in your inbox. > > > > If you do not want a copy of the "Sent" mail in your inbox, I believe you > > are outtaluck. mutt alone cannot deal with this, afaik. Mairix can help out here. It supports a search modus for e.g. the message-id of a mail. This normally returns a single mail, but adding the --threads switch also returns all mails of the thread this mail is related to. I am using Maildir (no imap, mbox, etc) In this case mairix works pretty efficient, as the search result is presented in a temporary % Maildir containing links to the real Mailfiles. The creation of this folder can be initiated from within mutt (with a look&feel like it is a mutt command). If interested in mairix and its integration into mutt, I could provide my config, which I copied from the net somewhere.
Re: 100,000 messages, and counting.
On 17Feb14 18:50 +, Alan Mackenzie wrote: > My inbox has now reached the grand total of 100,000 messages (_exactly_ > 100,000, coincidentally enough). This is partly a result of me being > subscribed to too many mailing lists, and partly of me not getting > around to clearing things out. mbox or maildir? > (Yes, I know I could do clever things to split incoming messages amongst > several mailboxes, but I don't _want_ to.) I also have just two mailboxes. inbox and trash! That's enough. For sorting/splitting there is mairix (or plain mutt searching) :) I started to use trash as my 2nd level mailbox, because startup of mutt took too long. Because deleting mails rewrote my entire mbox, I switched over to maildir, so no rewriting of the mbox file is necessary. Cheers, Bastian
Re: search in sent
On 27Feb14 07:40 +0100, vwf wrote: > I may make a mistake, but I fail to search in my sent mailbox. > In other mailboxes, by hitting '/' I can search the adress and subject > fields. In sent this does not work. Are there search options I am > unaware of, or is something else the matter? I use Maildir if important. When beeing in search folder, what does ? show? Is there a similar/same binding for / as in your other folders? Like: /search search for a regular expression If not, I suspect you have some hook, which reconfigures your key binding for the sent folder. -- Bastian
Re: mutt's counterpart feature to gmail's archive?
On 16Apr15 00:32 +0200, Quolick wrote: > What is mutt's counterpart feature to gmail's archive? what is used > here? I don't want to delete messages, but I want to have them > locally searchable, like gmail can do. > What is the best practice? Just to move to another folder? Plain and easy and comfortable: I just have two main mailboxes: inbox and trash. Also the fcc is set to inbox so that I can see in threaded view the history of dialogs/threads. To search the mailboxes I use mairix which I invoke inside mutt via a key-bind. Very quick and reliable by now. The most notable benefit for me was to get rid of the trouble how to sort mail into tons of mailboxes. The virtual view of mairix creates a temporary mailbox of of the search results. If there is interest I'll share some config and scripts on the mairix setup. -- Bastian
Re: mutt's counterpart feature to gmail's archive?
On 16Apr15 22:11 +0200, Heinz Diehl wrote: > > Also the fcc is set to inbox so that I can see in threaded view the > > history of dialogs/threads. > > I'm doing virtually the same by specifying > set record="+.INBOX" Exactly. > > To search the mailboxes I use mairix which I invoke inside mutt via a > > key-bind. Very quick and reliable by now. > > > If there is interest I'll share some config and scripts on the mairix > > setup. > > Please go ahead ;-) There are two parts. The key-bind in muttrc and a script, which simply fakes a cmd-line within mutt and executes mairix. Afterwards it automatically switches the folder view to the search results. You can find all the details on how to set it up here: https://pbrisbin.com/posts/mairix/ -- Bastian
Re: Cannot render Spanish accents in builtin pager
On 01Jun15 20:06 -0400, Xu Wang wrote: > I cannot seem to configure mutt such that the builtin pager renders > accents. > > "Todavía" is shown as "TodavM-CM--a" > "También" is shown as "TambiM-CM-)n" Did you compile mutt yourself? I had similar issues and solved this when building against libncursesw5 instead of libncurses5 (note the w for wide, which is utf support afaik) And of course the locale command shows: """ % locale LANG=en_US.UTF-8 LANGUAGE=en_US:en LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= """ Cheers, -- Bastian
Re: Cannot render Spanish accents in builtin pager
On 02Jun15 08:44 -0400, Xu Wang wrote: > This worked. Thank you so much for your help with this. All I had to > do was install libncursesw5-dev and reconfigure mutt and it worked. I > did not have to chance any configure flag. I am happy to hear that. My understanding is that the configure script checks first for ncurses and afterwards for ncursesw. Thus, it will prefer the use of ncursesw over ncurses. > I originally read this: > http://dev.mutt.org/trac/wiki/MuttFaq/Charset > which was helpful (although not very structured), and it mentions > something about about ncurses with wide char support, but I did not > try it because it is listed under > "UTF-8 chars are displayed fine, but the screen is garbled" > which I don't think described my problem. Also, I did not need to > specify "--enable-widec". That configure switch is not available in my branch. > Please let me know if an update is needed to that page and I will make > an account and attempt a change. However, since I do not know anything > about this topic deeply I am hesitant to do anything without further > confirmation. I guess the wiki page is worth updating, with noting the version of mutt. But, I am just a simple mutt user, so I don't feel to en- or even discourage you doing so ;-) Cheers, -- Bastian
Re: saving messages to files/permissions?
On 13Jun15 22:55 -0700, Ian Zimmerman wrote: > On 2015-06-13 21:59 -0700, Tom Fowle wrote: > > Tom> I often save individual incomming emails in seperate files in my > Tom> home directory with the mutt "s" command. In any session, the > Tom> first time I save to a particular file it goes fine. However if I > Tom> try to save another message to the same file, I get "Permission > Tom> denied." > > Tom> checking the permission of the file it is -rw- --- --- > > Tom> I can, of course open another console and chmod to correct this > Tom> without leaving mutt, but I don't recall this problem with my > Tom> previously installed old fedora. > > Wait, something is odd here. Are you running mutt as a different user? > If not, why would it have any trouble writing to a file with 0600 > permissions? Those two bits are _user_ read and write, after all. > > I think you should attack this angle before you try to change the > permissions. I think it is worth to solve the trouble of file permissions. FMPOV this behaviour is not typical to unix philosophy, because you cannot influence file modes via the umask syscall. This behaviour also bothered me, even though I use just one UID basically. See below for my reasons to work on it, if interested. > strace may be your friend. Code rules. In my current mutt (Mutt 1.5.23+89 (0255b37be491) (2014-03-12)) I find two locations, where umask and mode bits are set hard-coded, so no way to modify without re-compiling. First, main.c:599 umask (077); This could be set to 022, which also opens other permissions to other users. So you should know if you really want it. Second, lib.c:645 and :657 if ((fd = open (safe_file, flags, 0600)) < 0) Here again, when files are opened in a safe way when writing out attachements, file mode bits are set hard-coded :/ Here you can set 0666 as mode bits. The open syscall also binary-ands (&) the bits from the umask setting, either set them globally to 022 in main.c or - the way I'd propose - change umask before writing out attachements and then reset to the previous one. Finally, here is my trouble with it. I got used to save attachments to ~/public_html/$somewhere to have them available remotely via browser. I always had to chmod a+r manually to enable all users including the web server process to read that files. In addition, these hard-coded umask and file mode bit settings are in the mutt source repositories (see version reference above), so I think the same behaviour should be seen on fedora, but I don't about any patches from their side. Cheers, -- Bastian
Re: Forwarding mail with attachments?
On 15Jun15 08:41 +0100, David Woodfall wrote: > Is there a way of forwarding an email and all attachments too? Attachments are forwarded if you answer 'yes' to 'forwarding as attachment?'. Drawback is, you cannot reply-inline. -- Bastian
Re: saving messages to files/permissions?
On 15Jun15 11:31 +0200, Matthias Apitz wrote: > To the OP: Can you please post here: > > $ ls -ld . > $ ls -l file-to-save-in > $ id In addition: df -T . mutt -v Cheers, -- Bastian
Re: saving messages to files/permissions?
On 17Jun15 12:37 -0500, Derek Martin wrote: > On Sun, Jun 14, 2015 at 09:36:44PM +0200, bastian-muttu...@t6l.de wrote: > > On 13Jun15 22:55 -0700, Ian Zimmerman wrote: > > I think it is worth to solve the trouble of file permissions. FMPOV this > > behaviour is not typical to unix philosophy, because you cannot > > influence file modes via the umask syscall. > > This is wrong. The file permissions are what they are quite > specifically and intentionally for security reasons. If you want to > make the files less secure, you are required to make a conscious > decision on a case-by-case basis, and take action to do so, and that > is as it should be. Right, I want to make files less secure and I really know a lot about the implications. The point where I see room for improvement is the lack of configurability to be able to change the behaviour of writing out attachment files - not mailbox files. Everything tends to be configurable in mutt. Whereas, hard-coding umask and file mode bits does not look like the ultimate mutt-like solution FMPOV. > This issue has been discussed and debated ad nauseum in the past, and > this is one of those cases where the developers should do (and have > done) what is right without regard to what the users want, because > what the users want is simply just plain wrong--but they've proven too > difficult to be convinced of that. I'm not going to rehash the > argument here; if you search the archives, you should find the > discussion. > > Whether anyone likes it or not, the fact is that when it comes to > software security, most users--and even a large portion of the > developers--just don't have any idea what they are talking about, and > to some extent people who know better need to make the decision for > them to prevent the possibility of bad things happening on a > wide-spread basis. This is one of those cases--the small > inconvenience of having to manually change the permissions is VASTLY > outweighed by the harm that could be done by allowing for the file > permissions to be less restrictive by default. I can still survive while doing that. But I have to admit, I do not get the clue, why I should want my attachment files to be handled in an imposed and uninfluenceable 'top-secret' manner. All other files I work with in the same 'classification level' are created with the umask setting I chose in .profile. > However, it would be good to document this somewhere, since it's come > up more than once. Cheers, -- Bastian
mutt mail archives
The mutt homepage [1] links to the mutt mailing list archives for -users [2] and -dev [3]. Both are not reachable (at least right now). 1: http://www.mutt.org/mail-lists.html 2: http://marc.theaimsgroup.com/?l=mutt-users 3: http://marc.theaimsgroup.com/?l=mutt-dev The domain marc.theaimsgroup.com seems not to be resolvable anymore. Are there any other archives available? Cheers, -- Bastian
Re: Move old messages
On 27Nov15 15:18 +0200, Danny wrote: > How can I have Mutt move messages (to another folder) automatically after 5 > days when I go into a > folder? > > I am subscribed to many mailing lists and like to keep old messages for > archival > purposes. However, after a few days these folders are getting just too big. > > For example: When I open up the FreeBSD folder I want Mutt to automatically > move > the older messages to FreeBSD-OLD folder. I did achieved a similar goal with: folder-hook .folder push 'D~d>365d Deletes messages which date is >356 days. So yours might be: folder-hook .FreeBSD push 'T~s>5d;s.FreeBSD-OLD Use that with caution, its a draft and untested. But should give you an idea. Cheers, -- Bastian
Re: Move old messages
On 27Nov15 16:33 +0200, Danny wrote: > O.k ... I tried various combinations but it does not seem to work > > folder-hook .FreeBSD push 'T~s>5d;s/incoming/os/bsd/FreeBSD-OLD > is > what I tried last ... Right. Of course I inserted some typo. ~s is the metachar for the subject of the mail. Try it with a ~d which corresponds to the date received. folder-hook .FreeBSD push 'T~d>5d;s/incoming/os/bsd/FreeBSD-OLD Watch out: The first argument to folder-hook is a regexpr. So be careful with that. .FreeBSD will (most probably) match both of your mailboxes FreeBSD and FreeBSD-OLD. Better try first: folder-hook FreeBSD$ push 'T~d>5d;s/incoming/os/bsd/FreeBSD-OLD Here, the '$' marks the end of a line, thus the folder FreeBSD-OLD will not be matched. Cheers, -- Bastian
Re: Move old messages
> One thought, if I'm away for a week or more this would archive several > days of unread mail. Adding a simple ~R to the pattern seems to > eliminate this concern. Are there any side-effects I overlook? > > folder-hook FreeBSD$ push > 'T~R~d>5d;s/incoming/os/bsd/FreeBSD-OLD What I can tell you about the regex criteria is that ~R and ~d are and'ed together. From that knowledge your pattern looks ok. -- Bastian
Re: Move old messages
Hey Danny, for mailing lists please try to use inline responses. Keep the referenced mail on top and just as much as it gives enough context to understand the discussion by other readers whi might not have seen the original one. Find more in rfc1855 [1] 1: http://www.ietf.org/rfc/rfc1855.txt On 28Nov15 09:55 +0200, Danny wrote: > O.k ... The messages older than 5 days gets tagged but not moved to the > archived > folder ... I was wondering about your /incoming root folder. > The mails gets put into ~/mail/incoming/operating_systems/FreeBSD (by > procmail) > ... the folder I want it to go to is > ~/mail/incoming/archived/freebsd/freeBSD-Archived ... > > I think I am getting the paths wrong ... Please somebody correct me, mutt uses the 'folder' variable which points to the root of your mailboxes. Which mailbox type do you use, btw? According to what I know from your mails, make sure to set folder = '~/mail' Later on, you can use '=' which expands to that path, e.g.: folder-hook FreeBSD$ push 'T~d>5d;s=incoming/os/bsd/FreeBSD-OLD will save to a folder in ~/mail/incoming/os/bsd/FreeBSD-OLD Also make sure that the folder already exists, otherwise mutt will ask to create it. Additional remark: The tagged and saved mails are not purged immediately from you FreeBSD mailbox. They are marked with D and will be purged as soon as you save the mailbox. Cheers, -- Bastian
Re: Move old messages
> > Later on, you can use '=' which expands to that path, e.g.: > > > > folder-hook FreeBSD$ push > > 'T~d>5d;s=incoming/os/bsd/FreeBSD-OLD > > > > will save to a folder in ~/mail/incoming/os/bsd/FreeBSD-OLD > > I undestand this ... the messages are currently tagged "*" ... so that seems > to > be fine ... my problem is that I am NOT getting to the "D" stage ... I have > tried the "=" but still nothing ... I don't see any mistake here. The part that tags the mails seems to work: T~d>5d The second part should run the save-message command (s) on all tagges messages (;) to the mbox named (=...): ;s= Maybe you have bound the s key to another function? I would try that manually and see what happens step by step. -- Bastian
Re: sending mails readable on small screens
On 30Nov15 15:44 +, Samir Benmendil wrote: > On Nov 29, 2015 at 19:42, Matthias Apitz wrote: > >El d?a Sunday, November 29, 2015 a las 05:55:32PM +0100, Bernard Massot > >escribi?: > >>I'm struggling to build mails readable on small screens, ie mails whose > >>lines wrap correctly even when there are few columns. I'm indeed > >>thinking of smart phones. > >> > >>I thought format=flowed would be the answer. However the first mailer I > >>tried – K9 mail – doesn't support f=f. I guess Android's native app is > >>no better. So f=f isn't the universal solution. > >Your mail renders fine in my Ubuntu mobile phone BQ E4.5, in Dekko and in > >mutt, see the screens: > > > >Dekko: http://www.unixarea.de/screenshot20151129_180118205.png > >mutt: http://www.unixarea.de/screenshot20151129_180302430.png f=f seems to be the esoteric way to tackle that problem. All other users just make sure their terminal is at least 80 chars wide. text/plain is just what it is, plain text. No formating meta data in there. One more thing I did not entirely get is, do you intend to reformat all messages you receive or do you want to asure that messages you send will be reformated on the recipents side? Anyway, both approaches won't work, if you ask me. There are too many MTAs out there which all behave differently when composing, formatting and paging emails. > No it does not: http://rmz.io/ff.png That screen is approx 65 chars wide/narrow. But also I would not count that as not readable. > >>What do you suggest? It seems HTML is the only widely supported format, > >>which doesn't have line wrapping problems. So should I make Mutt > >>creating automatically an HTML part of a multipart/alternative, using an > >>empty HTML page template and wrapping paragraphs in tags? Is there > >>something more clever to do? > >No, please no HTML. > Indeed, please don't use HTML. I sign that, too, but I also think that you are not wrong - given that fact that most MTAs support html paging. > You might have better luck with "quoted-printable". "f=f" is much > nicer though. To my knowledge quopri is an encoding method. I would not say that could solve the problem here. Cheers, -- Bastian
Re: leaking timezone
On 22Mar16 08:40 +1100, Cameron Simpson wrote: > >>TZ=UTC mutt > >Thank you! A most elegant quick solution! > > On the othe hand, I do not think mutt makes the header. The input to my sendmail= script lists a date header. (1.5.24) So, mutt does it I assume. > I'm in compose mode right now with headers and the Date: header is not > there. Wild guess: Date: is added right before sending 'y' ? > This suggests that the mail system may be making yours also. So your > mutt "sendmail=" settings says what to use to dispatch email; if you > make that a tiny shell script which sets TZ and then runs sendmail (or > msmtp or whatever) then you can read email in your local timezone and > have the mail system generate a UTC > Date: header. Further idea: - Use the sendmail= script to modify the date header - Or configure/hack msmtp to rewrite/modify it Cheers, -- Bastian
Re: How do you survive without notmuch?
On 07Apr16 19:53 +0200, Andreas wrote: > Am 07.04.2016 um 01:19 schrieb Cameron Simpson: > > Usually when I reach for notmuch it is because I have mismanaged my > > folders. Hmm, that message about blah isn't there - where is it? Here, just a quick glimpse into my experience. I discovered an easy way of life, at the time I stopped to sort my mails into folders - either manually or automatically. For me it was just one big source of failures. Mails could sometimes be sorted into multiple folders, so where should I look to find that one again? And what the heck is the sent-folder for? It just rips threads apart. This made me change completely my email administration approx a decade ago. Now, I just use two maildirs. inbox and trash. Where trash is more the entire mail history and inbox a kind of todo or active threads. Mails I sent are also put into inbox, thus I can follow threaded discussions much better. To find emails by searching, I begun to use mutt's powerfull limit functionality on the trash. This became quite slow by time and growing mbox. Afer changing to maildir, I also got interested in mail indexers (started with mairix, now maildir-utils) which let me easily and dynamically switch to the context I desire. In addition to that, since using maildir-utils, I use `mu cfind` as my email address book via query_command. So there is no need to add mailaddresses to the alias file any more. By now I cannot imagine any solution which is more flexible (for me). Comments welcome! > Me too and while it does find the message it does not tell me /where/ it > is. How do you do this? I do not precisely know about notmuch, but the indexers I know about they create links to the original mail in a temporary maildir folder. At least follow those links. Actually, to find the location of a mail file grepmail is a nice tool, which I used long time ago. Cheers, -- Bastian
[SPAM?] Re: add the content of another email to new message
On 24Aug16 20:38 +1000, c...@zip.com.au wrote: > On 23Aug2016 19:47, Jethro Tull wrote: > > > On 16Aug2016 19:58, Jethro Tull wrote: > > > >I'm using vim as editor in mutt. I would like to find a way to dump the > > > >content of another email or part to a new message while being composed. > > > >Of > > > >course without running a new instance of mutt. > > > > > > Why not by running a new instance of mutt? > > > > > > Without that, you need some kind of tool that _vim_ can invoke to access > > > message content. How are you intending to designate that message from > > > inside > > > vim? [...] Some more thoughts on this: - If you figure out the filename of the email, from which you want to get some lines, then it could be a problem if that file has content-transfer-encoding = base64 or quopri and not 7bit. Similar issue might be content-type= text/html. And not to forget encrypted Mail. So, I suggest to use mutt to read/edit email in vim, because mutt does some stuff to present the mail in a readable way. - Another solution to gather lines from other mails might be to use mutt and vim's registers. Steps would be: 1. Postpone your mail (as described earlier) 2. Use mutt to find your source mails. In addition, mutt does all the content type/encoding handling when viewing/replying them. 3. Use named registers from vim and yank the precious content into them. 4. Repeat step 3 as much as needed, either with different ragisters or append to one register. 3. Open the postponed mail again and paste our registers. Tadaa .. (For that to work, verify that registers are saved after exiting vim. see :help viminfo.) Cheers, -- Bastian
Re: saved or deleted?
On 31Aug16 10:58 +0200, Gabriel Philippe wrote: > On Wed, Aug 31, 2016 at 8:42 AM, Jon LaBadie wrote: > > Rephrasing, how can I tell if a deleted message has been copied? > > > > Currently, if I am uncertain I have to copy it just in case and > > in the future, delete the duplicate if I created one. > > Not what you want, but if you have mutt with the trash feature, it can > be useful. > > If you have deleted a message, it will be moved to the trash, thus if > you have inadvertently deleted it you can get it back. But if you have > moved it somewhere else, it will not go to the trash. Sometimes I also have that problem to remember which key I pressed and which macro was executed, so I lost track of my mails and I also purged some mails by chance. Honestly, I am also not fully convinced by the $ status. It is not meaningful enough. I'd like to note that when a mail is saved to another *box the status line fickers 'Copying .. something'. I can't read it, its too quick for my local mailbox. Maybe a solution to that problem is to simply not clear the status line. Or even better: Maybe I want to see a log of the current mutt session (in a quake console style), and maybe also keep a real log of what I did ... What do you think? -- Bastian
Re: best practices answering multiple mails (at once?)
On 08Nov16 19:47 +0100, Simon Ruderich wrote: > > Hey Simon, your mail is exactly what saved me. I never noticed the ';' > > entry in the index help screen, and for one reason or another i had > > never had the need to operate on tagged messages until tonight, in > > long time i use mutt. So i was trying replying to multiple messages > > just tagging them and answering, which of course was not working. > > Yeah. Tagging is also really useful when moving and deleting > multiple mails. If you are new to tags, give <{tag,delete}-pattern> functions (default bound to keys T, D) a try. These are pretty helpful for me. -- Bastian
Re: Are there any good/recommended address book add-ons for mutt other than abook?
On 30Jan17 17:57 +0100, Peter P. wrote: > * Chris Green [2017-01-27 10:13]: > > On Thu, Jan 26, 2017 at 08:46:02PM -0200, Marcelo Laia wrote: > > > On 26/01/17 at 04:28, Chris Green wrote: > > > > Does anyone here use an address book for mutt other than abook? I use the maildir-utils "mu" as a mail indexer. That tool also creates a database of all email contacts found and as such it is kind of a address book. It integrates well into mutt's address completion function (pressing CTRL-T): set query_command="mu cfind --format mutt-ab %s" Good thing: You don't have to manually fill your email address book. It is all in the mailboxes Drawback: I haven't found an easy way to remove/modify entries, besides directly editing the email and the address book DB (which is ascii). But that was necessary just one time in four years I use mu. Cheers, -- Bastian
Re: dev.mutt.org is down again
On 11Jun17 10:57 -0400, Jack M wrote: > Anybody else notice that dev.mutt.org is not responding? Safari gives up and > says the server won't respond. Running "Traceroute" in macOS's Network > Utility.app shows a stall-out (or something) after the IP address > 137.82.233.53. dev.mutt.org is in maintenance over the weekend. This was announced on mutt-dev, though [1]. 1: http://marc.info/?l=mutt-dev&m=149704469016375&w=2 Cheers, -- Bastian
Re: [Mutt] Is linewrap dead? Now: Self hosted SMTP
On 12Sep22 21:07+0200, Mihai Lazarescu wrote: > Given the cheap VPS, I can mirror the setup on a second VPS from a different > provider with quick DNS switch in case of issues. I just did that approx half a year ago. Before, everything was rolling just fine (for more than 10 yrs). No dead ends of my outgoing mails. After transferring the domain over to the new hoster, some destinations did not receive my mails. Either filtered into spam, some got denied (where I got a nice SMTP error reply) and some just got silently dropped. This took me some time to figure out with each destination, why is that happening. And sometimes also just guessing. At least the mail-tester.com rate is 10/10, so it is not about my setup per se. The IP and/or subnet my VPS was in had a bad reputation at some denylist services. Question was then, how to get removed from them. Sometimes via automated forms and sometimes through personal mail-conversation with other mail operators (t-online.de was very nice and responsive to my surprise). For now, it seems fine again. And I would regret it to 'throw in the towel' because of that; but to be honest, I thought about that. After this experience there need to be very strong reasons to change my hoster again, meaning to change my IP/subnet again. Cheers, -- Bastian