yep

hi!

anyone in here coincidentally in the questions@, ports@ or ports-bugs@ lists? im worried a reply from me hasnt been delivered

you can check the archive

[tj]: i already checked, it gets updated once per week

nah

much faster than that

[tj]: it took a day for me until it appeared on there

and my reply which i sent 12 hours ago still isnt displayed

probably didn't make it

ugh ive had no time to get back to my freebsd project

[tj]: thats why i came here to ask if someone would be nice enough to check their inbox/spam

if it isn't on the archive then it won't have gone out to anyone?

because i thought that with the first reply aswell, but it appeared

latency should be about a minute

what if the message gets moderated first or something

I dunno if we moderate, I wouldn't know who would want to do that

chatgpt

I suspect for newcomers (first few posts to the list), they are moderated.

i see

just sent another one out, doubt its gonna appear within minutes

sorry I'm not sure how to help

i just thouht there might be a possibility it appeared in subscribers inboxes earlier before being displayed in the archives

[tj]: i think i know why it gets delayed

got a warning from my mail provider that "mx66.freebsd.org[2610:1c1:1:606c::19:5]:25: Network is unreachable"

downtime on the other end :/

cool

Maybe check your end.

CrtxReavr: im not hosting my own mailserver

what i can say is that my mails get delivered flawlessly & instantly to openbsd lists

riad: I am in questions@

polarian: maybe you can check if my replies got delivered if you have time so spare, but i kinda doubt it atp

but thanks

I dont know your email

so I cant

riad, That is mx66 which is up and online (but IPv6 only). But mx1 is both IPv4/IPv6 and it is up and online for mail transport. It still seems like there is some mail problem on your end of the mail transport. There are two MX systems available to accept your email from your email service provider.

rwp: is it maybe possible that "bad" ip's are completely rejected?

checking with netcat i get no response at all which makes me think some ip ranges get blocked

but when using a residential proxy i get a response instantly

riad, I don't have any operational knowledge of mx1 or mx66 .freebsd.org but yes it is possible they are blocking by firewall ranges of addresses.

I would say that normally mail relays don't usually block by ranges but perform other anti-abuse checks in the SMTP protocol. For example I use spamhaus.org ZEN DNSBL to block known spammers. But that gets them a rejection not firewall blocked.

But we live in a time of extraordinary abuse! It's an unprecedentedly high level. Which causes such severe problems that people get desperate trying to mitigate it. Desperate times call for desperate measure and admins to things that are not strictly good to do but must be done to keep sites online.

riad: You never got any other reply to your email other than the "mx66.freebsd.org[2610:1c1:1:606c::19:5]:25: Network is unreachable"?

Was a permanent error? What error code was it?

"traceroute -I mx1.freebsd.org" "traceroute -I mx66.freebsd.org" "mtr mx1.freebsd.org" "mtr mx66.freebsd.org" traceroute is in base but IPv4 only. mtr is a port/pkg. Should show where the route stops.

Hmm... I thought when I looked earlier that mx66 was IPv6 only, and said that at the time, but that is wrong. I must have squinted funny because both mail relays are both IPv4 and IPv6. That was a mistake on my part to say otherwise.

Yeah. I'm seeing no problems at all with the MX's mentioned.

So, I would assume if there was an actual delivery issue, riad would've received an error that explained what happened. It's very rare that FBSD's mail server just "blackhole" something (unless it's classified as blatant SPAM.)

ek: here is a paste from the entire email that i received

not much explanation besides network unreachable

and yeah that was the only reply which i received, funnily enough my first mail went through

and also never got anything like this before at all

im going offline, dont have a bouncer but you could send me an email, heh

riad has part'd the channel but that Delay DSN delivery status notification is not a bounce message but a notification that the message has not be transmitted in 4 hours. I always turn those off. Off is the default but many packagers enable it (delay_warning_time=4h) by default in the default template (not FreeBSD). The MTA will continue to retry to send the message.

Friend of mine burned a FreeBSD ISO to two different USBs and neither of them can boot. I'm of the opinion that both USBs are broken, given the error pattern; she disagrees, "because they normally work".

dd if=/some/iso of=/dev/whatever bs=1m should usually just work, if the method was different, that could be it.

Reinhilde: you need to use the memstick image and not the iso image

zi, (Reinhilde) I dd the iso images to a USB SD card and boot it no problem. It's a hybrid image.

Reinhilde, Did your friend "sync" after that dd finished to ensure that the data was flushed to the USB before removing it? If not then the tail end might not have gotten written.

I recommend using dd's bs=1M iflag=fullblock oflag=sync,direct flags which are portable across FreeBSD and GNU/Linux systems. Then when dd is done the data is sync'd already and the device can be detached/removed immediately.

Alternatively newer "pv" from ports/pkgs has a --direct-io option which now can do the same job, but it is a fairly new option feature and most GNU/Linux systems don't have --direct-io yet.

rwp, I'll ask her.

zi, ah.

ISO images do work on a USB stick. I always boot that way. Including for non-FreeBSD images too.

she says she used the memstick images

Reinhilde: has she verified that "any" USB os media will boot of any type? This may not be a FreeBSD specific issue as much as the machine itself

o0x1eef: same.. I use USB for booting almost everything to install with