On Thu, Jan 28, 2021 at 09:51:57PM +, Stuart Henderson wrote:
Not 100% sure but I think you can just edit it in the template file.
But unless you've got a properly configured mail setup on the machine
saving it as a text file is probably easier.
Editing it in the template file did the trick
On Thu, Jan 28, 2021 at 05:30:47PM +0100, Marcus MERIGHI wrote:
2. Where can I find the message that 'sendbug' composed? 'ls
/var/spool/smtpd/queue/*' does not show any messages in any of the
subfolders, did smtpd delete it because it couldn't be delivered?
Do you see
smtpd[30872]: warn: queue
On Thu, Jan 28, 2021 at 05:30:07PM -, Stuart Henderson wrote:
You could use "sendbug -P > sendbug.out" to get your report in a file
and send that from a different host. Or edit the file and
$ cat sendbug.out | mail -s "my bug report" -r my_lap...@domain.com \
-c my_lap...@domain.com
On Thu, Jan 28, 2021 at 08:41:46PM +0100, Radek wrote:
> Hi,
> a few days ago all my boxes using the same ISP stopped to send me emails from
> local users and daemons (daily outputs and any other cronjob reports) to
> @gmail.com.
> I have tried to send email to a few not_gmail mailboxes - the sa
On 2021/01/28 18:55, tetrahe...@danwin1210.me wrote:
> On Thu, Jan 28, 2021 at 05:30:07PM -, Stuart Henderson wrote:
> > > You could use "sendbug -P > sendbug.out" to get your report in a file
> > > and send that from a different host. Or edit the file and
> > >
> > > $ cat sendbug.out | mail
Hi,
a few days ago all my boxes using the same ISP stopped to send me emails from
local users and daemons (daily outputs and any other cronjob reports) to
@gmail.com.
I have tried to send email to a few not_gmail mailboxes - the same problem.
If i send emails from other boxes (using other ISP),
On Thu, Jan 28, 2021 at 03:25:46PM +, Marek Klein wrote:
> > On Wed, Jan 27, 2021 at 08:39:46AM +0100, Otto Moerbeek wrote:
> >
> > > On Tue, Jan 26, 2021 at 04:08:40PM +, Marek Klein wrote:
> > >
> > > > Hi,
> > > >
> > > > We are working on an appliance like product that is based on Ope
I'm trying to set up my system so I can use 'sendbug' to send in a bug
report for a kernel panic, and a number of issues have cropped up.
1. My mail provider won't let me send email from but
only from . Therefore I tried adding to ~/.mailrc:
set from "my_lap...@domain.com"
Unfortunate
On 2021-01-28, Marcus MERIGHI wrote:
> Hello,
>
> tetrahe...@danwin1210.me (tetrahe...@danwin1210.me), 2021.01.28 (Thu) 16:00
> (CET):
>> I'm trying to set up my system so I can use 'sendbug' to send in a bug
>> report for a kernel panic, and a number of issues have cropped up.
>>
>> 1. My mail
Hello,
tetrahe...@danwin1210.me (tetrahe...@danwin1210.me), 2021.01.28 (Thu) 16:00
(CET):
> I'm trying to set up my system so I can use 'sendbug' to send in a bug
> report for a kernel panic, and a number of issues have cropped up.
>
> 1. My mail provider won't let me send email from but only
On Thu, Jan 28, 2021 at 02:51:33PM +0100, open...@kene.nu wrote:
> In my case MED is changed with + on every eBGP hop. I use it to
> calculate the total MED over several hops to decide the best path from a
> latency point of view.
>
> My intention with listing the advertised prefix from R1 was to
In my case MED is changed with + on every eBGP hop. I use it to
calculate the total MED over several hops to decide the best path from a
latency point of view.
My intention with listing the advertised prefix from R1 was to show that
there is a MED present. As per the tcpdump I did, the MED attribu
On Thu, Jan 28, 2021 at 12:41:29PM +0100, open...@kene.nu wrote:
> Hello,
>
> I am experiencing this on 6.8, fully syspatched.
>
> root@R1():~ # uname -a
> OpenBSD R1 6.8 GENERIC.MP#4 amd64
>
> The problem is that R1 sends updates with MED set to 0 even though I expect
> it not to be. Upon revie
Hello,
I am experiencing this on 6.8, fully syspatched.
root@R1():~ # uname -a
OpenBSD R1 6.8 GENERIC.MP#4 amd64
The problem is that R1 sends updates with MED set to 0 even though I expect
it not to be. Upon reviewing a tcpdump pcap taken at R2, the MED attribute
is not even included in said upd
On Wed, Jan 27, 2021 at 11:12 PM vejetaryenvampir wrote:
> I think I was having the same problem when I changed the passphrase
> of my disk. I managed to fix it with installboot(8). You can
> access the bug report in here:
> https://marc.info/?l=openbsd-bugs&m=161075212820257&w=2
> I had the pan
15 matches
Mail list logo
